On Saturday 28 December 2002 08:35, Theo v. Werkhoven wrote:
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..
Hi, Thanks for answering......Why ignore it?, Welllll...because I didn't know what to do about it at that point and still don't, ie: the purpose of this message. Can't tell you why, but I thought it did write it and it would boot OK at the time and then fix it afterwards. Guess I was wrong about that. Live & learn.
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?
It is a SuSE rpm downloaded from their 8.1 repository. (k 5deflt_2.4.19-110_i586.rpm)
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.
Fixed that already. Soooo......Can anybody explain why, or help me get back those two options in the Lilo menu? lilo.conf still shows the failsafe label, but does not show it in the menu, and of course the memtest86 label is gone because I removed it to make it boot. (see above original post) TIA, Bob.S