Red Hat Bugzilla – Bug 51708
matrox dri fails with kernel errata
Last modified: 2007-04-18 12:35:50 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.2.19-7.0.8 i586; Nav)
Description of problem:
After upgrading to the 2.2.19 errata (this includes 6.2.1, 6.2.7, and
7.0.8) the mga module will no longer enable dri when starting X on a G400.
It fails in MGADRIScreenInit:
(EE) MGA(0): [drm] MGADRIScreenInit failed (DRM version = 2.0.0, expected
1.0.x). Disabling DRI.
Steps to Reproduce:
1. Install a base 7.0 system
2. Apply the kernel errata to bring the kernel up to 2.2.19
Actual Results: The X server starts, but does not enable dri as it did
before. If you revert back to a 2.2.16 or 2.2.17 kernel, it does.
Expected Results: DRI should be enabled, since this worked "out of the
I was getting SEGVs until I added the following lines to XF86Config-4 in
the "Modules" section, now I get the "Disabling DRI" message.
Created attachment 27673 [details]
X log file
Created attachment 27674 [details]
x config file
Well, XFree86 in 7.0 has not changed, so...
I've Cc'd Arjan for comment. If this is a real bug, it
must be a kernel DRM bug... Arjan?
6.2.1 and 7.0.1 have the exact same DRM as 2.2.16 (a patch was added to make
sure of this).
Created attachment 28614 [details]
startx output from 2.2.17-14 showing dri module loading
If the after the kernel upgrade DRI failed, then IMHO, the kernel
must have changed in some way to cause this. I've got a G400
running rigth now with our current 7.2 XFree86 and kernel, and DRI
is working so I'm closing this bug as fixed in current release.