Acpi HP6710b lid close bug

Common problem with HP6710b is to froze on lid close.
I found on arch wiki solution for this crap....
echo "1" > /proc/acpi/video/C098/DOS
I need to place this command on startup.... but where?
During run rc.local /proc/acpi/video/C098/DOS does not exists

Would surprise me. Does it work when your computer is up and running? Replacing the C098 by an asterisk should do the job too I think, since that value can differ between models. Even better is replacing that value by the one your system uses .

Similar Messages

The ACPI LID close event catched only 50% of the time.

I'm using acpid with s2ram to have my laptop suspend to ram when I close the lid.
This works fine... 50% of the time.
Here is what happen:
If the s2ram command is commented in my /etc/acpi/actions/lid.sh, and I run an acpi_listen in a terminal, I can see that each time I close or open the lid, the last number is incremented by 1:
button/lid LID 00000080 00000001
button/lid LID 00000080 00000002
button/lid LID 00000080 00000003
button/lid LID 00000080 00000004
button/lid LID 00000080 00000005
If the s2ram is NOT commented in my /etc/acpi/actions/lid.sh and I run acpi_listen in a terminal, here is what I see (we start the test with the lid opened):
1) I close the lid. The acpi_listen shows:
button/lid LID 00000080 00000001
2) The s2ram is executed and the laptop suspends to ram. That is fine.
3) I open the lid. The laptop resumes fine. Nothing happens in the acpi_listen output.
4) The /proc/acpi/button/lid/LID/state shows "open"
Here after is where the problem is:
5) I close the lid. The acpi_listen DOES NOT SHOW ANYTHING :-( => The /etc/acpi/actions/lid.sh will not be launched and the laptop will not be suspended
6) The /proc/acpi/button/lid/LID/state shows "close"
7) I open the lid. The acpi_listen shows:
button/lid LID 00000080 00000002 => As one can see the last number is now 00000002 which shows that the acpid daemon never received anything for the second lid closure :-(
8) I close the lid. The acpi_listen shows:
button/lid LID 00000080 00000003
2) The s2ram is executed and the laptop suspends to ram. That is fine.
So in fact it works the first time then I need to close/open/close the lid to have it suspend.
Any idea ?
Thanks in advance,

Solved it by adding a file to /etc/pm/sleep.d/80-acpid with:
#!/bin/sh
case "$1" in
hibernate|suspend)
thaw|resume)
/etc/rc.d/acpid restart
*) exit $NA
esac
You have to call pm-suspend or hibernate followed by an ampersand (&) otherwise the acpid restart fails.
EDIT: Sorry for the necro. Thought it was 2012. Either way I solved my problem with this so someone else might find it useful.
Last edited by Revolt (2012-02-28 22:49:53)

Gnome3: Cannot set laptop lid close action

I've checked the lid closing sensor with watch /proc/acpi/button/lid/LID/state and the status changes without problems, but i can't set the lid closing action in gnome-tweak-tool or under power options. The laptop suspends only when an external monitor is not connected, i want to change it so it always suspends when the lid is closed.
How can I fix this?
Screenshots
power options
gnome-tweak-tool
Last edited by klingt.net (2014-03-19 20:28:05)

Seems to be a bug in gnome, gnome-tweak-tool outputs the following messages:
INFO : GSettings missing key org.gnome.settings-daemon.plugins.power (key lid-close-battery-action)
INFO : GSettings missing key org.gnome.settings-daemon.plugins.power (key lid-close-ac-action)
INFO : GSettings missing key org.gnome.settings-daemon.plugins.power (key lid-close-suspend-with-external-monitor)
I added the keys manually to the schema but gnome-tweak-tool show this error when i try to start it with the new keys:
GLib-GIO-ERROR **: Settings schema 'org.gnome.settings-daemon.plugins.power' does not contain a key named 'lid-close-battery-action'
There are more people having a similar problem.
Last edited by klingt.net (2014-03-23 10:12:03)

First LID close works, but state never changes back to open

I am using a Razer Blade 14" with linux-ck kernel (although I have tested in the main kernel and the issue remains).
I like to be able to close the lid to suspend. But it is not working properly.
Note: I am using
cat /proc/acpi/button/lid/LID0/state
to figure out the state of the lid.
When I start the laptop, the lid is correctly reported as open. When I first close it, the laptop goes to sleep, and when I open it again, it wakes up.
However, it is now reported as closed, although I just woke it up by opening the lid.
If I close the lid, it also does not suspend (I have to manually suspend).
A related bug: when I manually suspend, if I close the lid before it is done suspending, the laptop just hangs and needs to be hard-rebooted.
I am not sure what logs I can post here, but will provide anything that people think is useful.
Thanks in advance for the help!
Rodrigo
EDIT: After some investigation, the related bug seems to be unrelated. It seems like suspend randomly hangs, and I got lucky enough to hang on the few times I tried to close the lid while it was suspended.
Last edited by rgomes (2013-11-23 19:03:59)

