Performance regression with last R300 Gallium3D update ?

[nanonyme]

I usually prefer LIBGL_DEBUG=verbose glxinfo >/dev/null
which works because the output you're interested in is in stderr.
Note that direct rendering has nothing to do with hardware rendering. Ignore it.

[mcslave]

I tried LIBGL_DEBUG=verbose glxinfo >/dev/null
libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/laurent/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/laurent/.drirc: No such file or directory.

and you're right, I don't have /etc/drirc or /home/laurent/.drirc

But today, after a new update of mesa and kernel, the problem has just disappeared.

a new problem has just occured but it's a new story and a new post!

thanks for your help.

[whizse]

I just wanted to point out that none of the messages about drirc are fatal, and can be ignored.