Problem
When Fedora 41 or older runs on a Raspberry Pi 4 (RPi4) and a system suspend is requested (either manually by the user, or automatically due to being idle for some time, depending on your desktop configuration), the device will suspend, but can’t be woken up. That effectively means that you have to perform a hard reboot and your unsaved data is lost.
You can discuss this issue here.
Cause
The Raspberry Pi manufacturer hasn’t implemented suspend support in the Linux kernel. While there are community efforts to improve suspend functionality for Raspberry Pi devices, these are still in progress and do not yet fully support the RPi4. The development focuses primarily on older models like RPi3 and Zero2W, leaving RPi4 support lagging due to its additional complexities.
Related Issues
Bugzilla report: #2283978
Workarounds
Don’t trigger suspend on Raspberry Pi 4 to avoid this problem. That means avoid requesting suspend through your graphical desktop interface, avoid running commands like systemctl suspend, and disable automatic suspend on idle in your desktop environment.
How to disable automatic suspend
GNOME
You need to disable automatic suspend in your user session and also at the login screen (when no user is logged in). Follow this article to perform both actions.
Other desktop environments
Depending on which DE, you are using, open its settings application, find the corresponding settings, such as Power, Power Management, or similar and switch off the automatic suspend.
How to completely prevent any suspend
You can mask systemd target that controls suspend. If you do that, you won’t be able to trigger suspend, even accidentally.
You can prevent any suspend with this command:
sudo systemctl mask suspend.target
Later, if you want to go back to default settings, you can revert it with:
sudo systemctl revert suspend.target