# System won't wake up after goes to sleep

**URL:** <https://deeptalk.lambda.ai/t/system-wont-wake-up-after-goes-to-sleep/2664>\
**Category:** Technical Help\
**Created:** [October 24, 2021, 10:59pm UTC](https://deeptalk.lambda.ai/t/system-wont-wake-up-after-goes-to-sleep/2664 "2021-10-24T22:59:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![votbod](https://avatars.discourse-cdn.com/v4/letter/v/5f8ce5/32.png) [@votbod](https://deeptalk.lambda.ai/u/votbod)\
**Post date:** [October 24, 2021, 10:59pm UTC](https://deeptalk.lambda.ai/t/system-wont-wake-up-after-goes-to-sleep/2664/1 "2021-10-24T22:59:44Z")

</div>

I can lock my tensorbook and if I move the mouse or hit a key then the prompt comes up to log back in. If it sits for a while though, when I try to get the prompt by moving the mouse or hitting a key, nothing happens. Based on (a comment from ( [Screen remains blank after wake up from suspend - Ask Ubuntu](https://askubuntu.com/questions/1032633/18-04-screen-remains-blank-after-wake-up-from-suspend) ), I tried to change the driver it was using to the non-server nvidia one from the [X.org](http://X.org) X server one. If I try the 470 server version it drops an error and prevents changing to that one. The same askubuntu entry mentions editting the /etc/default/grub file. Is this a suggested practice, and are there any ways to fix this issue?

---

<div class="post-metadata">

**Author:** ![Sigve](https://avatars.discourse-cdn.com/v4/letter/s/aeb1de/32.png) [@Sigve](https://deeptalk.lambda.ai/u/Sigve)\
**Post date:** [January 8, 2022, 6:04pm UTC](https://deeptalk.lambda.ai/t/system-wont-wake-up-after-goes-to-sleep/2664/2 "2022-01-08T18:04:19Z")

</div>

I have the same issue. Did you find a fix for this?

---

<div class="post-metadata">

**Author:** ![votbod](https://avatars.discourse-cdn.com/v4/letter/v/5f8ce5/32.png) [@votbod](https://deeptalk.lambda.ai/u/votbod)\
**Post date:** [January 30, 2022, 7:01pm UTC](https://deeptalk.lambda.ai/t/system-wont-wake-up-after-goes-to-sleep/2664/3 "2022-01-30T19:01:15Z")

</div>

Not really. Contacted support, but troubleshooting found nothing. Sent it in. They couldn’t replicate the error. Right now seems to be stable if I manually lock it when I step away rather than let it autolock but not sure if that’ll last or just seems to work for now.
