https://bugzilla.novell.com/show_bug.cgi?id=408724
User suse-beta@cboltz.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408724#c16
Christian Boltz
Yeah, the problem here is definitely that the old kernel is still being booted. The file is deleted, but it's still accessible. Or, well, it will be until the file system sees more activity. .. Running lilo again is really the best option here.
Seems your guess was right. # lilo Added LinuxV2 * Added FailsafeV1 Fatal: open /boot/initrd-2.6.18.8-0.7-default: No such file or directory (lilo.conf is attached to this bugreport already) After updating the version to ...0.10-default lilo could be installed successfully. And after a reboot uname -a even reports the correct kernel version :-) This means the kernel itself is OK and this bug is a candidate for the "most weird problem of the year" award ;-) The only remaining question is: Why was the version number not updated in all lilo.conf sections? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.