On Sat, 18 Dec 2010 18:32:49 -0500, Stephen Clark<sclark46@xxxxxxxxxxxxx> wrote:Hi Chris,
I had been using mesa-7.9.You need to "mount -tdebugfs debug /sys/kernel/debug".
I loaded mesa-7.10 similar results. There is no
/sys/kernel/debug/dri/0/i915_error_state
In fact there is nothing in the /sys/kernel/debug directory. Do I have
to enable
something.
With the later kernel - things are worse X becomes totally useless it looks2.6.25 to present marks the transition between UMS and KMS, i.e. moving
like my lcd panel lost horizontal sync. With the 2.6.25 kernel X is
still usable
this makes me think at least some of the problem is kernel related.
of the userspace modesetting code into the kernel. And that should not
have regressed. Can you please, grab an intel_reg_dumper of the working
setup and the lost-sync setup, and include a drm.debug=0xe dmesg (i.e. add
drm.debug=0xe to your boot commandline)?
With 2.6.37-rc6 and mesa 7.10 with hardware acceleration turned off in wine-Good, those drivers are recent enough that I should be able to use the
Dec 18 18:01:50 joker4 yum[5244]: Updated: mesa-libGL-7.10-0.17.fc15.x86_64
Dec 18 18:01:52 joker4 yum[5244]: Updated: mesa-libGL-7.10-0.17.fc15.i686
Dec 18 18:01:54 joker4 yum[5244]: Updated: mesa-libGLU-7.10-0.17.fc15.x86_64
Dec 18 18:02:02 joker4 yum[5244]: Updated: mesa-dri-drivers-7.10-0.17.fc15.x86_6
4
Dec 18 18:02:03 joker4 yum[5244]: Updated: mesa-libGLU-7.10-0.17.fc15.i686
Dec 18 18:02:11 joker4 yum[5244]: Updated: mesa-dri-drivers-7.10-0.17.fc15.i686
error state to find the broken code.
-Chris