On Tue, Oct 22, 2013 at 03:24:18PM +0200, Thomas Richter wrote:
> Am 22.10.2013 14:03, schrieb Chris Wilson:
> >Ah, /var/log/Xorg.0.log has greater verbosity than stdout/stderr. I am
> >just curious where we reject the -intel driver and hence fail to init
> >the screen.
>
> /var/logXorg.0.log is z
Am 22.10.2013 14:03, schrieb Chris Wilson:
Ah, /var/log/Xorg.0.log has greater verbosity than stdout/stderr. I am
just curious where we reject the -intel driver and hence fail to init
the screen.
/var/logXorg.0.log is zero bytes long at this point. I wouldn't call
this "greater". (-;
Let it b
On Tue, Oct 22, 2013 at 12:18:54PM +0200, Thomas Richter wrote:
> Hi Chris, hi Daniel,
> >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 availa
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 als
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
