Ubuntu Version:
Ubuntu Desktop 25.10
Desktop Environment (if applicable):
GNOME
Hardware:
Wo‑We R5 mini PC with an AMD Ryzen 5 3550H (Picasso / Raven2) CPU and AMI UEFI firmware (ADB20D 1.04, dated 2025‑04‑28).
Problem Description:
I want to use suspend (and resume) on this dual boot mini PC.
Reproduction (S3 / deep)
- Boot the system normally.
- Trigger suspend using:
sudo systemctl suspend - Allow the system to enter suspend.
- Attempt to wake using keyboard, mouse, or power button.
Observed result
- System appears to exit suspend partially:
- fans spin up
- power LED becomes steady
- No HDMI output (monitor reports no signal)
- Keyboard and mouse do not respond
- SSH is unreachable
- Magic SysRq does not produce any response
- System remains in this state indefinitely until powered off
After reboot, logs from the previous boot show:
PM: suspend entry (deep)
There are no resume‑related log entries (e.g. “PM: resume from suspend”, “ACPI: Waking up from system sleep state S3”, etc.).
Current workaround (for operability)*
The system is currently operated with GRUB options:
mem_sleep_default=s2idle no_console_suspend
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash no_console_suspend mem_sleep_default=s2idle"
This configuration restores reliable suspend/resume behaviour, but S3 (“deep”) cannot be used as the sytem does not wake up.
I have created a bug report, mainly to document the issue.
I am posting this here, in the hope that others can find it as well and maybe I get some additional clues or ideas to explore.