+++ This bug was initially created as a clone of Bug #182294 +++ Description of problem: The X-server won't start for both antive & VESA drivers. How reproducible: every time Steps to Reproduce: 1. Boot from CD 2. attempting to start X-server with native driver - Failed 3. attempting to start X-server with VESA driver - Failed Actual results: VGA+ display only. Expected results: video normal. Additional info: AMD Athlon 64 X2 processor ULi 1573 chipset ATI RV370 Sapphire X550 graphics card
I had problems with PCIID recognition for my X550 in rawhide in the runup to FC5, but at least VESA worked as a fallback and I could use a ChipId override after install to force Xorg to work, however on FC5 final neither the radeon or vesa drivers loaded during install, so I had to use vnc to install https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180016#c11
working ok for me with xorg 7.1 in fc6t2
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
(this is a mass-close to kernel bugs in NEEDINFO state) As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug. If you believe that this bug was closed in error, please feel free to reopen this bug.