Re: Weird lilo problem
Wienand Ian wrote
Run /sbin/lilo -v -l to try linear mode, if you get an error like
Warning : linear may generate cylinder # above 1023 at boot
Fatal : sector address 40122944 to large for linear ( try LBA 32 instead )
you'll know you've got problems.
I tried the command and that was exactly what happened. I checked my
partition table and here's what i got
# fdisk -l /dev/hda
Disk /dev/hda: 255 heads, 63 sectors, 2434 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 1217 9775521 c Win95 FAT32 (LBA)
/dev/hda2 1218 2434 9775552+ 5 Extended
/dev/hda5 1218 2346 9068661 83 Linux
/dev/hda6 2347 2387 329301 82 Linux swap
/dev/hda7 2388 2434 377464+ 82 Linux swap
Obviously you were right, my root partition (/dev/hda5) is above the
1023th cylinder. What bothers me is how come it works with the bf24
kernel... there are no special boot parameters, it's just a different
kernel. As far as i know, lilo should have done the same thing running
on whatever kernel, but it doesn't.
The easyest solution would be to move my root partition to the front of
the disk, that won't be a problem, for it is nothing more then a storage
space. But i would still like to get to the bottom of this, how come it
works when i run lilo on the bf24 kernel and not on others.
I wonder if it would work with this workaround: First i would change my
lilo conf settings to something like this
#to install to mbr of the drive
boot=/dev/hda
Default=Linux
#zero timeout so this stage doesn't wait
timeout=0
#and have it point my root partition
other=/dev/hda5
table=/dev/hda
label="Linux"
That would install lilo in the mbr of /dev/hda pointing pointing lilo to
boot from the mbr of /dev/hda5, which is my root partition. Then i would
run lilo again with my old lilo.conf, only change the boot device
boot=/dev/hda5
to make lilo install it's boot menu in the mbr of the root partition, so
lilo in mbr of the drive would point to mbr of the partition and i would
get the boot menu from mbr of the partition.
I will try that now and report the outcome here. If anyone gets an idea
why it works with the bf24 kernel and not with others, i would be most
happy to find out.;)
Reply to: