hello,

I've recently installed a Maxtor PCI EIDE ATA 133 for my Maxtor 160 GB hard drive (to brake away from the 137 GB limit. My system motherboard only has EIDE ATA 66) and I have trouble booting Lilo if I have my BIOS setup (Dell Dimension XPS B866r) configured a certain way. If I have my BIOS boot order configuration like this:

1st Boot Device [ Floppy ]
2nd Boot Device [ ATAPI CD ROM ]
3rd Boot Device [ ULTRA D0 ]

It's a dual boot system. /dev/hde is my Windows 2000 hard drive (160 GB hard drive/the one using the the Ultra ATA/133 PCI Adapter), /dev/hdb is my Linux HD (40 GB hard drive/ATA 66 motherboard socket. which is going to be /dev/hda soon). Anyhow, when I boot up Windows with this configuration, it boots up fine. However, when I attempt to boot from the Lilo diskette, I get the " L 99 99 99 99 99 99 99 .. " message. In order to boot up Linux from the Lilo diskette, I have to change my BIOS configuration by removing the 3rd Boot Device. Like this:

1st Boot Device [ Floppy ]
2nd Boot Device [ ATAPI CD ROM ]
3rd Boot Device [ disabled ]

Now, the Lilo menu shows up. If I choose Linux, it boots up fine. But choosing DOS/Windows is doesn't boot at all. I know (or I'm sure) it's not a kernel problem, since I can access/mount the Windows hard drive. But I can't get it to boot up with the first BIOS boot configuration to boot up Linux/Lilo. Please help my lame-o maroon butt out! My specs, cat /proc/pci, lilo.conf, lilo -v3, are listed below. Thanks!


System specs:
40 GB hard drive (/dev/hdb ; Slackware 9.1/Linux 2.4.22 ; using the ATA 66 socket from my motherboard)
Ultra ATA/133 PCI Adapter Card
160 GB (/dev/hde ; Windows 2000 ; using the Ultra ATA/133 PCI Adapter Card)
Lilo 22.5.7.2
Using liloconfig (Slackware)


cat /proc/pci:
Bus 2, device 12, function 0:
Unknown mass storage controller: Promise Technology, Inc. 20269 (rev 2).
IRQ 10.
Master Capable. Latency=64. Min Gnt=4.Max Lat=18.
I/O at 0xdfe0 [0xdfe7].
I/O at 0xdfac [0xdfaf].
I/O at 0xdfa0 [0xdfa7].
I/O at 0xdfa8 [0xdfab].
I/O at 0xdf90 [0xdf9f].
Non-prefetchable 32 bit memory at 0xfeafc000 [0xfeafffff].


lilo.conf:
# [snip the comments]
append="hdd=ide-scsi"
boot = /dev/fd0
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# [snip extra comments]
# DOS bootable partition config begins
other = /dev/hde1
label = DOS
table = /dev/hde
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /vmlinuz
root = /dev/hdb1
label = Linux
read-only


lilo -v3:
LILO version 22.5.7.2, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2003 John Coffman
Released 20-Aug-2003 and compiled at 19:15:26 on Aug 25 2003.

Warning: LBA32 addressing assumed
raid_setup returns offset = 00000000 ndisk = 0
BIOS VolumeID Device
Reading boot sector from /dev/fd0
Device 0x0200: BIOS drive 0x00, 2 heads, 80 cylinders,
18 sectors. Partition offset: 0 sectors.
pf_hard_disk_scan: ndevs=2
0340 EA1AA9C7 /dev/hdb
2100 0E56576C /dev/hde
Resolve invalid VolumeIDs
Resolve duplicate VolumeIDs
0340 EA1AA9C7 /dev/hdb
2100 0E56576C /dev/hde
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = 0
Filling in '/dev/hdb' = 0x80
Filling in '/dev/hde' = 0x81
device codes (canonical) = 3
Device 0x0341: BIOS drive 0x80, 255 heads, 4982 cylinders,
63 sectors. Partition offset: 63 sectors.
Using serial number EA1AA9C7 on bios 80
Warning: Unable to determine video adapter in use in the present system.
Using MENU secondary loader
Calling map_insert_data
Secondary loader: 17 sectors (0x3200 dataend).
Warning: The boot sector and map file are on different disks.
bios_boot = 0x00 bios_map = 0x80 map==boot = 0 map S/N: EA1AA9C7
Mapping message file /boot/boot_message.txt
Device 0x0341: BIOS drive 0x80, 255 heads, 4982 cylinders,
63 sectors. Partition offset: 63 sectors.
Using serial number EA1AA9C7 on bios 80
Calling map_insert_file
Message: 1 sector.
BIOS data check will include auto-suppress check

Boot other: /dev/hde1, on /dev/hde, loader CHAIN
Device 0x2101: BIOS drive 0x81, 255 heads, 19929 cylinders,
63 sectors. Partition offset: 63 sectors.
Using serial number 0E56576C on bios 81
Device 0x2100: BIOS drive 0x81, 255 heads, 19929 cylinders,
63 sectors. Partition offset: 0 sectors.
Using serial number 0E56576C on bios 81
Mapped 6 (4+1+1) sectors.
Added Windows *
<dev=0xe0,hd=220,cyl=132,sct=221>

Boot image: /vmlinuz
Device 0x0341: BIOS drive 0x80, 255 heads, 4982 cylinders,
63 sectors. Partition offset: 63 sectors.
Using serial number EA1AA9C7 on bios 80
Setup length is 10 sectors.
Mapped 2338 sectors.
Added Linux
<dev=0xe0,hd=220,cyl=132,sct=224>
"ro root=341 hdd=ide-scsi"

BIOS VolumeID Device
80 EA1AA9C7 0340
81 0E56576C 2100
Writing boot sector.
/boot/boot.0200 exists - no boot sector backup copy made.
Map file size: 29184 bytes.
RAID device mask 0x0000
Failsafe check: boot_dev_nr = 0x0200 0x0000

I suspect that when you tell the BIOS to boot "3rd Boot Device [ ULTRA D0 ]" that the BIOS is reordering the drive addresses. The BIOS may make the Maxtor IDE ports IDE 0 and IDE 1 and set the motherboard ports to IDE 2 and IDE 3. Thus the boot floppy lilo is looking for everything on the wrong addresses. Try configuring a boot floppy lilo with DOS on /dev/hda and Slackware on /dev/hdf.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Configuring DOS to /dev/hda and Slackware to /dev/hdf didn't work . They're not connected. Or am I doing something wrong?

Can you provide a sample configuration?

"Configuring DOS to /dev/hda and Slackware to /dev/hdf didn't work"

Some BIOS have the ability to reverse the order of the controllers, some do not. If it does reverse the order of the controllers then this would be your lilo.conf:


lilo.conf:
# [snip the comments]
append="hdh=ide-scsi"
boot = /dev/fd0
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# [snip extra comments]
# DOS bootable partition config begins
other = /dev/hda1
label = DOS
table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /vmlinuz
root = /dev/hdf1
label = Linux
read-only

Another way you could test this idea is to set the BIOS to:
1st Boot Device [ Floppy ]
2nd Boot Device [ ATAPI CD ROM ]
3rd Boot Device [ ULTRA D0 ]
and then try to boot a rescue CD. If the CD-ROM is on /dev/hdh then the BIOS probably will not boot it. If the BIOS does boot the rescue CD then you could try mounting each of your partitions and see which /dev/hdx addresses actually exist.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites