Bug 77113 - lilo hangs with LI or kernel panics
Summary: lilo hangs with LI or kernel panics
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 8.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-11-01 10:55 UTC by John B. Wier III
Modified: 2008-08-01 16:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-30 15:40:09 UTC
Embargoed:


Attachments (Terms of Use)

Description John B. Wier III 2002-11-01 10:55:36 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (Win98; U)

Description of problem:
Tyan dual 1.13 Intell PIII with768MB ram.  All IDE disk drive system. Three disks installed, all three attached to Maxtor Ultra133TX2 IDE controller.
Custom install. Choose install everything.
Did not see an option to turn on "reverse scan order when booting" during install processes. From the boot floppy I tried to use ide=reverse for the 
kernel boot param but it did not work. This option is not selected and compiled into the kernel by default.
Install did not choose smp support kernel.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Custom install. Choose install everything.
2.
3.
	

Actual Results:  Without the ide=reverse, lilo gets to LI and stops.
With ide=reverse, the kernel panics when trying to run init during boot.

Expected Results:  smp kernel should have been installed and ide=reverse should have been added to lilo.conf.

Additional info:

Tyan dual 1.13 Intell PIII with768MB ram.
All IDE disk drive system. Three disks installed, all three attached to Maxtor Ultra133TX2 IDE controller.

Comment 1 Bugzilla owner 2004-09-30 15:40:09 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/



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