-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lenz Grimmer wrote:
while browsing the Linux-Thinkpad mailing list for hints I stumbled over the suggestion to use "LIBGL_DEBUG=verbose glxinfo", which revealed the following error:
[SNIP] libGL: XF86DRIGetClientDriverName: 5.2.0 r300 (screen 0) libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/r300_dri.so libGL error: dlopen /usr/X11R6/lib/modules/dri/r300_dri.so failed (/usr/X11R6/lib/modules/dri/r300_dri.so: undefined symbol: _glapi_add_dispatch) libGL error: unable to find driver: r300_dri.so libGL: XF86DRIGetClientDriverName: 5.2.0 r300 (screen 0) libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/r300_dri.so libGL error: dlopen /usr/X11R6/lib/modules/dri/r300_dri.so failed (/usr/X11R6/lib/modules/dri/r300_dri.so: undefined symbol: _glapi_add_dispatch) libGL error: unable to find driver: r300_dri.so [SNIP]
I guess that's the root cause of the problem here - should I file a bug report about this?
Please disregard, I finally found the solution:
"rpm -e fglrx_7_1_0_SUSE102-8.33.6-1" solved it! The ATI driver RPM
installed an additional libGL.so library under /usr/X11R6/lib, that
was missing that symbol. Removing the package solved it, now the proper
libGL.so from the Mesa RPM (/usr/lib/libGL.so) is used instead and
direct rendering is finally enabled:
lenz@metis:~> glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 20060815 AGP 1x x86/MMX/SSE2 TCL
Bye,
LenZ
- --
- ------------------------------------------------------------------
Lenz Grimmer