Ubuntu Studio 26.04 doesn't wake up from sleep

Support and Help
,
1

[edit 8/13/26] I’d like to clarify my situation with what I actually know: My laptop’s power management settings are to sleep after 15 minutes idle, and to sleep if the lid is closed. If it goes to sleep, I can’t wake it up. I have to restart by holding the power button for 5 seconds.

I believe using the term, “hibernation,” was misleading.[/end edit]

I’m replying because I’m having the exact same problem: newly installed Ubuntu Studio 26.04 will not wake up from hibernation.

System Details:

Operating System: Ubuntu Studio 26.04
KDE Plasma Version: 6.6.4
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 7.0.0-29-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz
Memory: 8 GiB of RAM (7.7 GiB usable)
Graphics Processor: Intel® HD Graphics 5500
Manufacturer: Dell Inc.
Product Name: Inspiron 7558
System Version: A08

This is my first time back in *nix since 1990; so, I have a lot of catching up to do.

Ubuntu 26.04 won't suspend
Ubuntu Weekly Newsletter Issue 957
4

Moved to a new topic, as you cannot show that it’s really the same problem.

5

Hibernate is disabled by default on all official Ubuntu flavors. See PowerManagement/Hibernate - Community Help Wiki

6

My problem isn’t that it won’t hibernate; it’s that it won’t wake up. I’m not even sure that is the correct word, hibernate, in this situation.

In my Power Management settings, I have the laptop set to sleep after 15 minutes, and to sleep when the lid is closed. If it goes to sleep, I can’t wake it up. I have to restart by holding the power button for 5 seconds.

I don’t know what to look for in the system logs to see what is failing.

8

Ah, you seem to be describing “sleep” (suspend-to-RAM), which is different from “hibernate” (suspend-to disk).

Edited the title to more clearly describe the problem.

9

Thank you! What service or unit should I look at to see where the failure to wake up is occurring?

10

The problem there is dependent on your hardware, and it’s impossible to know just by knowing what your hardware is. A way to experiment is by adding acpi_osi= and any one of Linux, Windows, or none.

It basically comes down to how your machine handles ACPI calls.

11

In which conf file should I add this?

12

/etc/default/grub in the GRUB_CMDLINE_LINUX_DEFAULT= line.

13

Before I actually do it, this is what I’m going to do based on what you’re recommending:

from:

/etc/default/grub, line 10: GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash”

to: GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=linux"

Am I gtg?

14

You can keep quiet splash and add the additional parameter. As in:

GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash acpi_osi=linux”

15

OK. I tried acpi_osi=linux, windows and none sequentially.

Specifically I set GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash acpi_osi=linux”, then sudo update-grub in the terminal, then restarted and tested closed lid behavior. No change: won’t wake up requiring a hard restart.

I did the same test for windows and none. No effect.

Where should I look next? Is there a journal that is recording an error?

16

This is a known issue with my current computer. Forgo the acpi_osi= line and try this:

mem_sleep_default=s2idle

That will force the sleep to become completely idle, and your machine will not “act” like it’s sleeping so much as it’ll blank the screen and send the CPU completely to idle without powering the CPU down, while keeping the RAM active like normal.

I have the feeling it’s a kernel bug as my system is an Intel Core Ultra 7 and has a similar issue. It’s probably a workaround until whatever kernel bug is causing this gets fixed, but I’m no kernel expert beyond the lowlatency options.

1 Like
17

This topic was automatically closed 18 hours after the last reply. New replies are no longer allowed.