s2ram? (SOLVED)

Message

cybrjackle · Post by **cybrjackle** » Thu Feb 15, 2007 4:32 pm

https://bugs.gentoo.org/show_bug.cgi?id=156431

How would I build this?

cybrjackle · Post by **cybrjackle** » Thu Feb 15, 2007 6:17 pm

http://pastebin.ca/357439

Code: Select all

# emerge --digest -av suspend

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] sys-apps/suspend-0.5  0 kB [1] 

Total: 1 package (1 new), Size of downloads: 0 kB
Portage overlays:
 [1] /usr/local/portage

Would you like to merge these packages? [Yes/No] yes
>>> Creating Manifest for /usr/local/portage/sys-apps/suspend

>>> Emerging (1 of 1) sys-apps/suspend-0.5 to /
 * suspend-0.5.tar.gz MD5 ;-) ...                                         [ ok ]
 * suspend-0.5.tar.gz RMD160 ;-) ...                                      [ ok ]
 * suspend-0.5.tar.gz SHA1 ;-) ...                                        [ ok ]
 * suspend-0.5.tar.gz SHA256 ;-) ...                                      [ ok ]
 * suspend-0.5.tar.gz size ;-) ...                                        [ ok ]
>>> Creating Manifest for /usr/local/portage/sys-apps/suspend
 * checking ebuild checksums ;-) ...                                      [ ok ]
 * checking auxfile checksums ;-) ...                                     [ ok ]
 * checking miscfile checksums ;-) ...                                    [ ok ]
 * checking suspend-0.5.tar.gz ;-) ...                                    [ ok ]
>>> Unpacking source...
>>> Unpacking suspend-0.5.tar.gz to /var/tmp/portage/sys-apps/suspend-0.5/work
 * Applying suspend-0.5-build.patch ...

 * Failed Patch: suspend-0.5-build.patch !
 *  ( /usr/local/portage/sys-apps/suspend/files/suspend-0.5-build.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/sys-apps/suspend-0.5/temp/suspend-0.5-build.patch-6472.out


!!! ERROR: sys-apps/suspend-0.5 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_unpack
  ebuild.sh, line 751:   Called qa_call 'src_unpack'
  environment, line 3099:   Called src_unpack
  suspend-0.5.ebuild, line 24:   Called epatch '/usr/local/portage/sys-apps/suspend/files/suspend-0.5-build.patch'
  eutils.eclass, line 341:   Called die

!!! Failed Patch: suspend-0.5-build.patch!
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/sys-apps/suspend-0.5/temp/build.log'.

!!! This ebuild is from an overlay: '/usr/local/portage'
kainos suspend # cat /var/tmp/portage/sys-apps/suspend-0.5/temp/suspend-0.5-build.patch-6472.out
***** suspend-0.5-build.patch *****

===================================

PATCH COMMAND:   patch -p0 -g0 -E --no-backup-if-mismatch < /usr/local/portage/sys-apps/suspend/files/suspend-0.5-build.patch

===================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: suspend-0.5/Makefile
|===================================================================
|--- suspend-0.5.orig/Makefile
|+++ suspend-0.5/Makefile
--------------------------
No file to patch.  Skipping patch.
4 out of 4 hunks ignored
===================================

PATCH COMMAND:   patch -p1 -g0 -E --no-backup-if-mismatch < /usr/local/portage/sys-apps/suspend/files/suspend-0.5-build.patch

===================================
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 4 hunks FAILED -- saving rejects to file Makefile.rej
===================================

PATCH COMMAND:   patch -p2 -g0 -E --no-backup-if-mismatch < /usr/local/portage/sys-apps/suspend/files/suspend-0.5-build.patch

===================================
missing header for unified diff at line 5 of patch
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: suspend-0.5/Makefile
|===================================================================
|--- suspend-0.5.orig/Makefile
|+++ suspend-0.5/Makefile
--------------------------
No file to patch.  Skipping patch.
4 out of 4 hunks ignored
===================================

PATCH COMMAND:   patch -p3 -g0 -E --no-backup-if-mismatch < /usr/local/portage/sys-apps/suspend/files/suspend-0.5-build.patch

===================================
missing header for unified diff at line 5 of patch
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: suspend-0.5/Makefile
|===================================================================
|--- suspend-0.5.orig/Makefile
|+++ suspend-0.5/Makefile
--------------------------
No file to patch.  Skipping patch.
4 out of 4 hunks ignored
===================================

PATCH COMMAND:   patch -p4 -g0 -E --no-backup-if-mismatch < /usr/local/portage/sys-apps/suspend/files/suspend-0.5-build.patch

===================================
missing header for unified diff at line 5 of patch
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: suspend-0.5/Makefile
|===================================================================
|--- suspend-0.5.orig/Makefile
|+++ suspend-0.5/Makefile
--------------------------
No file to patch.  Skipping patch.
4 out of 4 hunks ignored

baeksu · Post by **baeksu** » Fri Feb 16, 2007 4:04 am

That patching part works for me. Remove the source file from /usr/portage/distfiles and try again.

cybrjackle · Post by **cybrjackle** » Mon Feb 19, 2007 6:21 am

Apparently I wasn't copying it over correctly and the format was messing up.

Thanks for checking I got it to build.

cybrjackle · Post by **cybrjackle** » Mon Feb 19, 2007 6:26 am

I should mention, s2ram ROCKS!

First time and it worked!

[UK]Superdude · Post by **[UK]Superdude** » Thu Jul 26, 2007 12:40 pm

Agreed! I'm surprised it has not been included in gentoo in some way or another. From the bug report it looks like a personality clash rather than anything technical. Grabbing it from sourceforge and make etc works out of the box surely an ebuild can cope with this.

baeksu · Post by **baeksu** » Fri Jul 27, 2007 6:06 am

i'd been using this since March. Back then the ebuild didn't work for me, so I built it by hand. Worked perfectly with powersaved, both s2disk and s2ram.

I recently bought a new PC, and I'm trying to configure the suspend again.

From what I remember, s2disk requires a special initrd for resuming, and the ebuild does not seem to do that. Is anyone using s2disk from this package, and if so, how did you do it?

[edit:] Also, anyone tried splashy? This packages is supposed to support that to give you some eye candy during suspend/resume.

[edit2:] s2ram is not working for me (machine powers off), but I managed to get s2disk (hibernation) to work. I'll try to get splashy working next week.

baeksu · Post by **baeksu** » Wed Aug 08, 2007 1:54 pm

Ok, I got s2ram and s2disk both working now. This package is great!

I really think this package should be included in portage. It works (IMO) better than suspend2, as you don't need to patch the kernel. It should work with all kernels without recompiling anything.

Also, with liblzf, s2disk is a lot faster than suspend2 for me. s2ram takes literally 3 seconds to resume from.

The building process for s2disk is a bit queer, though, as you have to manually edit the Makefile before building it. I don't know how this would be done through ebuilds, but I'm thinking of writing up a HowTo for manually getting these things running, if anyone is interested.

deno · Post by **deno** » Fri Aug 10, 2007 9:35 pm

baeksu wrote:Ok, I got s2ram and s2disk both working now. This package is great!

I really think this package should be included in portage. It works (IMO) better than suspend2, as you don't need to patch the kernel. It should work with all kernels without recompiling anything.

Also, with liblzf, s2disk is a lot faster than suspend2 for me. s2ram takes literally 3 seconds to resume from.

The building process for s2disk is a bit queer, though, as you have to manually edit the Makefile before building it. I don't know how this would be done through ebuilds, but I'm thinking of writing up a HowTo for manually getting these things running, if anyone is interested.

Well, I am. suspend2 doesn't work very well here.

Phlogiston · Post by **Phlogiston** » Sun Sep 02, 2007 11:52 pm

@baeksu: How did you get s2ram running? Here it does not even suspend correctly. The machine just dies in a way. I'm using the cvs version of the code btw. If anyone is interested in a working tarball, let me know.

baeksu · Post by **baeksu** » Tue Sep 04, 2007 3:56 am

Phlogiston wrote:@baeksu: How did you get s2ram running? Here it does not even suspend correctly. The machine just dies in a way. I'm using the cvs version of the code btw. If anyone is interested in a working tarball, let me know.

How do you launch s2ram? For me, it did really just work, I even managed to wake up the machine through usb mouse.

Also, I see they released 0.7 yesterday, so the cvs version might be a bit different 0.5 that I've been using. For one I see there's no documentation (except for Suse) in the 0.7 tarballs.

@deno: I wrote up a howto on my blog (link), but it's for the 0.5 version (and the splash doesn't work). I'm going to have a look suspend-0.7 to see how to get it working as well.

