# Can't resume after suspend

**URL:** <https://discourse.ubuntubudgie.org/t/cant-resume-after-suspend/4609>\
**Category:** Budgie Desktop\
**Created:** [January 23, 2021, 4:59pm UTC](https://discourse.ubuntubudgie.org/t/cant-resume-after-suspend/4609 "2021-01-23T16:59:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thob](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/thob/32/3095_2.png) [@thob](https://discourse.ubuntubudgie.org/u/thob)\
**Post date:** [January 23, 2021, 4:59pm UTC](https://discourse.ubuntubudgie.org/t/cant-resume-after-suspend/4609/1 "2021-01-23T16:59:27Z")

</div>

when I want to resume after suspend it seems the screen stays black and I need to reboot.  
Any cure for this? This is a brandnew AMD Ryzen 4800

Thanks

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 24, 2021, 1:54pm UTC](https://discourse.ubuntubudgie.org/t/cant-resume-after-suspend/4609/2 "2021-01-24T13:54:47Z")

</div>

Likely to be graphics and/or kernel related especially for such a new chipset.

Kernel 5.10 is just entering the proposed repo for 21.04. Latest graphics usually enter towards the end of the dev cycle so probably March or early april.

So I would first check by installing the 5.10.x kernel from the mainline ppa.

Then I would check the oibaf ppa for the bleeding edge graphic drivers.

---

<div class="post-metadata">

**Author:** ![thob](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/thob/32/3095_2.png) [@thob](https://discourse.ubuntubudgie.org/u/thob)\
**Post date:** [January 24, 2021, 5:14pm UTC](https://discourse.ubuntubudgie.org/t/cant-resume-after-suspend/4609/3 "2021-01-24T17:14:27Z")

</div>

I hope it is [related to my graphics driver issue](https://discourse.ubuntubudgie.org/t/budgie-wm-spike-up-tp-500/4614/2) and can be sorted out once I got the proper driver loaded/installed.

---

<div class="post-metadata">

**Author:** ![annakp12](https://avatars.discourse-cdn.com/v4/letter/a/50afbb/32.png) [@annakp12](https://discourse.ubuntubudgie.org/u/annakp12)\
**Post date:** [August 2, 2025, 8:05am UTC](https://discourse.ubuntubudgie.org/t/cant-resume-after-suspend/4609/4 "2025-08-02T08:05:51Z")

</div>

Hi! I had a similar problem and managed to fix it today so I thought I’d share my experience. I am very much a beginner but I’ll try my best to describe everything I did.

Version: Ubuntu Budgie 25.04. Laptop: Acer Aspire Vero 14”, Intel i5, 8GB RAM.

Issue: When I’d leave the laptop idle, whether with the lid closed or open, it would enter the suspend mode normally but only for a short time (for approx. 10-15 mins). If I tried to resume it after that time, it would be ok. However, if I left it longer, let’s say for 20-30 min or more, it would not resume after that. The laptop would just reboot each time.

Solution: changing sleep mode to deep solved the problem for me. I followed the steps from this post: [https://forums.linuxmint.com/viewtopic.php?t=421619](https://forums.linuxmint.com/viewtopic.php?t=421619) (I did not edit anything in BIOS though, changing the sleep mode alone helped).

Step-by-step process:

1. Edit GRUB:

```auto
sudo nano /etc/default/grub

```

Find the line:

```auto
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

```

Change it to:

```auto
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"

```

Save and exit.

2. Update GRUB:

```auto
sudo update-grub

```

3. Reboot and Verify:

After reboot, check current sleep mode:

```auto
cat /sys/power/mem_sleep

```

You should see:

```auto
s2idle [deep]

```

This means `deep` is now the default.

After that, I tested it by leaving the laptop idle for longer periods of time (with the lid open and then with the lid closed). The laptop was resuming normally even after an hour in the suspend state.

I hope this will be useful should anyone have this problem as well 🙂