LILO boot-time code does not care in the least about partition order.

As far as I can tell, the system where you are trying to use the drive does
not support LBA32 addressing, so it falls back to geometric (C:H:S)
addressing, and fails. The former system does support LBA32, hence, it is
able to boot.

The only solution on this older system is to create a boot partition below the
1023 cylinder limit. Then be sure that ALL boot files are down there:
kernels, initrds, & the LILO sector map file (map=). This last is critical.

Booting from DOS works, because DOS is located below the 1023 limit; hence,
you can address everything you need to boot.

--John


On Fri, 30 Sep 2005 00:45:25 +0200, "Peter T. Breuer" <ptb@oboe.it.uc3m.es>
wrote:

>harddrivecleaner@yahoo.com wrote:
>>>Make yourself a small /boot partition below cylinder 1024
>
>> I had tried that, but it didn't work until
>> just now, when I did a "fix partition order"
>> in the Linux fdisk's advanced menu.
>
>Nonsense. The order is unimportant. The placement is.
>
>> It was very odd. Partition 1 was the first
>> one on the disk, but somehow in the partition
>> table, not so.
>
>So? Who cares! Not your bios, not you. Your bios jumps to disk
>coordinates. It doesn't care or know in what partition they are.
>
>Peter