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.
I installed Slackware 11. Upon downloading the latest stable kernel (2.6.18), I configured it to add ReiserFS into the kernel (not as a module). All other options are rather conservative to try and ensure a boot.
I did the standard "make; make modules_install; make install".
Rebooting, I get
VFS: Cannot open root device "303" or unknown-block (3,3)
Please append correct "root=" boot option
Kernel panic - not sycing: VFS: Cannot open root device "303" or unknown-block (3,3)
"root=/dev/hda3" , the partition where the system resides.
Now I'm not sure what to do here. I've built 2.6 kernels before for slackware 10.2, and have not had a problem. I have also added support for ext2 and ext3, just to shotgun debug. Most other options are the default, except I added smp support for 2 processors, set the processor type to P4, and added the hyperthreading module. This matches my processor.
So I would like to track down this problem, but I need to know where to start looking. There has to be a better way than to build kernels at random until something hopefully boots. So any assistance is much appreciated.
I had the same problem. I had failed to check that I was compiling support for my IDE chipset into the kernel. I had just got complacent I guess. Without the IDE support the kernel could not work the hard disk.
During Make Menuconfig check under ATA/ATAPI?MFM/RLL support
Make sure you have selected support for your particular chipset.
I havn't checked out that link of yours yet, but yeah, I reconfigured my kernel and lilo (an error on my part invalidated my slack_old option so they pointed to the same thing), and rebooted for the heck of it. I expected it to fail, but it booted! I credit shotgun debugging. I selected a few generic IDE modules this time around, and something along those lines must have done it.
I still have a few errors that show up while booting, and they scroll by too damn fast to read, and they don't show up in the boot log. I'm working on that though.