# Not Coming Back From Suspend **URL:** \ **Category:** Linux\ **Created:** [April 27, 2021, 9:41pm UTC](https://forums.developer.nvidia.com/t/not-coming-back-from-suspend/176446 "2021-04-27T21:41:20Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![aplattner](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/aplattner/32/14043_2.png) [@aplattner](https://forums.developer.nvidia.com/u/aplattner)\ **Post date:** [April 28, 2021, 8:04pm UTC](https://forums.developer.nvidia.com/t/not-coming-back-from-suspend/176446/6 "2021-04-28T20:04:41Z")
systemd is not required, it’s just the default that the installer has support for. You can still use the old-style suspend & resume by not setting the `NVreg_PreserveVideoMemoryAllocations=1` module parameter for the nvidia module. From your bug report it looks like you don’t have that set, so nothing is supposed to have changed about suspend & resume. If you do want to try the new suspend path, the only requirements are to set `NVreg_PreserveVideoMemoryAllocations=1` and then be sure to trigger nvidia-sleep.sh before suspending and after resuming. That’s what the systemd units do but you can do it yourself using a script or something. ```auto #!/bin/bash /usr/bin/nvidia-sleep.sh suspend pm-suspend /usr/bin/nvidia-sleep.sh resume ``` (replace `pm-suspend` with whatever your actual suspend command is). --- _[View the full topic](https://forums.developer.nvidia.com/t/not-coming-back-from-suspend/176446)._