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 had the same problem, never did fix it. I think there was a post about changing all the drives to sdx from hdx in /etc/fstab? to get them mounted? Libata switchover? In the end I just used alien BOBS other script to create a current boot cd set to get started. I think the huge-smp kernel would work if I had set the frame buffer to default on boot, that was my other problem, the screen would go blank when it did get the drive mounted.
Using Generic 2.6.33-4-smp, I had to add modules for ext4, jdb2 and mbcache to the initrd. I think the problem is that if you're running with a kernel that has ext4 built in, the -m ext4 flag on mkinitrd doesn't actually load the module. I had to copy the ext4.ko over to the right location in the initrd-tree/lib/modules folder and add an insmod line to the load_kernel_modules file. Once ext4 _and it's dependencies_ were there, my system booted just fine. Btw, I had to go to a initrd boot because of my SATA RAID card that wasn't supported in the kernel. (Rocket Raid 2600x4).