Red Hat Bugzilla – Bug 50231
Anaconda can use ATI Xpert 128 but RHL Roswell acn not
Last modified: 2007-04-18 12:35:15 EDT
Description of Problem: The installer was able to go into graphical mode, however after installation X could not come up. I imagune there is a difference between the X in Anaconda and the X in the distro. How Reproducible: Happens with every install Steps to Reproduce: 1. Install in graphical mode 2. Startx 3. Actual Results: X doesn't start Expected Results: Additional Information:
Anaconda runs inside an XFree86-FBDev 3.3.6 Xserver on top of the Linux framebuffer. When configuring X in anaconda, a second X server is started which is the actual one that will be used, however it is also running on the framebuffer but as display :9. If this card is the Rage SM you mentioned in another report (I think it was an SM), then it still isn't supported yet. The X in b3 does not have the latest ATI patch which supportsRage TF and a few others. We still do not have the SM supported yet. Can you provide: lspci -vn Thanks Derek, TTYL
Created attachment 25311 [details] lspci -vn
This is the Xpert 128 (Rage SM). Graphical installs failed as X sig 11'ed in Beta 1 and Beta 2. When graphical installation worked in Beta 3, I assumed that you had already patched X for this problem. It didn't occur to me that anaconda would be using the frame buffer X server. Sorry I jumped the gun there...
No probo.. X not patched yet for SM.. I flagged this for final release tho so will try to get it in once I can build X again.
Hi Derek, I just whacked out Xpert2000 Rage SM support tonight, and patched XFree86. You can expect 4.1.0-0.9.13 to contain the new code. It is completely untested (I don't have one), so please gimme feedback, and bug reports. ;o)
Is this working with the Skipjack beta?
This actually was fixed in 7.2 and this card works fine with the beta's through beta3. I think I may have some marginal hardware as the GDM screen on logout tends to break up into thirds vertically. Or perhaps the timing are slightly agressive. Mike, you can go ahaed and close this.
Thanks dlt. Closing as fixed in 7.2 erratum 4.1.0-15 although it probably works in 4.1.0-3 also.