Do the artifacts show up in screen captures, or only on the display ?
Do the artifacts move around at all, particularly when the screen is being updated ?
Can you pastebin your xorg log ?
I'm getting artifacts all over my screen with the xf86-video-ati driver.
Here is my configuration:
Radeon 4850
Gentoo AMD64
Linux 2.6.31-rc2 (also tried 2.6.30)
xf86-video-ati git (also tried 6.12.2)
xorg-server-1.6.1.902
mesa 7.5-rc4 (also tried 7.4.x)
Here are some images of the artifacting:
KDM:
http://img168.imageshack.us/img168/1706/kdm.jpg
KDE 4.2:
http://img219.imageshack.us/img219/1530/kde.jpg
Openbox:
http://img504.imageshack.us/img504/3527/openbox.jpg
Is this a problem in the driver, or do I just have a really bad configuration? The fglrx driver did not have artifacting, so I know it's not the hardware.
If you need me to post any other information just ask. I'm not using that PC at the moment, so I'd have to fire it up.
But I'm thinking this is a driver issue, and I know some radeon devs browse here, so maybe I can get their attention on this issue.
Do the artifacts show up in screen captures, or only on the display ?
Do the artifacts move around at all, particularly when the screen is being updated ?
Can you pastebin your xorg log ?
Doesn't appear to show up in screen shots.
And the artifacts move all over the place, except those vertical lines you can see in KDE and KDM.
You can't really tell but on the Openbox picture, the corruption only happens in the area the terminal is. Ther other stuff is just dust on my screen. The area of corruption goes all the way across the screen, and is as tall as the console. If I move the console, the area moves with it.
If it makes any difference Xorg.0.log says it can't load DRI.
I have two screens, but they're just mirroring at the moment; I don't have Xinerma set up in xorg.conf yet, would that make a difference?
Xorg.conf:
Code:Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 EndSection Section "Files" EndSection Section "Module" Load "glx" Load "dri" Load "drm" EndSection Section "Monitor" Identifier "Monitor0" Option "VendorName" "Acer" Option "ModelName" "Generic Autodetecting Monitor" HorizSync 31.0 - 80.0 VertRefresh 56.0 - 75.0 Option "DPMS" "true" EndSection Section "Device" Identifier "Device0" Driver "radeon" Option "AccelMethod" "EXA" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024 +0+0, 1680x1050 +1280+0" EndSubSection EndSection Section "DRI" Group "video" Mode 0666 EndSection
Hi! Sorry for little offtopic (anther type artifacts on Radeon 4850). Can you take a look at this thread?
http://forum.mandriva.com/viewtopic.php?t=113470
Do you know, is it a bug in ati OSS driver or something else?
Sorry, I got mixed up; the thread was under the closed source forum. Ignore the comment about aticonfig.
You don't need the <load "dri"> or <load "drm"> lines in xorg.conf; I think that's where your "can't load DRI" message is coming from.
You mentioned you had two screens but conf only has one. Don't think that's the problem, but are you seeing artifacts on both screens ?
Oops, sorry about the wrong forum. It just said AMD/ATI and I didn't read the description.
Yes, I get artifacts on both screens.
The reason for the one screen section was for Xinerama. When I used TwinView on Nvidia it only had one screen section, so I made some assumptions.
Xorge.0.log
http://pastebin.com/m593fcde8
Okay, I tried out a Fedora 11 Live CD, and it works. I haven't installed it, as I don't have any space to put it at the moment, but here is my Xorg.0.log from Fedora 11 for comparison to the non-working one:
http://pastebin.com/m2e1187c9
It looks like it's using the radeon driver and vesa?
According to lsmod radeon and drm are loaded, and the LiveCD uses xf86-video-ati-6.12.2-14.fc11 (xorg-x11-drv-ati in yum)
I did try 6.12.2 on Gentoo, but I still had the same problem.
If I don't get this solved soon, I might just switch distros. It might just be a problem specific to Gentoo, or I have a crappy Xorg configuration or something.