Phlogiston · Post by **Phlogiston** » Tue Sep 04, 2007 9:37 am

baeksu wrote:
Phlogiston wrote:@baeksu: How did you get s2ram running? Here it does not even suspend correctly. The machine just dies in a way. I'm using the cvs version of the code btw. If anyone is interested in a working tarball, let me know.
How do you launch s2ram? For me, it did really just work, I even managed to wake up the machine through usb mouse.

The problem here is that it does not work with fglrx loaded.

s2disk works, but only when compiled without compression support. But its slower than suspend2 here, so I dropped it.

Also, I see they released 0.7 yesterday, so the cvs version might be a bit different 0.5 that I've been using. For one I see there's no documentation (except for Suse) in the 0.7 tarballs.

@deno: I wrote up a howto on my blog (link), but it's for the 0.5 version (and the splash doesn't work). I'm going to have a look suspend-0.7 to see how to get it working as well.

The documentation indeed sucks. I mean not even the settings in the suspend.conf file are documented.

Here the 0.5 did not compile. Maybe I'll check out 0.7 too.

baeksu · Post by **baeksu** » Wed Sep 05, 2007 10:18 am

Ok, so the documentation on the tarball has been included. More interestingly, there's new ebuilds in bugs.gentoo.org, though I haven't tried them yet.

It seems there's work being done on making this more accessible to Gentoo users as well (with fbsplash support coming soon hopefully).

@Phlogiston: compression is moving from liblzf to lzo, maybe that's why you couldn't compile it with compression support?

Personally, I'm still in suspend-0.5, but as soon as fbsplash is added, I'm going to try building with ebuilds from the bug. Hopefully that'll be soon.