Giulio Orsero wrote: >On Sat, 09 Feb 2002 10:46:07 -0600, Steve Cohen <[EMAIL PROTECTED]> wrote: > >>So I want to make a correct boot.b. The only way I can think of to do >>that is to rebuild the kernel. Since the kernel itself is fine, I'd >> >boot.b is part of the lilo package, nothing to do with the kernel. >$ rpm -qf /boot/boot.b >lilo-21.4.4-13 >$ > >You can check it's ok by veryfing lilo rpm > >$ rpm -V lilo > >If you think it's corrupt, just reinstall the lilo package > >rpm -Uvh --force lilo......rpm > >========= > >Have you tried, once booted with floppy using HD as root fs, to execute ># /sbin/lilo >and then reboot from HD? > OK, thanks, you were right, the boot.b date was a false lead. I forced reinstallation as you suggest above and it worked but the file was had the same date and version number. The date was the date redhat created it, not the date I installed it.
So I took your advice and reinstalled LILO. It works, sort of. It just loads whichever OS has been marked as default. (This is a dual-boot system, Win98 and RedHat). However, the Keyboard doesn't work when LILO comes up, so I can't type in anything or pick an OS other than the default. When I look in the BIOS Event Log that I can view from the BIOS setup utility at boot time, I see the following: "Pre-Boot Error Keyboard Not Functional". Whatever the cause of this, it may also be the reason why Grub failed. It is amazing how many different areas of functionality I've explored looking for the culprit. Now it's the keyboard in pre-boot state. (The keyboard works fine once I've managed to boot). Has anyone got any ideas on this one??? _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