dmesg doesn't report anything about the lid.
It it's of any use, here's the report when I close the lid for the first time, it suspends, I open it and it wakes back up, and I close and open it again (no action happens then).
[ 855.735445] PM: Syncing filesystems ... done.
[ 855.743716] PM: Preparing system for mem sleep
[ 855.743832] bbswitch: enabling discrete graphics
[ 856.273631] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 856.275441] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
[ 856.276063] PM: Entering mem sleep
[ 856.276116] Suspending console(s) (use no_console_suspend to debug)
[ 856.276512] wlan0: deauthenticating from 00:21:d8:49:a1:b3 by local choice (reason=3)
[ 856.303042] cfg80211: Calling CRDA for country: US
[ 856.303058] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 856.305387] sd 0:0:0:0: [sda] Stopping disk
[ 856.337313] mei_me 0000:00:16.0: suspend
[ 856.902051] PM: suspend of devices complete after 625.631 msecs
[ 856.902253] PM: late suspend of devices complete after 0.198 msecs
[ 856.913157] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[ 856.924119] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[ 856.946045] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[ 856.957112] PM: noirq suspend of devices complete after 54.857 msecs
[ 856.957425] ACPI: Preparing to enter system sleep state S3
[ 856.957634] PM: Saving platform NVS memory
[ 856.958313] Disabling non-boot CPUs ...
[ 856.959891] smpboot: CPU 1 is now offline
[ 856.961339] smpboot: CPU 2 is now offline
[ 856.963019] smpboot: CPU 3 is now offline
[ 856.964410] smpboot: CPU 4 is now offline
[ 856.965803] smpboot: CPU 5 is now offline
[ 856.967169] smpboot: CPU 6 is now offline
[ 856.968529] smpboot: CPU 7 is now offline
[ 856.968709] ACPI: Low-level resume complete
[ 856.968709] PM: Restoring platform NVS memory
[ 856.968709] Enabling non-boot CPUs ...
[ 856.968709] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 856.981274] Intel pstate controlling: cpu 1
[ 856.981329] CPU1 is up
[ 856.981355] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 856.993715] Intel pstate controlling: cpu 2
[ 856.993767] CPU2 is up
[ 856.993787] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 857.006143] Intel pstate controlling: cpu 3
[ 857.006193] CPU3 is up
[ 857.006215] smpboot: Booting Node 0 Processor 4 APIC 0x1
[ 857.018466] Intel pstate controlling: cpu 4
[ 857.018516] CPU4 is up
[ 857.018536] smpboot: Booting Node 0 Processor 5 APIC 0x3
[ 857.030876] Intel pstate controlling: cpu 5
[ 857.030919] CPU5 is up
[ 857.030936] smpboot: Booting Node 0 Processor 6 APIC 0x5
[ 857.043269] Intel pstate controlling: cpu 6
[ 857.043311] CPU6 is up
[ 857.043328] smpboot: Booting Node 0 Processor 7 APIC 0x7
[ 857.055674] Intel pstate controlling: cpu 7
[ 857.055712] CPU7 is up
[ 857.063860] ACPI: Waking up from system sleep state S3
[ 857.097072] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[ 857.119078] ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
[ 857.141070] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 857.163187] PM: noirq resume of devices complete after 98.903 msecs
[ 857.163364] PM: early resume of devices complete after 0.147 msecs
[ 857.163388] i915 0000:00:02.0: setting latency timer to 64
[ 857.163399] xhci_hcd 0000:00:14.0: setting latency timer to 64
[ 857.163433] mei_me 0000:00:16.0: irq 45 for MSI/MSI-X
[ 857.163449] ahci 0000:00:1f.2: setting latency timer to 64
[ 857.163521] ehci-pci 0000:00:1a.0: setting latency timer to 64
[ 857.163538] snd_hda_intel 0000:00:03.0: irq 46 for MSI/MSI-X
[ 857.163595] mei_me 0000:00:16.0: version message write failed
[ 857.163596] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
[ 857.163602] snd_hda_intel 0000:00:1b.0: irq 48 for MSI/MSI-X
[ 857.163717] ehci-pci 0000:00:1d.0: setting latency timer to 64
[ 857.468028] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 857.470879] ata1.00: configured for UDMA/133
[ 857.470917] sd 0:0:0:0: [sda] Starting disk
[ 857.494196] usb 1-13: reset full-speed USB device number 3 using xhci_hcd
[ 857.505658] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802225df540
[ 857.505659] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802225df5c0
[ 857.505660] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802225df580
[ 857.505660] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880222be98c0
[ 857.505661] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880222be9880
[ 857.658222] usb 1-14: reset high-speed USB device number 4 using xhci_hcd
[ 857.714527] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880037982080
[ 857.873499] PM: resume of devices complete after 712.120 msecs
[ 857.875809] PM: Finishing wakeup.
[ 857.875918] ath9k 0000:03:00.0: no hotplug settings from platform
[ 857.875810] Restarting tasks ... done.
[ 857.877445] video LNXVIDEO:00: Restoring backlight state
[ 857.877449] video LNXVIDEO:01: Restoring backlight state
[ 857.877452] bbswitch: disabling discrete graphics
[ 857.877462] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[ 858.699065] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[ 861.567705] wlan0: authenticate with c8:4c:75:d1:0f:ec
[ 861.582025] wlan0: direct probe to c8:4c:75:d1:0f:ec (try 1/3)
[ 861.783072] wlan0: send auth to c8:4c:75:d1:0f:ec (try 2/3)
[ 861.784100] wlan0: authenticated
[ 861.785101] wlan0: associate with c8:4c:75:d1:0f:ec (try 1/3)
[ 861.787455] wlan0: RX AssocResp from c8:4c:75:d1:0f:ec (capab=0x11 status=0 aid=1)
[ 861.787524] wlan0: associated
The only thing that seems to error is mei_me, but I don't know if that would be associated with the lid switch.
Last edited by rgomes (2013-11-22 17:59:44)

