Device will not consistently boot after sleep

Hi there!

I recently switched over to Fedora from Mint, and I’ve been having an issue where, if my laptop goes to sleep, it will sometimes not reboot at all (keyboard lights up, power light comes on, but screen stays black and iirc the caps lock light won’t come on) until I disconnect the battery. I thought for a while this was limited to sleep when closing the lid, but I just had it do so from the sleep timer. It has also happened both on battery and on AC power.

Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.8-200.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i9-13900H
Memory: 64 GiB of RAM (62.4 GiB usable)
Graphics Processor 1: Intel® Iris® Xe Graphics
Graphics Processor 2: NVIDIA GeForce RTX 4070 Laptop GPU
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus M16 GU604VI_GU604VI
System Version: 1.0

I am using the akmod/rpmfusion/whatever they’re called nvidia drivers, and not the Nouveau drivers, and I do have a windows dual boot setup (though I have not booted into windows since installing Fedora).

I was able to temporarily make the issue go away with the solution in this thread: Reddit - The heart of the internet. However, the issue did come back after a few days.

I have seen a number of threads detailing various similar issues, but none that seemed to show a proper solution (from what I could see, anyway. I may not have dug enough). I would love to hear if there is an at least mostly permanent solution, though I understand if there isn’t (I’m most certainly not running officially supported hardware).

Thanks in advance!

Sorry, I don’t find a solution in this page :frowning: What have you done precisely ?

Have you applied what the rpmfusion Howto NVIDIA Suspend recommends?

I’ve been struggling with this as well (as are many people it seems). There can be several causes, but in my case it is related to kwin_wayland (the compositor) not being able to get DRM master again (i.e. not being able to get control over the GPU).

Check the log for any lines that contain both ‘kwin_wayland’ and ‘failed’ (change the dates to what is applicable for you):

journalctl --since '2026-02-14' --until '2026-02-16' | grep -iE 'kwin_wayland.*failed'

If you see many errors like this, it’s the same issue (many being: tens, hundreds, not just a few):

feb 15 14:32:20 fedora kwin_wayland[2972]: Setting dpms mode failed!
feb 15 14:32:20 fedora kwin_wayland[2972]: Atomic modeset test failed! Permission denied
feb 15 14:32:20 fedora kwin_wayland[2972]: Setting dpms mode failed!
feb 15 14:32:20 fedora kwin_wayland[2972]: Atomic modeset test failed! Permission denied
feb 15 14:32:20 fedora kwin_wayland[2972]: Setting dpms mode failed!
feb 15 14:32:20 fedora kwin_wayland[2972]: Atomic modeset test failed! Permission denied
feb 15 14:32:20 fedora kwin_wayland[2972]: Setting dpms mode failed!
feb 15 14:32:20 fedora kwin_wayland[2972]: Atomic modeset test failed! Permission denied
feb 15 14:32:20 fedora kwin_wayland[2972]: Setting dpms mode failed!
feb 15 14:32:20 fedora kwin_wayland[2972]: Atomic modeset test failed! Permission denied
feb 15 14:32:20 fedora kwin_wayland[2972]: Setting dpms mode failed!
feb 15 14:32:20 fedora kwin_wayland[2972]: Atomic modeset test failed! Permission denied
feb 15 14:32:20 fedora kwin_wayland[2972]: Setting dpms mode failed!

In that case, read my bug report for more details and apply the /etc/environment workaround: https://bugs.kde.org/show_bug.cgi?id=516038 Make sure you fetch your VGA number before setting this file:

lspci | grep -i 'vga'