Hard lockup when closing laptop lid (Linux 2.6.23)

I just found this out a few days ago, telling my laptop to shut down a few hours later, and still finding it running half a day later, severely overheated (!).
I am running a custom kernel (2.6.23.1 with some of the kamikaze broken out patches). I get this:
- I unplug the laptop USB mouse
- I close the lid
- I reopen the lid, only to find my system completely locked up (no screen refresh anymore, no possibility to switch to a virtual terminal, no possibility to restart X or restart the system (Ctrl+Alt+Del/Backspace aren't working at all).
I have no action specified for closing the lid (I plan on making it do suspend to RAM as soon as this issue is cleared up). Now if I leave the USB laptop mouse plugged in all works fine. I can close the lid, open it up again, and my system remains fully usable.
To make sure this wasn't just me being clumsy and compiling a bad kernel, I tried the 2.6.23-ARCH kernel from testing. It exhibits exactly the same behaviour. 2.6.22-ARCH works just fine.
Are there people having the same issue?
Last edited by B (2007-10-21 12:16:32)

Okay guys . I got some goodies up . For those interested:
- 2.6.22.12 kernel with CFS v22, hrtimers, powertop, Reiser4 and default CPU frequency governor 'ondemand'
- iwlwifi 1.1.21
- Authentec fingerprint reader driver
I guess that should get you going pretty much . The iwlwifi drivers have been built out-of-tree since my efforts to merging in the newer mac80211 stack & latest iwlwifi drivers amounted to nothing but a boatload of patch errors :-( (yes i can hack up patches to work but I felt like not doing it, since iwlwifi builds just fine out-of-tree). This kernel is tailored to the 6510 hardware, I cannot tell what is different in the 6170b lineup, but you definitely should not try this kernel on just any machine .
If you have any questions, drop me a line.
Credit of course to waninkoko for his kamikaze patchset, from which most of the patches come.
Update: to the latest 2.6.22.12 kernel + corresponding driver packages
Last edited by B (2007-11-11 16:39:48)

Similar Messages

[SOLVED] how to prevent suspending/sleeping when closing laptop lid

Hi all,
My laptop, a Lenovo Thinkpad T430u, suspends whenever I close the lid. It's been doing this since I first installed Arch. I want to turn this feature off. How can I do it?
Relevant information:
acpid is installed
the configuration file /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'
logger "ACPI action undefined: $2"
esac
button/sleep)
case "$2" in
SLPB|SBTN)
logger 'SleepButton pressed'
logger "ACPI action undefined: $2"
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
logger 'AC unpluged'
00000001)
logger 'AC pluged'
esac
logger "ACPI action undefined: $2"
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000)
logger 'Battery online'
00000001)
logger 'Battery offline'
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
logger 'LID closed'
open)
logger 'LID opened'
logger "ACPI action undefined: $3"
esac
case $(cat /proc/acpi/button/lid/LID0/state | awk '{print $2}') in
closed) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force off ;;
open) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force on ;;
esac
logger "ACPI group/action undefined: $1 / $2"
esac
# vim:set ts=4 sw=4 ft=sh et:
dmesg output:
[ 1530.790532] PM: Syncing filesystems ... done.
[ 1530.805678] PM: Preparing system for mem sleep
[ 1530.844445] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 1530.856658] Freezing remaining freezable tasks ... (elapsed 0.10 seconds) done.
[ 1530.963435] PM: Entering mem sleep
[ 1530.963572] Suspending console(s) (use no_console_suspend to debug)
[ 1531.123543] iwlwifi 0000:03:00.0: iwl_pcie_cmdq_reclaim: Read index for DMA queue txq id (9), index 207 is out of range [0-256] 208 208.
[ 1531.124216] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1531.124579] sd 0:0:0:0: [sda] Stopping disk
[ 1531.360682] mei 0000:00:16.0: suspend
[ 1531.440517] ahci 0000:00:1f.2: power state changed by ACPI to D3hot
[ 1531.687309] PM: suspend of devices complete after 722.490 msecs
[ 1531.687784] PM: late suspend of devices complete after 0.469 msecs
[ 1531.688232] pcieport 0000:00:1c.3: System wakeup enabled by ACPI
[ 1531.714222] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[ 1531.727619] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[ 1531.754015] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[ 1531.767422] PM: noirq suspend of devices complete after 79.565 msecs
[ 1531.768301] ACPI: Preparing to enter system sleep state S3
[ 1531.797647] PM: Saving platform NVS memory
[ 1531.799282] Disabling non-boot CPUs ...
[ 1531.900721] smpboot: CPU 1 is now offline
[ 1532.004162] smpboot: CPU 2 is now offline
[ 1532.107554] smpboot: CPU 3 is now offline
I have pmutils and tlpinstalled
tlp config
# tlp - Parameters for power save
# Hint: some features are disabled by default, remove the leading # to enable them
# Set to 0 to disable/1 to enable TLP
TLP_ENABLE=1
# Seconds laptop mode has to to wait after the disk goes idle before doing a sync.
# Non-zero value enables, zero disables laptop mode.
DISK_IDLE_SECS_ON_AC=0
DISK_IDLE_SECS_ON_BAT=2
# Dirty page values (timeouts in secs).
MAX_LOST_WORK_SECS_ON_AC=15
MAX_LOST_WORK_SECS_ON_BAT=60
# Select a cpu frequency scaling governor: ondemand/powersave/performance/conservative
# Important:
# - You *must* disable your distribution's governor settings or conflicts will occur
# - ondemand is sufficient for *almost all* workloads, you should know what you're doing!
#CPU_SCALING_GOVERNOR_ON_AC=ondemand
#CPU_SCALING_GOVERNOR_ON_BAT=ondemand
# Set the min/max frequency available for the scaling governor.
# Possible values strongly depend on your cpu. For available frequencies see
# tlp-stat output, Section "+++ Processor".
# Hint: Parameters are disabled by default, remove the leading # to enable them,
# otherwise kernel default values are used.
#CPU_SCALING_MIN_FREQ_ON_AC=0
#CPU_SCALING_MAX_FREQ_ON_AC=0
#CPU_SCALING_MIN_FREQ_ON_BAT=0
#CPU_SCALING_MAX_FREQ_ON_BAT=0
# Set the cpu "turbo boost" feature: 0=disable / 1=allow
# Requires an Intel Core i processor and kernel 3.7 or later.
# Important:
# - This may conflict with your distribution's governor settings
# - A value of 1 does *not* activate boosting, it just allows it
#CPU_BOOST_ON_AC=1
#CPU_BOOST_ON_BAT=0
# Minimize number of used cpu cores/hyper-threads under light load conditions
SCHED_POWERSAVE_ON_AC=0
SCHED_POWERSAVE_ON_BAT=1
# Kernel NMI Watchdog
# 0=disable (default, saves power) / 1=enable (for kernel debugging only)
NMI_WATCHDOG=0
# Change CPU voltages aka "undervolting" - Kernel with PHC patch required
# Freq:voltage pairs are written to /sys/devices/system/cpu/cpu0/cpufreq/phc_controls
# CAUTION: only use this, if you thoroughly understand what you are doing!
#PHC_CONTROLS="F:V F:V F:V F:V"
# Hard disk devices, separate multiple devices with spaces (default: sda).
# Devices can be specified by disk id too (lookup with: tlp diskid).
DISK_DEVICES="sda sdb"
# Hard disk advanced power management level: 1(max saving)..254(off)
# Levels 1..127 may spin down the disk.
# Separate values for multiple devices with spaces.
DISK_APM_LEVEL_ON_AC="254 254"
DISK_APM_LEVEL_ON_BAT="128 128"
# Hard disk spin down timeout:
# 0: spin down disabled
# 1..240: timeouts from 5s to 20min (in units of 5s)
# 241..251: timeouts from 30min to 5.5 hours (in units of 30min)
# (see 'man hdparm' for details)
#DISK_SPINDOWN_TIMEOUT_ON_AC="0 0"
#DISK_SPINDOWN_TIMEOUT_ON_BAT="0 0"
# Select io scheduler for the disk devices: noop/deadline/cfq (Default: cfq)
# Separate values for multiple devices with spaces.
#DISK_IOSCHED="cfq cfq"
# SATA aggressive link power management (ALPM):
# min_power/medium_power/max_performance
SATA_LINKPWR_ON_AC=max_performance
SATA_LINKPWR_ON_BAT=min_power
# PCI Express Active State Power Management (PCIe ASPM):
# default/performance/powersave
# Hint: needs kernel boot option pcie_aspm=force on some machines
PCIE_ASPM_ON_AC=performance
PCIE_ASPM_ON_BAT=powersave
# Radeon graphics clock speed (profile method): low/mid/high/auto/default
# auto = mid on BAT, high on AC; default = use hardware defaults
# (Kernel >= 2.6.35 only, not with fglrx driver!)
RADEON_POWER_PROFILE_ON_AC=high
RADEON_POWER_PROFILE_ON_BAT=low
# WiFi power saving mode: 1=disable/5=enable
# (Linux 2.6.32 and later, some adapters only!)
WIFI_PWR_ON_AC=1
WIFI_PWR_ON_BAT=5
# Disable wake on lan: Y/N
WOL_DISABLE=Y
# Enable audio power saving for Intel HDA, AC97 devices (timeout in secs).
# A value of 0 disables / >=1 enables power save.
SOUND_POWER_SAVE=1
# Disable controller too (HDA only): Y/N
SOUND_POWER_SAVE_CONTROLLER=Y
# Set to 1 to power off optical drive in UltraBay (ThinkPads only)
# when running on battery. A value of 0 disables this Feature (Default).
# Drive can be powered on again by releasing (and reinserting) the
# eject lever or by pressing the disc eject button on newer models.
# Note: an UltraBay hard disk is never powered off.
BAY_POWEROFF_ON_BAT=0
# Optical drive device to power off (default sr0)
BAY_DEVICE="sr0"
# Runtime Power Management for pci(e) bus devices
# (Kernel >= 2.6.35 only): on=disable/auto=enable
RUNTIME_PM_ON_AC=on
RUNTIME_PM_ON_BAT=auto
# Runtime PM for *all* pci(e) bus devices: 0=disable / 1=enable
# Warning: experimental option, could cause system instabilities
RUNTIME_PM_ALL=0
# Set to 0 to disable/1 to enable usb autosuspend feature
USB_AUTOSUSPEND=1
# Devices from the following list are excluded from usb autosuspend
# (separate with spaces). Use lsusb to get the id's.
# Note: input devices (usbhid) are excluded automatically
#USB_BLACKLIST="1111:2222 3333:4444"
# Set to 1 to disable autosuspend before shutdown/0 to do nothing
# (workaround for usb devices that cause shutdown problems)
#USB_AUTOSUSPEND_DISABLE_ON_SHUTDOWN=1
# Restore radio device state (bluetooth, wifi, wwan) from previous shutdown
# on system startup: 0=disable/1=enable
# Hint: the parameters DEVICES_TO_DISABLE/ENABLE_ON_STARTUP/SHUTDOWN below
# are ignored when this is enabled!
RESTORE_DEVICE_STATE_ON_STARTUP=0
# Radio devices to disable on startup: bluetooth wifi wwan
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
# Radio devices to enable on startup: bluetooth wifi wwan
#DEVICES_TO_ENABLE_ON_STARTUP="wifi"
# Radio devices to disable on shutdown: bluetooth wifi wwan
# (workaround for devices that are blocking shutdown)
#DEVICES_TO_DISABLE_ON_SHUTDOWN="bluetooth wifi wwan"
# Radio devices to enable on shutdown: bluetooth wifi wwan
# (to prevent other operating systems from missing radios)
#DEVICES_TO_ENABLE_ON_SHUTDOWN="wwan"
# Radio devices to enable when wireless radio switch is turned on:
# bluetooth wifi wwan (Ubuntu + ThinkPad only)
#DEVICES_TO_ENABLE_ON_RADIOSW="wifi wwan"
# Battery charge thresholds (ThinkPad only, tp-smapi or acpi-call kernel module required)
# Charging starts when the remaining capacity falls below the START_CHARGE_TRESH
# value and stops when exceeding the STOP_CHARGE_TRESH value.
# Main battery (values in %)
#START_CHARGE_THRESH_BAT0=75
#STOP_CHARGE_THRESH_BAT0=80
# Ultrabay or slice battery (values in %)
#START_CHARGE_THRESH_BAT1=75
#STOP_CHARGE_THRESH_BAT1=80
# Set to 1 to disable use of tpacpi-bat on Sandy Bridge or newer Thinkpads
# and force usage of tp-smapi instead
#DISABLE_TPACPIBAT=1
# tlp-rdw - Parameters for the radio device wizard
# Possible devices: bluetooth/wifi/wwan
# Hint: parameters are disabled by default, remove the leading # to enable them
# Radio devices to disable on connect
DEVICES_TO_DISABLE_ON_LAN_CONNECT="wifi wwan"
DEVICES_TO_DISABLE_ON_WIFI_CONNECT="wwan"
DEVICES_TO_DISABLE_ON_WWAN_CONNECT="wifi"
# Radio devices to enable on disconnect
DEVICES_TO_ENABLE_ON_LAN_DISCONNECT="wifi wwan"
#DEVICES_TO_ENABLE_ON_WIFI_DISCONNECT=""
#DEVICES_TO_ENABLE_ON_WWAN_DISCONNECT=""
# Radio devices to enable/disable when docked
#DEVICES_TO_ENABLE_ON_DOCK=""
#DEVICES_TO_DISABLE_ON_DOCK=""
# Radio devices to enable/disable when undocked
#DEVICES_TO_ENABLE_ON_UNDOCK="wifi"
#DEVICES_TO_DISABLE_ON_UNDOCK=""
thanks guys
I love arch
Last edited by beitme (2013-06-08 10:05:37)

@ Karol, done
@ 65kid, here's my logind.conf
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min

IPod disconnected from iTunes when closing laptop lid

I recently received a new iPod Classic 120 Gb after the old one's battery died. When i connect the new one to my Macbook Pro and close the lid it disconnects from iTunes (it is still connected, it appears in Finder, just not in iTunes).
I got the latest version of iTunes and the iPod software. This never happened with the old iPod. Is there a fix for this?

Okay guys . I got some goodies up . For those interested:
- 2.6.22.12 kernel with CFS v22, hrtimers, powertop, Reiser4 and default CPU frequency governor 'ondemand'
- iwlwifi 1.1.21
- Authentec fingerprint reader driver
I guess that should get you going pretty much . The iwlwifi drivers have been built out-of-tree since my efforts to merging in the newer mac80211 stack & latest iwlwifi drivers amounted to nothing but a boatload of patch errors :-( (yes i can hack up patches to work but I felt like not doing it, since iwlwifi builds just fine out-of-tree). This kernel is tailored to the 6510 hardware, I cannot tell what is different in the 6170b lineup, but you definitely should not try this kernel on just any machine .
If you have any questions, drop me a line.
Credit of course to waninkoko for his kamikaze patchset, from which most of the patches come.
Update: to the latest 2.6.22.12 kernel + corresponding driver packages
Last edited by B (2007-11-11 16:39:48)

[Solved] preventing standby when closing laptop lid and more.

To be blunt, I'm on the verge of insanity at this point. I'm no newcomer to Arch, but this has me beat.
In short I'm not using my asus eepc 1015pem anymore, so I decided to make it a folding machine.
Everything works as intended except when I close the lid, it automatically goes to sleep and I haven't had any luck finding a solution.
All in all I have little use for any sort of power management, and things like CPU scaling and such, should obviously not be active.
So please do let me know where I can find the information I need.
My arch installation is completely basic and brand new, should that information matter
Best regards.
Last edited by zacariaz (2012-10-21 00:37:00)

2ManyDogs wrote:
zacariaz wrote:
WonderWoofy wrote:
You need to look into the powers of logind.conf (by that I mean the man page).
Also, I don't know why you would want to turn frequency scaling off. If it makes the cpu go full speed, so be it, but if not, it would be nice to not use quite as much power.
First of all, I want to thank you for the quick reply and secondly mention that this is a very low power device which will be running at full capacity 14/7, thus these think are not needed.
If it's running at "full capacity" cpu frequency scaling will allow the CPU to run at its top speed. There is no need to remove it. If at any point full speed is not required, even a low-power device will use less power with cpu scaling, and it allows the CPU to rest and cool off a little.
But hey, it's your box.
The reason it's important is only due to the doubt that the cpu might somehow be inhibited. If that's not the case, then it doesn't matter obviously.

Kernel 2.6.32.2-2 black screen after closing laptop lid (intel + KMS)

Today I updated my laptop with the new 2.6.32.2-2 kernel from core. Previous update of my system was just a few days back, so there are no massive changes to other packages and I also don't use testing packages.
Since the update, after closing the laptop lid (which just blanks my screen) and I want to continue working I just have a black screen (no backlight) and the screen won't respond to mouse or keyboard input. I have to reboot (ctr-alt-del or pushing my power button) or switch to VT1 and back to VT7 to get my screen back. I'm absolutely positive that this was not a problem before, it worked fine with 2.6.30 and 2.6.31 kernels with my same configuration.
HP 6730b laptop
Intel GMA 4500 (Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07))
Intel driver 2.9.1-1 using KMS with early start (modprobe.conf) and I rebuilt my initcpio to the new 2.6.32.2-2 kernel
Gnome 2.28.2
Can anyone confirm this behaviour? Should I file a bug somewhere? I read about lots of upgrade problems with this new kernel, but for the rest everything else works fine so far.
Thanks for your feedback.
Ulukai

