lba32 and geo_comp_addr

[soleblazer]

Hi all.

Got Win2k and a seperate RH NIX partition (hda4). I have LBA enabled in my bios. I wanted to get Win2k's boot loader to boot Linux, so I used my floppy to boot nix, did a dd bs 512 blah blah and plucked that bad boy down on c:. I edited my boot.ini correctly. I still get the "LI" characters coming up and thats it. Win2k is cool.

I did this:

Took out linear and replaced it with lba32 in the lilo.conf file, redid the dd.

After i edti the file to put lba32 in, I get a geo_comp_addr error that says I am above 1023. Shouldn't I be cool bc of lba32? I am using lilo 21, so do I need a new lilo?

From what I read what I want to do should work ok.

Thanks!

[bdg1983]

You may want to check to see if Lilo 21 supports booting past the 1024 cylinder limit.

Here's the Lilo Error Codes just in case.

LILO start messages

When LILO loads itself, it displays the word LILO. Each letter is printed before or after performing some specific action. If LILO fails at some point, the letters printed so far can be used to identify the problem. This is described in more detail in the technical overview.

Note that some hex digits may be inserted after the first "L" if a transient disk problem occurs. Unless LILO stops at that point, generating an endless stream of error codes, such hex digits do not indicate a severe problem.

[nothing]
- No part of LILO has been loaded. LILO either isn't installed or the partition on which its boot sector is located isn't active.

L [error] ...
- The first stage boot loader has been loaded and started, but it can't load the second stage boot loader. The two-digit error codes indicate the type of problem. This condition usually indicates a media failure or a geometry mismatch (e.g. bad disk parameters).

LI
- The first stage boot loader was able to load the second stage boot loader, but has failed to execute it. This can either be caused by a geometry mismatch or by moving /boot/boot.b without running the map installer.

LIL
- The second stage boot loader has been started, but it can't load the descriptor table from the map file. This is typically caused by a media failure or by a geometry mismatch.

LIL?
- The second stage boot loader has been loaded at an incorrect address. This is typically caused by a subtle geometry mismatch or by moving /boot/boot.b without running the map installer.

LIL-
- The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer. LILO All parts of LILO have been successfully loaded.


Disk error codes

If the BIOS signals an error when LILO is trying to load a boot image, the respective error code is displayed. The following BIOS error codes are known:

0x00 Internal error. This code is generated by the sector read routine of the LILO boot loader whenever an internal inconsistency is detected. This might be caused by corrupt files. Try re-building the map file. Another possible cause for this error are attempts to access cylinders beyond 1024 while using the LINEAR option.

0x01 Illegal command. This shouldn't happen, but if it does, it may indicate an attempt to access a disk which is not supported by the BIOS.

0x02 Address mark not found. This usually indicates a media problem. Try again several times.

0x03 Write-protected disk. This should only occur on write operations.

0x04 Sector not found. This typically indicates a geometry mismatch. If you're booting a raw-written disk image, verify whether it was created for disks with the same geometry as the one you're using. If you're booting from a SCSI disk or a large IDE disk, you should check, whether LILO has obtained correct geometry data from the kernel or whether the geometry definition corresponds to the real disk geometry. Removing COMPACT may help too. So may adding LINEAR.

0x06 Change line active. This should be a transient error. Try booting a second time.

0x07 Invalid initialization. The BIOS failed to properly initialize the disk controller. You should control the BIOS setup parameters. A warm boot might help too.

0x08 DMA overrun. This shouldn't happen. Try booting again.

0x09 DMA attempt across 64k boundary. This shouldn't happen. Try omitting the COMPACT option.

0x0C Invalid media. This shouldn't happen and might be caused by a media error. Try booting again.

0x10 CRC error. A media error has been detected. Try booting several times, running the map installer a second time (to put the map file at some other physical location or to write good data over the bad spot), mapping out the bad sectors/tracks and, if all else fails, replacing the media.

0x11 ECC correction successful. A read error occurred, but was corrected. LILO does not recognize this condition and aborts the load process anyway. A second load attempt should succeed.

0x20 Controller error. This shouldn't happen.

0x40 Seek failure. This might be a media problem. Try booting again.

0x80 Disk timeout. The disk or the drive isn't ready. Either the media is bad or the disk isn't spinning. If you're booting from a floppy, you might not have closed the drive door. Otherwise, trying to boot again might help.

0xBB BIOS error. This shouldn't happen. Try booting again. If the problem persists, removing the COMPACT option or adding/removing LINEAR might help.