Please re-enable build of s2ram binary

[Mikael Gerdin]

Please re-enable build of the s2ram-binary, it has some configuration options that are missing with the "/etc/acpi/sleep.sh"-way of suspending, primarily the VBE Mode option instead of VBE Save, which is the only way I've ever been able to resume my laptop from suspend-to-ram.

** Update **
Are you sure you don't need s2both? s2both is included in the latest uswsusp / μswsusp
http://suspend.sourceforge.net/intro.shtml says:
"s2both combines the funtionalities of s2ram and s2disk and it's very useful when the battery is almost depleted. s2both write system snapshot to the swap (just like s2disk) but then put the machine into STR (just like s2ram). If the battery has enough power left you can quickly resume from STR, otherwise you can still resume from disk without loosing your work. "

[Russ Dill (russ-dill)]

I'm in the same boat. s2ram works with '-f -p'. Why remove this?

Also, pm-utils looks for s2ram/s2disk in /usr/sbin, but its in /sbin

[psernetz (patrick-sernetz-com)]

My Satellite 6100 pro suspends real nice with s2disk... the normal sleep.sh method fails. Btw. it works just one time and then it fails and let the laptop crash while it is shutting down.

[Peter Meiser (meiser79)]

Hi, could you try improving Ubuntu's way of suspend-to-ram instead of using s2ram? Just a question, no offence.

[Gabriel Ambuehl (gabriel-ambuehl)]

I actually did post working acpi-support files for the hardware I have on the
wiki. There are some corner cases that seem to be handled better by s2ram,
though. And Ubuntu infrastructure can't do s2both for all I know.

[Russ Dill (russ-dill)]

On 9/13/07, Whoopie <email address hidden> wrote:
> Hi, could you try improving Ubuntu's way of suspend-to-ram instead of
> using s2ram? Just a question, no offence.
>

Seems like a rather abrasive solution. Take away a working, packaged
solution that works, and ask users to fix another solution that
doesn't work.

[Gabriel Ambuehl (gabriel-ambuehl)]

> Seems like a rather abrasive solution. Take away a working, packaged
> solution that works, and ask users to fix another solution that
> doesn't work.

Besides, pmi explicitely *has* support for powersaved, which in turn does work
best with uswsusp. Why acpi-support doesn't use s2ram by default, I don't
understand ;)

[Roman Kreisel (roman-kreisel+launchpad)]

I must agree with the others: re-enable the build of s2ram. First of all, there is no reason NOT to build it. If the only reason is "You don't need s2ram, there are other ways to do it", why do you offer uswsusp at all? There are also other ways to hibernate the system.

The next thing is, that if you remove s2ram, do it correctly:
 - Remove the s2ram-part from the package description
 - Remove the s2ram-part from the README.Debian
 - Implement the "-n"-funcionality from s2ram into s2both, so that users can verifiy if their machine is s2both (and s2ram)-ready

Regards
Roman

[Jochen Kemnade (jochenkemnade)]

I second the argument. As far as I understand, the "it can be done otherwise" argument holds for the main section, but does not apply to universe. Feel free to correct me if I'm wrong.
I'd also like s2ram to be re-enabled.

[ingo (ingo-steiner)]

The same from me: please give us back s2ram!

s2ram is the only tool to suspend my PC. The ACPI-functions in GNOME do not work neither with Gusty nor Feisty.

s2ram works perfectly on my ASUS M2N-E and my motherboard even was put onto the whitelist for s2ram by the developer. And now with Gusty s2ram has been removed.

Please add s2ram to the Ubuntu-package,
Ingo

[ingo (ingo-steiner)]

Info for you all:

you can force Synaptic to install the 'old' uswsusp 0.3 from Feisty's universe rpository - then s2ram works perfectly here on Gusty as well!

[ingo (ingo-steiner)]

even better solution is to just install the original Debian-package on Gusty which contains version 0.71.
Works perfect here and since my M/B is on the whitelist, I even do not require the '-f' option any more

[Savvas Radevic (medigeek)]

I see that s2ram is integrated in powersaved
http://packages.ubuntu.com/gutsy/admin/powersaved