moose jaw wrote:
ulukai wrote:@ Moose Jaw: I also looked into pm-suspend, but i guess it is only usefull for suspending and resuming sessions (something I never do)? Is there a command you know for simulating closing the lid and reopening it again?
Isn't suspending and resuming a session exactly what you're doing (or hoping to do) when you close your lid and then open it up again? I.e., putting the machine into a low-power sleep state and then having everything come back to where you were when you wake it up? You mentioned that the Gnome power management tools depend on pm-utils, which suggests that somewhere in there "pm-suspend" is getting called. If you can find out where it's getting called (i.e., in some script that Gnome power manager uses), and try changing it to "pm-suspend --quirk-vbestate-restore" (or one of the other quirks, perhaps), then that may bring your screen back on wakeup.
Hehe, nope I don't hope to suspend :-) I just close the lid to save the display (and some power) but want my machine to keep running (when downloading torrents or when I'm going to eat etc...) Also it keeps the dust from entering the keyboard ;-)
I also took a look at the post where there should be a patch present, but I think it's for another problem: flickering screens.
For me it's a bug in intel driver or kernel, but still it's strange that KDE doesn't suffer from this!

Kernel Panic when closing laptop during shut down

It was the 2nd day I had my MBP and was jsut heading to sleep.
I had selected Apple > Shut Down to turn off the comp, and closed the laptop (I put the screen down and whatnot)
Few minutes passed, and I still saw the sleep light on for some reason. I opened the laptop back up, and there was the Kernel Panic screen.
I have no idea why it did this. Should I be worried?
It was just the 2nd day the MBP was in my possession and it would be really lame if problems were already arising THAT early.
MacBook Pro Mac OS X (10.4.7)

The machine hadn't completed the shutdown process when you shut the lid and effectively told it to sleep. The conflict between the two tasks is what caused the panic. Wait until you see the MBP actually shut down before closing the lid. There are also some out there who suggest letting it cool a few minutes before shutting the lid to save the screen, which kind of makes sense depending on how intensively you'd been running it prior.

Time machine disk failure after closing laptop lid

I have a Seagate 1.5 TB disk that I'm using for a time machine backup (USB). For a long time, I had the disk formatted wrong and had this problem, but I re-formatted it (per Apple's instructions) and have been trying again. Now, with it correctly formatted, I still have the same problem.
This is a laptop, so I don't leave the Time Machine application on, nor do I leave the TM disk connected all the time. If I plug in the drive, run TM, and eject the disk before closing the laptop lid, I do not have any issues. If, however, the laptop lid is shut at any point after TM completes, I have can never seem to eject nor unmount the TM disk. For example, last night I ran TM and left the machine open overnight. In the morning, the machine was used and shut per usual routine, except the drive was still connected. Now there is a critical failure on the drive (Disk Utility can do nothing to repair the drive and suggests re-formatting). Last night, the computer was plugged in and went to sleep after 15 minutes. I have changed no settings regarding what the computer does on lid shutdown.
What used to work to eject/unmount the drive is to shutdown the computer. Then I would unplug the drive before re-starting. Now, however, I had errors with the drive (Disk Utility) and went ahead with a force eject. That worked, and the drive still had errors that Disk Utility could not address.
I have a Macbook Pro (13-inch, mid 2012) running Mac OS X Version 10.9.2 (13C64); processor 2.9 GHz Intel Core i7 with 8 GB 1600 MHz DDR3 memory. My main drive is 750 GB (Macintosh HD). I also backup a firewire 400 drive to this TM drive, capacity 250 GB.
So, first question: why is this happening over and over and over? Is there anything I can do, apart from immediate removal of the TM drive after the backup completes, to ensure that it doesn't happen in the future? Should I be concerned that the disk is failing mechanically?
Thanks

I don't think you quite understand how Time Machine really works. But then hardly anyone does. Time Machine is intended to be left enabled always whether a backup drive is connected or not. What Time Machine cannot handle properly is a situation where the backup drive loses power for whatever reason. Time Machine treats this, as does the OS, as an improper disconnect of an external drive without being properly ejected. This in turn throws Time Machine a little bit of a loop.
For you I would suggest not using Time Machine. Instead use a third-party backup utility that you can either schedule or run manually as you wish. They will work with the same drive you have used for Time Machine, but you will need to first erase the Time Machine drive using Disk Utility. Please DO NOT try dragging the Time Machine backups to the Trash.
Here are some good backup utilities you can try:
Suggested Backup Software
1. Carbon Copy Cloner
2. Get Backup
3. Deja Vu
4. SuperDuper!
5. Synk Pro
6. Tri-Backup
Others may be found at MacUpdate. Each one can be used for a trial period. No need to pay for one until you've decided on which one you like best. I, for example, use Carbon Copy Cloner but please don't take that as a recommendation over the others. It's just my preference. All can be operated manually or can be set up to backup on a schedule you determine. Some can even be set up to backup as soon as the backup drive is connected.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.

External HDD and closing laptop lid

I have a Seagate external hdd connected to my Macbook Pro via Firewire 800. I use it exclusively for Time Machine backups. Can I just close the lid of my laptop when it's done backing up or do I have to eject the drive each time?
-Skifahrer7

Hi Skifahrer7,
You do not need to properly eject the external HD before closing the lid. When the machine wakes (on lid open) it will automatically remount the volume/drive.

T500 Closing Laptop Lid but no External Monitor Output

Hello everyone. I have a Lenovo T500 (WInXP) with an external monitor. I usually just want to use that external monitor and not the one for my laptop. However, every time I close the lid, the output to the monitor disappears a few seconds later. I've used google and searched this forum and found something similar, change the power settings. I changed it so it would "Do nothing" when the lid is closed. However, this does nothing and doesn't help me.
Is there a registry I have ti change?
Related links I've look at and tried
From Knowledge Base:
http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/Configuring-a-ThinkPad-T500-to-run-with-the...
Another person
http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T500-goes-to-sleep-with-lid-closed/td-p/307...
T500 2081 CTO ~ T9600 2.8GHz ~ WXP Pro 32bit ~ WSXGA+ 15.4 LED ~ATI 3650 ~ 4GB DDR3 RAM ~ 500GB WD 7200rpm
Camera ~ AT&T WWAN ~ CD/DVD Combo Drive ~ Intel WiFi 5300 AGN

I didn't see if your connected to power? there are different settings for both power and battery.
There are also bios settings for the display, since I am using my T500 now with an external LCD I have it set to external display or something like that. Its worth a shot.
BIOS>>CONFIG>DISPLAY read the output options.
IT Specialist and Consultant
Lenovo Tablet Evangelist
Current Machines: IdeaCentre A300, ThinkPad Tablet, IdeaPad U410, and Yoga 3 Pro Touch
Deutsche Community Comunidad en Español
Lenovo - the latest in DOtabs, DOpads, DOcentre's, DOstations and DOservers!

Xorg not functional after closing laptop lid.

Hi all!
Recently I've bought a monitor and I wanted to use my laptop more like a pc. But when I close the lid my both my screens go black. I'd like to use my computer with the lid closed normally.
Also, when I open the lid back I still have black screen only, both on laptop and monitor.
When I go to other terminal (ctrl+alt+F1..6) everything is fine on both screens. When I press alt+f7 and go back I have a black screen again.
I've looked at https://wiki.archlinux.org/index.php/Acpid and then looked at /etc/acpi/handler.sh, but it seems that I have no action assigned at lid closure so it should do nothing.
Here is the mentioned file:
#!/bin/sh
# Default acpi script that takes an entry for all actions
minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
set $*
case "$1" in
button/power)
echo "PowerButton pressed!">/dev/tty5
case "$2" in
PBTN|PWRF) logger "PowerButton pressed: $2" ;;
*) logger "ACPI action undefined: $2" ;;
esac
button/sleep)
case "$2" in
SLPB) echo -n mem >/sys/power/state ;;
*) logger "ACPI action undefined: $2" ;;
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
echo -n $minspeed >$setspeed
#/etc/laptop-mode/laptop-mode start
00000001)
echo -n $maxspeed >$setspeed
#/etc/laptop-mode/laptop-mode stop
esac
*) logger "ACPI action undefined: $2" ;;
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000) echo "offline" >/dev/tty5
00000001) echo "online" >/dev/tty5
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
echo "LID closed!">/dev/tty5
open)
echo "LID opened!">/dev/tty5
esac
logger "ACPI group/action undefined: $1 / $2"
esac
As you can see on the bottom I do not have anything assigned to lid action.
Any thoughts?
cheers,
kajman

I'm using xfce4.
Here's my /etc/X11/xorg.conf.d/10-monitor.conf:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
EndSection
Section "Monitor"
Identifier "Monitor0"
EndSection
Section "Device"
Identifier "Device0"
Driver "radeon" #Choose the driver used for this monitor
EndSection
Section "Screen"
Identifier "Screen0" #Collapse Monitor and Device section to Screen section
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24 #Choose the depth (16||24)
SubSection "Display"
Depth 16
Modes "1366x768_60.00" #Choose the resolution
Virtual 1920 1080
EndSubSection
EndSection
But i think that this configuration may be irrevelant.
When I connect my external monitor I always type
xrandr --auto
When unplugging the monitor I also type the same command.
Also I have turned my laptop's screen off (using settings/screen I've unchecked "use this output").
Last edited by kajman (2012-02-15 17:42:43)

Tecra M7 : new bios shutdowns the digitizer when closing the lid.

it took me a moment to find the problem : power saving ? attacking wacom ? no. some very stupid "feature" in the new bios from Toshiba.
quote from the toshiba download site:
*Version 1.70 - 2006-10-24*
*Incorporated Intel requirements for improved stability.*
**Made changes to ensure that the digitizer is not activated when the LCD is closed.**
*Version 1.60 - 2006-09-21*
*Changed the temperature parameters.*
i have no idea what they were thinking but since when i move i often close the lid, it's very, very annoying because i need to reboot in order to get my tablet working again. the more recent features are not a matter, i'll keep xp pro.
now give me a download link to get the version 1.6 of the tecra M7 bios. thanks in advance, i count on you.

