Re: Weird lilo problem
Another thing i noticed... i have an lba32 line in my lilo conf,
obviously instructing lilo to use the lba32 mode for large disks. Now
when i run lilo -v in the bf24 kernel, where it works, it simply tells
about the images it has written, but when i run it on other kernels it
says "Ignoring entry 'lba32'" before it saying what it has added. Here's
the output:
# lilo -v
LILO version 22.2, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2001 John Coffman
Released 05-Feb-2002 and compiled at 10:23:47 on Jun 26 2002.
MAX_IMAGES = 27
Ignoring entry 'lba32' //note this line!!
Reading boot sector from /dev/hda
Merging with /boot/boot-menu.b
Boot image: /vmlinuz -> /boot/vmlinuz-2.4.19
Mapping RAM disk /initrd.img -> /boot/initrd.img-2.4.18-686
Added Linux *
Boot image: /vmlinuz-i686.old -> boot/vmlinuz-2.4.18-686
Mapping RAM disk /initrd.img -> /boot/initrd.img-2.4.18-686
Added Linux-686.OLD
Boot image: /vmlinuz.old -> boot/vmlinuz-2.4.18-bf2.4
Mapping RAM disk /initrd.img -> /boot/initrd.img-2.4.18-686
Added LinuxOLD
/boot/boot.0300 exists - no backup copy made.
Writing boot sector.
When run on the bf24 kernel the output is exactly the same, only without
the "Ignoring entry 'lba32'" line. I think that something in the kernel
is preventing lilo from using the lba32 mode. I went through the kernel
"make menuconfig" again, trying to find some reference to lba32, but i
couldn't find anything. Right now i'm pretty shure it's a kernel
configuration problem. Any more ideas?
Reply to: