Bug 164043 - FC3 Freezes durring Boot on Gateway 955 / Intel SR1300
Summary: FC3 Freezes durring Boot on Gateway 955 / Intel SR1300
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kudzu
Version: 3
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
URL:
Whiteboard:
: 164061 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-23 08:53 UTC by jack
Modified: 2014-03-17 02:55 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-09-18 19:27:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jack 2005-07-23 08:53:24 UTC
Description of problem:
After installing FC3 on a Gateway 955 Server ( Intel SR1300 ) everything ran 
as expected, but upon reboot from the install the server hangs on discovering 
new hardware. Found related issue for older FC version and they said to change 
modeprobe.conf ( actully they said modules.conf in etc which is no longer) and 
comment out the line that says "alias usb-controller ohci-hcd".
I did comment out the alias usb-controller ohci-hcd line, rebooted and the 
server locked up in the same place.
Basically we can't ssh into the box since it never boots.
We do have the Megaraid 300 controller running on this server as well, but 
this is recognized without issue by FC3.


Any help / ideas appreciated.

Comment 1 Peter Jones 2006-02-27 19:23:46 UTC
*** Bug 164061 has been marked as a duplicate of this bug. ***

Comment 2 Matthew Miller 2006-07-10 22:44:46 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!


Comment 3 Bill Nottingham 2007-09-18 19:27:13 UTC
Closing per prior comment.


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