Hello
Fact is that Toshiba offers all tablet PCs with WXP tablet edition and many additional software that offer full functionality when you use this tablet PC in tablet or normal mode.
So, in my opinion you should use tablet edition and install all available Toshiba tools and utilities.
I dont have much experience with tablet PCs but if you check Toshiba Europe support and download page under http://eu.computers.toshiba-europe.com > Support & Download you will see that your Tecra is fully supported for WXP tablet edition and you can download all necessary stuff.
Interesting is that there is also ready for download Installation instruction document with exact installation order.
You can also visit Canadian download page under http://209.167.114.38/support/Download/ln_bymodel.asp and see what is available there.
I really think you need to install all Toshiba specific tools and utilities to have full control and possibility to use it in both modes.
Sorry I cannot tell you more about all this.

Strange behavior when closing laptop

Hello all,
I'm posting this in a new thread because I don't believe it fits with the other current threads.
An odd thing happens every now and then when I close my laptop to put it to sleep.
I lift the lid again and a strange "veil" (darkening) cascades down my desktop and an opaque warning in various languages (Korean, Chinese, etc.) appears with the English translation on top that reads "You must restart your computer. Hold down the power button manually or click the Restart button."
This has happened a couple of times.
I had called Apple Care and the tech led me through resetting the PMU.
I think today, after work, I'm going to a local Apple Care repair shop and see if they can run some sort of diagnostic on my MBP.
Just wondering if anybody else has experienced this problem?

Hi,
What you are experiencing is called a "Kernel Panic" and it is basically a software crash at the deepest level of the operating system (the kernel). Frequently, kernel panics are due to problems with drivers. Have you installed any new software recently? Particularly if it is software related to a new hardware item.
Some maintenance steps may help you in resolving this issue. Verify your disk with Disk Utility, clear system and application caches with a tool like Onyx (downloadable fron the Apple site). Also, you can look at the system logs with the Console application in the Utilities folder. The information there can be quite cryptic, but it won't harm to have a look at some logs. There may be warnings or error messages that can give you an ideas as to what is wrong.
Good luck,
Juan-Pablo

Sets into sleep when closing le lid, even with the display connected

I have the problem, that when I close the lid of my MacBook, it goes to sleep mod. This even happens when I connect the display. Even following the steps on the Apple.com page, it still goes into sleep mode.
Please help me avoid this sleep mode problem, I want to use my display instead of my computers screen. (yes, I have a wireless keyboard and mouse, paired all of them)
Thanks

Welcome to the Apple Discussions!
You can't avoid it. This is the way it's supposed to work.
If you have the AC adapter plugged in, an external display plugged in and an external mouse and keyboard (USB or Bluetooth), you can WAKE the computer after it's gone to sleep with the lid closed. But it will go to sleep when you close it. This is detailed here:
http://support.apple.com/kb/HT3131
-Doug

MBP C2D Restarting when closing the lid

Every once in a while when I close the lid on my MBP, the computer restarts. When I open the lid it finishes the restart process and runs normally. Any ideas why this would all of a sudden start happening??

Wait for the light on the release button to start blinking before moving the laptop. The sudden motion sensor can act up as you move the laptop when it's still in the process of 'falling asleep'.

Screen not turning off when closing the lid

I have Windows 7 64-bit installed on my MacBook Air 13.3" as the only OS.
Everything is working great with the bootcamp drivers except that when I close the lid the screen does not turn off. I don't want to turn off the notebook but only want the screen to turn off when the lid is down. I have looked a lot for a solution and am not able to find anything which can solve this problem.
There is nothing in the power options that can be done. Bootcamp is supposed to recognize this by itself, but unfortunately it doesn't.
Does anyone know a work around for this?
Thank you

That is correct. I have noticed the same thing. Windows 7 gives better battery life on MacBook Air then Mac OSX.
I went to talk to a Genius about this, pretty useless, told me to wait for an update. It has been half a year but no update yet. This is the only problem with the Bootcamp drivers I have experienced. I have managed to live with it, but is still pretty annoying. I always once in a while think about finding a way to fix it, but there is nothing that can fix this problem. Unless someone at Apple sees and listens to what is going on in the online fourms and fix the problem.

Hard lockup when closing laptop lid (Linux 2.6.23)

Similar Messages

Maybe you are looking for