[SOLVED] Power button and laptop lid close rules not followed (KDE)

I'm using KDE 4.9.1, and the rules I set for the power button and lid close events in the KDE power management settings are not followed.
Currently, I have the power button press event set to trigger hibernation, and the lid close event set to turn off the display. Instead, the power button causes the laptop to power down immediately, as if the 'poweroff' command was issued. Closing the lid causes the system to suspend to ram.
This problem seemed to have started when I installed 'laptop-mode-tools' and 'acpid'. The problem persisted even when I uninstalled the said packages from the system. Most solutions on the internet involve adjusting the contents of files in /etc/acpi/, but that directory does not exist on my system. I also tried deleting the power management configuration files in the ~/.kde4/share/config directory, but that didn't fix the problem either.
Hibernation works if I choose 'hibernate' from the KDE menu.
Thanks for any help.
Last edited by rb3 (2012-09-28 05:46:56)

That's not a good solution.
Changes in systemd default behaviour are reasonable. It guarantees that if your graphical enviroment has no suspend support, it will still suspend when the lid is closed.
For example, closing the laptop lid at KDM login screen will now suspend the laptop. I remember a topic when someone nearly killed his notebook battery with overheat in that situation (the laptop did not suspend when the lid was closed at kdm screen).
This change also brings native (non-acpid) suspend support to lighweight desktop enviroments.
The source of the «double suspend» problem is in acynchronized update of systemd and KDE.
Updating KDE to 4.9.2 (which will be released in several days) will fix this without editing the config file.
Make sure you restore the original logind.conf after updating to KDE 4.9.2.
See:
http://lists.freedesktop.org/archives/s … 06604.html
https://bugs.kde.org/show_bug.cgi?id=307412
https://git.reviewboard.kde.org/r/106533/

Acpid no longer shutsdown on lid close

Previous to some recent updates acpid and the event I had would shutdown my laptop when I closed the lid. It no longer works. I have acpid running always as a daemon.
My /etc/acpi/handler.sh:
#!/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
My /etc/acpi/events/lid file:
event=button/lid (LID0)
action= sudo /sbin/shutdown -h now
Any ideas greatly appreciated.

Easiest way I found to suspend the system to memory (to make it sleep) is by using /sys/power/state (this doesn't work with all the machines).
$ cat /sys/power/state
will tell you the supported modes and what you are looking for is "mem". For example "disk" will do a hibernation but to recover you need to modify boot time kernel options.
If your system supports "mem" state, then all you need to do is
$ echo -n mem >/sys/power/state
and it should go to sleep, pressing power button or opening the lid should power it back on.
Now if that worked fine you can script it into the /etc/acpi/handler.sh:
button/lid)
case "$3" in
close)
#echo "LID closed!">/dev/tty5
echo -n mem >/sys/power/state
open)
#echo "LID opened!">/dev/tty5
esac
Note that we don't actually do anything on lid "open", since recovery is taken care by "BIOS".

Getting Arch to pm-suspend on lid close [SOLVED]

Hello,
I want Arch to suspend to RAM when I close my laptop lid. Here is what I did:
I installed pm-utils. I also followed the wiki and set it up so that I can just say
sudo pm-suspend
and the computer suspends with the need to type in your password.
Then, I installed acpid to have a way to capture acpi events.
Now, from what I read on the wiki and in these forums, I had to edit /etc/acpi/handler.sh
Here is the pertinent code that I edited:
button/lid)
#echo "LID switched!">/dev/tty5
logger "ACPI lid switched $1 $2"
if [ -n "`grep close /proc/acpi/button/lid/LID/state`" ]; then
/usr/sbin/pm-suspend
logger -s "ACPI lid closed";
elif [ -n "`grep open /proc/acpi/button/lid/LID/state`" ]; then
logger -s "ACPI lid opened"
else
logger -s "Couldn't detect Lid state"
fi
but the problem is that when I close the lid, it writes "ACPI lid closed" to the logfile, but instead of suspending the laptop, it just blanks the screen. Here is what it says in the log file
Apr 18 11:02:45 Treadstone logger: ACPI lid closed
Apr 18 11:02:45 Treadstone acpid: client connected from 4790[0:1000]
Apr 18 11:02:45 Treadstone acpid: 1 client rule loaded
Apr 18 11:02:47 Treadstone acpid: client 4790[0:1000] has disconnected
Apr 18 11:02:47 Treadstone logger: ACPI lid switched button/lid LID
Apr 18 11:02:47 Treadstone logger: ACPI lid opened
Any help will be greatly appreciated.
Last edited by mgangav (2009-04-18 19:46:01)

