On Mon, Sep 25, 2000 at 09:24:26PM -0500, Branden Robinson wrote: > >> First, I looked at the logged output from X. There was a conflict >> between drm 1.0 and 2.0 or something like that, and the next statement >> was "dri disabled". Shucks. > [...] >> Any ideas?
In the snipped-out part of the quote, I indicated that I managed to get rid of the drm conflict message and the "dri disabled" message by switching to the Matrox-supplied binary-only driver. > Well, XFree86 CVS just resynced with the DRI at sourceforge, the Mesa > version is now 3.4, etc. etc. Maybe try a bleeding edge kernel? I have been using 2.4.0-test8 since it was released. I suppose that I could try a test9-preX, but has there really been much movement there with respect to the DRI for the mga? Thank you for your response. -- Thomas E. Vaughan <[EMAIL PROTECTED]> CIMMS/NSSL, Norman, OK, USA
