Lilo lock

[HedCheez]

I just installed RH 7.1 (please dont flood me with anti RH 7.1 posts) on an older 166. When I boot the system the "L" in Lilo displays and then the system locks. I have tried the linear option in /etc/lilo.conf to no avail. Any help would be appreciated.

[Gnu/Vince]

On the 8th day, God said: "Don't cross the 1024th cylinder"

[Neurotica]

RH 7.1 doesnt setup lba32? Thats odd... Lilo has had support to boot past the 1024 cyl for some time now.

HedCheez:

If you made a boot disk, boot off of it, then edit /etc/lilo.conf and put in the option "lba32", and type lilo.

If that doesnt work, download the newest LILO from freshmeat (www.freshmeat.net) and install that instead...Keeping in mind to use the option lba32. If that STILL fails, view the readme files with lilo, and there were some suggestions if you are having problems.

Im guessing lilo just wasnt setup correctly on your machine though. Best to recongiure it manually.

You may also try installing lilo to the MBR instead of the linux partition. Normally I dont like to do this, but one some weird machines its the only way that works correctly. Here is my lilo conf, I will explain each line to help you configure.
do not include my comments
---------------------------
boot = /dev/hda2

#This is where you want lilo installed
#/dev/hda is the harddrive "2" is the
#partition. If you want it installed to the
#MBR just put /dev/hda (hda is the first hard
#drive, hdb is the slave, hdc is the
#secondary master, hdd is the secondary slave

prompt
vga = normal

#Ignore the above, leave em if you got em

lba32

#Make sure you have lba32!


image = /boot/vmlinuz
root = /dev/hda2
label = linux
read-only

# Yours should look similar above, this is
#the linux boot, change "root" to what your
#linux partition is


other = /dev/hda1
label = nt
table = /dev/hda
# These are you other operating systems if
#you have one.. if you dont, dont include
#this

[Convert]

If LILO fails when printing out "LILO", it means the following:
LI: Geometry mismatch or /etc/lilo/boot.b was moved without running the map installer

LIL: Geometry mismatch or media (disk) failure

Don't know about just 'L' though, probably a geomotry mismatch also. If you have access to dos or windows (like with a foppy disk), run fdisk /mbr, then try to reinstall LILO. Make sure you have a boot disk that works before killing the MBR.

[Ami Hughes]

While I would have liked to remove my profile and personal information from LinuxNewbie.org, I am not permitted to do so. While I have contacted internet.com for the abuse from the administration at linuxnewbie.org I have to wait for any further action. I used to do the popular posts for Pretty Fonts in Netscapes which was closed to because of Derek who goes under the username "Neurotica". They also have a habit of sabotaging your member ratings so becareful of that. You can learn more about that by visiting my web site or calling me at home. That information is in my signature.

[DMR]

While I would have liked to remove my profile and personal information from LinuxNewbie.org, I am not permitted to do so. While I have contacted internet.com for the abuse from the administration at linuxnewbie.org I have to wait for any further action. I used to do the popular posts for Pretty Fonts in Netscapes which was closed to because of Derek who goes under the username "Neurotica". They also have a habit of sabotaging your member ratings so be careful of that. You can learn more about that by visiting my web site or calling me at home. That information is in my signature.


Whining is off-topic for this forum. We have a place for rants, and this isn't it.

Have a nice day :)

[bdg1983]

abuse from the administration at linuxnewbie.org I have to wait for any further action

What the hell are you talking about? I've been around awhile here and have certainly never been abused.

And why are you hijacking so many threads to post that?

Ever thought of requesting to have your profile removed? I wouldn't mind.

Sorry, I guess I should contribute something to the thread.

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).

[ 03 April 2001: Message edited by: mdwatts ]

[DMR]

Also, check your BIOS to see if LBA mode is enabled there.