B wrote:You need check the pm-suspend log for pointers .
Ok, I checked the pm-suspend.log Here are it's contents:
Initial commandline parameters:
Sat Apr 18 11:45:03 EDT 2009: Running hooks for suspend.
/usr/lib/pm-utils/sleep.d/00auto-quirk suspend suspend: Adding quirks from HAL: --quirk-dpms-on --quirk-dpms-suspend --quirk-vbe-post --quirk-vbemode-restore --quirk-vbestate-restore --quirk-vga-mode-3
success.
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: Linux Treadstone 2.6.28-ARCH #1 SMP PREEMPT Sun Mar 8 10:18:28 UTC 2009 i686 Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz GenuineIntel GNU/Linux
Module Size Used by
ipv6 260340 10
i915 58372 2
drm 83880 3 i915
fuse 53020 2
joydev 11712 0
snd_seq_oss 31872 0
snd_seq_midi_event 8192 1 snd_seq_oss
snd_seq 49968 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 8204 2 snd_seq_oss,snd_seq
snd_pcm_oss 40192 0
uvcvideo 57736 0
compat_ioctl32 3072 1 uvcvideo
videodev 34176 1 uvcvideo
v4l1_compat 15364 2 uvcvideo,videodev
snd_mixer_oss 16512 1 snd_pcm_oss
arc4 3712 2
ecb 4608 2
b44 28560 0
ssb 40964 1 b44
pcmcia 35532 1 ssb
sdhci_pci 9088 0
sdhci 17028 1 sdhci_pci
container 5248 0
mii 6528 1 b44
iwl3945 91128 0
mmc_core 46876 1 sdhci
uhci_hcd 24592 0
yenta_socket 25996 1
rsrc_nonstatic 13056 1 yenta_socket
pcmcia_core 34452 4 ssb,pcmcia,yenta_socket,rsrc_nonstatic
snd_pcsp 11048 0
sg 26804 0
mac80211 161184 1 iwl3945
snd_hda_intel 412980 0
snd_hwdep 9092 1 snd_hda_intel
psmouse 55828 0
ehci_hcd 36876 0
video 18704 0
output 4608 1 video
snd_pcm 70020 3 snd_pcm_oss,snd_pcsp,snd_hda_intel
snd_timer 21384 2 snd_seq,snd_pcm
snd_page_alloc 10120 2 snd_hda_intel,snd_pcm
snd 50852 10 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcsp,snd_hda_intel,snd_hwdep,snd_pcm,snd_timer
soundcore 8160 1 snd
cfg80211 31760 2 iwl3945,mac80211
serio_raw 7172 0
usbcore 136848 4 uvcvideo,uhci_hcd,ehci_hcd
i2c_i801 10896 0
i2c_core 22804 1 i2c_i801
intel_agp 27836 1
agpgart 31572 3 drm,intel_agp
iTCO_wdt 12836 0
iTCO_vendor_support 4996 1 iTCO_wdt
acer_wmi 16320 0
rfkill 11596 4 iwl3945,acer_wmi
led_class 5508 2 iwl3945,acer_wmi
wmi 7848 1 acer_wmi
evdev 11296 7
thermal 17180 0
processor 41388 3 thermal
fan 6276 0
button 7824 0
battery 12036 0
ac 6020 0
rtc_cmos 12332 0
rtc_core 17564 1 rtc_cmos
rtc_lib 4480 1 rtc_core
ext3 127112 2
jbd 46996 1 ext3
mbcache 8708 1 ext3
sr_mod 16708 0
cdrom 35360 1 sr_mod
sd_mod 26904 5
pata_acpi 6016 0
ata_piix 23300 4
ata_generic 6788 0
libata 157856 3 pata_acpi,ata_piix,ata_generic
scsi_mod 102164 4 sg,sr_mod,sd_mod,libata
total used free shared buffers cached
Mem: 2065460 482372 1583088 0 60728 194692
-/+ buffers/cache: 226952 1838508
Swap: 2931852 0 2931852
success.
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: /bin/stty: standard input: Inappropriate ioctl for device
success.
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90chvt suspend suspend: success.
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
/usr/lib/pm-utils/sleep.d/95led suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend suspend: success.
/etc/pm/sleep.d/99lock suspend suspend: xscreensaver-command: warning: $DISPLAY is not set: defaulting to ":0.0".
No protocol specified
xscreensaver-command: can't open display :0.0
Returned exit code 1.
Sat Apr 18 11:45:05 EDT 2009: Inhibit found, will not perform suspend
Sat Apr 18 11:45:05 EDT 2009: Running hooks for resume
/usr/lib/pm-utils/sleep.d/98smart-kernel-video resume suspend: success.
/usr/lib/pm-utils/sleep.d/95led resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
/usr/lib/pm-utils/sleep.d/90clock resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90chvt resume suspend: success.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg resume suspend: /bin/stty: standard input: Inappropriate ioctl for device
success.
/usr/lib/pm-utils/sleep.d/01grub resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
/usr/lib/pm-utils/sleep.d/00auto-quirk resume suspend: success.
From what I can tell, it seems that xscreensaver doesn't want to start for some reason. By the way here are the contents of my /etc/pm/sleep.d/
#!/bin/bash
case $1 in
suspend)
xscreensaver-command -l
resume)
echo "Coming out of sleep mode"
echo "Doing something else"
esac
I wonder if xscreensave has anything to do with this?

