Red Hat Bugzilla – Bug 208758
anaconda displays only black screen and mousepointer
Last modified: 2008-04-24 10:09:46 EDT
Description of problem: i'm not able to install fc6test4 because in graphic mode
only black screen and mouse pointer is shown. in text mode (after
loading driver for sata) only blue screen. on my other pc graphic mode was
usable (but the installer window was in the upper left corner of display)
Version-Release number of selected component (if applicable):
How reproducible: every time
Steps to Reproduce:
1. booting from fc6-pre-release / test4 dvd
amd xp 2000+
nvidia geforce 5200
30gb at ide controller
40gb and 80gb at raid controller but used as ide controller
250gb at sata controller
perhaps because of harddisk configuration?
Can you switch ttys in text mode when it hangs? Are your keyboard LEDs flashing?
have no keyboard leds (wireless keyboard)
i'm able to stwitch ttys...
in tty3 the last 7 lines say:
Running anaconda script /usr/bin/anaconda
unsing only installclass _Fedora
_Fedora is only installclass, using it
Display mode = t
Method = cdrom://hdc:/mnt/source
anaconda floppy device fd0
no /tmp/fcpconfig; not configuring zfcp
in tty4 last few lines:
<6>Lock_Nolock (built...) installed
<6>JFS: nTxBlock = 4008 nTxLock = 32067
<6>SGI XFS with ACLs, security attributes, large block numbers, no debug enabled
<6>SGIXFS Quato Management subsystem
<6>device-mapper: ioctl: 4.7.0-ioctl initialised: email@example.com
<6>device-mapper: multipath: version 1.0.4 loaded
<6>device-mapper: multipath round-robin: version 1.0.0 loaded
<6>device-mapper: multipath emc: version 0.0.3 loaded
<5>autit(1159791429.605:3): audit_pid=655 old=0 by auid=42984967295
looks like a raid problem...
with "linux nodmraid" its all ok...
Bouncing to anaconda since this appears to be unrelated to X.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
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 ***