My Slackware Box was working perfectly with kernel 2.4

then I installed the kernel 2.6.7 from CD 2, following the instructions found on the web and on the Slackware docs too.

I have updated LILO, apparently without problems, adding a new entry for Linux with 2.6.7 kernel

after the reboot, I choosed Linux with kernel 2.6.7 and it worked good (I have some problems with the sound server but... i was only testing the 2.6.7 kernel, so i wasn't worried about it)

reboot again,

choose the usual Linux entry (with kernel 2.4)
(that wasn't modified at all)

ERROR: kernel panic, unable to mount Root FS

WHAT's happened???????????

I mean: if it was working before and I have not modified it, and i have followed all the instructions, why it's broken now?

thanks a lot!

given that 1) you did not recompile your 2.4 kernel, and 2) you did not change the filesystem, i would say you mucked up lilo.conf, let's see it in here--

thanks for your attention secesh

1) no changes and/or recompilations with kernel 2.4

2) no changes at all with filesystems.......

Installing the Kernel 2.6.7, of course, I have added a new entry in the LILO config file, but I have unchanged the other sections. I have only added a new entry... that's all

Maybe the kernel 2.6.7 install did change the vmlinuz symlink in /boot that points to the kernel,
ie :

before :
vmlinuz -> vmlinuz-2.4.26

After:
vmlinuz -> vmlinuz-2.6.7

If it is that, just change the 2.4.26 lilo entry so that boot with vmlinuz-2.4.26 instead of just
vmlinuz.

Thanks a lot Cedrik

You was right! (and your solution works ok)

thanks

the whole idea of having the symlink vmlinuz seems unneccessary to me, to be honest. isn't it clearer and simpler to just use the name of the kernel image you want to boot in lilo.conf? does anyone know the history behind this tradition? the only time i can see it coming in useful is to have only two entries in lilo.conf like this:

image = /boot/vmlinuz-2.4.26
label = stable
read only

image = /boot/vmlinuz
label = unstable
read only


and then have vmlinuz point to whichever unstable kernel you feel like testing that day. it could theoretically save you the trouble of changing the lilo.conf file, but instead you have the trouble of constantly changing the symlink. also, would that even work? i seem to remember not being able to boot a new kernel after trying something like that...but it was late at night after recompiling for like the third time, so i don't know if it was due to that or not.