Bug 115621 - Installation locks up at Run /sbin/loader
Summary: Installation locks up at Run /sbin/loader
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-13 22:57 UTC by Ian Anderson
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-05-03 21:04:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ian Anderson 2004-02-13 22:57:20 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
Boot off FC2-test1-i386 CD from IDE DVD-ROM drive on an ASUS
P4R-800-VM motherboard (ATI 9100 IGP chipset).
Problem occurs in both text mode and graphical

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


How reproducible:
Always

Steps to Reproduce:
1.Boot off CD
2.Wait for it to reach Run /sbin/loader
3.
    

Additional info:

Comment 1 Jeremy Katz 2004-02-14 19:46:33 UTC
Does booting with 'linux nopcmcia' help?

Comment 2 Ian Anderson 2004-02-14 21:40:02 UTC
Tried booting with both 'linux nopcmcia' and 'linux noprobe'
still dies at Running /sbin/loader, no obvious difference.


Comment 3 Ian Anderson 2004-02-18 00:52:19 UTC
Good news: can get past Running /sbin/loader if I disable the on-board
USB EHCI controller
Bad news: this disables my USB mouse so it is not a solution.

Comment 4 Douglas Peale 2004-03-03 06:56:06 UTC
I have the same problem with a USB mouse plugged in it hangs at
/sbin/loader. If I have a PS/2 mouse plugged in, it boots fine &
installs fine, even if that PS/2 mouse is the same mouse with the USB
to PS/2 adapter installed.

Comment 5 Jeremy Katz 2004-04-15 04:58:58 UTC
Does this continue to happen with test2?

Comment 6 Ian Anderson 2004-04-15 21:37:42 UTC
Problem appears to have been resolved by a combination of test2 and
BIOS upgrade to system.


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