You are not logged in.
After a recent system update my monitor no longer finds a signal after suspend. It was working as expected previously.
I'm using dwm and slock, running on an AMD GPU with a service for before and after.
Before=sleep.target calls
Environment=DISPLAY=:0
ExecStartPre=/usr/bin/xset dpms force off
ExecStart=/usr/bin/slockAfter=sleep.target calls
Environment=DISPLAY=:0
ExecStartPre=/usr/bin/xset dpms force on
ExecStart=/usr/bin/xreset/usr/bin/xreset bash script
xrandr --output HDMI-1 --mode 2560x1440 --rate 74.60After resuming from suspend the After=sleep.target calls service is called (I checked with a debug line in /usr/bin/xreset) to log the output of xset q:
DPMS is Enabled
Monitor is On
The only workaround I have is to switch to another tty and that wakes the monitor, or by restarting dwm
I've tried searching for a solution, would appreciate any help. Thanks
Last edited by alldayidream (2022-10-17 14:59:44)
Offline
What's the output of "xrandr --display :0 -q" when the output lost the signal?
(You can "xrandr --display :0 -q | curl -F 'file=@-' 0x0.st" to feed it into a pastebin service from the console)
Online
Same output for both before suspend, and after suspend and no signal
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 16384 x 16384
DP-1 disconnected primary (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
2560x1440 59.95 + 74.60* 72.04 60.00 50.00
Offline
What does it look like if you don't run the xreset script?
Why do you run it itfp?
And what if you make it
xrandr --output HDMI-1 --off
sleep 3
xrandr --output HDMI-1 --mode 2560x1440 --rate 74.60Online
What does it look like if you don't run the xreset script?
The same output as post #3
Why do you run it itfp?
Before the system update a couple of days ago, everything was working as expected, after suspend slock would be open/visible, the newly added After=sleep.target service is a hack to fix the current issue
The suggested solution of adding
xrandr --output HDMI-1 --off
has fixed the problem
Thanks again for your help
Offline
Ftr, the cause is probably that the output unregisters (hence the workaround requirement) and the HDMI handshake fails (because HDCP was made to annoy us) and needs an extra invitation.
Online