" Powersave
s2ram is integrated in the latest version of powersaved, there are some configuration variables that let you select the workaround if your machine is not yet in the whitelist. They are explained here. "
http://en.opensuse.org/S2ram#Up_to_date_packages_for_various_distributions

But I have no clue how to direct you to use this.
Otherwise, have you considered using s2both?

"s2both combines the funtionalities of s2ram and s2disk and it's very useful when the battery is almost depleted. s2both write system snapshot to the swap (just like s2disk) but then put the machine into STR (just like s2ram). If the battery has enough power left you can quickly resume from STR, otherwise you can still resume from disk without loosing your work."
http://suspend.sourceforge.net/intro.shtml

[Jean-Baptiste Quenot (jbq-caraldi)]

Confirmed, downgrading to Feisty's uswsusp fixes the problem.

[trikrasne (trikrasne)]

please re-enable build of the s2ram-binary, it was the only working method to suspend for me on HP NX8220 with feisty.

downgrading to Feisty's uswsusp (or upgrading to debian uswsusp 0.7) doesn't work for me out of the box. are there any additional steps i must do?

[trikrasne (trikrasne)]

oh, it works for me to!!!
but it's important to first istall gutsy's default uswsusp-0.6 and only than debian's uswsusp-0.7.

[Jérémy Subtil (bigmadwolf)]

To make things definitely clear I sent a mail to the developer which had removed the build of s2ram from the package uswsusp, asking him a kind of justification.

Matthew Garrett answered:
We use pm-utils in 8.04, and if things work with s2ram and not that then it's a bug that should be filed rather than something that should be worked around using a package that isn't installed by default. Keeping s2ram in the archive just confuses the issue horribly.

So I tried pm-utils, and it works perfectly for me. Please give up the Debian/Feisty package and try pm-suspend in the new package.

[ingo (ingo-steiner)]

> Keeping s2ram in the archive just confuses the issue horribly

This way reminds me somewhat on the 'Redmond attitudes':

a) collect information from what is available around and build a own piece of software out of that.
b) if it works without major complaints try to prohibit other solutions to be used.
c) do not disclose details of the proprietary solution.

To proove type 'man s2ram' and type 'man pm-suspend'
Currently with Ubuntu we still do have a solution: use Debian's uswsusp

But this is probably the way to fix Bug#1 ?

[ingo (ingo-steiner)]

Forgot to attach the link to uswsusp 0.7-1:

http://packages.debian.org/sid/uswsusp

[trikrasne (trikrasne)]

pm-suspend works fine for me with the generic ATI driver. but not wih fglrx, which is why i wanted to use uswsusp so bad in the first place. so for me - no help.

[Jeff Fortin Tam (kiddo)]

I dont use (have) a swap. This feature is vital to me.

[ingo (ingo-steiner)]

It is absolutely crazy:

Meanwhile I have 6GB of good ECC-RAM and do not need a swap anymore!
(with an USV there is no danger of power loss) and s2ram works perfect.

If writing those 6GB to the hard-disk it will take about 2.5 minutes (40MB/s) and re-reading another 2.5 min.
Alltogether by far longer than shutdown and reboot!

So s2both and s2disk are obsolete!

[Bob/Paul (ubuntu-launchpad-bobpaul)]

>Keeping s2ram in the archive just confuses the issue horribly.
Here's a solution -- put the s2ram binary in it's own package. Have both pm-utils and swsusp dependent on this third package. The pm-suspend script can execute the s2ram binary rather than introduce more bugs by trying to re-implement it.

The other acceptable solution is to leave s2ram in swsusp, since that is part of the swsusp project and just have 2 tools that do the same job. I'm sorry you have trouble receiving bug reports on your fork of s2ram, but when I install swsusp with apt-get I expect to get everything that I would get building from source on my own (minus stuff that's excluded cause it's non-free) just as I expect from any other package I've ever installed with apt-get. Nobody forced you to fork the package, please let me continue to use the original. That's why I use free software in the first place.

[ingo (ingo-steiner)]

> That's why I use free software in the first place.

Absolutely right!
Just silently removing s2ram from uswsusp package without proper documentation of that modification, may even violate the GPL.

[Benson Margulies (bimargulies)]

add another vote for putting this back.

[Benson Margulies (bimargulies)]

Well, that would be nice, too.

