Bug 97446
Summary: | (IEEE1394) Re-Boot hangs at Initializing firewire controller (ohci1394) | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Amin Adatia <amin> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | alan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i586 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:41:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Amin Adatia
2003-06-16 00:17:38 UTC
This does not appear to be an anaconda problem. Seems like a driver issue. You can boot with 'nofirewire' to get around it. Boot with "nofirewire" then update to the errata kernel. That should help with this problem that some people hit. Let me know how that goes The problem was fixed by using the floppy disk to boot and then at the boot prompt linux single nofirewire Then modified the etc/grub file with nofirewire parameter. The current errata kernel should let you just use your firewire ytryrty i'm new at this, and i have the same problem, first when i installed red hat 9 but with "linux nofirewire" i could install it, but then I get the hang at "Initializing firewire controller (ohci1394) at reboot time after the installation completes. Can you tell me how to solve this problem... 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/ |