I notice that as part of this upgrade, you changed motherboards but kept
your old hard disk. This means that you changed BIOSes, and you are using a
hard disk that Linux fdisk'd under one BIOS with a new, different BIOS. This
may be a small problem or a big one, depending on whether the new BIOS is
weird (only a few are, but they do exist).
As Richard said, the LI piece of your problem is almost surely a geometry
mismatch -- the new motherboard's BIOS identifies the boot partition as
lying outside the 1024-cylinder boundary. The other problem
("LILO..........................") may be the same thing -- I'm not adept at
telling from the number of dots just where the process hangs, though I
imagine it is possible to do so.
Anyway ... take a look at how the new BIOS identifies your hard disk and see
if there are alternate settings that will put the boot partition (whatever
it is) in the first 1024 cyliners as seen by the BIOS (LBA remapping fakes
this position in a way that the BIOS can use).
At 04:04 PM 1/19/00 +0000, Richard Adams wrote:
>On Wed, 19 Jan 2000, Jeroen Van de Voorde wrote about, Upgrade hardware /
LILO-SW7.0 Bug?:
>> finaly got all the pieces to upgrade the hardware:
>> From: AT case, K6-2 233 + motherboard
>> To: ATX case, PII 300 + motherboard
>> All the other stuff is still the same.
...
>> the
>> original kernel booted the new hardware perfectly, except for the loader
>> (LILO) it got stuck at:
>> LILO..........................
>> and it did that over and over again.
...
>> What I've noticed is that when running the setup, and installing a new
>> LILO from scratch I got just LI when booting, no mather installing in
>> expert nor automaticly.
>
>That sounds like a geometry problem the disk cyls is quite possable set to
>more than 1024 which would irritate lilo.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
