Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
Okay, I have tried everything I can think of and looked everywhere on the net but can't find anything on this specific weirdness. I have successfully compiled kernels four or five times now and have not run into any problems just following standard the usual procedure: as root: download kernel into directory /usr/src/linux,
zcat /proc/config.gz > /usr/src/linux/.config
cp arch/i386/boot/bzImage /boot/vmlinuz-etc,,,
cp System.map /boot etc
I have not had any problems until kernels 3.7.1 and 3.7.2.
But this is not the REALLY strange thing. I also used Slackpkg to upgrade the kernels to 3.7.1 and, using Grub2, was able to load them all into the menu. If I go to boot, they ALL panic with some message like "VFS: cannot find filesystem for root. or Please set root= to proper parameters."
So, I then installed the 3.2.* kernels from Slackware CD. Updated grub2.cfg. No problems with any of these kernels.
I don't know what to make of it.
Last edited by Cyanobacteriophage; 01-13-2013 at 06:02 AM.
"VFS: cannot find filesystem for root. or Please set root= to proper parameters."
In that case (and I've had it with 3.7.1) the root filesystem isn't compiled into the kernel. You can get away with that if you have an initrd with all the required modules in it. Far better to compile in your chipset drivers, and the filesystems of / and /boot; Maybe usb stuff if you're using a usb boot. Everything else can be modules.
No, it wasn't the file system strangely. But it was apparently something that I did leave unchecked in the SATA and PATA support section to with my disk controller possibly (?). Thank you for the help anyway though.