Thinkpads Forum

I'm stumped here. It used to work fine, but now I can't seem to get it to work.

When I close the lid, or try to put it to sleep from the menu, it appears to work fine, then, the checklist disappears and it goes straight to my screensaver.

Any ideas?

Try forcing suspend-to-ram directly: If it does work, then the problem is most likely caused by something Ubuntu-GUI-specific.

comps wrote:Try forcing suspend-to-ram directly:

Code: Select all

echo mem > /sys/power/state

If it does work, then the problem is most likely caused by something Ubuntu-GUI-specific.

It came up with a whole list of things that failed to suspend, flashed, and just left me at the desktop again.

i-SnipeZ wrote:It came up with a whole list of things that failed to suspend, flashed, and just left me at the desktop again.

Try to get this "whole list of things" from "dmesg" output (pastebin it / post it here). You may also try pm-utils, namely pm-suspend.

Also, knowing what version of Ubuntu you're using would be helpful. Are you using 10.04 or 10.10?

ThinkRob wrote:Also, knowing what version of Ubuntu you're using would be helpful. Are you using 10.04 or 10.10?

10.10. I'll post the list of things shortly...

Sorry it's taken me this long, but here's what I'm assuming you want, I'm not a total linux noob, but, I'm still learning quite a bit:

[ 456.290120] PM: Entering mem sleep
[ 456.290219] Suspending console(s) (use no_console_suspend to debug)
[ 456.321583] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 456.321780] sd 0:0:0:0: [sda] Stopping disk
[ 456.350097] tpm_tis 00:0a: tpm_transmit: tpm_send: error -5
[ 456.350106] legacy_suspend(): pnp_bus_suspend+0x0/0x90 returns -5
[ 456.350111] PM: Device 00:0a failed to suspend: error -5
[ 456.571320] PM: suspend of drv:usb dev:1-5 complete after 249.681 msecs
[ 456.571383] PM: suspend of drv:usb dev:usb1 complete after 235.173 msecs
[ 456.910378] PM: suspend of drv:sd dev:0:0:0:0 complete after 588.797 msecs
[ 456.910408] PM: suspend of drv:scsi dev:target0:0:0 complete after 588.789 ms

Try disabling VTd in the BIOS.

ThinkRob wrote:Try disabling VTd in the BIOS.

It was, and has been, disabled. Re-enabling it doesn't effect the outcome when I try to suspend.

i-SnipeZ wrote: It was, and has been, disabled. Re-enabling it doesn't effect the outcome when I try to suspend.

Huh. I only suggested that since I'd seen issues with it in the past.

Not that it helps, but the X200 definitely functions flawlessly under Debian 6.0 and Ubuntu 10.04 -- so I'd guess it's a regression from 10.04 -> 10.10.

A few more things to try:

- disable wireless prior to suspend
- switch ttys to a non-X one before suspend
- disable TPM via the BIOS

Also, I assume you're running the latest BIOS version?

Yes I am. It was working fine, however, I remember a kernel update around when it stopped suspending. So I may have to revert somehow?

i-SnipeZ wrote:Yes I am. It was working fine, however, I remember a kernel update around when it stopped suspending. So I may have to revert somehow?

Oh dear. You got Ubuntud. Well -- if it was a kernel update that broke it, there's not much that you can do short of tracking down an older version of the package or switching to the mainline PPA. I'd recommend the latter, as I'd suspect it's less likely to break userland.

(Honestly, this sort of thing is the reason that I'm rather critical of Ubuntu: I've never had a "mainstream" distro issue as many breaking updates as Ubuntu does.)

I've been noticing this as well. As good as Ubuntu is, I'm afraid to update anything. I may just reinstall, and only install security updates. At least it only takes a little less than an hour for me to get all set up again.

Well, I found a solution, at least for now. From the standard USA repo theres a program called "StartUp-Manager". It's just a simple GUI interface for editing the GRUB boot loader. Anyway, Ubuntu keeps the last version of the kernel as well as the most recently updated. I simply selected the boot with the old kernel, now everything works as it should. I'm not sure how this will be effected with future kernel updates (hopefully this problem is fixed by then) but, for now it works just fine.

Thanks for all the help.
-Ryan

i-SnipeZ wrote:Well, I found a solution, at least for now. From the standard USA repo theres a program called "StartUp-Manager". It's just a simple GUI interface for editing the GRUB boot loader. Anyway, Ubuntu keeps the last version of the kernel as well as the most recently updated. I simply selected the boot with the old kernel, now everything works as it should. I'm not sure how this will be effected with future kernel updates (hopefully this problem is fixed by then) but, for now it works just fine.

Well you might have a bit of a problem if your current kernel turns out to have security holes... but I guess for now it's a workaround.

Realize I'm posting on an old thread, but think this info may be useful for others: had a painful time getting suspend to work on an X200 tablet (7453-BN9, BIOS 3.21) with opensuse 12.3 (just a quick default install from USB live image). I've just got the machine second hand and am testing functionality & setting it up prior to actual use. It would go into suspend as normal but would not resume via opening lid or any key presses. Had to hard reset by long press on power button. It turned out for me that enabling the security chip in the BIOS was the required change. After that suspend worked fine. No idea why this change is needed, and I did not have any issues with suspend on my X200s, though I don't know what the BIOS security setting is on that machine.

Cross reference to other posts on Lenovo Forums where I found the BIOS change info: http://forums.lenovo.com/t5/T400-T500-a ... rue#M12002 and http://forums.lenovo.com/t5/W-Series-Th ... nding#M599