Magnus -- this suggests that the asl file is faulty!
I've recently had to re-install my laptop, and I've done a minimal amount of hacking to get things right.
1. When I ran the live CD, I pressed the left arrow to access the GRUB line, and changed the vga setting to vga=0. This saves you having to change the bootloader later -- when you install, it omits the "framebuffer" bootup and defaults to pure text 80x25 bootup. This is often necessary for Hibernate/Suspend to work for some reason.
2. After installation, I had to go into KDE Control Centre ( > Power Control > Laptop Battery) to enable KLaptop. You have to set the "Helper Application" on the ACPI Config, and set "Show Battery Monitor" in the Battery tab . If you don't get the ACPI Config tab, this suggests that there is not a full ACPI implementation (at least that's how the OS sees it) and it may be time to mess with DSDT.
3. Where KLaptop falls short for me is that it does not seem to recognise the Sleep and Power buttons. So I can set the lid switch to Hibernate, but that's it. At this point the Sleep and Power Buttons do nothing (well if I hold the Power Button down for 4 secs it switches off).
4. Next thing I installed KPowerSave and ran it. Now the Power button works. The sleep button appears to work, but I cannot return to my desktop. I then Quit from KPowerSave, and told it not to run in future. Power button still works...
5. The sleep button was the remaining problem. Following some e-mail correspondence with the testing team, Jmiahman suggested that I look at what the program klaptop_acpi_helper actually does. So after running klaptop_acpi_helper --help, I tried running it with the --suspend switch in a console, and it suspended and returned perfectly.
6. The next thing I did was to alter the file /etc/acpi/events/sleep to read as follows:
rebooted and tried the sleep key. It slept. Pressed space bar. It woke up - perfectly.
Now the original second line in the file reads:
It's fairly obvious that pmsuspend doesn't work on my machine!
Why does one program work and another does not? Hard to say.
I note that the "suspend-s2ram" has an entirely different executable: "s2ram". Wonder what that does? Let's test it! Back in a few minutes!
EDIT: Nope. It did not recover.
The point being that there seem to be multiple tools for this but only one works for me.
I think the difference is that KLaptop uses "wltool" (Whitelist Tool) which is a database of various hardware with conditions and actions for recovery from various situations. But I could be wrong...