From: Keith Packard <keithp@keithp.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] i915 KMS dual head broken on DELL latitude E6420 in 3.1-rc*
Date: Thu, 15 Sep 2011 00:43:36 -0500 [thread overview]
Message-ID: <yunobym743b.fsf@aiko.keithp.com> (raw)
In-Reply-To: <20110914232717.GA5410@type.famille.thibault.fr>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Thu, 15 Sep 2011 01:27:17 +0200, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
Non-text part: multipart/mixed
> Hello,
>
> I'm trying to upgrade from 3.0 to 3.1-rcsomething on a DELL latitude
> E6420, but dual head is broken. Here is the scenario:
>
> - Turn computer on with VGA1 connected. Both LVDS1 and VGA1 show the
> text console fine.
> - Start X. VGA1 shows X fine, but LVDS1 (1600x900 resolution) shows an
> odd screen: completely black on the left part (about 1060x900), sort
> of gray on the right part (about 540x900). Playing with xrandr doesn't
> help, I can at best make it completely black with --off, and not get
> it back again with --auto or anything else.
Can you try disabling frame buffer compression?
i915.i915_enable-fbc=0
I'm about to send a patch to disable this by default; I've gotten two
people saying that this helps them already.
--
keith.packard@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2011-09-15 5:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 23:27 [REGRESSION] i915 KMS dual head broken on DELL latitude E6420 in 3.1-rc* Samuel Thibault
2011-09-15 5:43 ` Keith Packard [this message]
2011-09-15 7:41 ` Samuel Thibault
2011-09-15 8:12 ` Samuel Thibault
2011-09-15 14:22 ` Keith Packard
2011-09-16 16:30 ` Samuel Thibault
2011-09-16 18:10 ` Samuel Thibault
2012-01-05 2:16 ` Samuel Thibault
2012-01-05 9:53 ` Samuel Thibault
2013-01-22 9:47 ` [REGRESSION FIXED] " Samuel Thibault
2013-01-22 13:04 ` Daniel Vetter
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=yunobym743b.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.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.