HT3131 Won't my computer overheat if the lid is closed?

If I close the lid of my computer when it is connected to an extern monitor will the computer overheat? Should I lift the lid a little? Is there a way of preventing the screne from turning back on when it is connected to the external monitor?

Hjoh wrote:
If I close the lid of my computer when it is connected to an extern monitor will the computer overheat?
Yes
Should I lift the lid a little?
Yes, make the lid ajar.
Is there a way of preventing the screen from turning back on when it is connected to the external monitor?
Good question, I don't know.

Similar Messages

HT1338 Why won't my computer pick up the wireless in my home? All other computers in my home can get internet

Why won't my computer pick up the wireless in my home? All other computers in my home can get the internet.

Turn Off your computer. Then turn Off (disconnect power cord for 30 seconds or longer) the wireless router & then back On. Now boot your computer. Hopefully it will see the WiFi.
 Cheers, Tom

Won't sleep when I close the lid - HELP!

A while ago, my iBook G4 1GHz was knocked off of a table. The display was smashed and the whole display assembly was destroyed. I bought a new (used) display assembly and installed it. Worked fine, but when I closed the lid, the iBook woudn't sleep. I checked the placement of the magnet in the top case and I reset the PMU. Still no sleep. So I contacted the company that sold me the display and got a different one. Still won't sleep when I close the lid. I checked all of the energy settings, reset the PMU and even tried to force sleep with a magnet from another broken iBook. Still no sleep when I close the lid. It will sleep when I choose sleep from the Apple menu (OS Tiger) and when it sits for a while with the lid open, but not when I close the lid. Any thoughts?

My original problem has not been solved. The iBook still won't go to sleep when I close the lid. I have checked out any possible software causes, and have ruled them out. I have checked to make sure no keys were being pressed when I closed the lid. I took a magnet from another iBook top case and ran it down the side of the display to try to force sleep. No effect. I don't have any Firewire or USB devices attached, to that's not it. Apple, this board, PBFixit.com, and my local Apple-affiliated repair center have no idea why I am having this problem. Two display assemblies have experienced this problem. The original display had been destroyed in a drop. Could some internal damage, like maybe to the logic board, result in such a problem? It's odd that I am the only person out there who has had this problem. Weird, to be sure.

Can the lid be closed and still run the computer with an external display?

I purchased a 19" LCD display to hook to my G3, everything works fine but I cannot find any reference on whether the lid for the laptop can be closed while running the computer. Can anyone help answer this for me? Currently I am looking at my laptop with the lid half-closed, or is that open...Any help would be greatly appreciated.
Thanks!
PowerBook G3 333MHz Mac OS X (10.3.9) The Lombard, 384MB RAM

Make sure the computer is plugged in on the AC power adapter. (this is because the power requirements are higher for an external display.)
- Close the PowerBook's display. The PowerBook will go to sleep.
- Connect the external monitor.
- Turn on the external monitor.
- Connect an external Apple USB keyboard and mouse.
- Now the PowerBook will wake from sleep.
Next time when you want your Powerbook to sleep use the "sleep" option from the Blue Apple menu (on the left top).
Hopefully this is helpfull or solved your problem. Consider rewarding some points!
Please see the "helpfull" and "solved" button's on top off this message! Apple: Why reward points?

Lenovo t61 comes out of standby automatically after the lid is closed

Hi,
I have a t61 + wind 7 + 32 bit + ultimate edition. It was working fine till now and suddenly I have noticed its coming out of the standy mode suddenly. I close the lid, its going to standby mode i see the little semi circle on the top and everything is fine. Suddenly when it finds any known wifi signal or any thing, which I think I have noticed, its comes out of stand by ....I can tell that from the beep it makes and the light suddenly goes off. After sometime I notice that the battery dies, as its in normal mode even when the lid is closed and it consumes all of the battery. Please let me know what settings have to be changed to get rid of this F error. I am facing a lot of trouble as it consumes all of the battery when I open the lid even if its fully charged. I think it has to do with some settings. I have verified everything power manager, wireless adapater etc. Any gurus pls suggest.
thanks,
Manu

a couple things you can check...
open up Device Manager and see if Allow this device to wake the computer is enabled for your mouse and/or your wired ethernet device on the Power Management tab of their Properties sheets.
hth.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
PM requests for individual support are not answered. If a post solves your issue, please mark it so.
X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
I am not a Lenovo employee.

Powerbook does not sleep when the lid is closed

my tibook does not go to sleep when i close the lid. the screen stays on when the lid is closed. the screen was replaced a few months ago. i have to hit the power button and choose sleep or choose sleep from the menu. does anyone know how to fix this. Thanks.

Hi, fatchance. You have a hardware issue. The reed switch that puts the PB to sleep when it is closed is a two-part device. The latch mechanism in the main body of the Powerbook contains a magnet (which you can detect by moving a paper clip over it), and the switch itself is located inside the small latch opening in the display bezel. When the display is closed, the magnet is supposed to actuate the switch, putting the PB to sleep. If that isn't happening on your PB, the switch is broken or its wiring is damaged. Either way, the remedy will be to replace the entire display assembly. It's made not to be disassembled. Most technicians won't do so, because of the great likelihood of damaging the display housing/bezel or the display itself while prying it apart (it's epoxied together). Since the display is the PB's most costly part, replacing it merely to fix your reed switch would be a poor bargain, and I can't recommend it. Just put the PB to sleep manually or set a suitable sleep delay in the Energy Saver control pane instead.

My macbook pro shuts down OSX and all my programs when the lid is closed

Hi,
I am having a problem. My macbook pro shuts down OSX and all my programs when the lid is closed. I close the lid, and then I hear the shutdown music and then when I open it again it automatically restarts OSX and all my windows and programs are closed, any info gone.
This doesn't happen all the time. Just once a day or maybe twice a day. It seems like it happens basically when I have my computer just the way I want it, to keep an eye on things for the day.
I just recently switched to a mac and while somewhat savvy, I am not a programmer or techie, but it seems to me that when I shut the lid, it should do the same thing every time.
I have a intel core 2 duo 17 inch macbook pro with 2.33 processr and 2 gig ram, if that helps.
I am in alaska and there is no genius bar here and I am hoping to figure this out before I begin bugging our local independant mac store about this.
Thanks in advance,
Lylah
17 inch Macbook Pro Mac OS X (10.4.9) intel core 2 duo 2.33g. 2 gig ram

Ahhh, enlightenment!
That would make sense. What I usually do, after closing the lid, is to wait for the apple to turn off and then set it down on it's side leaning it against the side table. I will try to wait for it to indicate that it is fully asleep before I move it next time. Personally, I prefer my computer to NOT fall asleep at all, but I am told it is not an option. Apparently this function is hardware related accoring to my local mac shop. They tracked it down for me because I hated this feature when I first bought my computer and was trying some way around it.
The shutdown music I was refering to was that music the mac makes when shutting down, which doesnt usually occur when it goes to sleep, unless it is malfunctioning like this.
What does resetting the pmu do? (what is a pmu as well?)
Thank you very much.
Lylah

T540p will not go to sleep when the lid is closed

I recently got a T540p and all settings in Windows 8.1 are set to "sleep" when either the power button or lid is closed. Neither of these work, the screen stays on when the lid is closed. If I let the computer idle long enough, the computer will enter sleep. I've used Lenovo System Update to get the latest drivers and there is nothing outstanding. Could someone please advise if there is anything else to check?

Hi Adamstirtan,
Welcome to Lenovo Community!
As per the query we understood that you are facing issue with system not going to sleep mode on your ThinkPad T500.
Go to Control Panel\All Control Panel Items\Power Options\Choose what closing the lid dose – When close the lid – On battery sleep – Plugged in sleep.
To prevent programs from waking your computer:
Open Power Options by clicking the Start button Picture of the Start button, clicking Control Panel, clicking System and Security, and then clicking Power Options.
On the Select a power plan page, click Change plan settings for the plan that you want to change.
On the Change settings for the plan page, click Change advanced power settings.
On the Advanced settings tab, expand Sleep, expand Allow wake timers, choose Disable for both when your computer is running on battery and when it's plugged in, and then click OK.
Hope this helps.
Best regards,
Hemanth Kumar

KDE - Keep Screen Turned Off When The Lid Is Closed

Hello all,
I configured KDE to turn off the screen when I close my lid and this part works OK.
Problem is, once I move the mouse while the lid is closed the screen wakes up (it's not hard to tell, light gets out from the sides).
If I configure the lid action to be sleep, the computer sleeps and wakes up with lid close/open with the mouse not getting in the way.
Any idea on how I can configure it to block mouse input while the lid is closed so the screen stays off?
Thanks, Adam.
Last edited by adam777 (2012-09-24 08:26:39)

Doug.
You're a genius!!! It worked. It wasn't the keyboard that was not reset properly, it is the escape (hey, it kind of looks like Escape - with a Ellen degeneres slang ) key. It is on the fritz and does not want to sit properly. I removed it temporarily, and, voila, it works again.
Thanks again for the headache solved. Now on to my 3 and 5 year old girls - a totally different problem. Maybe it is their CPU???

Can i choose the resolution of my external display for when the lid is closed when my lid is open

When I close the lid of my MacBook Pro for an external display apple chooses a resolution that isn't compatible with my display can I choose the resolution when the lid is open in any way of my external display for the mode when the lid is closed?

Hi there, I had a similar problem and was unable to resolve it. I spent about an hour on the phone with a very helpful AppleCare rep who was also completely stuck. It would seem that the only solution is to choose a setting with trial and error while the lid is closed.
My MacBook ended up getting stuck on a closed-lid reoslution that wasn't supported, so I had to do a screen-share with another device to see what the video card was sending to the external display and change it back that way.

After 10.8.2 update i can no longer wake my macbook from standby with keyboard when the lid is closed

I just updated to 10.8.2 and now i can no longer wake my macbook froom standby when the lid is closed, it directly goes back to sleep
steps to reproduce:
1. attach secondary monitor and keyboard
2. close lid
3. wait 5 seconds for going to standby
4. press any key on keyboard and type in user-credentials (notice how the 2nd monitor becomes the mainscreen)
5. wait 5 seconds
6. standby again
side note:
i also have sudo nvram boot-args="iog=0x0" enabled, because i like to not use the integrated screen when its attached to a secondary screen, but since it goes back to standby right after login this is pretty much pointless

Same here, I think changed something in 10.8.2 that wrecked the "Open-MBP Clamshell Mode." sigh

[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.

Dragon Naturally Speaking with the lid/screen closed

I want to use Dragon Naturally Speaking with the lid/screen closed. Please tell me what settings. Thanks in advance.

Hi,
I did few tests which my laptops, they sit on docking stations with their lid closed and the sounds were so weak because due to the location of the internal microphones. You need to use an EXTERNAL microphone, you can set you laptop to stay ON after closing the lid:
http://windows.microsoft.com/en-au/windows7/change-what-happens-when-you-close-your-laptop
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your 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)

Won't Wake Up After Opening The Lid

This has been happening for awhile now (checked with my father in law, who has a macbook pro, and he says the same thing happens to his): I close the lid, it goes to sleep. When I open the lid again, half the time it'll wake up, and half the time it won't (even pressing buttons, etc). I'll have to hold down the power button to turn it off, then press it again to turn it on and start up from scratch, losing whatever I was working on. There's seemingly no rhyme or reason to it...but it happens about half the time. The other thing I notice, when this happens, is that the "sleep" light (that is usually flashing when it's sleeping normally) turns on solid when I close the lid rather than flashing, and turns off when I open it.
Anyone else have this problem? Any way to fix it? I have the newest firmware.
Message was edited by: Evan!

I cannot solve your problem but I did have the same problem which has now evolved into my computer NEVER going to sleep and my bluetooth does not work I have tried all the advice I can find and nothing works. Of course my waranty expired four months ago so now I will have to come up with the money to fix it if I want this resovled. If your warenty is still good I suggest having someone look at it before it evloves into a bigger problem.

HT3131 Won't my computer overheat if the lid is closed?

Similar Messages

Maybe you are looking for