From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Lukas Subject: Re: External display Date: Sun, 16 Jan 2011 09:13:44 +0100 Message-ID: <1295165624.2596.3.camel@hoss.staad.pingworks.net> References: <1295008688.2327.43.camel@hoss.staad.pingworks.net> <849307$b585ru@azsmga001.ch.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by gabe.freedesktop.org (Postfix) with SMTP id 57FB89E79C for ; Sun, 16 Jan 2011 00:13:59 -0800 (PST) In-Reply-To: <849307$b585ru@azsmga001.ch.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Chris Wilson Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org Hi Chris, > > > > I am using a Dell E6410 notebook running Ubuntu. Most of the time I am > > running this notebook in a docking station with closed lid and with an > > external (DVI) monitor attached to the dock. > > > > Running different kernels I see different behaviour regarding the > > display configuration after boot. > > > > Booting a 2.6.32 based kernel the internal display is turned off, the > > external display is turned on and running at it's native resolution of > > 1920x1200. > > This is what I would expect. > > Once upon a time we trusted the lid status and reported the internal > screen as disconnected when the lid was closed. We were beset by bugs > reporting broken lid status and the LVDS not working. So we gave up. > Usually between the BIOS and userspace responding to lid notification > events, the LVDS is turned off when the lid is closed. > > See commit 6e6c822868f113dabe3c33bdd91e883cc28fa11b > Author: Eric Anholt > Date: Wed Mar 17 13:48:06 2010 -0700 > > drm/i915: Stop trying to use ACPI lid status to determine LVDS connection. > > I've been getting more and more quirk reports about this. It seems > clear at this point that other OSes are not using this for determining > whether the integrated panel should be turned on, and it is not > reliable for doing so. Better to light up an unintended panel than to > not light up the only usable output on the system. > > Signed-off-by: Eric Anholt > Acked-by: Jesse Barnes > > You may want to try: > > diff --git a/drivers/gpu/drm/i915/intel_lvds.c > b/drivers/gpu/drm/i915/intel_lvds > index 9795eb5..45b1fe4 100644 > --- a/drivers/gpu/drm/i915/intel_lvds.c > +++ b/drivers/gpu/drm/i915/intel_lvds.c > @@ -474,11 +474,9 @@ intel_lvds_detect(struct drm_connector *connector, bool for > struct drm_device *dev = connector->dev; > enum drm_connector_status status = connector_status_connected; > > - /* ACPI lid methods were generally unreliable in this generation, so > - * don't even bother. > - */ > - if (IS_GEN2(dev) || IS_GEN3(dev)) > - return connector_status_connected; > + /* ACPI lid methods were generally unreliable, so don't even bother. */ > + if (INTEL_INFO(dev)->gen >= 5 && !acpi_lid_open()) > + status = connector_status_disconnected; > > return status; > } > thanks for your response and patch. But this patch did not change anything for me, sorry. The internal display is still turned on when booting with closed lid. I would guess this function is only called for lvds displays while the internal display on the Dell E6410 is an eDP? I have added a printk just before the conditional and I have never seen the output in dmesg. I would not bother too much about using gnome-display-properties (or xrandr) to turn the internal display off once after login. What I think is a little bit annouying is that the internal display is turned back on after each DPMS blanking. Thanks and Regards, Christoph