On Wed, Mar 5, 2008 at 1:42 PM, Savvas Radević <email address hidden> wrote:

> ** Description changed:
>
> Please re-enable build of the s2ram-binary, it has some configuration
> options that are missing with the "/etc/acpi/sleep.sh"-way of
> suspending, primarily the VBE Mode option instead of VBE Save, which is
> the only way I've ever been able to resume my laptop from suspend-to-
> ram.
> +
> + ** Update **
> + Are you sure you don't need s2both? s2both is included in the latest
> uswsusp / μswsusp
> + http://suspend.sourceforge.net/intro.shtml says:
> + "s2both combines the funtionalities of s2ram and s2disk and it's very
> useful when the battery is almost depleted. s2both write system snapshot to
> the swap (just like s2disk) but then put the machine into STR (just like
> s2ram). If the battery has enough power left you can quickly resume from
> STR, otherwise you can still resume from disk without loosing your work. "
>
> --
> Please re-enable build of s2ram binary
> https://bugs.launchpad.net/bugs/134238
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Jeff Fortin Tam (kiddo)]

Savvas Radević,
I *can NOT* use s2both. ONLY s2ram will work with me. As explained in previous comments. Hibernating+suspend just does NOT work, whereas suspend does.

[ingo (ingo-steiner)]

> Are you sure you don't need s2both? s2both is included in the latest uswsusp / μswsusp

s2both (like s2disk) is useless for me:

writing my 6GB of ECC-RAM to disk takes by far longer than shutdown and reboot!
For what did I invest in ECC-RAM and a UPS?

Ingo

[DaveAbrahams (boostpro)]

Those looking for s2ram might want to try http://leoslog.wordpress.com/2008/03/29/putting-the-thinkpad-t60p-to-sleep-in-ubuntu-hardy-heron-beta/

[Marian Sigler (maix42)]

+1 vote for re-adding s2ram.

@DaveAbrahams: Ehr, no, I will not add a debian repo to my ubuntu.

[Saeid Zebardast (saeidzebardast)]

please re-adding s2ram. I need s2ram. +1.

[Alan Jenkins (aj504)]

Yay, I'm glad to see this confirmed & nominated, if not yet implemented.

I'd just like to add: when "s2ram" was removed, it was left in the "command-not-found" data. That means if uswsusp is not installed and you try to run "s2ram", it lies to you - telling you that s2ram can be found in the uswsusp package.

[sebastien teyssier (steyssier)]

+1 vote. s2ram works for me since Edgy ! I'm on Hardy and pm-utils can't make my computer suspend 'out of the box'

[robert114 (robertreems)]

Ingo, I've got a ASUS M2N mobo as well. but with the uswsusp 0.7-1 package from http://packages.debian.org/sid/uswsusp my machine still won't return from suspend properly. I just got a black screen, did you have this issue as well? If so could you send me a e-mail? <email address hidden> I'd like to fix my issue.

Thanx

[Sune Keller (sune-keller)]

The following is the case on my IBM ThinkPad X32 running Intrepid Ibex on September 10th:

I couldn't suspend with pm-suspend but it worked with pm-suspend-hybrid and pm-hibernate. Also, the suspend option had gone missing from my Gnome Power Manager menu.
pm-is-supported --suspend failed while --hibernate and --suspend-hybrid succeeded.
After some investigation I found that the reason was that /usr/lib/pm-utils/pm-functions chose to try and use uswsusp methods in general (s2disk, s2both, s2ram) for the various suspend functions because of the presence of s2disk:
"
    # Try userspace software suspend
    if [ -c /dev/snapshot ] && command_exists s2disk ; then
        SLEEP_MODULE="uswsusp"
    fi
"
Now s2ram doesn't come with uswsusp any longer, so later on the command will not succeed and the check needs to be altered.

Removing uswsusp fixed this problem for me, because /usr/lib/pm-utils/pm-functions chose the default "kernel" method for suspend instead now that s2disk didn't exist any longer, and now it works fine for me.
Gnome Power Manager still doesn't show the suspend command in its menu, but that might show up after a reboot.
uname -a yields "Linux skx 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 GNU/Linux" for what it's worth.

[Eric Drechsel (ericdrex)]

Great sluething, Sune! I was almost as far along, having figured out that pm-is-supported --suspend was failing due to missing s2ram, but hadn't made the connection that removing uswsusp might make the problem go away. I can confirm that gnome-power-manager regrows the suspend option after an "/etc/init.d/dbus restart". I think we should file a bug as "installing uswsusp causes failure of pm-is-supported --suspend".

[Felipe Figueiredo (philsf)]

For those of you who can't suspend with pm-suspend, check out the workaround in bug #212660, and see if it helps.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/212660/comments/15

In my case, it worked without the chmod command.

[Jaba (jpylvanainen)]

I have working suspend with default ubuntu installation. Although hibernate is not working.
It seems that it saves the state to disk and shutdowns the computer, but by boot there's
no mention of resume or anything else that has something to do with suspend.

With uswsusp I can have working hibernate but not suspend.

I have MSI Wind u100 and Ubuntu Intrepid as operating system.

It would be nice to have both suspend and hibernate to work at the same time.

Has oneone solution to this.

Thanks

[Alan Jenkins (aj504)]

Jaba wrote:
> I have working suspend with default ubuntu installation. Although hibernate is not working.
> It seems that it saves the state to disk and shutdowns the computer, but by boot there's
> no mention of resume or anything else that has something to do with suspend.
>
> With uswsusp I can have working hibernate but not suspend.
>
> I have MSI Wind u100 and Ubuntu Intrepid as operating system.
>
> It would be nice to have both suspend and hibernate to work at the same
> time.
>
> Has oneone solution to this.
>
> Thanks
>

What is your swap partition (or do you use a swap file instead)?

What does your GRUB line look like?

uswsusp uses a configuration file to find the swap partition, which is
then copied to the initramfs. Without uswsusp, there is supposed to be
a "resume=dev" boot option, and resume_offset=N for swap files). I
don't think the standard Ubuntu hibernation supports swap files, so it
doesn't generate a resume_offset=N option.

If that's your problem, please open a new bug (or find an existing one)
for swap file support.

I guess the problem with suspend to ram not working with uswsusp is this
bug, that you don't have an s2ram binary. But uswsusp isn't exactly a
Ubuntu supported package; it's not looking like this will be fixed any
time soon :).

[Chow Loong Jin (hyperair)]

On Mon, 2008-10-20 at 09:55 +0000, Jaba wrote:
> I have working suspend with default ubuntu installation. Although hibernate is not working.
> It seems that it saves the state to disk and shutdowns the computer, but by boot there's
> no mention of resume or anything else that has something to do with suspend.
>
> With uswsusp I can have working hibernate but not suspend.
>
> I have MSI Wind u100 and Ubuntu Intrepid as operating system.
>
> It would be nice to have both suspend and hibernate to work at the same
> time.
>
> Has oneone solution to this.
>
> Thanks
>
Replace /usr/lib/pm-utils/module.d/uswsusp with the attached. Then, try
again. If it still doesn't work, restart the computer and try again.
--
Chow Loong Jin

[Aliov (aliov)]

Please readd s2ram, and provide up to date version of the only one software that does sleep my computer correctly.

I was waiting interpid to see new version of uswsusp with s2ram!

[tetzlav (tetzlav-web)]

+1

[diehardlinux (diehardlinux)]

I must conclude with the others on this issue. I two would find use for the command: s2ram. Like others here and abroad I experience a similar problems when attempting to go into "suspend mode" my machine shutdown instead of suspending, and in the process it does not recover from the suspend. I have read other issues which may link to the third party Nvidia drivers, but research & results seem to be inclusive.

I am now using an abnormal amount of power and my system occasional does not power up correctly after a full shutdown in Ubuntu 8.04. As of today I will continue to use an abnormal amount of power. I really hope the community is able to reinstate the support in question.

Thanks for reading,
John

[Alan Jenkins (aj504)]

diehardlinux wrote:
> I must conclude with the others on this issue. I two would find use for
> the command: s2ram. Like others here and abroad I experience a similar
> problems when attempting to go into "suspend mode" my machine shutdown
> instead of suspending, and in the process it does not recover from the
> suspend. I have read other issues which may link to the third party
> Nvidia drivers, but research & results seem to be inclusive.
>

