External display
Subsystems (2)
Hi,
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.
Booting the same system with a drm-intel-next based kernel the internal display is turned on (although the lid is closed), the external display is on and shows a resolution of 1024x768.
Logging into X the internal display stays on, the external display changes resolution to 1920x1200.
I can use gnome-display-properties to turn the internal screen off. But after each DPMS blanking the internal display is turned on again. :(
Is this some expected behaviour or should this be considered a bug?
Thanks in advance.
Regards,
Christoph
Chris Wilson
Acked-by Jesse BarnesQuoted 6 lines · Christoph Lukas
Hi,
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.
Quoted 7 lines
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 <[email protected]> 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.
You may want to try:
(quoted diff) +0 -0
b/drivers/gpu/drm/i915/intel_lvds
index 9795eb5..45b1fe4 100644
drivers/gpu/drm/i915/intel_lvds.c +3 -5
@@ -474,11 +474,9 @@ intel_lvds_detect(struct drm_connector *connector, bool forstruct 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; }
Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre
Quoted 15 lines · Chris Wilson
Quoted 6 lines · Christoph Lukas
Hi,
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.
Quoted 7 lines
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.
Quoted 6 lines
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.
You can always boot with video=LVDS-1:d kernel parameter, that will disable your LVDS connection and run your external monitor in native resolution.
Only thing is, you have to remove that parameter every time you boot your notebook without it being connected to docking station.
Quoted 3 lines · On Friday 14 January 2011 14:57:57 Ivan Bulatovic wrote:
You can always boot with video=LVDS-1:d kernel parameter, that will disable your LVDS connection and run your external monitor in native resolution.
Thanks for the trick. I'll try it as soon as I get home :)
Regards,
Damnshock
Quoted 7 lines · On Friday 14 January 2011 18:58:25 Damnshock wrote:
Quoted 3 lines · On Friday 14 January 2011 14:57:57 Ivan Bulatovic wrote:
You can always boot with video=LVDS-1:d kernel parameter, that will disable your LVDS connection and run your external monitor in native resolution.
Thanks for the trick. I'll try it as soon as I get home
Unfortunately it doesn't work for me: the LVDS is still on and my external monitor works with the internal resolution by default :S
Regards
Quoted 7 lines · Damnshock
Quoted 6 lines · On Friday 14 January 2011 18:58:25 Damnshock wrote:
Quoted 3 lines · On Friday 14 January 2011 14:57:57 Ivan Bulatovic wrote:
You can always boot with video=LVDS-1:d kernel parameter, that will disable your LVDS connection and run your external monitor in native resolution.
Quoted 6 lines
Quoted 1 line
Thanks for the trick. I'll try it as soon as I get home
Unfortunately it doesn't work for me: the LVDS is still on and my external monitor works with the internal resolution by default :S
Regards
What does xrandr -q say when notebook is on docking station ?
Quoted 1 line · On Sunday 16 January 2011 18:14:10 Ivan Bulatovic wrote:
What does xrandr -q say when notebook is on docking station ?
I have no dock, just the lid closed and happen to use an external monitor. Does that matter?
Regards
Quoted 6 lines · Damnshock
Quoted 1 line · On Sunday 16 January 2011 18:14:10 Ivan Bulatovic wrote:
What does xrandr -q say when notebook is on docking station ?
I have no dock, just the lid closed and happen to use an external monitor. Does that matter?
Regards
No, not really :)
Hi
Quoted 3 lines
You can always boot with video=LVDS-1:d kernel parameter, that will disable your LVDS connection and run your external monitor in native resolution.
using video=eDP-1:d disabled the internal display for me. Thanks for the hint.
Quoted 2 lines
Only thing is, you have to remove that parameter every time you boot your notebook without it being connected to docking station.
Yes, and using this kernel parameter you won't be able to undock the running system. :)
Cheers,
Christoph
Hi Chris,
Quoted 47 lines
Quoted 5 lines
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.
Quoted 7 lines
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
6e6c822868f113dabe3c33bdd91e883cc28fa11bAuthor: Eric Anholt <[email protected]> Date: Wed Mar 17 13:48:06 2010 -0700drm/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 <[email protected]>Acked-by Jesse Barnes <[email protected]>You may want to try:
drivers/gpu/drm/i915/intel_lvds.c +0
-1@@ -474,11 +474,9 @@ intel_lvds_detect(struct drm_connector *connector, bool forstruct drm_device *dev = connector->dev;enum drm_connector_status status = connector_status_connected; -/* ACPI lid methods were generally unreliable in this generation, so
drivers/gpu/drm/i915/intel_lvds.c intel_lvds_detect(struct drm_connector *connector, bool for · line 482
Quoted 10 lines
drivers/gpu/drm/i915/intel_lvds.c +3
-4-* 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