Hello SuSE folks, Running 8.0 Just did an upgrade of my kernel to 2.4.19 Did my mk_initrd and then a LILO. The LILO message stated " added Linux* skipping /boot/vmlinuz.suse added /windows (dual boot) fatal open /boot/memtest.bin No such file or directory" When I rebooted it failed at LI. Had to reboot with a floppy and then edited lilo.conf by removing the memtest line. Then rebooted properly. But, without the two options of failsafe and memtest. Can anybody explain/help me fix what has caused this? Also there is no time delay to choose the OS. Boots almost immediately to Linux. Thanks, Bob S.
On Fri, 27 Dec 2002, Bob just had to get this off his chest:
Hello SuSE folks,
Running 8.0 Just did an upgrade of my kernel to 2.4.19 Did my mk_initrd and then a LILO. The LILO message stated " added Linux* skipping /boot/vmlinuz.suse added /windows (dual boot) fatal open /boot/memtest.bin No such file or directory"
When I rebooted it failed at LI. Had to reboot with a floppy
Why did you ignore this error? I'm sure it also said it didn't write lilo so that should've given you ample warning not to reboot just yet..
and then edited lilo.conf by removing the memtest line. Then rebooted properly. But, without the two options of failsafe and memtest.
Can anybody explain/help me fix what has caused this? Also there is no time delay to choose the OS. Boots almost immediately to Linux.
Did you use a SuSE kernel (rpm) for the upgrade or did you build one yourself? Boot delay in lilo.conf has nothing to do with the installation of another kernel, see if your $EDITOR saved a backup copy so you can see what changed. Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 27N , 4 29 45E. SuSE 8.0 x86 Kernel k_Athlon 2.4.19-4GB See headers for PGP/GPG info.
participants (2)
-
Bob S.
-
Theo v. Werkhoven