Bug 39035 - OpenGL compositing window managers doesn't work on ATI Radon Xpress 200M (and probably other r300 cards) on xserver 1.10
Summary: OpenGL compositing window managers doesn't work on ATI Radon Xpress 200M (and...
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.6 (2010.12)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-07 06:05 UTC by Adam Maćkowiak
Modified: 2016-02-25 06:53 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg |grep drm (3.75 KB, text/plain)
2011-07-07 10:50 UTC, Adam Maćkowiak 		no flags Details
dmesg |grep drm (on 1.10) (2.25 KB, text/plain)
2011-07-07 13:06 UTC, Adam Maćkowiak 		no flags Details
Xorg.0.log (44.63 KB, text/plain)
2011-07-07 13:22 UTC, Adam Maćkowiak 		no flags Details
compiz --replace (11.68 KB, text/plain)
2011-07-08 03:45 UTC, Adam Maćkowiak 		no flags Details
xorg.conf (5.19 KB, text/plain)
2011-07-08 12:13 UTC, Adam Maćkowiak 		no flags Details
1.9 Xorg log (35.14 KB, text/plain)
2011-07-14 09:38 UTC, Adam Maćkowiak 		no flags Details
1.10 Xorg log (36.16 KB, text/plain)
2011-07-14 09:38 UTC, Adam Maćkowiak 		no flags Details
Diff between 1.9 and 1.10 xorg logs (26.01 KB, text/plain)
2011-07-14 09:39 UTC, Adam Maćkowiak 		no flags Details
View All

Description Adam Maćkowiak 2011-07-07 06:05:25 UTC 
This happens on every distro that uses xserver 1.10. This happens only when compositing window window manages that uses openGL is enabled (I tested compiz and kwin). Desktop doesn't refresh automatically and I have to to hover mouse to refresh it. For example: when I move window I can't see that window moved (I still see it at old place) I have to hover mouse at this window to see that it moved.
In Kubuntu 11.04 I had to downgrade xserver to 1.9 and compiz to 0.8 to get compiz working correctly (I couldn't get kwin to work).

My graphics card: 01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress 200M]
My driver:
OpenGL vendor string: DRI R300 Project
OpenGL renderer string: Mesa DRI R300 (RS400 5A62) x86/MMX/SSE2 NO-TCL DRI2
OpenGL version string: 1.5 Mesa 7.12-devel (git-6bde225 natty-oibaf-ppa+glsl-to-tgsi)
(but this happens on Gallium 3d driver too)
Comment 1 Alex Deucher 2011-07-07 06:49:59 UTC 
Please attach your xorg log and config and dmesg output if using KMS.  Is it just the ppa code that is problematic or is the stock code a problem as well?
Comment 2 Adam Maćkowiak 2011-07-07 10:50:43 UTC 
Created attachment 48861 [details]
dmesg |grep drm
Comment 3 Adam Maćkowiak 2011-07-07 10:54:57 UTC 
I'll attach xorg log later when I get LiveCD with xserver 1.10.

