Arch Linux

Lockheed

Member

Registered: 2010-03-16

Posts: 1,520

Hibernation issue

I have a problem with hibernate script. This is what happens:

1. I run dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate
2. System hibernates nicely and quickly.
3. I power the computer back on
4. System resumes nicely (%s goes really fast)
5. Instead of desktop, I see black screen with blinking "_" sign in the top left corner.

At this point I have to hard-reset the computer.

ewtoombs

Member

Registered: 2009-07-23

Posts: 28

Re: Hibernation issue

Why are you writing your own hibernate script? uswsusp comes with scripts of their own. 's2disk' will hibernate, I believe.

Lockheed

Member

Registered: 2010-03-16

Posts: 1,520

Re: Hibernation issue

1. Because that's the Arch wiki way.
2. Because

s2disk: Could not mount tmpfs on /proc/16203. Reason: Operation not permitted

thayer

Fellow

From: Vancouver, BC

Registered: 2007-05-20

Posts: 1,560

Website

Re: Hibernation issue

1. Because that's the Arch wiki way.
2. Because

s2disk: Could not mount tmpfs on /proc/16203. Reason: Operation not permitted

You mean the arch wiki article that's flagged as poorly written?

FWIW I've always used pm-utils, also the Arch Wiki way, and I've had few issues. Basically, you just add the resume path to /boot/grub/menu.lst and then run:

# pm-hibernate

Last edited by thayer (2011-05-14 15:08:05)

---

thayer williams ~ cinderwick.ca

kgas

Member

From: Qatar

Registered: 2008-11-08

Posts: 718

Re: Hibernation issue

I have similar issue with pm-hibernate only with netbooks. It resumes from hibernation but have a black rectangle on the top of every thing. A screen shot shows every thing normal and log files did not help much to identify the issue. It started after kernel version 2.6.32 iirc.

Lockheed

Member

Registered: 2010-03-16

Posts: 1,520

Re: Hibernation issue

So I tried pm-utils but it also involves script and when I run it, I get

Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.