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.
Hi guys. I've had this problem only using the 2.6.16 kernel and this doesn't seem to be the case with the 2.6.15. I've compiled the kernel source and set all appropriate options using make menuconfig. I've made the filesystems I use, ext2/ext3 built into the kernel and thus have no modules.
I receive a VFS kernel panic every single time I try to boot from this kernel. Somewhere I was advised that if I was using slackware I should have an initrd. From what I understand the entire point of the initrd is to load modules the kernel does NOT have built in functionality for before loading the root partition. This is contradictive seeing as how I have ext3 built IN and thus have NO MODULES. So I tried it anyway by rebuilding the kernel with ext3 set to module and created the ramdisk with:
Now, when I did this with 188.8.131.52 the kernel panic was replaced with some error about killing INIT. However my point is that at LEAST the ramdisk was LOADED as specified by my lilo.conf.
When I loaded the 2.6.16 kernel the ramdisk FAILS TO LOAD ENTIRELY and I get the usual VFS kernel panic trying to load root. I didn't expect it to work, however I at least hoped to see the initrd run to begin with. 2.6.15 at least loaded the ramdisk before failing, whereas 2.6.16 just refuses to load the ramdisk.
You are correct =] I've enabled whatever sata related items I saw in the make menuconfig. tbh I dont even know if it is truly SATA because when I installed XP on this system I didn't need the SATA raid driver disk. On every single desktop PC I've ever built in my existance, when I was installing to a SATA drive I needed that RAID disk during the xp installation procedure. I did not need that disk when installing xp on this laptop. The specs for the laptop however indicate that the drive is indeed SATA. I am more than a bit confused about this.
If it is SATA, how can I get the 2.6 kernel to recognize it? Will I need to find some type of Intel specific driver for it?