According to /var/log/XFree86.0.log, DRI is enabled and functioning, but according to glxinfo it's using the Mesa indirect renderer, and 3D is not accelerated. This is using a G400.
I'm not surprised by this at all. mga isn't functioning on this card at all for me period let alone snazzy DRI. ;o) Added to the mga todo list.
Can you attach your server log and config Bill? I want to try and corelate some things..
Not my machine. Trond will have to attach a log file.
This defect is considered MUST-FIX for Florence Gold release
Created attachment 9485 [details] dmesg output
Created attachment 9486 [details] dmesg output
Created attachment 9487 [details] the XFree log
Created attachment 9488 [details] X configuration file
[teg@halden teg]$ rpm -q XFree86 XFree86-4.0.2-7 [teg@halden teg]$ uname -a Linux halden.devel.redhat.com 2.4.0-0.99.24smp #1 SMP Wed Feb 7 18:18:32 EST 2001 i686 unknown [teg@halden teg]$ Dual PIII, Intel 840 Motherboard.
This is probably a permissions bug... when you're root, it works as before: Hard X crash.
Created attachment 9489 [details] Dmesg file when X crashed
Michael, the dmesg output indicates something weird in the drm driver...
No problems here with a G200 and a G400, XF86 4.0.2-7, kernel 2.4.1-ac6 with a couple of patches from the RPM
You need to have Section "DRI" Mode 0666 Endsection in the XF86Config-4 for DRI to be accessible by non-root users, btw, regardless of whether the functionality actually works or not.
the original cause of the bug (bad DRI permissions) is fixed now. mga DRI is as schizophrenic as always.