Red Hat Bugzilla – Bug 443171
xorg-x11-drv-ati-6.8.0-10 badly driving a radeon 3200
Last modified: 2018-04-11 10:44:19 EDT
Description of problem:
The hardware is the ATI Radeon 3200 in the 780G chipset driving a Westinghouse
24" 1920x1200 monitor. All of which is properly detected by X via PCI discovery
However, X chooses to drive the monitor at 1600x1200 resulting in distortion and
2D performance that is lacking. Well, lacking does not even come close; 2D
reminds me of the days when people loved the imagine #9 because it could do 2D.
Further, Fedora top menu bar->System->Preferences->Hardware->Screen Resolution
includes things like 1600x1200 and 1440x1050 but not the EDID detected 1920x1200.
3D is also lacking (240 fps glx gears compared to 2k fps glxgears using ati's
driver), but that's unsurprising.
Version-Release number of selected component (if applicable):
Install Fedora 9 Preview
Steps to Reproduce:
1. Assemble a 780G system
2. Install Fedora 9
EDID line from /var/log/Xorg.0.log:
(II) VESA(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203
1209 1235 +hsync -vsync (74.
Workaround is obviously to go find ATI's unfree catalyst drivers or, figure out
how to help Novell finish the radeonhd driver ..
can you attach the xorg log?
There is no acceleraton for this hardware available, granted it shouldn't be
unuseably slow but it is all being rendered by the CPU so it won't be that fast.
I blanked F9 preview in favor of Mythdora 5 beta2 and am testing that at the
moment so I don 't have more of the log than I posted. I *smacks forhead* I
shouldda done that.
Please reopen if possible.
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.