[solved] Suspend on closed lid

Hi,
I want my netbook (Wind) to automagically suspend when I close the lid, I got laptop-mode and pm-utils installed, everything works great, but I can't get it to suspend instead of just turning off the screen.
The ACPI event "lm_lid..sh" just calls "laptop_mode auto", I tried to overwrite it with "/usr/sbin/pm-suspend" but to no effect. I also couldn't find anything in the laptop-mode config where I could set something like that.
Last edited by madhatter (2008-11-28 15:09:45)

argh nevermind I'm an idiot.
I didn't realize that I haven't got acpid installed
Last edited by madhatter (2008-11-28 15:09:16)

Similar Messages

[SOLVED]Gnome 3.4 is not suspending when the lid is closed.

Hey..
Since upgrading to gnome 3.4.1, my laptop does not suspend when the lid is closed.
I have read this this thread without getting a clear answer...
I have checked the setting in gnome tweak tool, and they are both set to "Suspend"
The laptop has no problem suspending, if i run the command, or choose the option in the menu to the right.
Is this a bug ?
What can i do to fix it. ?
Last edited by Munken (2012-06-20 05:54:08)

See this thread for updates on the problem.

System always auto-suspends when the lid is closed

Hello,
I am trying to prevent my laptop (a System76 Lemur Ultra 3) from suspending when the lid is closed. No matter what I change in the configuration, the laptop always suspends when the lid is closed. The output of journalctl is as follows after this happens:
Feb 21 04:35:32 hostname systemd-logind[196]: Lid closed.
Feb 21 04:35:32 hostname systemd-logind[196]: Suspending...
Feb 21 04:35:32 hostname systemd[1]: Starting Sleep.
Feb 21 04:35:32 hostname systemd[1]: Reached target Sleep.
Feb 21 04:35:32 hostname systemd[1]: Starting Suspend...
Feb 21 04:35:33 hostname systemd-sleep[2001]: Suspending system...
Feb 21 04:35:33 hostname kernel: PM: Syncing filesystems ... done.
Feb 21 04:35:33 hostname kernel: PM: Preparing system for mem sleep
Feb 21 04:35:43 hostname kernel: Freezing user space processes ... (elapsed 0.06 seconds) done.
Feb 21 04:35:43 hostname kernel: Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Feb 21 04:35:43 hostname systemd[1]: Time has been changed
Feb 21 04:35:43 hostname systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
Feb 21 04:35:43 hostname systemd-logind[196]: Lid opened.
Feb 21 04:35:43 hostname acpid[190]: client 1812[0:100] has disconnected
Feb 21 04:35:43 hostname kernel: PM: Entering mem sleep
Feb 21 04:35:43 hostname kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 21 04:35:43 hostname kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 21 04:35:43 hostname kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 21 04:35:43 hostname kernel: PM: suspend of devices complete after 1092.547 msecs
Feb 21 04:35:43 hostname kernel: PM: late suspend of devices complete after 0.556 msecs
Feb 21 04:35:43 hostname kernel: jme 0000:03:00.0: wake-up capability enabled by ACPI
Feb 21 04:35:43 hostname kernel: ehci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
Feb 21 04:35:43 hostname kernel: ehci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
Feb 21 04:35:43 hostname kernel: PM: noirq suspend of devices complete after 66.095 msecs
Feb 21 04:35:43 hostname kernel: ACPI: Preparing to enter system sleep state S3
Feb 21 04:35:43 hostname kernel: PM: Saving platform NVS memory
Feb 21 04:35:43 hostname kernel: Disabling non-boot CPUs ...
Feb 21 04:35:43 hostname kernel: smpboot: CPU 1 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 2 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 3 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 4 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 5 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 6 is now offline
Feb 21 04:35:43 hostname kernel: smpboot: CPU 7 is now offline
Feb 21 04:35:43 hostname kernel: Extended CMOS year: 2000
Feb 21 04:35:43 hostname kernel: ACPI: Low-level resume complete
Feb 21 04:35:43 hostname kernel: PM: Restoring platform NVS memory
Feb 21 04:35:43 hostname kernel: Extended CMOS year: 2000
Feb 21 04:35:43 hostname kernel: Enabling non-boot CPUs ...
Feb 21 04:35:43 hostname systemd-sleep[2001]: System resumed.
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Feb 21 04:35:43 hostname kernel: CPU1 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Feb 21 04:35:43 hostname kernel: CPU2 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Feb 21 04:35:43 hostname kernel: CPU3 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
Feb 21 04:35:43 hostname kernel: CPU4 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
Feb 21 04:35:43 hostname kernel: CPU5 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
Feb 21 04:35:43 hostname kernel: CPU6 is up
Feb 21 04:35:43 hostname kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Feb 21 04:35:43 hostname kernel: CPU7 is up
Feb 21 04:35:43 hostname kernel: ACPI: Waking up from system sleep state S3
Feb 21 04:35:43 hostname kernel: ehci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
Feb 21 04:35:43 hostname kernel: ehci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
Feb 21 04:35:43 hostname kernel: PM: noirq resume of devices complete after 133.251 msecs
Feb 21 04:35:43 hostname kernel: PM: early resume of devices complete after 0.425 msecs
The first thing I did was to disable systemd's acpi features by setting /etc/systemd/logind.conf as follows:
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See logind.conf(5) for details
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
IdleAction=suspend
IdleActionSec=45min
However, the behavior was the same as before. I also tried setting
LidSwitchIgnoreInhibited=no
but after reading man 5 logind.conf it seems that this is unnecessary (and it had no effect when I tried it).
acpid is also installed but I have commented out the contents of /etc/acpi/handler.sh as well as all the scripts in /etc/acpi/actions. I noticed that there is also a UPower daemon which was installed as a dependency and thought that it might be triggering the suspend. I tried setting
IgnoreLid=true
in /etc/UPower/UPower.conf but this also had no effect.
systemctl list-units has the following output:
UNIT LOAD ACTIVE SUB DESCRIPTION
proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
sys-devices-pci0000:00-0000:00:1b.0-sound-card0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1b.0/sound/card0
sys-devices-pci0000:00-0000:00:1c.2-0000:02:00.0-net-wlan0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0/net/wlan0
sys-devices-pci0000:00-0000:00:1c.3-0000:03:00.0-net-eth0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/net/eth0
sys-devices-pci0000:00-0000:00:1d.0-usb2-2\x2d1-2\x2d1.2-2\x2d1.2.1-2\x2d1.2.1.1-2\x2d1.2.1.1.1-2\x2d1.2.1.1.1:1.2-sound-card1.device loaded active plugged 0819
sys-devices-pci0000:00-0000:00:1d.0-usb2-2\x2d1-2\x2d1.2-2\x2d1.2.1-2\x2d1.2.1.3.device loaded active plugged Deskjet_5400_series
sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device loaded active plugged ST9500420AS
sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda2.device loaded active plugged ST9500420AS
sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda.device loaded active plugged ST9500420AS
sys-devices-pci0000:00-0000:00:1f.2-ata3-host2-target2:0:0-2:0:0:0-block-sr0.device loaded active plugged TSSTcorp_CDDVDW_SN-208AB
sys-devices-platform-serial8250-tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
sys-devices-platform-serial8250-tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devices-platform-serial8250-tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devices-platform-serial8250-tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
sys-module-configfs.device loaded active plugged /sys/module/configfs
sys-subsystem-net-devices-eth0.device loaded active plugged /sys/subsystem/net/devices/eth0
sys-subsystem-net-devices-wlan0.device loaded active plugged /sys/subsystem/net/devices/wlan0
-.mount loaded active mounted /
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
media-usbhd\x2dsda1.mount loaded active mounted /media/usbhd-sda1
sys-kernel-config.mount loaded active mounted Configuration File System
sys-kernel-debug.mount loaded active mounted Debug File System
tmp.mount loaded active mounted Temporary Directory
cups.path loaded active waiting CUPS Printer Service Spool
systemd-ask-password-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
systemd-ask-password-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
acpid.service loaded active running ACPI event daemon
atd.service loaded active running ATD daemon
cronie.service loaded active running Periodic Command Scheduler
cups.service loaded active running CUPS Printing Service
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running Getty on tty1
laptop-mode.service loaded active exited Laptop Mode Tools
polkit.service loaded active running Authorization Manager
postfix.service loaded active running Postfix Mail Transport Agent
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
upower.service loaded active running Daemon for power management
wicd.service loaded active running Wicd a wireless and wired network manager for Linux
acpid.socket loaded active listening ACPID Listen Socket
cups.socket loaded active running CUPS Printing Service Sockets
dbus.socket loaded active running D-Bus System Message Bus Socket
dmeventd.socket loaded active listening Device-mapper event daemon FIFOs
lvmetad.socket loaded active listening LVM2 metadata daemon socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
systemd-journald.socket loaded active running Journal Socket
systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
systemd-udevd-control.socket loaded active listening udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
printer.target loaded active active Printer
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
suspend.target loaded active active Suspend
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
74 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Any ideas on what might be causing the system to suspend when the lid is closed would be appreciated.
Thanks
Last edited by Superposition (2013-02-21 15:48:06)

qinohe wrote:You don't have to disable acpi!
Since you made the complete switch to systemd, why not let systemd handle this kind of events?
I was referring to the suggestion of setting acpi=off on the kernel line. systemd can only run a few preset actions on events like lid close (e.g. suspend, poweroff, ignore, etc.). I need to run custom scripts. Also, for some reason I still do not fully understand, it was not working properly. The log in my original post seems to show that it was initiating the suspend.
qinohe wrote:
progandy wrote:Yes, it is easier, but my laptop should react differently depending on the power source. With AC power lid-switch locks the screen, in battery mode it suspends. That is impossible with systemd.
Yes you need something like laptop-mode-tools for that, I know systemd will not do that, for now.
But that is not the issue here!, the issue here is that the llid-switch-button' shouldn't be used at all.
For as far as possible I would still recommend systemd to handle your events!, but it's your decision finally!
You need acpid for that not laptop-mode-tools. This is exactly what apcid is for --- running user scripts on ACPI events.
Anyway, I finally have this fixed though I still have no idea what the problem was. I ran out of ideas on how to fix it and #archlinux didn't know either so I went the painful but sure route. I did full reinstall and reinstalled all programs. logind was still behaving as this point (not ignoring it's logind.conf file as it seemed to be before the reinstall) after this so I concluded that the packages installed were not the problem at least with their default configs. After that, I gradually restored the config files I cared about while testing to see if logind still worked correctly. Contrary, to what I expected it never broke and I was able to restore all modified configs and get correct behavior.
I suspect there was some old out of date config file somewhere that was causing the problem but it's hard to say which one it was. I could probably figure it out with a bit more experimentation but have already spent enough time fixing this...
In case anyone else needs a similar configuration, the relevant files are as follows. This sets up the system to lock whenever systemd executes a suspend action. It also sets up acpid to suspend on lid close.
Make sure you have installed acpid and enabled it to run at startup.
/etc/systemd/logind.conf
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See logind.conf(5) for details
[Login]
/etc/systemd/logind.conf
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min
/etc/acpi/handler.sh
#!/bin/bash
# Default acpi script that takes an entry for all actions
case "$1" in
button/power)
case "$2" in
PBTN|PWRF)
logger 'PowerButton pressed'
/usr/bin/systemctl poweroff
logger "ACPI action undefined: $2"
esac
button/sleep)
case "$2" in
SLPB|SBTN)
logger 'SleepButton pressed'
/usr/bin/systemctl suspend
logger "ACPI action undefined: $2"
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
logger 'AC unpluged'
/usr/sbin/laptop_mode auto
00000001)
logger 'AC pluged'
/usr/sbin/laptop_mode auto
esac
logger "ACPI action undefined: $2"
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000)
logger 'Battery online'
/usr/sbin/laptop_mode auto
00000001)
logger 'Battery offline'
/usr/sbin/laptop_mode auto
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
logger 'LID closed'
/usr/sbin/laptop_mode auto
if [ $(cat /sys/class/power_supply/ADP0/online) -eq 0 ]; then
/usr/bin/systemctl suspend
fi
open)
logger 'LID opened'
/usr/sbin/laptop_mode auto
logger "ACPI action undefined: $3"
esac
logger "ACPI group/action undefined: $1 / $2"
esac
# vim:set ts=4 sw=4 ft=sh et:
Last edited by Superposition (2013-02-23 23:15:54)

Difference between running pm-suspend and closing the lid.

Hi!
Today i noticed this strange thing: i'm using xfce4.10 and pm-utils to suspend.
This morning i noticed that running a "pm-suspend" from my terminal, won't switch off my wireless card, while suspending with xfce buttons or closing the lid, would do it.
Why? What is the difference between these two actions (running pm-suspend and closing the lid)? As far as i know, the only difference is that there is no call to upower running pm-suspend from terminal.
ps: sorry for the subject, that is not describing the question the best!
Last edited by nierro (2012-06-17 11:03:55)

Uhm yes, i know SUSPEND_MODULES array can do it.
What i was wondering is: xfce4-power-manager uses pm-suspend to suspend. So why does it something pm-suspend alone doesn't? As i said, the only difference for me, is that that button relies upon upower too. So i suspect it is upower that switch off my wireless card, isn't it?
My question is not how can i reach the same behaviour with pm-suspend alone, but what does that button in the xfce4-panel.
I'm only curious!

Advice about using the laptop with closed lid while connected to external display

Hello all HP forum members!
I have an ENVY 17 with Win8.1 64bit, a great laptop, but I need an advice about using it while connected via HDMI cable to an external display (TV).
When I play heavy 3D games, the computer produces more heat than usual (of course this is normal), but doing so with closed lid, could this harm the display in some way, as a result of the heat?
Thanks!

Hi @VVel ,
Thank you for visiting the HP Support Forums and Welcome. It is a great site for information and questions. I have looked into your issue about your HP ENVY 17 Notebook and issue with keeping the Notebook on while closing the lid. Here is a document on changing the Power option.
Control Panel - Power Options - upper left - Choose what closing the lid does.
Change Plan Settings and also check Advanced Settings. Make sure you do this for both battery and power.
Hope this helps.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

ACPI doesn't detect closed lid until other acpi event

Basically I have the same problem as described in this thread:
https://bbs.archlinux.org/viewtopic.php?id=121224
No solution is posted so I bring this up again.
As said when I close the lid, acpi doesn't detect it not in the acpi.log neither with acpi_listen. When I insert the battery, acpi immediately detects the closed lid and my laptop goes in suspend as it's supposed to.
This happens with a WM + acpi + laptop-mode-tools, in Xfce and in Gnome. KDE however works fine.
The logs when I close the lid and then insert the battery:
acpi.log
Jan 21 20:51:31 localhost acpid: client 1254[0:1000] has disconnected
Jan 21 20:51:31 localhost acpid: client connected from 1254[0:1000]
Jan 21 20:51:31 localhost acpid: 1 client rule loaded

I can tell with the lid closed because of which lights are on.
Anyway, I don't see anything interesting at all in the logs. This is so weird.
EDIT: I'm thinking that it might be conflicting kernel modules. For example I have phc-intel and acpi-cpufreq. Plus I'm using the CK kernel. So when I get home today, I'll first try removing phc-intel, then acpi-cpufreq, then I'll try stock kernel.
Last edited by pogeymanz (2011-06-22 17:32:56)

Charging iPhone with closed lid on mbp

I've been researching, but found nothing this specific so far. Related links:
- http://support.apple.com/kb/HT1476 - This says it may or may not charge
- http://forums.mactalk.com.au/11/72536-snow-leopard-not-charging-iphone-while-lid -closed.html - This says it should work since Leopard and if it's not working to reset the SMC should fix it (I haven't tried yet): http://support.apple.com/kb/HT3964
- http://forums.macrumors.com/showthread.php?t=795007 This is not the same model, but for him it seems to not work anyway
- http://discussions.apple.com/thread.jspa?threadID=2126178 Suggests http://support.apple.com/kb/HT3131 for dealing with closed lid, but requires external display, among other things that don't come to this case (or so I guess)
To me, experience showed that closing the lid with the iPhone already connected works fine. I'm using a macbook pro 2009, as already hinted elsewhere. It's 13'' if that makes any difference.
But if I have the computer sleeping in the bag and want to just plug the iPhone for charging convenience, then it doesn't work. I have to remove it, open the lid, wait for charging to begin, then I can safely close, sleep, put it back on the bag, and it will be charging.
So I wonder how this is supposed to work, and if I can "fix" this behavior. Anyone knows?

I actually solved it on my own luck. Oddly enough, just need to remove and re-plug.
Here, this is a small chart:
1- Computer with lid open, up and running with energy - whatever AC or not.
normal behavior, everything as expected: plug in iPhone it starts charging.
2- Computer with closed lid, sleeping as blinking light indicate and plugged in AC power.
normal behavior, everything as expected: plug in iPhone it starts charging.
3- Computer with closed lid for long time, unplugged from AC power, no cables on it whatsoever.
plug in iPhone - nothing happens.
unplug it and plug in again in either port - it starts charging!
If you close the lid and don't wait it gets to sleep (that is, white blinking light - if you want to be sure, wait till the computer cools down, if it was hot - that's sleep mode) you'll get normal behavior right on the first plug time. The trick of plugging again seem to work always from my tests. So this is a undocumented feature that took me freaking long enough to uncover!
Now it's aight!

Thinkpad X200 Cannot Resume from Standby (by Closing Lid)

I am having such problem lately. I suspect it is caused by new updates performed by system update,
Now my thinkpad could not resume after i made it to go standby by closing lid. When i open the lid, the standby LED just light up and dont respond to Fn+Suspend or power button, and the screen is just blank. Plugging in the power gives the same reult. The issue really annoys me as i always need to shutdown and bootup again. Any sugguestion? My thinkpad is Thinkpad X200 and the OS is Windows XP SP2

they told me that there are some drivers that need to be updated, so i updated the Display drivers, the wireless lan, and the power management drivers. but, it did not worked and i still counld resume from reopening the lid. i still have to shut the machine down to get it work again .
Here are the drivers that i updated.
Intel Display Driver for Windows XP
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-70127
ThinkPad Power Management driver for Windows Vista, XP, 2000, Me, 98 SE
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4GXPEG
Wireless LAN ThinkPad (11bg, 11abg, 11abgn) for Windows XP, 2000
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-70480
I will call them again tomorrow.

Helix cannot sleep when closing lid

Helix does not sleep after closing lid, even though I set to let it sleep in power plan in windows.
I previously do not have this problem. Not notice anything changed.
Any suggestions? Thanks!
Solved!
Go to Solution.

Somehow, after rebooting, this problem is gone. So next time, I will try a reboot first. Thanks!

DVI to VGA Adapter Closed Lid Mode Distorted Picture on TV

Hi
I managed to hook up the DVI to VGA adapter and view on my Sanyo TV. Nothing fancy just a older TV.
I am feeding through the Yellow Video output into the video input on the TV. (Also tried s-video)
Viewing with the macbook lid open no problems. Remembered that I could close the lid.
Followed the instructions online about connecting, closing the lid and waking up using my bluetooth mouse.
First time things went well - able to use Front Row and View Slideshows etc. also steaming video from Safari, (TV Land for my kid)
Then the screen began to flash - and change to black with rolling images.
Like you used to have in the 60-70's black and white TV - multiple images rolling past over and over.
I tried rebooting - starting new connections, using different cables, using both VGA and S-Video directly into the TV and not through my reciever.
Any ideas!
I can't use closed lid mode at all. I must instead, dim my screen.
Help?
Thanks
Buddy

Thanks, BSteely, I have the latest QT and iTunes already. Closing the lid seems to kick the MacBook external display into some special mode that Front Row can't display videos in. For example, you get the Front Row interface, but as you select movies/TV shows, the preview window on the left side is blank. Open the cover, and have both displays going, and you can see the previews fine (and of course, you can see the movies/TV shows play fine as well when you click on them)
Running Quicktime Player full screen works fine without Front Row in either open or closed lid mode. So it is apparently something wrong with Front Row itself.

TV + Closed-Lid Mode?

Is running in closed-lid mode on the MacBook using a television with the Apple Video Adapter supported? I can't get it to work properly.
Brian

Make sure your power saving settings aren't unusual - I find normal works fine. Configure your external displays with the lid open and then with the power cable connected try closing the lid. It will fall asleep immediately - let it. Then when the light throbs try waking it back up again with the remote... It works for me, but it did try my patience before I came up with a routine that I was happy with.
Also - how do you connect your TV? My TV has a monitor / DVI out and it's quite happy with that. I shouldn't think that S-Video should be too different. Has anyone tried with S-Video? Hope this helps...
macbook 2.0Ghz Mac OS X (10.4.8) 2 Gb RAM

10.5.2 wake/sleep and closed-lid problems

As of 10.5.2 my MBP no longer works correctly in closed lid mode using a hardware
setup that previously worked flawlessly. After plugging in power and video, plugging
in the USB keyboard seems to wake the system, but no video. I then must open the
lid, unplug the USB and video and try to get the system to respond. I often must cycle
the power to reset the system--very disturbing to do that.
Also as of 10.5.2, I have had to power-cycle the machine when it has refused to wake
in open-lid mode and this weekend I the entire machine froze (no mouse movement,
no expose, etc) in the middle of work using a graphics-intensive program and I had
to reboot by cycling the power.
A friend also reported similar issue in which the system would not respond after the
screensaver became active.
Are others seeing problems like these? I am beginning to suspect that the post-10.5.2
graphics update has problems.

I just wiped my HD and reinstalled everything besides the Graphics Update. I can now close the lid of my MBP and use my external monitor alone. The Graphics Update had made that impossible.
Further, I am in the habit of putting my MCP to sleep and putting it in a backpack in the morning, meeting friends for breakfast, and re-awakening it at the office. When I did get to my office, I found (as another user had on another thread) that the MBP, even closed, had woken itself up and was hot as heck. I am uncertain that sleep will work properly under 10.5.2, but I know that the display wackiness of the Graphics Update was driving me nuts. I will not install it until Apple fixes it.
I looked around for awhile for a way to uninstall the Graphics Update, but could not find it...I suspect it exists somewhere.
The 10.5.2 Combo update (343MB download) DOES NOT include the Graphics Update, and at this time, I seem quite ok with everything else updated.

15-r007TU-Display does not turn on when it automatically turns off after closing lid.

I just purchased hp 15-r007TU, Windows 8.1 x84. I'm facing a strange problem. After all initial setup, I put the laptop on to download and install all lates Windows 8.1 patches. The display is set to tuen off automaticaaly after 5 minutes. After 5 min it did turn off as set. But then I can not turn it back on. I pressed all (except power) keys, used touch pad, closed lid and opened but it stayed off. Laptop was on and running as I could see HDD lights flickering, I could hear system sounds on pressign mute/volume keys, also I could toggle WiFi with key. I then pressed power off key to turn Windows off normally. I did turn off. I again turned it on, I could see 'hp' logo with spinning wheel and then nothing. Display is off and I don't see start screen. I have to hard reset (press power button for more than 5 seconds) then display is normal. This happens every time the display turns itself off automatically after set time or I close the lid. Only after hard reset it works normally and I see the start menu.
The power settings I use are:
1. never put system to standby after preset time. (either on battery or AC power)
2. turn display off after 5 min. (both on battery or AC power)
3. when I close lid - do nothing. (both on battery or AC power)
4. when I press power button - shut down
I am using Windows 8.1 x64 with all latest patches installed. BIOS updated to lates available. All latest drivers installed.
I have not yet set password to the system to log in.
Help would be immensly appreciate. The device is still in warrenty if it needs to be replaced.

Hello K1200LT,
Welcome to the HP Forums!
I understand the computer will not sleep when you shut down the lid. You seem to have already done most of the troubleshooting I would've suggested.
To be honest, it is either a hardware or software-related issue. To determine this, I would like you to reinstall the operating system. It will clear up any software conflicts and allow you to start fresh.
First, please ensure you backup your files. Here is information on how to do this: Backing Up Your Files (Windows 8)
Once this is done, it is safe to reinstall the operating system. Performing an HP System Recovery (Windows 8)
If the same situation occurs, the computer likely has faulty hardware. At that point, please contact HP phone support. You can utilize this website to learn how to contact HP appropriately, based on your region: Contact HP Worldwide
Please let me know what happens. Thanks!
Mario
I worked on behalf of HP.

Closed Lid Operations Wont Work

I am a big fan of the closed lid with external mouse, keyboard, and display (minimize spill risks in college dorm room). I just got a new macbook pro after 4 great years with my g4 powerbook and I cannot get the new machine to work with the lid closed. I have tried working with both displays then closing it, but it won't wake up. I tried putting it to sleep and attaching the external display but it doesn't wake up. The for either if I try to open the machine to use it normally the built in display, keyboard, and trackpad are non-responsive and so are all my external items. Has anyone else had this problem or any ideas on what could be going on.

Jonathan , I am experiencing the same exact problems with my Macbook Pro 15 inch. I first started noticing about a month ago that the computer was getting unusually HOT to the touch , and after one day I set the lid down, when I tried to open it back up, it remained on , but no screen, and unresponsive. I have had to restart it everytime since then. It also now takes a lot longer than usual to reboot. I hope the people at Apple resolve this soon, because this is WAY too expensive to be having these problems on a new machine Ive only had for 5 months.

Closed lid, fans always running

Howdy. I've been using my MBP in closed lid mode attached to a Cinema Display. I expected the fans to run constantly when in use, especially with XP running in Parallels. When I put the computer to sleep--still attached to monitor, usb keyboard, bluetooth mouse and power adapter--it acts as I suspect it would, fans stop, front LED starts fading in and out. However, I'll come back later and the LED will be solid, display blank, and the fans running away. The keyboard or mouse will wake the computer and then it runs as normal. This has happened overnight as well as in half an hour, and several times.
I am kind of getting concerned about using the computer this way. Fans always fail, and I am not really looking forward to opening the computer up again.
I guess my questions are: why would the computer be running the fans, especially after being in sleep for hours, and is it shortening my MBPs expected life using it with the lid closed?
Thanks.

I'd guess/assume that something is actually waking it from sleep and causing the heat/fan activity and that when you return you're not actually waking it up just re-activating it from screensaver mode ...
Run Utilities/Console and click 'All Messages' top left - what lines appear during the time you think it should be sleeping ?
It isn't shortening the life of the hardware using it in clamshell mode but if something is causing it to overheat regularly that will have an impact on internal components/motherboard that could be detrimental.

[solved] Suspend on closed lid

Similar Messages

Maybe you are looking for