Red Hat Bugzilla – Bug 29026
Matrox DRI is disabled?
Last modified: 2005-10-31 17:00:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.18 i686)
Seems according to the SRPM of XFree86 4.0.2-9 in the wolverine beta, that
Matrox DRI has been disabled
Steps to Reproduce:
1.Grab the SRPM
Actual Results: No DRI for Matrox
According to the changelog of the SRPM in the wolverine beta, the Matrox
DRI is disabled "because it's broken".
Well, it IS broken on post version of the official XFree 4.0.2 version, and
the DRI team are working on it to fix it and the fix will only appear on
Could someone PLEASE put the DRI from the official XFree 4.0.2 back please?
otherwise, Redhat 7.1 will be totally unusable for Matrox users who wants
to use 3D on their X windows (and Matrox got big part of the Linux
developers and users)
It's enabled in more recent builds (0.9.2); it won't be configured
by default, though.
Umm.. what do you mean for those things:
1. build 0.9.2??? what version is that? the build of Redhat 7.1 beta's? the
number is not cleared to me..
2. By meaning of "it won't be configured by the default" - do you mean with
3. Where can I get this "build 0.9.2" (which I totally don't understand what
Please relax guys. Matrox DRI was disabled because it was totally broken,
and I'd rather ship NO DRI driver than ship one that is broken and receive
500 bug reports all duplicates. In the mean time, I have decided to disable
DRI via Xconfigurator so that those that want to turn it on just to see that
yes, it is broken, will have the luxury of doing so. ;o)
XFree86 4.0.3 is not out yet, and does *NOT* currently have a fix for this
bug in it. Our 4.0.2 package contains all of the current code in what will
become 4.0.3. If 4.0.3 is out soon, I will update the RPM to it before next
release, if not then I'll be shipping 4.0.2 + everything currently going into
4.0.3 - which currently doesn't include working DRI on Matrox.
Also, there is no XFree86-4.0.2-0.9.2, rather it is -9.1.25, and is a test
version. Bill made a typo. I am working with Matrox to try and resolve these
issues ASAP, but there is no working driver currently. Nonetheless, your
request is honored in my latest build. Hopefully we can squash this nasty
soon though so DRI is working on these cards.