s2ram isn't a cure-all. Please don't assume it would work on your
system just because the normal pm-utils fail.

If you _have_ tested s2ram and it works, you should still report your
current suspend problems as a separate bug. If no-one knows about it,
no-one can fix it :-).

Thanks
Alan

[Launchpad Janitor (janitor)]

This bug was fixed in the package uswsusp - 0.8-1.1ubuntu1

---------------
uswsusp (0.8-1.1ubuntu1) jaunty; urgency=low

  * Merge from Debian unstable (LP: #241115, #132603), remaining Ubuntu
    changes:
    - debian/control: modify libsplashy1-dev to libusplash-dev in Build-Depends
      field
    - debian/rules: don't run debconf-updatepo in clean target
    - add usplash support, I hope the patch is good
  * s2ram is built in Ubuntu again (LP: #134238).
  * debian/control: modify splashy (>= 0.3) to uspash in Suggests field.

uswsusp (0.8-1.1) unstable; urgency=low

  * Non-maintainer upload to fix pending l10n issues.
  * Remove extra and useless debian/po/ff/ directory
  * Debconf translation updates:
    - Japanese. Closes: #489939
    - German. Closes: #493747
    - French. Closes: #493771
    - Romanian. Closes: #493772
    - Galician. Closes: #494050
    - Finnish. Closes: #494087
    - Italian. Closes: #494096
    - Basque. Closes: #494277
    - Basque. Closes: #494277
    - Czech. Closes: #494410
    - Swedish. Closes: #494412
    - Russian. Closes: #495412
    - Portuguese. Closes: #495451
    - Spanish. Closes: #495499
    - Slovak. Closes: #495516

uswsusp (0.8-1) unstable; urgency=low

  [ Michael Biebl ]
  * New upstream release (closes: #459844).

  [ Tim Dijkstra ]
  * The "Sorry this took so long, but a baby and a house got in the way" - release
  * Add patch for LFS (closes: #451249)
  * Remove use of grep in initramfs (closes: #443434)
  * New models in the whitelist (closes: #473160, #467109, #475367, #448484,
    #458566, #458566, #470314, #487656, #444810)
  * Ask shutdown_method at low priority (closes: #448536)
  * Change CONFIG_SOFTWARE_SUSPEND to CONFIG_HIBERNATION (closes: #452030, #470861)
  * Update whitelist for MacBook1,1 (closes: #458308)
  * Make CLI arguments consistent, update manpages (closes: #471120)
  * Document shutdown_method (closes: #490568)
  * Debconf translation updates (closes: #470578, #491418, #489939)
    Thanks: Vincent Zweije [nl], Martin Ågren [sv], Hideki Yamane [jp]
  * Do not hang when user supplies an empty passphrase. Thanks Mikko Rapeli
    for the patch. (closes: #457963)
  * Fix typo in README (closes: #448450)
  * Remove libzf licence from copyright file (closes: #474389)
  * Disable erroneous comress ratio output. This is fixed upstream by now, but
    it's not worth the trouble backporting IMHO. (closes: #443677, #443818)
  * Disable improved key handeling patch. This version is not working
    anymore. New version is applied upstream, no time for backporting before
    lenny, sorry.
  * Remove hack for devfs style node names (closes: #450680)

uswsusp (0.7-1.1) unstable; urgency=low

  * Non-maintainer upload to fix longstanding l10n issues and FTBFS.
  * Fix FTBFS by (temporarily?) build-depending on glib. Thanks to
    Bart martens for the patch. Closes: #456841
  * Debconf templates and debian/control reviewed by the debian-l10n-
    english team as part of the Smith review project. Closes: #445590
  * [Debconf translation updates]
    - Romanian. Closes: #446434
    - Galician. Closes: #446608
    - Czech. Closes: #446669
    - Vietnamese. Closes: #446997
    - Finnish....

[Thomas Hotz (thotz-deactivatedaccount)]

Is this bug now fully fixed for you?

[Alan Jenkins (aj504)]

Installing uswsusp on 12.04 now gets me s2ram. (Which is effectively deprecated / unmaintained / obsolete now, but hey :). That is, it still works for existing machines, but new whitelist entries are no longer being added).