Hello All, I recently put a new SATA drive in my computer and decided to start with a fresh install of Arch. Before this upgrade, suspend to RAM worked fine (although I don't know if it was with kernel or uswsusp). (I should say, I'm not sure if the SATA upgrade is a cause of my problem or simply a coincidence) Although I copied my /etc/suspend.conf and /etc/pm from the old drive I must be missing something because it's not working anymore (nothing else apart from the hard drive has changed). When I do pm-suspend, the computer correctly powers down and the power LED goes from green to orange... when I wake up the computer however, instead of resuming, it reboots. So far, I've tried the following: echo mem > /sys/power/state: suspends, reboots instead of resuming pm-suspend --auto-quirks: suspends, reboots instead of resuming s2ram -n: tells me the system is unknown s2ram -f: suspends but reboots instead of resuming s2ram -f -a 3 and other variations: same, reboots instead of resuming The pm-suspend.log file is not very helpful -- it shows that the computer correctly suspends, but the last entry is "performing suspend" and there's no information on resume of course because the computer restarts instead of resuming. To rule out modules, I tested a minimal setup explained in the SUSE doc: * edit the grub kernel command to start only bash: init=/bin/bash * mount /sys and /proc by hand: mount /sys && mount /proc * manually suspend to RAM: echo mem > /sys/power/state Again, the power LED goes orange, but when I wake up the computer it restarts. I've tried different BIOS settings in case I had accidentally changed something there, but it made no difference. It seems the resume hook isn't working -- even though I re-mkinitcpio'ed the kernel images with the resume hook (also tried the uresume hook -- I'm a bit confused about this, though I think uresume is for uswsusp and resume for kernel suspend). Is there a way of seeing what happens when the wake-up event occurs? I tried adding a hook in /etc/pm/sleep.d for the resume event, but of course it's not reached, so I get nothing out. Any suggestions on how to debug this issue further would be much appreciated. I've been staring at the problem so long that I might have missed something obvious... Steve Hardware: MSI MS-6741 VIA K8T800 Socket 754 Motherboard Seagate SATA hard drive Kernel 2.6.30.6-1