The lilo.conf that you quote at the end of the message is your lilo.conf for
RH 5.2 . It isn't right for RH 6.1, which uses kernel version 2.2.12, I
think (certainly 2.2.something). If your RH 6.1 "install" does not include
rerunning LILO with a different lilo.conf file, that is almost surely the
source of your problem with 6.1.
If you are doing a LILO reinstall for 6.1, we need to see the lilo.conf
associated with it -- you already know that 5.2 works (or at least once
worked). And for the final 5.2 failure ... is this the lilo.conf associated
with it? If so, reboot with your recovery disk and see if
/boot/vmlinuz-2.0.36-0.7 is actually present on the hard drive.
As to your disk geometry ... what does the BIOS say about it? For purposes
of spotting 1024-cylinder problems, we don't case about fdisk's report on
the disk (which derives from the kernel's IDE support) but about what the
BIOS sees (which LILO uses, since LILO runs before the kernel is running).
The kernel may be remapping a geometry that presents problems at the BIOS
level. But even so, if both 5.2 and 6.1 are using the first partition (hda1)
as /boot, it is so small that it must be within the 1024-cylinder limit ...
so while a geoetry problem is possible, I'd say it is unlikely.
At 03:14 PM 11/23/99 -0600, Stephen Hargrove wrote [in part]:
>I /had/ RH5.2 running perfectly on my laptop (Gateway 2500, P266) and
>decided to upgrade to RH6.1. I'm installing LILO in the MBR, as Linux is
>the only OS on this machine. When the system is booting, instead of LILO:
>it gets to LI and sticks, forcing me to power cycle.
....
>FYI, here's my lilo.conf:
>
>boot=/dev/hda
>map=/boot/map
>install=/boot/boot.b
>prompt
>timeout=58
>image=/boot/vmlinuz-2.0.36-0.7
> label=linux
> root=/dev/hda1
> read-only
>
>Any ideas on where I should begin looking?
....
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