ACPI button/lid problem

Hello all,
I have been running Arch on this laptop for quite some time now. Recently though I had to do a reinstall of it because I messed it up while trying to do something. Anyway, I got everything working except for the lid problem, i have the age old when I close it, it freezes. I have installed ACPI and it recognizes the Lid event, however it is still frozen I checked the /var/log/messages.log and this is what showed up:
Jun 19 11:33:12 UsbArch logger: ACPI group/action undefined: video / VID1
Jun 19 11:33:12 UsbArch logger: ACPI group/action undefined: video / VID
All I can tell is that it doesnt recognize the laptop screen or something. On the last install acpi worked like a charm, I dont know why it is not working now. Any help would be much appreciated. Thank you, Levi.

I bet it does not freeze.
Test it, follow these steps exactly as they are written:
Start xwindows
open a terminal
close the lid
open the lid
wait for a second
then type this
xset dpms force on
then press enter
Your monitor should come back on.
If this works you will need to edit your /etc/acpi/actions/lm_lid.sh file
also make sure that you install laptop_mode and acpid
here is the content of my lm_lid.sh
#!/bin/sh
test -f /usr/sbin/laptop_mode || exit 0
#lid button pressed/released event handler
#From: http://gentoo-wiki.com/HOWTO_Automatically_turn_off_your_monitor
if grep -q open /proc/acpi/button/lid/LID/state
then
XAUTHORITY="$( ps -C xinit f|sed 's/.*-auth $.*$serverauth.*/\1Xauthority/p' )" /usr/bin/xset -display :0.0 dpms force on
/usr/sbin/laptop_mode auto
/usr/bin logger dpms force on
else
XAUTHORITY="$( ps -C xinit f| sed -n 's/.*-auth $.*$serverauth.*/\1Xauthority/p' )" /usr/bin/xset -display :0.0 dpms force off
/usr/bin logger dpms force off
fi
Last edited by timetrap (2008-06-20 20:20:51)

MacBook Pro lid closes

I purchased a MacBook Pro 17" a couple of weeks ago now and noticed that when the MacBook is at a 90 degree angle the lid closes.
For example when I'm using my MacBook on my lap and have knees up the screen closes. It seems to be the hinges are loose. Is this normal? Or are the hinges week and should I contact apple?
*sorry if this is not the right field within the forum but I thought it's related to display just more hardware side**
Thanks for any response.

And I quote- If the position of the screen is affected by gravity, there's a problem with the hinges.
90degrees aka balanced, gravity is pulling downward equally, disturb that balance aka move the mac and the screen falls, call apple.
If it's balanced at 90degrees without problem, 91-140deg and 89-0deg will still have issues. Proper hinges should not let the screen move at all (or very little) when you move your mac...
I work with My MBP screen at a 110degree angle, if the hinges were loose on mine, the screen would continually fall to 140deg.

Urgent: Shut down when lid closes problem

My Mabook pro / mid 2010 / Yosemite 10.10 shuts down when lid closes. This is new in the last few days, not after any system updates. It wont restart after lid opens again, unless repeatedly holding down power button for long periods. Strangely, the sleep light is on before I open the lid, but once lid is open, it's completely off.
Does anyone know the cause and/or fix for this? I'm really worried it's the beginning of the end, and I rely on this machine for work and need to travel in a few days! Thanks in advance for any trouble shooting tips.

Just to clarify; when I say "this is new" I mean the problem, not the laptop.

[systemd] Toggle whether lid close makes laptop sleep

Before migrating to systemd, I had a nice setup using laptop-mode where I would use the laptop "Sleep key" as a toggle for whether closing the lid put the laptop into sleep mode or not. This was just a few lines reading/writing to a file ~/.lidsleep, which I hacked into the laptop-mode shell scripts. Having switched to systemd, and wanting to do the same the "systemd way", I've come up short.
What I have managed to do is temporarily disable the "lid -> sleep" action, with this command:
# systemd-inhibit --what=handle-lid-switch cat
where the function of the final `cat` is to be a program that does not return until I type ^C.
I basically have two questions:
1) How can I make systemd perform an arbitrary command when I press the "Sleep key"?
2) Short of something like running `pgrep systemd-inhibit && pkill systemd-inhibit || systemd-inhibit --what=handle-lid-switch cat`, what is the best way to setup a toggle like this?
Final bonus question, if these two are answered:
My previous setup also included restoring the toggle to its default state (lid -> sleep : yes) when resuming from hibernate (not suspend). How would I do this using systemd?

