SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Are you using reiserfs? Probably you didn't make the initrd image properly or you didn't add it to lilo.conf. If you did the latest, did you run lilo to update the boot loader?
Edit: It would help to know if that doesn't work, if you're using a SATA drive. 2.6 kernels detects the drives as sdXX instead of hdXX.
I just solved this myself a few days ago. When I configured my new kernel I left out support for DOS partitions in the Advanced Partitions section. When I added it back in everything was fine.
If you're upgrading to a 2.6 kernel your kernel may be loading one of the new libata SATA modules. If so your drives will be recognized as SCSI devices, e.g. /dev/sda rather than /dev/hde or whatever. Of course LILO and /etc/fstab are still looking for the old root partition name ergo the kernel panic.
This is a major PITA ... If you're not sure please post /etc/fstab, /etc/lilo.conf and the output of /sbin/lspci ... I eventually figured out a solution that involved booting into rescue mode but I'm sure I found the hardest possible way to do it. Anyone find a simple solution?
That's what I thought because I completely replaced Windows. Turns out that since the disk was originally formatted by Windows (way back then) I stll need the kernel to read DOS-based partitions. It worked for me. It might be worth a try.
so do I ...... I kernel panic about vfs too.....same error messages.....
but maybe this is could be my fault....when I configure kernel 2.6.14.3 with xconfig I load "config-2.6.13" can be this the problem?
can anyone help me please......
I have 4 times try to compile kernel and it always got kernel panic....
I use reiserfs too and I have run "lilo"......
so any idea and suggestion would be gratefull.....
thanx in advance ...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.