MSI Monitor won't Sleep

Heat_195 · 29 November 2021 04:04

I notice that after 45 mins which is what I have it set to, it will attempt to go to sleep but then wake up immediately afterwards. So something is causing the wake up. Its a MSI Optix 342CQRV 34" UW. Using a HDMI cable which is what this monitor "prefers" as the DisplayPort cable doesn't even work with my build.

Ironically with my similar issue of the keyboard and mouse not being able to wake up the PC (and then once the power button is pushed those two still are asleep), when I'm on the sddm splash screen there is some timeout where then my monitor WILL actually go to sleep! Yeah it only works on the lockout screen which reminds me maybe that's what I need to do to get it to shut off if all else fails but I rather not.

What I've tried:

xset +dpms
xset dpms 30 45 60

What happens with that is the screen will go off but then on again, followed by another 15-40 seconds before it does that again. Then there is a pattern of the screen going off and on repeatedly 3 times where you get less than a second between black screens. Another 1 min and the cycle repeats itself. From:

https://bbs.archlinux.org/viewtopic.php?id=230068

```text
System:    Kernel: 5.14.16-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
           parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
           root=UUID=b3313c80-ab52-480d-9e9a-0f5523dc311a rw rootflags=subvol=@ quiet splash
           rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1
           resume=UUID=edae4f59-58e7-43b3-ae50-453efb741e26 loglevel=3
           Desktop: KDE Plasma 5.23.3 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
           Distro: Garuda Linux base: Arch Linux
Machine:   Type: Desktop Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 1.0 serial: <filter>
           UEFI: American Megatrends LLC. v: A.50 date: 01/15/2021
CPU:       Info: 8-Core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP
           arch: Zen 3 family: 19 (25) model-id: 50 (80) stepping: 0 microcode: A50000B cache:
           L2: 4 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 121375
           Speed: 4232 MHz min/max: 1400/3800 MHz boost: enabled Core speeds (MHz): 1: 4232
           2: 4467 3: 4424 4: 4226 5: 4547 6: 4119 7: 3852 8: 4306 9: 4415 10: 4408 11: 4490
           12: 4143 13: 4203 14: 4297 15: 3863 16: 3947
           Vulnerabilities: Type: itlb_multihit status: Not affected
           Type: l1tf status: Not affected
           Type: mds status: Not affected
           Type: meltdown status: Not affected
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, STIBP:
           always-on, RSB filling
           Type: srbds status: Not affected
           Type: tsx_async_abort status: Not affected
Graphics:  Device-1: AMD Cezanne driver: amdgpu v: kernel bus-ID: 30:00.0 chip-ID: 1002:1638
           class-ID: 0300
           Display: x11 server: X.Org 1.21.1.1 compositor: kwin_x11 driver: loaded: amdgpu,ati
           unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1
           Screen-1: 0 s-res: 3440x1440 s-dpi: 96 s-size: 910x381mm (35.8x15.0")
           s-diag: 987mm (38.8")
           Monitor-1: HDMI-A-0 res: 3440x1440 dpi: 110 size: 797x333mm (31.4x13.1")
           diag: 864mm (34")
           OpenGL: renderer: AMD RENOIR (DRM 3.42.0 5.14.16-zen1-1-zen LLVM 12.0.1)
           v: 4.6 Mesa 21.2.4 direct render: Yes
Audio:     Device-1: AMD driver: snd_hda_intel v: kernel bus-ID: 30:00.1 chip-ID: 1002:1637
           class-ID: 0403
           Device-2: AMD Family 17h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel
           v: kernel bus-ID: 30:00.6 chip-ID: 1022:15e3 class-ID: 0403
           Sound Server-1: ALSA v: k5.14.16-zen1-1-zen running: yes
           Sound Server-2: JACK v: 1.9.19 running: no
           Sound Server-3: PulseAudio v: 15.0 running: no
           Sound Server-4: PipeWire v: 0.3.40 running: yes
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
           driver: r8169 v: kernel port: f000 bus-ID: 2a:00.0 chip-ID: 10ec:8168 class-ID: 0200
           IF: enp42s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    Local Storage: total: 950.15 GiB used: 182.08 GiB (19.2%)
           SMART Message: Unable to run smartctl. Root privileges required.
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: Corsair MP600 CORE
           size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4
           type: SSD serial: <filter> rev: EGFM52.3 temp: 31.9 C scheme: GPT
           ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Lexar model: USB Flash Drive
           size: 14.91 GiB block-size: physical: 512 B logical: 512 B type: SSD serial: <filter>
           rev: 1100 scheme: MBR
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
           ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Cruzer Glide
           size: 3.73 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
           rev: 2.01 scheme: MBR
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition: ID-1: / raw-size: 78.12 GiB size: 78.12 GiB (100.00%) used: 21.18 GiB (27.1%) fs: btrfs
           dev: /dev/nvme0n1p3 maj-min: 259:3
           ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 576 KiB (0.2%)
           fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
           ID-3: /home raw-size: 818.91 GiB size: 818.91 GiB (100.00%) used: 160.9 GiB (19.6%)
           fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
           ID-4: /var/log raw-size: 78.12 GiB size: 78.12 GiB (100.00%) used: 21.18 GiB (27.1%)
           fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
           ID-5: /var/tmp raw-size: 78.12 GiB size: 78.12 GiB (100.00%) used: 21.18 GiB (27.1%)
           fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
           ID-1: swap-1 type: partition size: 34.18 GiB used: 0 KiB (0.0%) priority: -2
           dev: /dev/nvme0n1p2 maj-min: 259:2
           ID-2: swap-2 type: zram size: 29.29 GiB used: 2.2 MiB (0.0%) priority: 100
           dev: /dev/zram0
Sensors:   System Temperatures: cpu: 33.5 C mobo: N/A gpu: amdgpu temp: 25.0 C
           Fan Speeds (RPM): N/A
Info:      Processes: 472 Uptime: 1d 11h 48m wakeups: 1 Memory: 29.29 GiB used: 12.25 GiB (41.8%)
           Init: systemd v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages:
           pacman: 1861 lib: 525 Client: Unknown Client: garuda-assistant inxi: 3.3.08

anon26187667 · 29 November 2021 04:30

Seems like something's being a naughty child and refusing to go to sleep
In case it's something immediately waking it up, what's enabled in:

cat /proc/acpi/wakeup

Do you have an external keyboard or mouse connected (if you do have a mouse, could it be that? That's what was blocking my machine sleeping as it's so sensitive.

Heat_195 · 29 November 2021 06:19

cat /proc/acpi/wakeup
File: /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
GPP6      S4    *disabled
GP17      S4    *enabled   pci:0000:00:08.1
XHC0      S4    *enabled   pci:0000:30:00.3
XHC1      S4    *enabled   pci:0000:30:00.4
GPP0      S4    *disabled
GPP5      S4    *disabled
GPP3      S4    *enabled   pci:0000:00:02.1

The keyboard and mouse shouldn't be sensitive enough as they were connected to other PCs before without this issue. I don't know how to pull up specific info on those devices.

filo · 29 November 2021 08:25

As first thing, I would try to see if something changes maybe changing the HDMI cable.
I would also try maybe some other kernels...
Other than that, for the part below, I premise that I don't know much about this topic.
I just found a couple of interesting ideas that maybe you could work on a bit.
The first one is about using sudo systemd-inhibit --list to look for block inhibitors.

The second is about the possibility of configuring an InhibitDelayMaxSec

Bro · 29 November 2021 13:37

In addition to what @filo has suggested, please check your machine's BIOS for settings like "Wake on LAN" or some such. Also, please ensure your BIOS is up to date.

regards

Heat_195 · 30 November 2021 03:20

From sudo systemd-inhibit --list

WHO            UID  USER PID     COMM            WHAT                                                                       WHY                                       MODE
ModemManager   0    root 658     ModemManager    sleep                                                                      ModemManager needs to reset devices       delay
NetworkManager 0    root 600     NetworkManager  sleep                                                                      NetworkManager needs to turn off networks delay
UPower         0    root 2676    upowerd         sleep                                                                      Pause device polling                      delay
PowerDevil     1000 xxx  2650    org_kde_powerde handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch KDE handles power events                  block
discord        1000   xxx 602736  Discord         sleep                                                                      Application cleanup before suspend        delay
steam          1000   xxx 2543818 steam           sleep                                                                      Cleanup before suspend                    delay

6 inhibitors listed.

I didn't see "wake on LAN" in my BIOS when I checked that. I'll save trying a displayport cable and updating the BIOS as a last resort as that cable doesn't work and I don't want to buy another, and I'm not comfortable updating the BIOS for now out of fear of even the tiny chance I'll brick the MB.

When I locked my screen it never went off, darn.

I'd like to know more about how to find the corresponding devices using the

cat /proc/acpi/wakeup

cmd. In the form GPP6, XHC0, etc.

anon26187667 · 30 November 2021 03:43

XHC is USB 3
GPP I dunno, run

lspci | grep 08.1

For GP17, then 02.1 for GPP3 (etc)

Heat_195 · 30 November 2021 03:47

lspci | grep 08.1
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus

lspci | grep 02.1
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge

Heat_195 · 9 December 2021 19:22

Reading the links suggested leads me to look at xset monitor ID which might give me
a springboard to test something out. Problem is how does one find the
monitor ID to use to plug in to xset switches? Well searching yields
nothing. I can't use the cmd:

xset -display [display] dpms force standby

without knowing the display ID.

Its difficult to learn anything when there is nothing to go off of. How to create a udev rule to maybe bypass this issue? No vid made any sense explaining what is going on about udev rules so I'm just lost.

Bro · 10 December 2021 13:27

OMFG, do you also wear suspenders along with a belt? Are you afraid to cross the street?

Chances are your 2021 BIOS is OK, but you still will want to learn to be unafraid of your computer. It is you who is its master, not the other way around. And updating BIOS’ on modern machines tends to be anti-climatic nowadays.

I’d be happy to walk you through it at any point, should you choose to do so.

system · 24 December 2021 13:28

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.