You are not logged in.
Pages: 1
Aspire One D250
After the updates I recently installed a few days ago, my suspend is not working properly. When I close my laptop lid it suspends as normal then it resumes as normal when I open the lid, but after about 10 seconds the laptop goes back to sleep and I need to wake it again. It then runs normal from then on.
I dont see any errors in pm-suspend.log... where else should I be looking?
Offline
I've noticed the same on my laptop. Kernel 3.0, no problems. 3.1 breaks suspend. I think it's due to ACPI being unable to tell the difference between lid open and close events. If you run "acpi_listen" and then close and open the lid, as soon as lid open registers, it suspends again. So far, I've been unable to fix this. I'm stumped as well.
Laptops:
MSI GS60 Ghost
Asus Zenbook Pro UX501VW
Lenovo Thinkpad X120e
Offline
I've noticed the same on my laptop. Kernel 3.0, no problems. 3.1 breaks suspend. I think it's due to ACPI being unable to tell the difference between lid open and close events. If you run "acpi_listen" and then close and open the lid, as soon as lid open registers, it suspends again. So far, I've been unable to fix this. I'm stumped as well.
Yup just tested that and as soon as lid open registered it went back to sleep... hope someone has a quick solution :\
Offline
I added "close" to the end of the event and it no longer wakes up when the lid is opened which helps a ton. Going to try to find a way to make it wake on lid open later tonight. :\
event=button/lid (LID close)
action=/usr/sbin/pm-suspend
Offline
I just downgraded back to 3.0.7 for the time being.
Offline
I believe that acpi registers the state of the lid into "/proc/acpi/button/LID" or something like that, if that helps. I tried setting up an if/than command using awk in the handler.sh that looks for opened/closed in this file and handles the event based on that. It didn't work.
Last edited by TheHebes (2011-11-16 02:11:40)
Laptops:
MSI GS60 Ghost
Asus Zenbook Pro UX501VW
Lenovo Thinkpad X120e
Offline
Sounds very similar to a problem I used to have. The solution is likewise similar.
Offline
This is how I changed my /etc/acpi/handler.sh:
...
button/lid)
case $(cat /proc/acpi/button/lid/LID0/state | awk '{print $2}') in
closed) pm-suspend ;;
open) ;;
esac
#echo "LID switched!">/dev/tty5
;;
...
Works OK now.
Offline
I had the same issue with my laptop. The problems seems to be that they changed the "button/lid" event to run twice, once for "closed" and once for "open".
button/lid)
case $3 in
close)
pm-suspend
esac
;;
That is my "button/lid" event. (The awk in the previous post would only be required if acpi_listen doesn't have anything to specify whether the laptop is being opened or closed)
Offline
I had the same issue with my laptop. The problems seems to be that they changed the "button/lid" event to run twice, once for "closed" and once for "open".
button/lid) case $3 in close) pm-suspend esac ;;
That is my "button/lid" event. (The awk in the previous post would only be required if acpi_listen doesn't have anything to specify whether the laptop is being opened or closed)
I can confirm that this fixes the issue.
Laptops:
MSI GS60 Ghost
Asus Zenbook Pro UX501VW
Lenovo Thinkpad X120e
Offline
Pages: 1