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
" 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.. Does the memtest.bin file actually exist in the /boot directory on your machine?
and then edited lilo.conf by removing the memtest line. Then rebooted properly. But, without the two options of failsafe and memtest. Again does the file (kernel) vmlinuz.suse exist in the /boot dir?
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)
Hmmmm if the files are there, then I am not sure. If they are not there, you need to put the files there, edit the lilo.conf file and run lilo. It seems like the bootloader cannot find the above files. This is a guess on my part. I'm sure others with more experience with Suse (Linux in general) can help. -- Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
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.
Theo v. Werkhoven wrote:
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
...............<snip a lot of previous stuff>.........
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' ?
OK Theo, this is what I have. -------------------------------------------------------------- /boot: System.Map-2.4.19-4GB boot.0300 boot.0341 initrd initrd.shipped lilo.log map map2 message *vmlinuz.gz vmlinuz vmlinuz.autoconf.h vmlinuz.config vmlinuz.shipped vmlinuz.version.h ------------------------------------------ lilo.config: boot = /dev/hda change-rules reset read-only menu-scheme = Wg:kw:Wg:Wg lba32 prompt timout = 80 message = /boot/message image = /boot/vmlinuz label = linux root = /dev/hdb1 vga = 781 initrd = /boot/initrd append = "hdc=ide-scsi" image = /boot/vmlinuz.suse label = failsafe root = /dev/hdb1 vga = 791 initrd = /boot/initrd.suse append = "ide=nodma apm=off acpi=off hdc=ide-scsi" optional other = /dev/hda1 label = windows (and, of course, I deleted the memtest lines to make it boot) ------------------------------------------------------ The result of the "rpm -qpl k%5deflt_2.4.19-110_i586.rpm | grep boot" produced a "no such directory or file". (Tried many times in different variations) FYI the kernel was installed using "apt-get install k_deflt" which it obtains from the official SuSE gwdg.de repository.
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.
Hope this can help a little bit. Don't know why I can't grep that rpm. Bob S.
participants (4)
-
Bob S. -
Marshall Heartley -
R. Stia
-
Theo v. Werkhoven