As WonderWoofy suggests, why not just tell systemd to not handle lid close or the sleep key (not sure it does that but if it does) and continue to use your existing solution with laptop mode tools?
systemd is not, that I know of, supposed to handle stuff like key presses and it is deliberately designed so that you can have a more sophisticated system hand events such as lid closing and so on. Moreover, it doesn't replace the remaining functionality of laptop-mode tools so assuming you used that for other things too, you'll need it anyway. That is, I can't even see how this would let you uninstall laptop-mode tools if you've been using it without giving up a bunch of other stuff. Could you explain why you want to do it without laptop-mode tools etc.?

How to trigger lid close programatically?

Is there a way to trigger the lid close action programmatically with a script or through terminal? I can achieve this by placing a small magnet near the SD slot on my macbook pro, but obviously magnets and hard drives don't mix.
Thanks guys.

I see, in that case you don't want to sleep your Mac. Can you not simply turn down the brightness on the internal display?
If you use an external keyboard you can use your MacBook Pro in "Clamshell mode": Mac notebooks: How to use your computer in closed clamshell (display closed) mode with an external display. The requirement is to have an external keyboard, and its power adapter must be connected.

ProBook 4710s - sound disabled after lid close

Hello, I have a problem: When I connect headphones to the laptop, it works fine, until I close the lid. Then the sound stops working. I have tried to find it in Windows Control Panel (I have Windows 7), but there wasn't such an option. The sound is disabled only when it runs from battery; when I connect it to the electricity, I can use it with an external monitor and speakers and it works fine (even if the lid is closed). I have set "No action" after lid close, so the laptop doesn't go to sleep mode. It just stops playing sound.

Hi,
Download audio driver from here.
Intructions how to install it in XP.
Extract this driver with Winrar.
Open Device manager and expand the Sound, video and game controllers section.
Right click on Either the High Definition Audio Device if you have the generic Microsoft drivers, or the Conexant High Definition SmartAudio 221 if you have older Conexant drivers and choose "Update Driver Software..."
Click Browse my computer for driver software, then click "Let me pick from a list of device drivers on my computer"
Click "Have Disk..." then Browse to the folder where the drivers were extracted .......\XP32 for 32-bit XP. Click OK.
Select one of the "Conexant High Definition SmartAudio 221" models in the list, there will be multiple identical entries.
Click Next, and you're done.
I'm not sure which one from the list will work for You. On CQ60 few users confirmed then first one worked for them.
** Say thanks by clicking the "Thumb up" icon which is on the left. **
** Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue. **

[SOLVED] Laptop Lid Close

I've been using arch on my laptop for a while now and have been having problems when I close the lid on my laptop. What I want my a laptop to do is nothing except simply turn the screen off when the lid is shut. However, at the moment when I close the lid, it doesn't suspend or sleep or anything, the screen turns off, but when I open the lid, I am presented with a black screen(lit up). I have to turn my laptop on and off to use it again, or change tty and then restart the x-screen. Any help would be much appreciated. Thanks in advance.
Last edited by compty (2013-12-30 08:15:22)

Thanks,
I'm using acpid to handle the event and in the /etc/systemd/logind.conf I have only the following line uncommented:
HandleLidSwitch=ignore
Which to my understanding should prevent systemd from controlling the event yes?
And at the moment I currently have the default acpi setup,
so the anything event:
# Pass all events to our one handler script
event=.*
action=/etc/acpi/handler.sh %e
And the following hander.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
logger "ACPI group/action undefined: $1 / $2"
esac
# vim:set ts=4 sw=4 ft=sh et:
I know I need to add the commands etc to perform the various functions, but I thought that this handler.sh would do nothing?
I'm also using xfce. My laptop is a Dell Inspiron 7720.
Any advice on what I might be doing wrong?

[SOLVED]laptop suspend when LID close, even set HandleLidSwitch=ignore

