Bug 74471 - Install hangs at "Partition Check" line if floppy controller disabled in bios
Summary: Install hangs at "Partition Check" line if floppy controller disabled in bios
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-24 22:08 UTC by Paul Reiner
Modified: 2008-08-01 16:22 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2004-09-30 15:39:56 UTC


Attachments (Terms of Use)

Description Paul Reiner 2002-09-24 22:08:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 
1.0.3215; .NET CLR 1.0.3705)

Description of problem:
The installer hangs just after the lines below if the FDC is disabled in bios. 
Since I have an IDE LS-120 superfloppy, I didnt need (i disabled) the floppy 
controller

TEXT ON SCREEN:

Partition Check

hdda: hda1 hda2 <hda5>



HANG!

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


How reproducible:
Always

Steps to Reproduce:
1.disable floppy controller in bios
2.boot from cd
3.hit enter at boot: prompt
	

Actual Results:  hang during/just after hard disk enumeration

Expected Results:  World peace. if thats not possible, how about simply NOT 
hanging

Additional info:

Comment 1 Michael Fulbright 2002-09-27 19:37:00 UTC
This is during the kernel initialization from what I can tell, reassigning...

Comment 2 Bugzilla owner 2004-09-30 15:39:56 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.