Description of problem:
Generates an exception after language selection. Also fails in text mode
Version-Release number of selected component (if applicable):
Intel D975XBX motherbord, ATI RADEON x1900GT, Sil 3114 raid0 With 2 WDC740D,
Seagate ST3320620AS SATA drive, @ Gb ram
Steps to Reproduce:
1.Boot from CD
2.Install (tried linux ide=nodma)
Created attachment 142663 [details]
Does booting with 'linux nodmraid' help?
Yes I was able to complete the installation
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
There is a bug where the dmraid stuff just blocks. This bug has not been solved
yet and we are still working to fix it. However there is a work around. If
you use nodmraid, the installer will ignore/skip the dmraid stuff allowing the
install to finish. This is a workaround and does not fix the problem.
There is a long list of bugs that are filed against this problem. This bug is
one of them. We have decided to close all the related nodmraid bugs and leave
just one open that will represent all of the others. So this bug will be duped
for this reason.
*** This bug has been marked as a duplicate of 409931 ***