Dual Head + radeon driver + mergefb + beryl. DRI problem now. Beryl problem now.

[ArcosCom Linux User]

Sorry, I take a mistake: I have no bears, I have beers.

And, with only one monitor enabled, beryl works now, but with the 2
monitors I have the messages sended.

More help?

El Lun, 2 de Julio de 2007, 13:14, ArcosCom Linux User escribió:
> This "works for me (tm)" but I don't like uninstalling fglrx driver, I
> like the two drivers coexist to allow me change the configurations.
>
> Fine, at least, now I have yet DRI working. ¡¡¡THANKS!!! (you have 2 bears
> here in Spain).
>
> The problem now is with beryl:
>
> === BEGIN ===
> $ beryl --test-only
> **************************************************************
> * Beryl system compatiblity check                            *
> **************************************************************
>
> Detected xserver                                : AIGLX
>
> Checking Display :0.0 ...
>
> Checking for XComposite extension               : passed (v0.3)
> Checking for XDamage extension                  : passed
> Checking for RandR extension                    : passed
> Checking for XSync extension                    : passed
>
> Checking Screen 0 ...
>
> libGL warning: 3D driver claims to not support visual 0x4b
> Checking for GLX_SGIX_fbconfig                  : passed
> Checking for GLX_EXT_texture_from_pixmap        : passed
> Checking for non power of two texture support   : passed
> Checking maximum texture size                   : failed
>
> Root window size (2960/1050) is bigger then maximum texture size
> (2048x2048)
>
> X Error of failed request:  GLXBadContext
>   Major opcode of failed request:  144 (GLX)
>   Minor opcode of failed request:  4 (X_GLXDestroyContext)
>   Serial number of failed request:  38
>   Current serial number in output stream:  40
> === END ===
>
> ¿How I can solve this problem? ¿Do I need anything else in my xorg.conf?
>
> Regards
>
> El Lun, 2 de Julio de 2007, 12:14, Michel Dänzer escribió:
>> On Mon, 2007-07-02 at 12:10 +0200, ArcosCom Linux User wrote:
>>>
>>> About "LIBGL_DEBUG=verbose glxgears":
>>> name of display: :0.0
>>> libGL: XF86DRIGetClientDriverName: 5.2.0 r300 (screen 0)
>>> libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
>>> libGL error: dlopen /usr/lib/dri/r300_dri.so failed
>>> (/usr/lib/dri/r300_dri.so: undefined symbol: _glapi_get_dispatch)
>>> libGL error: unable to find driver: r300_dri.so
>>> libGL: XF86DRIGetClientDriverName: 5.2.0 r300 (screen 0)
>>> libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
>>> libGL error: dlopen /usr/lib/dri/r300_dri.so failed
>>> (/usr/lib/dri/r300_dri.so: undefined symbol: _glapi_get_dispatch)
>>> libGL error: unable to find driver: r300_dri.so
>>
>> Move fglrx's libGL.so.1.2 out of the way (beware, adding a suffix will
>> only work until the next ldconfig run).
>>
>>
>> --
>> Earthling Michel Dänzer           |
>> http://tungstengraphics.com
>> Libre software enthusiast         |          Debian, X and DRI developer
>>
>>
>
>
> _______________________________________________
> xorg mailing list
> xorg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xorg
>