You are not logged in.
Hello
After an update (one or two days ago) i've noticed that i can no longer resume from a suspended state.
I've tried the whole archwiki pm-utils stuff about mkiniciop with resume hook, without autodetect and an i tried to use the resume /swap parameter in grup menu.list.
Sadly, nothing helped.
The pm-suspend log is clean of errors and the kernel log does not show anything strange.
Also the pm-is-supported --suspend shows me an 0, which is would me correct.
Can somebody help?
Regards, Archdove
Last edited by Archdove (2012-01-06 09:29:23)
Offline
Have a look in pacman's log, what was all entailed in that update. Maybe that gives an indication where to look.
The resume /swap parameter you mention only has to do with hibernation to disk (and not suspend to RAM). Does that work?
How do you suspend (pressing the button, using a desktop manager menu)?
You don't write what happens when you try to resume. Blank screen?
Offline
Haven't tried hibernate yet. Will do this tomorrow (today actually).
I suspend running pm-suspend as root or simply closing the screen. I'm running Gnome3 with the gnome-shell.
What happens is, that to suspending process seems to work fine. (the log says that anyway).
When i open the screen again, i can hear something of what i think is the hard drive, an then nothing is happening. The screen remains black.
I'm working on a Lenovo W510 and the LED on the power button is blinking. (Softly not energic)
Looking into the Log and Trying Hibernate is a task for tomorrow. Thanks for your reply.
Lg, Archdove
EDIT:
I've tried hibernate and it works even worse than suspend. The computer does not shut down but there is a blinking underscore in the top left corner.
On the 12.12 was the last successful awake from suspend so e copied the log of that day to pastie: http://pastie.org/3025321
Unfortunately i can't find anything special in the log. On the day after however was a Kernel update and i think its quiet possible that this is the cause.
EDIT2:
Here's the log of the 13.12: http://pastie.org/3027336
First Failed resume was then.
Last edited by Archdove (2011-12-16 17:33:56)
Offline
So. For everyone facing the same Problem. Just downgrade the Kernel to 3.1.4
Her a link to the package: http://arm.konnichi.com/core/os/x86_64/ … pkg.tar.xz
A bug report has been created. Hopefully they patch it soon.
Offline
Also for downgrading, pacman may still have your old (working) package in the cache as described here:
https://wiki.archlinux.org/index.php/Do … g_Packages
It's better to use that, if available, since it saves you from picking a wrong one (e.g. 64 bit on a 32bit machine..).
@Archdove: Thanks for uploading the logs, but I don't see anything special in those as well.
Offline
Unfortunately i've already deleted the cache. My System partition is far to small and i have yet to find the time to change that.
There is a way to prevent packages from updating right? Is this what i'm looking for? https://bbs.archlinux.org/viewtopic.php?id=35627
Nothing to be done from within pacman?
Anyway, thanks for the help. Cheers!
Offline
You are welcome. Yes, thats how to do it. See also:
https://wiki.archlinux.org/index.php/Pa … g_upgraded
which actually matches your case.
Offline
I have the same problem, and hopefully will the downgrading work but I can't risk breaking my system at the moment because I need some work done. So could you link to your bugreport so that I can check it before I have time to test it, because maybe a future update will fix it!
Thanks
Offline
No good either with linux-3.1.6-1
Still going with 3.1.4-1
Possible Workaround:
kernel /vmlinuz-linux root=/dev/sda5 ro resume=/dev/sda2 vga=0 hpet=disable
(the hpet=disable part)
Last edited by Archdove (2011-12-31 17:47:45)
Offline
I have the same problem after updating into 3.1.6. Not only suspend but also current cpu policy doesn't work. The cpu policy what I have configed when using battery mode should be "powersave" but becomes "ondemand"automatically.
I have to downgrade back to 3.1.5, now everything works well.
Last edited by hooluupog (2012-01-01 07:13:40)
Offline
I have reinstalled linux 3.1.6.1, now evrything goes with me very well. ![]()
Offline
I'm having the same problem (unable to resume from suspend) with both 3.1.5 and 3.1.6.
I initially suspected it may have to do with the Catalyst driver. However, I have tried both catalyst-hook and catalyst-daemon for handling the module rebuild after upgrade. I even tried removing and reinstalling the driver after kernel upgrade.
I'm currently 'stuck' on 3.1.4, which isn't a problem really, but it would be nice if I could figure out what's causing the problem instead of waiting for each kernel update.
EDIT: Looks like I posted before searching the forums thoroughly enough.
It appears this issue is related with the following two threads:
Not resuming after suspend
kernel 3.1.5 kills suspend to ram
Adding the "hpet=disable" to my kernel line seems to have solved (or at least provided a workaround) for the issue.
Last edited by achilleas.k (2012-01-02 14:59:14)
Offline
This should be fixed in 3.1.7
http://www.kernel.org/pub/linux/kernel/ … eLog-3.1.7
Offline
Great to know. Thanks!
Offline
It works for me now with 3.1.7-1! ![]()
Offline
3.1.7-1 Fixed it. Thanks!
Offline