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

List:       kwin
Subject:    Re: Force compositing possible?
From:       "A. Bischof" <a.bischof () gmx ! net>
Date:       2011-03-29 21:14:39
Message-ID: 4D924BBF.2060309 () gmx ! net
[Download RAW message or body]

Am 29.03.2011 16:14, schrieb Thomas Lübking:
> Am 29.03.2011, 15:45 Uhr, schrieb A. Bischof<a.bischof@gmx.net>:
>
>> Hi,
>>
>> first of all, I hope it's correct to post my problem here, if it
>> belong's elsewhere, please let me know.
> ->  kwin@kde.org - but you can oc. call for general help on kde-devel as
> well :-)

Kind, thanks! :-)

>> I'm trying to get compositing running with KDE 4.4.5 and an embedded ATI
>> gfx-card, free radeon driver on Debian stable/testing
> 4.4.5 is pretty dated - the driver might just have been (hard) blacklisted
> than...
>
>> It runs with KMS, I have hardware acceleration running (Xorg.0.log):
>> (II) RADEON(0): Sync:  Separate  Composite
>>           compiled for 1.7.7, module version = 1.0.0
>>           compiled for 1.7.7, module version = 2.5.0
>> (II) RADEON(0): [DRI2] Setup complete
>> (II)         Composite (RENDER acceleration)
>> (II) RADEON(0): Acceleration enabled
>
> xdpyinfo| grep -iE 'composite|damage'
> should print
>
>       Composite
>       DAMAGE

true:
# xdpyinfo| grep -iE 'composite|damage'
     Composite
     DAMAGE



> otherwise the extension is not loaded (no idea how that driver logs them,
> nvidia says:
> [ 59332.321] (II) Initializing built-in extension COMPOSITE
> [ 59332.321] (II) Initializing built-in extension DAMAGE
>
>> I can use Cube-Switching as one can enable it under Multiple Desktop ->
>> Switching.
> So compositing /is/ active - the config dialog is just messed?
> The suspended/enabled state calculation was pretty much borked (and has
> therefore been removed for 4.7)
> You could just close the dialog and call
>
> kwriteconfig -file kwinrc -group Compositing -key Enabled true
> kwriteconfig -file kwinrc -group Compositing -key OpenGLIsUnsafe false
> kwriteconfig -file kwinrc -group Compositing -key CheckIsSafe true
 >
> then restart systemsettings - does kwin somehow crashrestart when KDE
> starts up?

well, that did the trick - no crashes, neither at KDE start nor after 
these lines, and compositing full configurable.

Are these changes permanent, or do I have to enter the three lines above 
somewhere?

> You'll likely have to enforce indirect rendering (export
> LIBGL_ALWAYS_INDIRECT=1) since the driver is likely buggy in this regard
> (they all / mesa were ...)

seems not to be necessary, everything work's fine now.

Thanks alot!

Cheers
Andre

_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin

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