lilo error

Fabio Fracassi f.fracassi at gmx.net
Sat Nov 11 11:29:42 PST 2000


On Saturday 11 November 2000 18:21, you wrote:
> When I run lilo, I get the following:
>
> bash-2.04# /sbin/lilo
> Warning: device 0x0345 exceeds 1024 cylinder limit.
>    Use of the 'lba32' option may help on newer (EDD BIOS)
> systems.
> Fatal: geo_comp_addr: Cylinder number is too big (1262 >
> 1023)
>
> I'm not sure, but I'm afraid that this means that I won't be
> able to boot into LFS because the partition to too high on
> the drive. My partition table looks like this:
>
> Disk /dev/hdb: 255 heads, 63 sectors, 1868 cylinders
> Units = cylinders of 16065 * 512 bytes
>
>    Device Boot    Start       End    Blocks   Id  System
> /dev/hdb1             1        13    104391   83  Linux
> /dev/hdb2            14        30    136552+  82  Linux swap
> /dev/hdb3            31      1178   9221310   83  Linux
> /dev/hdb4          1179      1433   2048287+   5  Extended
> /dev/hdb5          1179      1433   2048256   83  Linux
>
>
> /dev/hdb1 is where the /boot directory for my Suse install
> lives. /dev/hdb5 is where my LFS install is. I'm thinking
> that I might be able to use /dev/hdb1 for the /boot
> partition for the LFS system, too, but there are some
> duplicate file names.
>
> bartleby:~ # ls /boot
> ..                  bg          chos.loader        lost+found
> ...                 boot.b      chos.loader-bsect  os2_d.b
> System.map-2.2.14  chain.b     chos.loader-linux  vmlinuz
> XF86Config         chos.bsect  commands.conf
> vmlinuz-2.0.34
>
> bartleby:~ # ls /mnt/lfs/boot
> ..   System.map   boot-text.b  chain.b    os2_d.b
> vmlinuz-2.0.34
> ...  boot-menu.b  boot.b       lfskernel  vmlinuz
>
>
> What's the best way to get out of this mess?
>

Try GRUB!  (ftp://alpha.gnu.org/pub/gnu/grub/grub-0.5.96.tar.gz)
I've written an Hint 
(http://archive.linuxfromscratch.org/lfs-hints/GRUB-Howto)

GRUB solved all similar problems for me :)

Hope that helps

Fabio






-- 
Unsubscribe: send email to lfs-apps-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message




More information about the blfs-support mailing list