From: Roland S. <rsc...@hi...> - 2006-04-03 00:12:47
|
Felix K=C3=BChling wrote: > Am Sonntag, den 02.04.2006, 23:37 +0300 schrieb Andrey Khavryuchenko: >> Hi! >> >> I've set up the above on my IBM T30 notebook (Radeon Mobility 7500) (l= inux) >> and both glxinfo and glxgears fps confirms that: >> >> $ glxinfo | grep direct >> direct rendering: Yes >> >> $ glxgears >> 3775 frames in 5.0 seconds =3D 754.980 FPS >> 3777 frames in 5.0 seconds =3D 755.370 FPS >> >> Nevertheless, the application I need (pymol, http://www.pymol.org) ref= uses >> to use accelerated 3d: >> >> $ LIBGL_DEBUG=3Dverbose ./pymol >> libGL: XF86DRIGetClientDriverName: 5.0.3 radeon (screen 0) >> libGL: OpenDriver: trying /usr/lib/X11/modules/dri/radeon_dri.so >> libGL error: dlopen /usr/lib/X11/modules/dri/radeon_dri.so failed (/us= r/lib/X11/modules/dri/radeon_dri.so: undefined symbol: _glapi_Dispatch) >> libGL error: unable to find driver: radeon_dri.so >=20 > Compare the output of "ldd ./pymol" with "ldd /usr/bin/glxgears". My > guess is that pymol is linked with a different libGL. Try specifying > -L<path to the right libGL> when you link pymol. Alternatively, if this still doesn't help, it may be possible that=20 somehow libGL.so doesn't get loaded correctly. Pymol actually seems to=20 contain some workaround for the problem when libGL.so isn't loaded with=20 RTLD_GLOBAL, but I'm not sure why it is needed, as it is linked directly=20 against libGL (and this is only a problem if libGL gets dlopen'ed).=20 Maybe libGL gets loaded through python or something. If that workaround=20 doesn't work for some reason, you could try LD_PRELOAD=3D/usr/lib/libGL.s= o=20 (or wherever it is). Roland |