i've modify
HandleLidSwitch=ignore
systemctl restart systemd-logind.service
But when close LID, it suspend.
Then i click some key on keybord , it come back.
/var/log/everything:
Mar 21 11:20:59 localhost logger: ACPI action undefined: PNP0C0A:00
Mar 21 11:21:06 localhost dbus-daemon[317]: dbus[317]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.229" (uid=1000 pid=22838 comm="systemctl stop laptop-mode.service ") interface="org.freedesktop.systemd1.Manager" member="StopUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Mar 21 11:21:13 localhost systemd[1]: Stopped Laptop Mode Tools.
Mar 21 11:21:15 localhost logger: ACPI action undefined: PNP0C0A:00
Mar 21 11:21:37 localhost systemd[1]: Reloading.
Mar 21 11:21:37 localhost systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
Mar 21 11:21:37 localhost [358276.901952] systemd-fstab-generator[22955]: Failed to create mount unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
Mar 21 11:21:47 localhost logger: ACPI action undefined: PNP0C0A:00
Mar 21 11:22:02 localhost logger: ACPI action undefined: PNP0C0A:00
Mar 21 11:22:23 localhost logger: LID opened
Mar 21 11:22:31 localhost systemd[1]: Starting Sleep.
Mar 21 11:22:31 localhost systemd[1]: Reached target Sleep.
Mar 21 11:22:31 localhost systemd[1]: Starting Suspend...
Mar 21 11:22:31 localhost logger: LID closed
Mar 21 11:22:31 localhost systemd-sleep[23159]: Suspending system...
Mar 21 11:22:32 localhost kernel: [358330.844138] PM: Syncing filesystems ... done.
Mar 21 11:22:32 localhost kernel: [358331.305611] PM: Preparing system for mem sleep
Mar 21 11:22:47 localhost kernel: [358331.412348] Freezing user space processes ... (elapsed 0.02 seconds) done.
Mar 21 11:22:47 localhost kernel: [358331.439427] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Mar 21 11:22:47 localhost kernel: [358331.452995] PM: Entering mem sleep
Mar 21 11:22:47 localhost kernel: [358331.453150] Suspending console(s) (use no_console_suspend to debug)
Mar 21 11:22:47 localhost kernel: [358331.466400] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
Mar 21 11:22:47 localhost kernel: [358331.749415] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Mar 21 11:22:47 localhost kernel: [358331.749546] sd 0:0:0:0: [sda] Stopping disk
Mar 21 11:22:47 localhost kernel: [358332.106062] i915 0000:00:02.0: power state changed by ACPI to D3hot
Mar 21 11:22:47 localhost kernel: [358332.242667] PM: suspend of devices complete after 497.619 msecs
Mar 21 11:22:47 localhost kernel: [358332.243146] PM: late suspend of devices complete after 0.473 msecs
Mar 21 11:22:47 localhost kernel: [358332.243658] xhci_hcd 0000:03:00.0: wake-up capability enabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.269361] ehci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.282850] ehci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.309313] PM: noirq suspend of devices complete after 66.169 msecs
Mar 21 11:22:47 localhost kernel: [358332.309974] ACPI: Preparing to enter system sleep state S3
Mar 21 11:22:47 localhost kernel: [358332.310597] PM: Saving platform NVS memory
Mar 21 11:22:47 localhost kernel: [358332.317339] Disabling non-boot CPUs ...
Mar 21 11:22:47 localhost kernel: [358332.320383] smpboot: CPU 1 is now offline
Mar 21 11:22:47 localhost kernel: [358332.323050] smpboot: CPU 2 is now offline
Mar 21 11:22:47 localhost kernel: [358332.325460] smpboot: CPU 3 is now offline
Mar 21 11:22:47 localhost kernel: [358332.327433] ACPI: Low-level resume complete
Mar 21 11:22:47 localhost kernel: [358332.327483] PM: Restoring platform NVS memory
Mar 21 11:22:47 localhost kernel: [358332.328066] Enabling non-boot CPUs ...
Mar 21 11:22:47 localhost kernel: [358332.331542] smpboot: Booting Node 0 Processor 1 APIC 0x1
Mar 21 11:22:47 localhost kernel: [358332.355520] CPU1 is up
Mar 21 11:22:47 localhost kernel: [358332.358971] smpboot: Booting Node 0 Processor 2 APIC 0x2
Mar 21 11:22:47 localhost kernel: [358332.587540] CPU2 is up
Mar 21 11:22:47 localhost kernel: [358332.590984] smpboot: Booting Node 0 Processor 3 APIC 0x3
Mar 21 11:22:47 localhost kernel: [358332.605172] CPU3 is up
Mar 21 11:22:47 localhost kernel: [358332.610534] ACPI: Waking up from system sleep state S3
Mar 21 11:22:47 localhost systemd[1]: Time has been changed
Mar 21 11:22:47 localhost systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
Mar 21 11:22:47 localhost acpid: client 328[0:0] has disconnected
Mar 21 11:22:47 localhost systemd-sleep[23159]: System resumed.
Mar 21 11:22:47 localhost kernel: [358332.611098] i915 0000:00:02.0: power state changed by ACPI to D0
Mar 21 11:22:47 localhost kernel: [358332.661492] ehci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.688143] ehci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.715055] sdhci-pci 0000:01:00.0: MMC controller base frequency changed to 50Mhz.
Mar 21 11:22:47 localhost kernel: [358332.741549] xhci_hcd 0000:03:00.0: wake-up capability disabled by ACPI
Mar 21 11:22:47 localhost kernel: [358332.741712] PM: noirq resume of devices complete after 130.745 msecs
Mar 21 11:22:47 localhost kernel: [358332.743008] PM: early resume of devices complete after 0.206 msecs
Mar 21 11:22:47 localhost kernel: [358332.743043] i915 0000:00:02.0: setting latency timer to 64
Mar 21 11:22:47 localhost kernel: [358332.743146] mei 0000:00:16.0: irq 46 for MSI/MSI-X
Mar 21 11:22:47 localhost kernel: [358332.743195] ehci_hcd 0000:00:1a.0: setting latency timer to 64
Mar 21 11:22:47 localhost kernel: [358332.743215] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
Mar 21 11:22:47 localhost kernel: [358332.743301] snd_hda_intel 0000:00:1b.0: irq 49 for MSI/MSI-X
Mar 21 11:22:47 localhost kernel: [358332.743481] ehci_hcd 0000:00:1d.0: setting latency timer to 64
Mar 21 11:22:47 localhost kernel: [358332.743508] ahci 0000:00:1f.2: setting latency timer to 64
Mar 21 11:22:47 localhost kernel: [358332.743611] iwlwifi 0000:02:00.0: RF_KILL bit toggled to enable radio.
Mar 21 11:22:47 localhost kernel: [358332.744213] mei 0000:00:16.0: wd: failed to find the client
Mar 21 11:22:47 localhost kernel: [358332.811881] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Mar 21 11:22:47 localhost kernel: [358332.981624] usb 4-1.2: reset high-speed USB device number 3 using ehci_hcd
Mar 21 11:22:47 localhost kernel: [358333.061455] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 21 11:22:47 localhost kernel: [358333.061936] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
Mar 21 11:22:47 localhost kernel: [358333.061944] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD] (Node ffff880149a55cf8), AE_NOT_FOUND (20120913/psparse-536)
Mar 21 11:22:47 localhost kernel: [358333.062035] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
Mar 21 11:22:47 localhost kernel: [358333.062041] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF] (Node ffff880149a55d20), AE_NOT_FOUND (20120913/psparse-536)
Mar 21 11:22:47 localhost kernel: [358333.062591] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
Mar 21 11:22:47 localhost kernel: [358333.062599] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD] (Node ffff880149a55cf8), AE_NOT_FOUND (20120913/psparse-536)
Mar 21 11:22:47 localhost kernel: [358333.062690] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
Mar 21 11:22:47 localhost kernel: [358333.062696] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF] (Node ffff880149a55d20), AE_NOT_FOUND (20120913/psparse-536)
Mar 21 11:22:47 localhost kernel: [358333.062739] ata1.00: configured for UDMA/100
Mar 21 11:22:47 localhost kernel: [358333.074899] sd 0:0:0:0: [sda] Starting disk
Mar 21 11:22:47 localhost kernel: [358333.246448] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
Mar 21 11:22:47 localhost kernel: [358333.253820] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Mar 21 11:22:47 localhost kernel: [358333.391539] restoring control 00000000-0000-0000-0000-000000000101/0/2
Mar 21 11:22:47 localhost kernel: [358333.391541] restoring control 00000000-0000-0000-0000-000000000101/1/3
Mar 21 11:22:47 localhost kernel: [358333.391543] restoring control 00000000-0000-0000-0000-000000000101/2/6
Mar 21 11:22:47 localhost kernel: [358333.391544] restoring control 00000000-0000-0000-0000-000000000101/3/7
Mar 21 11:22:47 localhost kernel: [358333.391545] restoring control 00000000-0000-0000-0000-000000000101/5/9
Mar 21 11:22:47 localhost kernel: [358333.693001] PM: resume of devices complete after 950.103 msecs
Mar 21 11:22:47 localhost kernel: [358333.694210] PM: Finishing wakeup.
Mar 21 11:22:47 localhost kernel: [358333.694214] Restarting tasks ... done.
Mar 21 11:22:47 localhost kernel: [358333.706265] video LNXVIDEO:01: Restoring backlight state
Mar 21 11:22:47 localhost logger: ACPI action undefined: PNP0C0A:00
Mar 21 11:22:47 localhost acpid: client connected from 328[0:0]
Mar 21 11:22:47 localhost acpid: 1 client rule loaded
Mar 21 11:22:47 localhost systemd[1]: Started Suspend.
Mar 21 11:22:47 localhost systemd[1]: Service sleep.target is not needed anymore. Stopping.
Mar 21 11:22:47 localhost systemd[1]: Stopping Sleep.
Mar 21 11:22:47 localhost systemd[1]: Stopped target Sleep.
Mar 21 11:22:47 localhost systemd[1]: Starting Suspend.
Mar 21 11:22:47 localhost systemd[1]: Reached target Suspend.
Mar 21 11:22:50 localhost logger: ACPI action undefined: PNP0C0A:00
Last edited by whille (2013-03-21 05:26:24)

You are still using acpid. That is triggering the suspend, not logind.
Edit: Also use [ code ] [ /code ] tags (without the spaces) for things like your logs. Hit the "quote" button if you are more of a visual learner.
This is how you use code tags.
Last edited by WonderWoofy (2013-03-21 03:38:53)

Acpi HP6710b lid close bug

Similar Messages

Maybe you are looking for