Red Hat Bugzilla – Bug 394611
anaconda produces a black screen when X11 install proceeds on X1650
Last modified: 2018-04-11 09:04:36 EDT
Description of problem:
When installing Fedora 8 x86_64 on a workstation with a Radeon X1650 Pro PCIE
card, anaconda identifies the card and then the screen goes black as the X11
based installer window should appear.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot the Fedora 8 x86_64 installer DVD on a workstation with a Radeon X1650
Pro PCIE graphics card.
2. Select the default GUI installation method.
After the media check, anaconda probes the video card and the screen goes black
when the X11 based installation windows should appear. At this point, I can't
get to a virtual console to check the status of the X11 startup. Attempts to
pass the 'xserver=vesa' option on the kernel flags to the installer don't help.
Anaconda doesn't honor this flag and always seems to be trying to start up X11
with the radeon driver.
The 'xdriver=vesa' kernel option should have at least allowed me to force
anaconda to use the vesa driver so that the X11 based GUI installer option would
I still think (despite the reassignment of this bug to the xorg-x11-drv-ati
maintainer) that the anaconda maintainer should still be involved. The question
remains as to why 'xdriver=vesa' is not honored by anaconda. I'll guess I'll
file that as a different bug.
Unfortunately, I have to say as a xorg bugs bugmaster, that our X server should
just work without any kernel paramters magic.
Have you managed to install the Fedora 8 with text-based installation? If yes,
could you give us please file /var/log/anaconda.xlog from the failed graphical
installation? If you managed to install, does your X work now? Could we get also
as a separate uncompressed attachments both /etc/X11/xorg.conf and
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.