All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chun-Yu Shei <cshei@cs.indiana.edu>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Problems w/Sandy Bridge & 27" monitor
Date: Thu, 16 Aug 2012 00:47:58 +0200	[thread overview]
Message-ID: <20120815224757.GG5533@phenom.ffwll.local> (raw)
In-Reply-To: <502C24D2.7070506@cs.indiana.edu>

On Wed, Aug 15, 2012 at 06:38:10PM -0400, Chun-Yu Shei wrote:
> Hi,
> 
> I recently upgraded to a 27" monitor (2560x1440) from a 23" one
> (1920x1080), and had to switch to Windows because the new monitor is
> unusable in Linux.  Today, about a month later, I decided to give
> Linux another try, since there have been several updates to the
> Intel graphics driver since then.
> 
> Unfortunately, it seems that it's still unusable with
> xf86-video-intel 2.20.3 -- after a little while, the video signal to
> the 27" monitor completely stops, and it goes into power saving
> mode.  I'm running dual monitors with the old 23", and that one
> continues running fine when this happens.  This happens on my
> ThinkPad X220 (i5-2540M).  The 27" is connected via DisplayPort, and
> the 23" via DVI.  SNA is enabled, if it makes any difference (I
> haven't tried turning it off, but I probably should).  This is the
> biggest problem I'm facing when it comes to Linux support.
> 
> I also gave the new "TearFree" option a try, and while it does a
> great job of eliminating tearing, it makes the two monitors become
> mirrors of each other for some reason.  If I take a screenshot with
> the GNOME tool, the screenshot comes out as expected (unmirrored),
> but the video output on the two monitors is mirrored in reality.
> Disabling "TearFree" fixes this.
> 
> Also, when I'm using the ThinkPad's built-in display, it sometimes
> turns off for no apparent reason, although it's not too big of a
> deal since a suspend/resume cycle seems to fix things (and I haven't
> used 2.20.3 long enough to experience this yet).
> 
> Any ideas/things I can do to help track these issues down?

For the screen blanking issues, the kernel is the important part. Please
boot with drm.debug=0xe added to your kernel bootline and grab the full
dmesg.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-08-15 22:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 22:38 Problems w/Sandy Bridge & 27" monitor Chun-Yu Shei
2012-08-15 22:47 ` Daniel Vetter [this message]
2012-08-27 18:47   ` Chun-Yu Shei
2012-08-27 19:08     ` Daniel Vetter
2012-08-27 19:30       ` Chun-Yu Shei
2012-08-27 19:32         ` Daniel Vetter
2012-08-27 19:50           ` Chun-Yu Shei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120815224757.GG5533@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=cshei@cs.indiana.edu \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.