You are not logged in.
Pages: 1
Hello,
I have already seen these threads https://bbs.archlinux.org/viewtopic.php?id=146852 and https://bbs.archlinux.org/viewtopic.php?id=34858.
However I cannot get this to work, my computer suspend when I close the lid but I have to press the power button in order to wake up.
I cannot see any LID label in the file /proc/acpi/wakeup. I know that with acpi_listen I get lid close and lid open.
The command cat /proc/acpi/button/lid/LID0/state gives "state: open" so I guess my LID is called LID0.
Thank you
Last edited by coincoin (2013-11-08 01:12:31)
Offline
Which desktop environment are you running? Are you using the console? KDE? Gnome? Xfce4?
I ask, because all of those (except the console) may have their own mechanisms for sleep/suspend.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Doesn't systemd handle it by default? It ignores inhibitors for LID (unlike other ways of suspending). Don't know why systemd would only put it to sleep and not wake it up, though.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
I would like to hook to this post; i already opened one but this is specific; i recently bulk update my arch box and now resume from lid open does not work anymore. I don't use apcid by default and was usinf pure systemd (wm envirnoment) to handle acpi inputs.
If i start the acpid daemon i can see both LID CLOSE and LID OPEN from the listener. I have no LID0 (name of my lid) in /proc/acpi/wakeup but don't remamber if it was there before the update.
I woudl like to track down why the lid is not handled by systemd anymore; i already downgrade systemd, upower and kernel 3.11-6 from the previous update without luck.
I also noticed the battery is now charging to 100% and i have to solve this too but is for another thread (it was charging till 80% before).
...why not
Offline
Thanks for your replies.
I use Openbox as a window manager no desktop manager.
Like j0lly, the acpid dameon can notice both LID close and open. I know the name of my LID is LID0 but I cannot track it in /proc/acpi/wakeup. Well j0lly if you can fix it let me know ;p
Offline
I have the exact situation with a vaio pro.
This machine is purely managed by systemd, no acpid, no DE, nothing.
/proc/acpi/button/lid/LID0/state reports proper state, but LID0 not listed in /proc/acpi/wakeup
It was working in my last boot, now its driving me crazy.
Offline
I have the same problem with my Vaio Pro too.
It used to work and all of a sudden it stopped working.
Anyone has found a solution?
Offline
Hey guys yesterday I recovered my laptop's hard drive to its factory state (With windows 8 and everything). I booted to Windows 8 and checked and opening the lid did wake the laptop.
I updated all the drivers in Windows 8 (I don't think there was a BIOS update).
Now! I am booting my laptop with an external hard drive which has Arch Linux on it and opening the lid does wake the device! I do not know if I remove everything on my laptop's hard drive and install Linux again what will happen but at least it is working now.
Maybe all I need to do was to boot into Windows and test the lid there and then boot back into Linux.
Offline
Pages: 1