Created attachment 20139 [details] xorg.conf I use a dual-DVI X1650 to drive my two displays -- a 1680x1050 LCD and a 1280x1024 LCD. When the "UseAtomBIOS" option is not used, I see problems with the 1680x1050 LCD display after X has been running for an extended period. I see two problems on the 1680x1050 display: 1. The image on the 1680x1050 display will "shake" back and forth slightly (by a pixel or 2 horizontally). This is most noticeable when working with text, such as e-mail or terminal windows. 2. The 1680x1050 display will occasionally "black out" for a second or so. After much experimentation, I have discovered that these problems do not occur when I enable "UseAtomBIOS".
Created attachment 20140 [details] lspci -vvv output
Created attachment 20141 [details] X.org log without UseAtomBIOS
Created attachment 20142 [details] X.org log with UseAtomBIOS
Ian, could you please run: rhd_dump 1:5.0 -r 0x7A80,0x7B18 for both the AtomBIOS and non-AtomBIOS case? rhd_dump can be found in utils/conntest in the source tree. It requires libz and pciutils to build. Thanks!
Created attachment 20306 [details] Output of rhd_dump with UseAtomBIOS turned on
Created attachment 20307 [details] Output of rhd_dump with UseAtomBIOS turned off
Ian, the differences in register values seem to be irrelevant. Could you run some more tests for me, please? Replace Option "UseAtomBIOS" "yes" by: Option "AtomBIOS" "crtc=on pll=on output=on" The results should be the same as with "UseAtomBIOS". Please check which of the arguments: crtc=on pll=on output=on are required to make it work.
(In reply to comment #7) > Please check which of the arguments: > crtc=on > pll=on > output=on > are required to make it work. Option "AtomBIOS" "pll=on" is the setting that makes things work.
I have upgraded on version 1.2.5 of the driver, on Fedora 10, and the behavior has changed. I now don't get any image at all on the 1680x1050 LCD without setting "pll=on". Is this progress? ;-)
Just an FYI that the patch in bug #22229 has fixed some PLL-related problems that I've seen with the radeon driver on this hardware. Might be worth checking to see if radeonhd (non-AtomBIOS path) is doing the same thing that radeon was.
Have you tried radeonhd (with Option "AtomBIOS" "pll=on")? radeon and radeonhd have pretty different mode acceptance policies - so it could be possible that we're not hit by this bug. radeonhd also doesn't use fractional dividers yet, and I'm unsure about the consequences.
Does this issue occur with the preferred ati driver (xf86-vide-ati)? If so, please move this to the Driver/Radeon component. Development of radeonhd has pretty much halted and development focus is on the ati driver. Please see http://www.x.org/wiki/radeonhd If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch.
Closing due to lack of response. Please reopen and move to the Driver/Radeon component if this issue persists with xf86-video-ati
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.