[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Kwin direct rendering disabled on ATI
From:       Bogdan Maxim <bm () ancud ! de>
Date:       2011-04-01 12:14:02
Message-ID: 201104011414.02349.bm () ancud ! de
[Download RAW message or body]

Sorry for bothering you with menial problems, I tried the kde forum, the irc 
channels as well as my distro's forum and couldn't get any information AT ALL. 
In order to file a bug report I thought I first had to pinpoint  the component 
that is malfunctioning, so this mailing list was basically the last resort. I 
did not mean to misuse it.

Regarding your suggestions, none seem to work. Forcing direct rendering with 
KWIN_DIRECT_GL=1 does enable direct rendering but it makes the desktop 
virtually unusable.

Restarting compositing doesn't do anything, the situation doesn't change a 
bit. The performance is not "bad," it is just choppy and annoying and 
impossible to live with.

Now the question is, where do I post the bug?  Is it X-related? Is it 
Kwin/KDE(what component)? Is it the sucky fglrx without the possibility of a 
workaround? I am willing to go through the necessary paces to debug this 
issue, but I could really use some guidance from someone who has an actual 
idea about this.

Also, when you say "use the Xorg driver. Seriously" are you referring to the 
open Radeon driver? Cause that has bad performance too. Rather similar to 
fglrx, a bit worse. 

Here is the glxinfo output: http://pastebin.com/EdSNQrEF

Thank you for your support.

Max

On Thursday 31 March 2011 16:25:16 Thomas Lübking wrote:
> ftr:
> kde-devel is not exactly a user helpdesk, rather open bug reports or head
> over to the kde user forum for general help.
> also you should contact kwin@kde.org since you've trouble with a
> particular application (iff this was a developer thing ;-)
> 
> in short:
> ---------
> the catalyst driver (fglrx) is broken ever since (just google...), dri
> support isn't (wasn't? - you didn't post your glxinfo) properly detected
> and in consequence glsl fails as well.
> you should be able to enforce direct rensering by exporting
> "KWIN_DIRECT_GL=1"
> If you can, you should use the Xorg driver. Seriously.
> 
> BUT: your issue sounds more like some leak (just indirect rendering has a
> little overhead but not time driven or on a "i see dead pixels" level -
> "dri != HW acceleration", it's just about "who talks to the GPU -
> application or X11")
> 
> Try to suspend/resume compositing (press SHIFT+Alt+F12 twice) - if it's
> getting better, inspect top and xrestop for memory usage.
> also turn off all effect plugins (but NOT compositing) and see whether the
> issue remains.
> There are still at least some known leaks and state invalidations (prone
> statements) in some effects (but it's getting better ;-)
> It could as well be a leak in the driver.
> 
> <mantra>
> DO NOT, NEVEREVER, USE QHash::operator[] UNLESS YOU REALLY KNOW WHAT
> YOU'RE DOING! ;-)
> </mantra>
> 
> Cheers,
> Thomas
> 
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]