[Dri-devel] Re: [XFree86] Re: DRI weirdnesses for RADEON 9200

[Ian R. <id...@us...>]

manu wrote:

> Le 30.10.2003 17:07:54, manu a =E9crit :
>=20
>> So I ran glxinfo see below which told me that Direct Rendering is not =
=20
>> enabled! This is crazy as you can check in the XFree log (file =20
>> attached).
>> Hope someone can tell me more about this, be it to file this directly =
=20
>> as a bug on bugzilla ;-)
>> Thanks
>=20
> Responding to myself : sorry it seems that the problem is because the =20
> r200_dri.so module is linked against libexpat.so.1 which is not on my =20
> system. So I just made a link to the one I had and all is working great=
 =20
> now!
> glxgears gives me ~1535 FPS. Is it OK? (Radeon 9200 with 64MB).
> Thanks for the help, and sorry for eating the bandwidth ;-)

Ah!  Actually, thank you very much. :)  The problem seems to be that=20
with libexpat.so missing, there are unresolved symbols in r200_dri.so.=20
The dlopen of r200_dri.so in OpenDriver (lib/GL/dri/dri_glx.c, line 184)=20
fails.  HOWEVER, it only logs a message if LIBGL_DEBUG is set.  I=20
removed libexpat from my system and was able to recreate the crash.=20
With LIBGL_DEBUG set I get a nice message about not being able to open=20
the driver.

My person opinion is that the error messages in OpenDriver (but not the=20
ones in GetDriverName) should be printed regardless of the setting of=20
LIBGL_DEBUG.  That would have helped find the source of this problem=20
much sooner.  We basically got lucky that Manu figured out that libexpat=20
was missing for himself. :)