Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to upgrade my 2.6.19.1 Kernel to 2.6.20-rc3, but I can't boot with the new kernel. The message
Code:
waiting for root filesystem
stay forever...
So my question, what could have change between 2.6.19 and 2.6.20 regarding filesystems ? I took the same config file as the one I was using for compiling the 2.6.19 version.
My system :
Laptop Core 2 Duo
100 Go SATA, with ext3
Debian SID
Using old .config file won't work. One should do at least make oldconfig. It still may not work, make oldconfig is known to choke when parts of config tree are moved. The only clean solution is to build it from scratch.
Could this be an initramfs issue? i.e. kernel is compiled requiring initramfs but there's no initramfs image? Debian's dpkg takes care of this for me, so I can't tell you how to get around it. I believe it's under Device Drivers -> Initial RAM Filesystems... You may also need RAM disk support.
Come to think of it, check your configuration for the SATA drivers section. They're making a lot of changes to libata and you may have run across a situation where your boot drive has changed from /dev/hd* to /dev/sd* under the new kernel, but grub/lilo is still pointing to /dev/hd*. If that's the case, you need to turn off whatever is running your pata device as a sata device. You could maybe change grub/lilo, but that would make booting from your fallback kernel difficult.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.