On Mon, Oct 21, 2013 at 10:12:07AM +0200, Thomas Richter wrote: > Daniel, others, > > last Friday, I tried drm-intel-nightly on an IBM R31 Thinkpad. This > also comes with a 835GM chipset (same as the Fujitsu), but the > display is connected via LVDS and not via the NS2501 DVO. > > *) Panning also causes the flicker we know already. Interestingly, > kernel 3.2.0-4 *does not* cause this flicker, it only flickers on > the external > screen, but not internally. > > Is there any way to read the i915 registers from the working 3.2.0-4 > panning and compare that to what the drm-nightly kernel installs? > Something must be different. > > *) If I connect an external monitor *before* turning the machine on, > X creates a segfault. On this machine, no Xorg.conf exists and it is > up to X to > configure the screens correctly: A full drm.debug=6 dmesg, Xorg.0.log and xrandr --verbose would be useful starting point to distangling what is going on. Is this an 830gm or an 845g? google says 830gm, so there should be 2 crtcs available for you to drive the two outputs independently, and we need to find out what is going wrong. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
