Comment 3 for bug 292256

Wow.. I tried so many things to get this working again.
There are bugreports about this issue everywhere.
It's even listed as a kernel bug: http://bugzilla.kernel.org/show_bug.cgi?id=10985

What happened?

From what I have found out, the following thing happened:
- Ubuntu was using uswsusp / s2ram to suspend prior to intrepid. Everything was fine.
- Someone decided that uswsusp was not cool and removed it from the repository, to force everyone to use pm-utils.
  ( see https://bugs.launchpad.net/ubuntu/+source/uswsusp/+bug/134238 )
- pm-utils uses the kernel builtin suspend functions.
- this is the point at which we are at the "kernel bug". Everything is bad.

What to do?

Well, pm-utils / pm-suspend seems to have the same "quirk" options as s2ram had, with the difference that s2ram works for me and pm-suspend doesn't. I tried nearly every quirk / combination of quirks (which took hours!).

I will now describe what I did, to get suspend working on my laptop again.
(My laptop is a Samsung q30, but i had the same issues)

Because I couldn't find uswsusp in the ubuntu repository i downloaded it from
http://packages.debian.org/en/sid/uswsusp
and installed it.

Next step is to find out, which quirks your laptop needs.
Many laptops are listed in the s2ram whitelist.
If your laptop is in this list, a simple "sudo s2ram" in the console should do the trick.
If not, you have to force s2ram and probably use some quirks.
(All options are listed if you type "s2ram --help" or "man s2ram")

The ibm x40 laptop is listed in this whitelist (from what i have seen),
so you should be able to use "sudo s2ram".
If that does not work, try "sudo s2ram --force --acpi_sleep 3".
For my Samsung Q30 "sudo s2ram --force --vbe_post" did the trick.

Last step was to force ubuntu to use s2ram again...
But that's another (very ugly) story.
Please let me know if your x40 laptops do suspend using s2ram and if you want me to write how i managed to force ubuntu to use s2ram.