Bug 20973 - Laptop screen remains on with external monitor and lid closed
Summary: Laptop screen remains on with external monitor and lid closed
Status: RESOLVED DUPLICATE of bug 11455
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Gordon Jin
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-31 08:32 UTC by David
Modified: 2009-03-31 23:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description David 2009-03-31 08:32:08 UTC
Binary package hint: xserver-xorg-video-intel

Hi,

I'm running an up-to-date version of Gutsy on Dell Latitude D500 laptop, which has an intel graphics card.

With the intel driver (version 2:2.1.1-0ubuntu3), installed by default, the laptop's LCD panel remains on when the laptop is used with an external monitor connected and the lid closed, using a docking station. This is obviously wasting power and making it quite warm!

The laptop panel is off when GRUB loads, but is switched on when X starts and the login screen appears. Using the key combinations to cycle CRT/LCD display has no effect.

As a workaround, i have installed 'i810switch' and run the command 'i810switch lcd off' after login.

This problem does NOT occur using Kubuntu Feisty, with the i810 driver - with this the laptop lcd remains off if booted with lid closed and external monitor attached.

Relevant sections from 'lspci':
***************************
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) (prog-if 00 [VGA])
        Subsystem: Dell Unknown device 0152
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
        Region 1: Memory at faf80000 (32-bit, non-prefetchable) [size=512K]
        Region 2: I/O ports at c000 [size=8]
        Capabilities: [d0] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
        Subsystem: Dell Unknown device 0152
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M]
        Region 1: Memory at faf00000 (32-bit, non-prefetchable) [size=512K]
        Capabilities: [d0] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

From xorg.conf:
**************
Section "Device"
        Identifier "Intel Corporation 82852/855GM Integrated Graphics Device"
        Driver "intel"
        BusID "PCI:0:2:0"
EndSection

Section "Monitor"
        Identifier "Generic Monitor"
        Option "DPMS"
EndSection

Section "Screen"
        Identifier "Default Screen"
        Device "Intel Corporation 82852/855GM Integrated Graphics Device"
        Monitor "Generic Monitor"
        DefaultDepth 24
        SubSection "Display"
                Modes "1024x768"
        EndSubSection
EndSection
Comment 1 Gordon Jin 2009-03-31 23:52:48 UTC
We don't have a reliable way to detect lid status in current driver.

For now you could use the workaround of setting Ignore for LVDS in xorg.conf, see http://bugs.freedesktop.org/show_bug.cgi?id=11455#c7.

*** This bug has been marked as a duplicate of bug 11455 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.