Hey Jesse,
A while back I had similar problems. From command line I manually
re-installed lilo to the MBR and I also had to manually edit the
lilo.conf file to comment out errors (lilo.conf in /etc, and use
the example from man lilo.conf as a guideline). My guess is that there is
something in the lilo.conf that does not match a change you made to your
bios. Worth confirming all settings.
On the command line I used: #lilo -i -L -S
and -t (if you want to test)
-v (for verbose mode to debug what's actually going on)
Confirm that the boot-loader is not corrupted (use -i, default
boot-loader is /boot/boot.b or /boot/vmlinuz if memory serves)) and -b to
ensure that lilo is installing on the MBR on the correct hard drive
(default is /dev/hda). If corrupted, copy the vmlinuz from the boot CD to
/boot/)
Good luck Jesse and
Happy New Year everyone.
Peter
On Mon, 29 Dec 2003, Jesse Kline wrote:
>
> Happy holidays everyone,
>
> I seem to have managed to break my boot loader. It's a strange problem
> that I'm having troubles wrapping my head around, so I hope someone on
> the list can help me out. Hopefully I can explain it properly. It seems
> to have started the other night when I tried to use the redstorm
> overclocking feature in my bios. It didn't work out as I rendered my
> system un-bootable. After playing with the bios for awhile I was able to
> get the boot loader to load, but if I selected the linux-enterprise
> kernel (Mandrake 9.2) Lilo would give me the following error:
> Error 0x01
> 0 - keytable read/checksum error
> However it can load the "linux" kernel in runlevel 5 and failsafe mode,
> but when I boot into runlevel 5 with that kernel none of my settings in
> the XF86Config-4 file are loaded and my display is all screwed up. I
> tried re-installing lilo with no success, and if I install Grub, it will
> not load at all giving my a Read Error while loading stage 2 or stage
> 1.5.
> The strange thing is that if I power down the machine for awhile then
> lilo will load the linux-enterprise kernel no problem, saying Bios Data
> Check Successful, but once I reboot the computer I get the error message
> again.
> As you can see it doesn't make sense to me. I've tried googling for a
> solution, but I've found nothing concrete although some of what I have
> found points to the bios sending incorrect hard drive parameters to the
> boot loader, so once again I think that I broke it by messing around in
> the bios.
> I really hope someone has some idea as to what is going on here.
>
> Thanks,
>
> Jesse
> --
> Jesse Kline, RHCT
>
>
> _______________________________________________
> clug-talk mailing list
> [EMAIL PROTECTED]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>
_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
