[SOLVED] dwm screen suspend weird behavior

nsakey · 2025-07-02 09:30:48

Hi, everyone
I've recently made fresh install of arch linux, and currently using basic dwm, without any patches or whatever.
I'm experiencing the next issue: if I will leave my pc turned on, and do not touch for a while the screen goes black.
If i touched right after it went black, it will be fine, everything works. If I will not touch it for a while, I wouldn't be able to see the screen, only thing I could is type pkill dwm blindfolded. Also screen might stutter.
I can't go from black screen also when I'm doing something with display settings, example changing refresh rate or any other setting that will require monitor going black and restart.
It doesn't happen on xfce or windows(duh).

gpu: 4090
monitor: 57" Odyssey Neo G9 G95NC
wm: dwm

Last edited by nsakey (2025-07-25 15:53:28)

seth · 2025-07-02 12:33:19

if I will leave my pc turned on, and do not touch for a while the screen goes black.

https://wiki.archlinux.org/title/Displa … _Signaling

It doesn't happen on xfce

Do you use a compositor (picom) along dwm?
The symptoms kinda sound as if the output powers down and unregisters on DPMS - and then either never shows up again (fumbled handshake, HDMI?) or some userspace daemon responds and disables the monitor.
Can you switch to another VT and query

DISPLAY=:0 xrandr -q

when this happens?
Does the monitor come back if you physicall de- and re-attach it?
https://aur.archlinux.org/packages/x-on-resize is a generic X11 daemon to "automatically do stuff with outputs as they appear" but you can also use udev rules, https://wiki.archlinux.org/title/Udev#E … _unplugged

nsakey · 2025-07-02 14:05:11

> Do you use a compositor (picom) along dwm?
No I don't

> Does the monitor come back if you physicall de- and re-attach it?
You mean reattach cable? no.

Will answer later on other stuff.
Thank you.

nsakey · 2025-07-23 14:30:28

I'm still looking into your ideas.
Some updates:
- it fixes if I change tty and go back
- it doesn't happen with my old mony oddysey g7
- Sometimes mony goes off and tries to be on, but it get into stutter(seems unrelated)

seth · 2025-07-23 15:38:03

it fixes if I change tty and go back

How is the monitor attached? HDMI?
Can you run the Odyssey Neo G9 G95NC at the same resolution as the Odyssey G7?
Or try to blindly (shortcut) cycle the resolution? ("xrandr --output … --mode 3840x1080; sleep 5; xrandr --output … --auto")

nsakey · 2025-07-24 13:03:39

Display port for new one
HDMI for old one
I can test other setups

> Can you run the Odyssey Neo G9 G95NC at the same resolution as the Odyssey G7?
I can, will test it

> Or try to blindly (shortcut) cycle the resolution? ("xrandr --output … --mode 3840x1080; sleep 5; xrandr --output … --auto")
Will do

Oh by the way, I have 4090 and it has display port 1.4. So it's not supporting this monitor.
I've setup in monitor settings for 120 hz
And for some reason it thinks that the default resuloution is 5120x1440 not 7680x2160

nsakey · 2025-07-24 13:19:49

> Can you run the Odyssey Neo G9 G95NC at the same resolution as the Odyssey G7?
I've run it in 2k, there is no such issue in this case.

seth · 2025-07-24 14:06:08

HBR3 will at a push (and with a little DSC) still do 7680x2160 @60Hz?
Do you then still have those issues?

nsakey · 2025-07-25 12:21:11

Seems like on 60HZ it's all good

seth · 2025-07-25 12:34:26

Even at 7680x2160 ?
You might run into the HW limits where 7680x2160 @120Hz is attempted and fails - how are you setting the lower resolution?
xrandr script of xorg config?
https://wiki.archlinux.org/title/Xrandr … esolutions (you perhaps don't have to add a modeline, but setting the PreferredMode might help)

nsakey · 2025-07-25 12:40:35

> Even at 7680x2160 ?
Yes

xrandr only

seth · 2025-07-25 12:55:28

If you prefer running 5120x1440@120Hz over 7680x2160@60Hz consider adding a default configuration to avoid race conditions or the server picking the "wrong" modeline when the monitor gets (logically) attached after the DPMS.

nsakey · 2025-07-25 13:39:31

I will keep 7680x2160@120Hz.
It has only this issue, and it's manageable with xset -dpms / xset s off.
I think this thread should be closed.
Thanks a lot for your time and your expert help!

seth · 2025-07-25 14:17:14

I thought your GPU is limited to HBR3 and 7680x2160@120Hz doesn't work and you're running on 5120x1440@120Hz ??

Mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

nsakey · 2025-07-25 15:52:38

7680x2160@240Hz doesn't work
7680x2160@120Hz does with this bug

nsakey · 2025-08-28 07:21:13

I believe fix is to use gpu with DP 2.1
Closed

Arch Linux

#1 2025-07-02 09:30:48

[SOLVED] dwm screen suspend weird behavior

#2 2025-07-02 12:33:19

Re: [SOLVED] dwm screen suspend weird behavior

#3 2025-07-02 14:05:11

Re: [SOLVED] dwm screen suspend weird behavior

#4 2025-07-23 14:30:28

Re: [SOLVED] dwm screen suspend weird behavior

#5 2025-07-23 15:38:03

Re: [SOLVED] dwm screen suspend weird behavior

#6 2025-07-24 13:03:39

Re: [SOLVED] dwm screen suspend weird behavior

#7 2025-07-24 13:19:49

Re: [SOLVED] dwm screen suspend weird behavior

#8 2025-07-24 14:06:08

Re: [SOLVED] dwm screen suspend weird behavior

#9 2025-07-25 12:21:11

Re: [SOLVED] dwm screen suspend weird behavior

#10 2025-07-25 12:34:26

Re: [SOLVED] dwm screen suspend weird behavior

#11 2025-07-25 12:40:35

Re: [SOLVED] dwm screen suspend weird behavior

#12 2025-07-25 12:55:28

Re: [SOLVED] dwm screen suspend weird behavior

#13 2025-07-25 13:39:31

Re: [SOLVED] dwm screen suspend weird behavior

#14 2025-07-25 14:17:14

Re: [SOLVED] dwm screen suspend weird behavior

#15 2025-07-25 15:52:38

Re: [SOLVED] dwm screen suspend weird behavior

#16 2025-08-28 07:21:13

Re: [SOLVED] dwm screen suspend weird behavior

Board footer