LinuxQuestions.org - Lilo with Ubuntu, dual boot with Mandrake

First, I apologize for a lilo question. I'm not finding answers in the other threads I've searched which makes me wonder if it's an Ubuntu issue. Perhaps you can help.

I just installed Ubuntu (Hoary install) on an existing dual-boot system. I installed it over the previous WinXP partition. Ubuntu wanted to use Grub as the bootloader, but it failed on the install. It did however present me with Lilo which was already listed because I had been dual-booting with WinXP/Mandrake.

Now the newb problem.
Ubuntu loads fine (love it), but I'm not presented with a menu to choose to boot into Mandrake, which I had hoped for. I checked the partitions to see how things were listed and it looks like:

Code:

Disk label type: msdos

Minor    Start      End    Type      Filesystem  Flags

1          0.031  27862.734  primary  ext3        boot

2      27862.734  38154.375  extended              lba

5      27862.765  37636.655  logical  ext3

6      37636.686  38154.375  logical

I then brought up the lilo.conf file and edited it to be (not listing the comments):

Code:

boot=/dev/hda

root=/dev/hda1

install=menu

map=/boot/map

delay=40

vga=normal

default=Linux

image=/vmlinuz

        label=Linux

        read-only

        initrd=/initrd.img

image=/vmlinuz.old

        label=LinuxOLD

        read-only

        optional

        initrd=/initrd.img.old

other=/dev/hda5

        label="Mandrake 10.1"

When I then /sbin/lilo I receive a message:

Code:

Warning: LBA32 addressing assumed

Reading boot sector from /dev/hda

Warning: Kernel & BIOS return differing head/sector geometries for device 0x80

    Kernel: 65535 cylinders, 16 heads, 63 sectors

      BIOS: 1024 cylinders, 255 heads, 63 sectors

Warning: '/proc/partitions' does not match '/dev' directory structure.

    Name change: '/dev/dm-0' -> '/dev/evms/hda1'

    Name change: '/dev/dm-1' -> '/dev/evms/hda5'

    Name change: '/dev/dm-2' -> '/dev/evms/hda6'

Using MENU secondary loader

Calling map_insert_data



Boot image: /vmlinuz -> boot/vmlinuz-2.6.10-4-386

Mapping RAM disk /initrd.img -> boot/initrd.img-2.6.10-4-386

Added Linux *



Skipping /vmlinuz.old

Boot other: /dev/hda5, loader CHAIN

Fatal: First sector of /dev/hda5 doesn't have a valid boot signature

Now there are a bunch of useful Ubuntu comments in the lilo.conf file, but I don't think they'd be causing a problem (although I haven't tested that yet). Any idea of what I am missing or doing incorrectly?