Forwarded from https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/133192 2007-08-17 Since the updates a few days ago on gutsy, my screen only shows garbage with only the mouse pointer shown normally. This is on a radeon 9250. (the version which was uploaded mid-August is 6.6.193)
disabling glx makes the problem to go away.
screenshots: http://launchpadlibrarian.net/8882127/Afbeelding%20002.jpg http://launchpadlibrarian.net/9255354/00001.jpg
6.7.194 is still broken for him.. logs are coming.
(In reply to comment #1) > disabling glx makes the problem to go away. More likely what matters is the DRI, which is also disabled implicitly when GLX is disabled. AFAICT nobody actually tried with tiling disabled - the option name is "ColorTiling".
Ok, I'll ask that. Here is the log with glx enabled: http://launchpadlibrarian.net/9512620/Xorg.0.log
on trying ColorTiling: "Tried that, doesn't help. Also tried only disabling DRI as mentioned in the upstream report, but that doesn't do anything either. Only disabling glx works."
(In reply to comment #6) > on trying ColorTiling: [...] Saw that... again, the option name was spelt incorrectly in the downstream bug report, and the log file shows it misspelt in the same way and thus ineffective.
Disabling dri is the only thing which made it work: http://launchpadlibrarian.net/9522639/Xorg.0.nodri2.log
This bug is actually about the AGPMode mess that's going on :) Setting it to "4" works for the reporter.
Unfortunately, as far as we can tell it's just impossible to always pick a default value for AGPMode that works, and in general leaving it unchanged from what the BIOS set up seems most reliable. I'm afraid it looks like the cases where that doesn't work need to change it in the BIOS setup or xorg.conf.
If I understand the current code correctly, the default is to leave it unchanged for v3 cards, but to use x1 for v2 cards. This breaks for some v2 cards. I think the old behaviour of leaving v2 cards unchanged also broke on some cards.
Sure, this bug is about V3 though, but the same problem also occurred when we defaulted to 4x for that. Right now it's looking like leaving it unchanged is most reliable overall, and we should probably switch back to that for non-V3 as well.
if this is still an issue with the driver from git, we can add a quirk for your card/gpu combo.
closing due to lack of feedback.
it was apparently fixed already with a quirk, sorry for not closing this earlier :)
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.