Bug 7571 – Lilo displays LI after SERVER install

Bug 7571 - Lilo displays LI after SERVER install

Summary:	Lilo displays LI after SERVER install

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	lilo (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-12-03 16:41 EST by MLHarmon
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 13:47:34 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description MLHarmon 1999-12-03 16:41:26 EST

I have loaded Red Hat 6.1 on my Compaq Prosignia 300.
After successfully loading a SERVER install to my server
and reboot, the following happens;

LI appears in the upper left corner of my screen and the server just
locks up and does nothing more.

MHARMON@CSSIUSA.COM

Comment 1 Daniel DiPaolo 1999-12-27 05:39:59 EST

Now, I'm not sure about this, but the Linux reference I use - "Red Hat Linux
Unleashed" tells me that that is actually an error code that LILO will return.
According to my book, it means that "the second-stage boot loader loaded, but
could not run".  But, I don't know what that means.

You may check to make sure that and make sure you didn't make some bogus changes
to lilo.conf using a boot disk.

Comment 2 Riley H Williams 1999-12-28 13:18:59 EST

I had this very situation occur earlier today. It turned out to be because the
partition table was set up for the disk in LBA mode but the BIOS was declaring
it to be in NORMAL mode instead, with the result that references outside of
cylinder 0, head 0 were going to the wrong part of the disk.

You may wish to tweak your BIOS and find out if a different mode setting fixes
the problem.

Comment 3 Cristian Gafton 2000-01-04 17:26:59 EST

Assigned to dledford

Comment 4 lukep 2000-02-07 04:09:59 EST

I had the same problem and gave up on linux for about a week, but just a few
days ago I had a problem with my computer and installing windows 2000 and wound
up formatting my harddrive, after that I managed to install linux for some
reason even though I was installing it on a second seperate harddrive.

Comment 5 Jeremy Katz 2002-06-04 00:58:29 EDT

Do you still have this problem with more current versions of Red Hat Linux?

Comment 6 Jeremy Katz 2002-06-29 17:47:46 EDT

Closing due to inactivity.  If you have further information, please reopen this bug.

Comment 7 Red Hat Bugzilla 2006-02-21 13:47:34 EST

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.