SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Some reason I'm having one hell of a time to get it installed.
When I do the default install, somehow my network is not getting picked up, so I attempt to recompile the kernel. I'm using the huge26 kernel, I've also attempted to use the kernel 2.4 but I also have issues with that kernel recompiling as well for some reason. Seems to only happen on this system because I've done installs of slackware on many other types of computers, this is the only one I'm having the issue with it.
I recompile the kernel I get VFS: Cannot open root device 802 or unknown-block 8,2
Please append a correct root= boot option
Kernel Panic no syncing VFS unable to mount root fs on unknown block 8,2
System is a 3500+ AMD
Asus Alife A8N21-SLI Deluxe
Seagate sata 300gb harddrive.
So somehow a module is not getting installed even though I thought I've loaded the correct models for this motherboard.
you should not have to cook your own kernel to get your pc to work.
from what I gather, that nic should work w/the huge26 kernel.
basically what i did to get huge 26 in was to:
use the sata kernel to install, the default one whih is what u want as u have an sata board,
i did a full install,
then after all the software is intalled, and the installer prompts for the kernel, i chose the huge26.
now when u reboot, you will get errors of missing modules, that's becuase u installed 2.4sata modules, headers, and includes, and just the kernel only for huge26 but nothing else.
now you'll put in your cd again, log in a root, mount your cdrom, install the huge26 stuff except headers from extra cd (as I doubt you'll need them). reboot.
now once you get back to linux, you probably should run 'netconfig' which is part of pkgtool again. you see udev now saw modules for your 26 kernel, and also's develops the udev rule for you for your nic.
after netconfig reboot...we do this since we use udev now..ugh rebooting linux for networking I know...then you should be fine.
Pat v. gives a good explanation of this too in the cd1 text files and also in the extra cd. Obviously Pat's word is better than mine, but that is a summary of what I did to get huge26 right off the bat.
I have had a similar problem and am unable to solve it. I'm running an Acer TravelMate 2420 laptop with Slackware 11, and I need to get the onboard Intel PRO/Wireless 2200BG working. There is, luckily, a driver for it, but it requires a 2.6 kernel. So I have compiled and installed the kernel - several times - and it panics on this message.
VFS: Cannot open root device "303" or unknown-block(3,3)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bloc(3,3)
What's interesting is that my other kernel (the basic sata.i bzImage that comes on the DVD) boots fine with the exact same lilo.conf settings.
The 18.104.22.168 kernel boots excellently. The 2.6.18 kernel does not. Any help for the wireless needy?
I should add that the partition in question uses reiserfs, and that I'm 99% sure I've installed the right kernel drivers for the job. "Reiserfs support" and all its subsets save debug mode ave been enabled (I've tried it without the subsets too). My IDE controller is an Intel 82801FB, which is supposed to work with the Intel PIIXn chipsets driver, also set to be installed.
That error you get is most likely because you didn't build in reiser as "yes" under file systems.
Reiser is set to yes, and this page seems to have nothing relevant I don't already do (I didn't have it set to low-latency, high memory, hyperthreading, or multiple processors, but I don't have that much memory, only one processor, and I don't see how the latency setting would have an effect although I'll try it). Thank you anyway, though.
The fact that your kernel doesn't see the root file system is a common error of let's say reiser not being built in. Maybe you need to modprobe your IDE ports? or did you check out the blacklisted modules?
When I built mine, I basically took Mr. Pat V's 2.6.18 testing kernel package that he included in /extra and tweaked it a little is all. Then created my new rc.modules-2.6.18 and alls' well. Maybe you didnt make that file, it's needed by /etc/rc.S ?
Reiser and my IDE controller are built-in, so if I need an initrd I can't imagine what for.
That said, it slipped my mind to write a new rc.modules because I... er, didn't know... to do it (I try to fake not being a n00b, but it slips through sometimes). So I'll give that a try and get back with the results.
Okay. I tried to write the modules.rc, activating everything that vaguely looked like it would be useful to booting up for me. Still the same error message. I've tried it with pretty close to the stock setup in /testing, and I've tried it with a custom kernel, and I get the same problem. This is, honestly, bewildering the bejeezus out of me. My file system is built in. My IDE controller is built in. My lilo.conf is set up correctly. I'm getting very, very confused.
it might be that the new kernel sees your old hda1 as sda1. Try to reboot from install cd with huge26.s kernel, run lilo -r to reinstall lilo with sda in mind and edit fstab and change here hda to sda as well. That is what I did when upgrading from 2.4 to 2.6.
After a couple of days illness, I'm back trying to smash bricks together on this thing.
I've definately compiled the IDE drivers (I forgot to at first before I posted here, then I thought about it, put them in, and it didn't help). I better be compiling the right ones, as I hit 'y' on all of them after a couple trials just to be sure.
Alien Bob's wiki is down right now but I'll pore over it letter by letter when it comes back.
Copying the bzImage to a vmlinuz and putting it in lilo did nothing.
Switching the hdas to sdas also did nothing. lilo -r told me that /dev/sda3 was not a directory so I did it manually, but at the very least I did enough to stop the 2.4 kernel from booting until I went in and fixed it.
Interestingly, the Knoppix 5.0.1 live-DVD boots perfectly on kernel 2.6.17 off the DVD. But copying the kernel and its bit of lilo.conf onto my hard disk and booting it, I get the same message. So that's interesting (and tells me it's probably not my kernal configuration that's to blame).
Just FYI, I now have 22.214.171.124 working. What did I do? I completely re-installed Slackware with the 26huge.s kernel, then compiled my own the way I liked it. Everything worked like a charm. So, while that was odd, I am happy now.