(OP addition): First make sure your BIOS->config->power-sleep state is correct (or whatever it is called). It should be set to Linux. Default is probably windows. Not having this set properly can block you from setting [deep].
/sys/power/mem_sleep indicates the method of suspend that will used. Availability of the various methods is system dependant.
The typical default is deep
, as you have shown:
doug@s19:~$ cat /sys/power/mem_sleep
s2idle [deep]
meaning Suspend-to-RAM
would be used if mem
was written to /sys/power/state
to suspend the system.
By changing it to s2idle
:
doug@s19:~/system-info$ echo s2idle | sudo tee /sys/power/mem_sleep
s2idle
doug@s19:~/system-info$ cat /sys/power/mem_sleep
[s2idle] deep
Then Suspend-To-Idle
would be used if mem
was written to /sys/power/state
to suspend the system.
The other way to tell the system which method of suspend to use is via the /sys/power/state
itself. The options for a given system can be listed:
doug@s19:~$ cat /sys/power/state
freeze mem disk
freeze
can be used for Suspend-To-Idle
and mem
can be used for Suspend-to-RAM
, depending on the setting in /sys/power/mem_sleep
.
Suspend-To-Idle
will wake from suspend faster, but uses a lot more power than Suspend-to-RAM
. For my test server, the mains power for a very idle system is about 37.8 Watts. Suspend-To-Idle
uses about 29.4 Watts. Suspend-to-RAM
uses about 2.8 Watts. I used these commands to suspend the system:
doug@s19:~$ echo freeze | sudo tee /sys/power/state
freeze
doug@s19:~$ echo mem | sudo tee /sys/power/state
mem
And pushed the power button to wake the system.
Reference.