LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Dual Boot, Lilo (https://www.linuxquestions.org/questions/linux-software-2/dual-boot-lilo-9276/)

Nikta 11-27-2001 12:24 PM
Dual Boot, Lilo
 
I am running Microshaft Me on my system currently and I really want to get a copy of redhat on here as well. I have to keep windows because this computer shares the internet on my network.

I partioned my drive using Fdisk and reserved 5 Gb for linux. I then created a linux native and a swap partion using the disk druid. Redhat copied the files and installed onto my system. Opon reboot the system just halts during post, with the a message "LI"

What the hell is that? I didn't see any opertunity to install a dual loader (if one exists). It might be good to know that I was attempting to intall a workstation, using the GUI gnome..

Anyone's know how would be super apperticated..
Thanks,
Nick

DMR 11-28-2001 08:08 PM
That is the bootloader, and it's choking at the second stage of the load.
Quote:
Taken from The LiLo's User Guide in /usr/share/doc/lilo-[...]/, p.44:
If the screen displays:

(nothing)
No part of LILO has been loaded. LILO either isn't installed or the partition on which its boot sector is located wasn't started. Use a boot floppy. Check '/etc/lilo.conf' and run /sbin/lilo again.

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. You will find a list of error codes on the same page of the User Guide. The 'geometry mismatch' error might occur, if you've moved the kernel to a different location or changed the partition setup and forgot to run lilo afterward.

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
Same as above. Running /sbin/lilo should help.

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

LIL?
Second stage boot loader has been loaded at an incorrect address. See LI.

LIL-
Corrupt descriptor file table. See LI.
What version of Redhat? If it's using an older version of lilo, the kernel will have to exist below the 1024 cylinder of the drive.


All times are GMT -5. The time now is 07:49 AM.