>
>If the other drive was hanging the IDE bus then lilo would never have gotten
>far enough to give the "LI" part of the prompt. More likely the geometry of
>this new drive is causing lilo to have a heart attack. Therefore
>eliminating lilo should eliminate the problem. lilo absolutely does care
>about another drive being added to the system, and this is the part that
>happens right after the I is output to the console.
>
>Here is what the docs say:
> 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.
>
>Since the first stage boot loader ran, it is unlikely that the IDE bus is
>being frozen by the second drive, or else it would freeze it during the
>initial POSTing by the BIOS, not after lilo had already been read into
>memory from the drive.
>Warren Melnick
While I am in error regarding the IDE bus causing a problem, I am not in error
regarding LILO not caring about additional discs. You have to read
between the lines. The part you referenced refers to the geometry of the
BOOT disc, not any other disc. You'll notice that the lilo config file
has no informatiohn regarding the system configuration. It only points to
the boot drive of interest.
The disc that I added to my system was not liked by the BIOS, because it was
too large. So I just set it to be 512 MB in size. When Linux booted,
it queried the disc and got the REAL size of the disk and worked with it just
fine.
I am confused as to why this disk is causing trouble.
MB
--
e-mail: [EMAIL PROTECTED]
Bart: Hey, why is it destroying other toys? Lisa: They must have
programmed it to eliminate the competition. Bart: You mean like
Microsoft? Lisa: Exactly. [The Simpsons - 12/18/99]
Visit - URL:http://www.vidiot.com/ (Your link to Star Trek and UPN)
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
