Screen blanks on lid close, never comes back

[Colin Law]

On 17 January 2011 21:32, Nicolas Calderon
<nicolas.calderon.asselin at gmail.com> wrote:

Please don't top post, it makes it difficult to folllow the thread,
insert your reply at appropriate points in previous message.  Thanks.

> The issue is not with suspending but with screen blanking.
> Power Manager (AC and Battery) do not offer the option to do nothing on lid
> close ("When lid is closed"), but I tried it by setting it in gconf.
> As far as suspend goes, I was simply saying that I observe the same issue if
> I close and reopen the lid quickly. If I let the laptop suspend and resume,
> the screen comes back correctly. But I don't want my laptop to suspend when
> the lid is closed.

In that case I am confused.  Is the screen blanking by itself or is it
the screensaver or what?  Please try and explain simply (so I can
understand) what you do and what happens.

I think there might be heating issues if you were allowed to do
nothing on lid closure.

Colin

> --
> Nicolas Calderon
>
>
>
> On Mon, Jan 17, 2011 at 3:24 AM, Colin Law <clanlaw at googlemail.com> wrote:
>>
>> On 17 January 2011 00:10, Nicolas Calderon
>> <nicolas.calderon.asselin at gmail.com> wrote:
>> > I have installed Ubuntu 10.10 on my ThinkPad R51 laptop, but have been
>> > having issues where the screen goes blank when I close the lid but never
>> > comes back. The computer is not crashed though, as I can still ssh in.
>> > I tried 3 settings in power management: do nothing, blank screen and
>> > suspend.
>>
>> Where in Power Management are you setting this?  The options I have on
>> the Mains and Battery tabs for "When laptop lid is closed" are
>> Suspend, Hibernate and Shutdown.
>>
>> Assuming that you want it to suspend, if you select Suspend from the
>> shutdown menu directly, without closing the lid, does that work ok?
>> If not then the issue is to do with suspend rather than the lid
>> operation.
>>
>> Colin
>>
>> > To set power manager to do nothing, I had to set through gconf, so I'm
>> > not
>> > sure that option is valid.
>> > Blank screen is a given option in power manager, and results in the
>> > described issue time after time.
>> > Suspend can also lead to the issue if the lid is reopened too quickly
>> > (the
>> > laptop doesn't have the time to go to sleep).
>> >
>> > I am left with the impression that this is a software issue (debian did
>> > not
>> > do that and I had it just before installing Ubuntu, but debian could not
>> > suspend) that leaves the video card state broken. I tried following
>> > instruction on to force pipe a quirck
>> > (https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen#Problem: Lockup
>> > When
>> > Closing Lid with Intel Graphics) because I have an intel graphics card,
>> > but
>> > xorg tells me this option is not used (WW in xorg.conf). I attached the
>> > output to a few files or command outputs:
>> > lspci -vvnn | grep "VGA Compat":
>> > 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM
>> > Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA
>> > controller])
>> >         Subsystem: IBM Device [1014:0557]
>> >         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>> > ParErr-
>> > Stepping- SERR- FastB2B- DisINTx-
>> >         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
>> > <TAbort- <MAbort- >SERR- <PERR- INTx+
>> >         Latency: 0
>> >         Interrupt: pin A routed to IRQ 11
>> >         Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
>> >         Region 1: Memory at d0000000 (32-bit, non-prefetchable)
>> > [size=512K]
>> >         Region 2: I/O ports at 1800 [size=8]
>> >         Expansion ROM at <unassigned> [disabled]
>> >         Capabilities: [d0] Power Management version 1
>> >                 Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA
>> > PME(D0-,D1-,D2-,D3hot-,D3cold-)
>> >                 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>> >         Kernel driver in use: i915
>> >         Kernel modules: i915
>> > /var/log/Xorg.0.log.old
>> > http://pastebin.com/55uX0D1r
>> > Notable errors:
>> > [    24.110] (EE) VESA: Kernel modesetting driver in use, refusing to
>> > load
>> > [    24.110] (WW) Falling back to old probe method for vesa
>> > and a few hundreds of:
>> > [    24.456] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
>> >
>> > intel_reg_dumper (good and bad state)
>> > attached, and here is the diff:
>> > 110c110
>> > <             VGACNTRL: 0x22040000 (enabled)
>> > ---
>> >>             VGACNTRL: 0x80000000 (disabled)
>> > It might be worth noting that whenever I close the lid and reopen it (or
>> > just press the lid button), the screen comes visible for a fraction of
>> > second, but long enough for me to see that whatever needs to be shown
>> > gets
>> > updated (If I kill my gnome session through ssh, I can see gdm logging
>> > in
>> > that fraction of seconds). Also, it's not just an issue with the
>> > backlight
>> > as it does come back on on lid open, and stays on.
>> > Someone on #ubuntu (Freenode) suggested it might have to do with ACPI. I
>> > tried moving /etc/acpi/lid.sh to /etc/acpi/lid.sh.bak, but it didn't
>> > seem to
>> > make a diffrence. I don't know enough about ACPI to rule it out though.
>> > Thanks in advance,
>> > --
>> > Nicolas Calderon
>> >
>> >
>> >
>> > --
>> > ubuntu-users mailing list
>> > ubuntu-users at lists.ubuntu.com
>> > Modify settings or unsubscribe at:
>> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>> >
>> >
>>
>> --
>> ubuntu-users mailing list
>> ubuntu-users at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
>