EDIT: Updated instructions due to several mistakes.
jondecker is going to try as well, so I will start putting in the detail. the following is all on the MD you want to suspend, not the core.
- make sure Suspend to RAM (STR) is enabled in your BIOS.
- in /etc/acpi/events/powerbtn - make sure it is pointing at /etc/acpi/powerbtn.sh
- make a backup copy of powerbtn.sh, then edit the original to have these contents...
# Initiates a shutdown when the power putton has been
# Skip if we just in the middle of resuming.
test -f /var/lock/acpisleep && exit 0
- now create a file called /usr/pluto/bin/suspend.sh (with appropriate permissions for exec) and put this in it...
echo "LMCE Suspend Process Started" > /var/log/pluto/sus.log
## Turn on WOL
ethtool -s eth0 wol g
## Find local IP address
LocalIP=$(ip addr show dev eth0|grep "inet "|cut -f6 -d" "|cut -f1 -d/)
## Use local IP address to find MD device number
FindMDDeviceQ="SELECT PK_Device FROM Device
## Identify immediate children DCE devices that are currently Registered
JOIN DeviceTemplate ON Device.FK_DeviceTemplate=DeviceTemplate.PK_DeviceTemplate
LEFT JOIN Device AS Device_Parent on Device.FK_Device_ControlledVia=Device_Parent.PK_Device
LEFT JOIN DeviceTemplate AS DeviceTemplate_Parent
OR (Device_Parent.FK_Device_ControlledVia=$DeviceID AND DeviceTemplate_Parent.FK_DeviceCategory IN (6,7,8) ) )
AND DeviceTemplate.FK_DeviceCategory <> 1
## Send SYSCOMMAND_0 (device shutdown) message to all immediate children. These devices will relay the message to all decendents
for Device in $DeviceList; do
/usr/pluto/bin/MessageSend "$DCERouter" 0 "$Device" 7 0 163 "start_local_devices"
## Send SYSCOMMAND_0 message to MD device itself
/usr/pluto/bin/MessageSend dcerouter 0 $DeviceID 7 0 163 "start_local_devices"
## Wait for DCE devices to complete their shutdown
for ((i = 0; i < MaxLoopCount; i++)); do
Devices=$(cat /usr/pluto/locks/pluto_spawned_local_devices.txt | grep -v '^$' | tr '\n' ',')
if [[ -z "$Devices" ]]; then
Q="SELECT COUNT(*) FROM Device WHERE PK_Device IN ($Devices) AND Registered=1"
if [[ "$RegCount" -eq 0 ]]; then
echo "Waiting for $RegCount devices to shutdown"
echo "Done waiting"
## Kill the LM processes
killall -q -s SIGKILL -r lmce_launch_manager\*
- now edit /etc/hibernate/hibernate.conf - make sure that only TryMethod ram.conf is not commented out
- now edit /etc/hibernate/ram.conf - make sure that TryMethod ususpend-ram.conf is not commented out, but the other two methods are commented out.
- now edit /etc/hibernate/ususpend-ram.conf - if your hardware is not recognised when test the hibernate, you may need to uncomment USuspendRamForce yes. The other options are for various compatibility levels that effect whether the resume works or not... haven't got my hardware to resume successfully yet.... apparently that is a common problem with Linux suspend
- now create a file in /etc/hibernate/scriptlets.d - call it suspend and insert this code ....
AddSuspendHook 15 LMCESuspend
You are ready to test! From a shell, type hibernate-ram. You should see the MD suddenly drop out to the launch manager and then the launch manager die, followed by the MD going into suspend mode. In the shell you will see the hibernate script printing how many DCE devices are left to shutdown, every second. Note the VDR device takes about 15 seconds to shutdown on my system, but all the others are pretty much immediate. So if you are using VDR, you may see a delay between the MD dropping to launchmanger, and the launchmanager actually dying.
If that all works ok, try resuming your system and let me know if it was successful. As I say, try some of the other options in ususpend-ram.conf if the resume is unsuccessful. Also, the config in acpi above, should allow you just to tap your power button and it go into suspend from there.