Hello, When running startx so the standard session with twm and the thatched background is displayed what I can best describe as shearing occurs in the background. The output is crystal clear when using DVI but exhibits this issue when using the VGA port or a DVI->VGA converter. Using the vesa driver, this problem does not appear on the VGA port. If while I get the shearing I run something like dmesg in the xterm it looks like there is a problem with the vertical sync and darker stripes appear and then disappear temporarily while xterm is scrolling text... So I'm guessing the problem is with programming the DAC somewhere... I'm attaching logs of X.Org running with radeon and with vesa. The config for the same is both, I just changed driver from radeon to vesa. The HorizSync/VertRefresh is there only to force the vesa driver into 1280x1024 (for some reason it otherwise goes into 640x480); it has no effect on the radeon driver's output. From lspci (problem happens with both cards): 06:02.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] 07:01.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] Thanks!
Created attachment 9329 [details] xorg.conf
Created attachment 9330 [details] Log (with VESA, working)
Created attachment 9331 [details] Log (with radeon)
The radeon log file isn't consistent with the config file; it shows two screen sections used. Please clarify this. Also, does this happen with depth 16 and/or lower resolutions?
Happens regardless of how many screens are used and the same for both cards (although DVI on both is fine). It's better when used in depth 16 with the radeon driver but still noticeable (although less so).
does this still happen with the latest version of the ati driver from git?
Bugzilla Upgrade Mass Bug Change NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO. - benjsc fd.o Wrangler
I believe this was fixed in git a while ago (im-proper program of tvdac adj). Please test a more recent version of the ati driver. Please re-open if the problem persists.
Just to update the bug: in the end this was resolved and the culprit was a faulty VGA cable which didn't pass through the I2C data from the monitor correctly, so the refresh rate wasn't getting set to the one it should have been set to. Many thanks to Alex for taking the time to help diagnose the problem, much appreciated!
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.