From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description of problem: I get the hang at "Initializing firewire controller (ohci1394) at reboot time after the installation completes. Subsequent reboots from emergency diskette or disk hang at the same place. Is Linux really ready for prime time? This is a poor experience with first use of Linux. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Start the Machine 2.Select Linux OS 3. Actual Results: Goes through a few steps and then hangs at the firewire controller. It is also impossible to get to the Interactive boot method since the time to enter the capital I is less than it takes for the auto-sequence to begin. Expected Results: System should have started Additional info: Normal priority means what exactly? Here the system HANGS and nothing can be done? I have now lost 4 days of work.
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/