Repository navigation
Black screen after resume from S3 on NVIDIA: CRTC restore fails with EINVAL and nothing is drawn until something forces a frame (hyprctl reload recovers instantly)
#17002
Unanswered
SpaceOwO-jpg
asked this question in
Bugs - DRM
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hyprland version
v0.57.2
Is this a regression?
Unknown. I see it on 0.57.1 and 0.57.2. It became noticeable on 2026-11-13; earlier resumes on the same setup came back, but see "How often" below — a key press or mouse movement usually hides it.
What's the bug?
Already reported?
I searched issues and discussions. The closest I found is #16315 ("Session lock held across s2idle suspend: outputs never present again after resume"), which was closed by the bot without a reply. The symptom is similar (compositor alive, screen black after resume with a session lock held), but the details differ: here it is S3 on a single NVIDIA GPU, the restore commit fails with EINVAL, and
hyprctl reloadfully recovers the display.System info and version
Full
hyprctl systeminfois attached (hyprctl-systeminfo.txt). Summary:NVreg_PreserveVideoMemoryAllocations=1, kernel suspend notifiers in usestart-hyprlandsystemctl suspend-then-hibernate, only the suspend phase runs;/sys/power/mem_sleepiss2idle [deep]render:cm_enabled = true(default),misc:vrr = 0Description
After waking the machine from S3, both monitors stay black. Hyprland, the lock client and all other clients keep running,
hyprctlanswers, and there is no crash, no coredump and no NVRM/Xid message. The screen stays black until something makes Hyprland render a frame. If nobody touches the machine, that never happens.What the Hyprland log shows on every resume (outputs enabled at suspend time):
At the same timestamps the kernel logs, twice per CRTC:
After
Session got activated!there are two outcomes:Applying monitor rule for DP-21–3 ms later, modesets both outputs, and the picture is back about 0.4 s after wake.hyprctl reload;Applying monitor rule for DP-2followed 4 ms after the IPC connection and the picture returned.Things that end outcome 2:
hyprctl reload: monitor rules are applied within a few ms, every time.grim -o DP-2): the rule apply is logged 0.13 ms afterNew image copy capture session.Things that do not end it:
hyprctl -j monitors all, and an IPC call to the lock client.If the outputs were DPMS-off when the machine suspended, the restore step logs no error.
How often
hyprctl reload).hyprctl reload1.5 s after resume, so I have not let it sit black on this version. In 2 of 4 logged resumes nothing happened betweenSession got activated!and the workaround's reload about 1.2 s later; in the other 2 Hyprland applied the monitor rules by itself within 3 ms.Workaround
A small script that listens for logind's
PrepareForSleep (false)and reloads the config after resume. With it the picture has come back within about 2 s on every resume since.Logs
Attached, filtered to session / DRM / monitor / IPC lines (debug logging with timestamps):
log-0.57.1-black-until-reload.txt: suspend, resume at 14:38:20, black untilhyprctl reloadat 14:39:12.log-0.57.2-resume.txt: the same sequence on 0.57.2, ended by the workaround's reload 1.2 s after activation.kernel-log.txt: kernel messages for both resumes.hyprctl-systeminfo.txtI can provide full unfiltered logs or run a hands-off test on 0.57.2 with the workaround disabled if that helps.
Reproduction steps
How to reproduce
start-hyprland.systemctl suspend-then-hibernate(or let the idle daemon do it).hyprctl --instance 0 reloadbrings the picture back immediately.Expected behaviour
After resume the outputs are modeset and the lock screen is shown without any further input.
Attachments
hyprctl-systeminfo.txt
kernel-log.txt
log-0.57.1-black-until-reload.txt
log-0.57.2-resume.txt
I acknowledge that:
I have searched all (open and closed) discussions and issues and my problem is not there.
I have read the Code of Conduct and agree to follow it.
I wrote this request with my own hands, my own keyboard, and in my own words.
All reactions