Yes, I have that parameter in grub.cfg and regenerated but it is still a no go. Running "systemctl suspend" in the terminal will turn off the computer, and closing the lid will produce the same result.
Doing "systemctl status qubes-suspend.service" shows suspend as loaded and inactive(dead) Doing "journalctl -u qubes-suspend.service" shows "Dom0 systemd[1]: starting Qubes suspend hooks ... Dom0 systemd[1]: qubes-suspend.service: Main process exited, code=exited, status=203/EXEC Dom0 systemd[1]: Failed to start Qubes suspend hooks. Dom0 systemd[1]: qubes-suspend.service: Unit entered failed state Dom0 systemd[1]: qubes-suspend.service: Failed with result 'exit-code'." In terminal to check mem_sleep value "sudo cat /sys/power/men_sleep " shows deep selected "s2idle [deep]" -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cfeaf978-430b-4c7d-8931-41e4719447cc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
