On Sun, 29 Dec 2002, Bob just had to get this off his chest:
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.
Linux and Unix in general do not give messages just for the heck of it. When al goes ok it's silent, anything else should be regarded as important.
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)
Could you post a listing of /boot, the contents of lilo.conf and the output of 'rpm -qpl k_deflt_2.4.19-110_i586.rpm |grep boot' ? If it is an official SuSE kernel then it should have the vmlinuz.suse file, otherwise (like the Mantel kernels) probably not. The rpm shouldn't delete memtest though, it's hard to believe it did. 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.