This problem happens both on stock and ppa drivers. I installed driver from this PPA to get mesa dri instead of gallium 3d dri (which has much worse performance).
Comment 4 Adam Maćkowiak 2011-07-07 13:06:52 UTC 
Created attachment 48865 [details]
dmesg |grep drm (on 1.10)
Comment 5 Adam Maćkowiak 2011-07-07 13:22:37 UTC 
Created attachment 48866 [details]
Xorg.0.log
Comment 6 Adam Maćkowiak 2011-07-07 13:30:16 UTC 
I noticed that I broke wacom tablet support by downgrading xorg :(
I need to get it work in this month.
Comment 7 Alex Deucher 2011-07-07 14:18:53 UTC 
Can you bisect the xserver and track down what commit is causing the problem?
Comment 8 Adam Maćkowiak 2011-07-08 03:38:39 UTC 
I upgraded xserver to 1.10 to get wacom tablet support. It's probably OpenGL issue, because kwin with xrender works (with some rendering bugs in xul and gtk app but it works). I also upgraded compiz to 0.9 branch and it crashes (segfault) when I'm trying to run it.

Sorry I don't know how to do bisect. :(
Comment 9 Adam Maćkowiak 2011-07-08 03:45:33 UTC 
Created attachment 48887 [details]
compiz --replace
Comment 10 Michel Dänzer 2011-07-08 05:49:45 UTC 
(In reply to comment #3)
> This problem happens both on stock and ppa drivers. I installed driver from
> this PPA to get mesa dri

And the problem isn't specific to that 3D driver?

If not, does disabling page flipping work around the problem?

> instead of gallium 3d dri (which has much worse performance).

r300g is expected to perform better pretty much across the board these days. Make sure it's built with LLVM support.
Comment 11 Alex Deucher 2011-07-08 06:42:45 UTC 
Also make sure you are getting interrupts.  'cat /proc/interrupts' and make sure the numbers on the radeon line are increasing.  If not, you may try booting with:
pci=nomsi or irqpoll on your kernel command line.
Comment 12 Adam Maćkowiak 2011-07-08 06:47:49 UTC 
(In reply to comment #10)
> And the problem isn't specific to that 3D driver?
Yes, It happens on stock, and ppa dri. Both gallium 3d and mesa.
> If not, does disabling page flipping work around the problem?
Sorry, I don't know how to do it, I googled it but I couldn't find anything interesting (I found only definition what page flipping is)

> r300g is expected to perform better pretty much across the board these days.
> Make sure it's built with LLVM support.
It has worse performance than mesa (especially with disabled kms), I can see it in games.
Comment 13 Michel Dänzer 2011-07-08 06:55:01 UTC 
(In reply to comment #12)
> > If not, does disabling page flipping work around the problem?
> Sorry, I don't know how to do it, I googled it but I couldn't find anything
> interesting (I found only definition what page flipping is)

See the radeon manpage:

       Option "EnablePageFlip" "off"

in xorg.conf.

> > r300g is expected to perform better pretty much across the board these days.
> > Make sure it's built with LLVM support.
> It has worse performance than mesa (especially with disabled kms), [...]

r300g only works with KMS. You were probably hitting software rendering with KMS disabled.
Comment 14 Adam Maćkowiak 2011-07-08 12:12:42 UTC 
(In reply to comment #11)
> Also make sure you are getting interrupts
Numbers on the radeon line are increasing.


(In reply to comment #13)
>does disabling page flipping work around the problem?
No compiz and kwin OpenGl still aren't working.

I attached my xorg.conf.
Comment 15 Adam Maćkowiak 2011-07-08 12:13:15 UTC 
Created attachment 48903 [details]
xorg.conf
Comment 16 Adam Maćkowiak 2011-07-12 14:39:07 UTC 
Anyone? Please I really want compositing.
Comment 17 Alex Deucher 2011-07-12 14:50:03 UTC 
Did you try pci=nomsi or irqpoll on your kernel command line in group?
Comment 18 Alex Deucher 2011-07-12 14:50:33 UTC 
(In reply to comment #17)
> Did you try pci=nomsi or irqpoll on your kernel command line in group?

s/group/grub/
Comment 19 Adam Maćkowiak 2011-07-12 16:02:38 UTC 
(In reply to comment #18)
> (In reply to comment #17)
> > Did you try pci=nomsi or irqpoll on your kernel command line in group?
> 
> s/group/grub/

Yep, I tried it.

pci=nomsi - compiz still crashes with same output
irqpoll - linux doesn't even boot (it instantly restarts)
pci=nomsi irqpoll - compiz still crashes with same output
Comment 20 Michel Dänzer 2011-07-13 07:15:43 UTC 
Many things are still unclear, e.g.: What exactly does "I couldn't get kwin to work" mean? That the same problem happens with kwin even with xserver 1.9, or something else? Did you double-check in Xorg.0.log that page flipping was really disabled?

Maybe you can also attach Xorg.0.log from xserver 1.9 (with working compiz), and look for any interesting differences to the log from 1.10.
Comment 21 Adam Maćkowiak 2011-07-13 09:24:16 UTC 
(In reply to comment #20)
> Many things are still unclear, e.g.: What exactly does "I couldn't get kwin to
> work" mean? That the same problem happens with kwin even with xserver 1.9, or
> something else?
No, on 1.9 kwin OpenGL had some rendering problems (for exapmle, blinking windows on minimization and changing virtual desktop)
On 1.10 kwin OpenGL won't even run.
> Did you double-check in Xorg.0.log that page flipping was
> really disabled?
Yes, I did it.
> Maybe you can also attach Xorg.0.log from xserver 1.9 (with working compiz),
> and look for any interesting differences to the log from 1.10.
I'll attach it today.
Comment 22 Adam Maćkowiak 2011-07-14 09:37:18 UTC 
Sorry you had wait, but I hadn't got time yesterday.

I'm attaching Xorg 1.9 and 1.10 and diff between them (I removed timestamps using sed before I made diff). I hadn't found any interesting changes, but it's probably because I'm not experienced user.
Comment 23 Adam Maćkowiak 2011-07-14 09:38:15 UTC 
Created attachment 49092 [details]
1.9 Xorg log
Comment 24 Adam Maćkowiak 2011-07-14 09:38:48 UTC 
Created attachment 49093 [details]
1.10 Xorg log
Comment 25 Adam Maćkowiak 2011-07-14 09:39:51 UTC 
Created attachment 49094 [details]
Diff between 1.9 and 1.10 xorg logs
Comment 26 Alex Deucher 2011-07-18 10:08:32 UTC 
Does adding noapic to the kernel command line in grub help?  See the last few comments in bug 37679.
Comment 27 Adam Maćkowiak 2011-07-28 15:21:56 UTC 
Disabling ACPI didn't help.
Comment 28 Michel Dänzer 2011-08-02 09:56:54 UTC 
(In reply to comment #27)
> Disabling ACPI didn't help.

Note Alex asked for "noapic", not "noacpi".
Comment 29 Adam Maćkowiak 2011-08-02 13:04:18 UTC 
(In reply to comment #28)
> (In reply to comment #27)
> > Disabling ACPI didn't help.
> 
> Note Alex asked for "noapic", not "noacpi".

I tried noapic, noacpi and both of them (to be sure) and they didn't helped.
Comment 30 Christopher M. Penalver 2016-02-25 06:53:56 UTC 
Adam Maćkowiak, Kubuntu 11.04 reached EOL on October 28, 2012. For more on this, please see https://wiki.ubuntu.com/Releases .

If this is reproducible on a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

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.