| 1 |
On 11/23/2010 02:20 AM, Robin Atwood wrote: |
| 2 |
> On Tuesday 23 November 2010, Nikos Chantziaras wrote: |
| 3 |
>> On 11/22/2010 09:40 PM, Robin Atwood wrote: |
| 4 |
>>> On Tuesday 23 November 2010, Nikos Chantziaras wrote: |
| 5 |
>>>> On 11/22/2010 07:02 PM, Robin Atwood wrote: |
| 6 |
>>>>> I have just gone through the steps to use the Radeon KMS driver on my |
| 7 |
>>>>> old laptop which has an RV350 [Mobility Radeon 9600 M10]. Everything |
| 8 |
>>>>> seems to work all right and I get the right "render string" from |
| 9 |
>>>>> glxinfo. However, I thought it might enable compositing to work on the |
| 10 |
>>>>> KDE4 desktop but there is no change. What's more, glxgears used to |
| 11 |
>>>>> give about 2200 FPS but now it's 50! So have I been wasting my time? |
| 12 |
>>>> |
| 13 |
>>>> You have to enable compositing yourself in System Settings. |
| 14 |
>>> |
| 15 |
>>> Of course, but it didn't take. |
| 16 |
>>> |
| 17 |
>>>> KMS means you're using DRI2 now, which results in a VSync'ed OpenGL |
| 18 |
>>>> rendering. Though I'd expect 60FPS because of VSync, not 50 :-P |
| 19 |
>>>> |
| 20 |
>>>> One other thing you should do is to enable the "gallium" USE flag and |
| 21 |
>>>> |
| 22 |
>>>> re-emerge Mesa. Then switch to the Gallium driver using: |
| 23 |
>>>> eselect mesa r300 gallium |
| 24 |
>>>> |
| 25 |
>>>> Because that driver is the recommended one for your hardware (R300). |
| 26 |
>>>> The classic driver should be avoided. |
| 27 |
>>> |
| 28 |
>>> Thanks, I would try that, but... |
| 29 |
>>> |
| 30 |
>>> # emerge -av media-libs/mesa |
| 31 |
>>> |
| 32 |
>>> These are the packages that would be merged, in order: |
| 33 |
>>> |
| 34 |
>>> Calculating dependencies... done! |
| 35 |
>>> [ebuild U ] x11-libs/libX11-1.4.0 [1.3.6] USE="-doc -ipv6 |
| 36 |
>>> -static-libs - test (-xcb%*)" 2,036 kB |
| 37 |
>>> [ebuild R ] media-libs/mesa-7.8.2 USE="nptl pic xcb -debug |
| 38 |
>>> (-gallium) - motif (-selinux)" VIDEO_CARDS="radeon -intel -mach64 -mga |
| 39 |
>>> -nouveau -r128 - savage -sis -svga -tdfx -via" 0 kB |
| 40 |
>>> |
| 41 |
>>> I set "gallium" in /etc/make.conf but (-gallium) means the flag is turned |
| 42 |
>>> off in a profile somewhere? |
| 43 |
>> |
| 44 |
>> Oh, you're not on ~arch. I assumed to much. I don't know how that |
| 45 |
>> works on old versions of the drivers and Mesa, or whether Gallium3D was |
| 46 |
>> any good with old versions of Mesa. I can only confirm that it works on |
| 47 |
>> recent versions. |
| 48 |
>> |
| 49 |
>> For your KDE problem, try adding/changing these in your |
| 50 |
>> ~/.kde4/share/config/kwinrc: |
| 51 |
>> |
| 52 |
>> [Compositing] |
| 53 |
>> Backend=OpenGL |
| 54 |
>> CheckIsSafe=false |
| 55 |
>> DisableChecks=true |
| 56 |
>> Enabled=true |
| 57 |
>> GLDirect=true |
| 58 |
>> GLTextureFilter=1 |
| 59 |
>> GLVSync=false |
| 60 |
>> OpenGLIsUnsafe=false |
| 61 |
> |
| 62 |
> When I try to enable compositing KDE gives a message that it's not possible. |
| 63 |
> Setting "Disable checks" also gives an error message. So I cannot see any |
| 64 |
> actual benefit. |
| 65 |
|
| 66 |
Try the whole thing I posted, because some of the settings do *not* have |
| 67 |
a GUI button and can only be enabled/disabled by editing kwinrc. |
Archives