Monitors don't turn off

[slano]

I have exactly the same issue, fresh install of mint 21, new user. both monitors go to sleep after period defined in Power management, but both wake up after a couple of seconds. I tried forcing off state with set dpms force off, but the behavior is exactly the same..

I had no issues when running mint 20.3. I tried 5.15.0-43-generic as well as -oem kernel, same behavior.

any way I can investigate what is waking monitors up?

[SMG]

any way I can investigate what is waking monitors up?

These types of issues are often hardware dependent and thus it is important to follow the forum rule about creating a new topic for your issue. I have split your post into a new issue to comply with that rule.

Please open the System Reports app and click the System Information tab on the left. Your computer's information should come up in the right pane. Then click Copy and paste the results into a reply window here so we can see how Linux Mint views your hardware.

[slano]

Thanks a lot, I'll create new topic next time.

Here's the System info:

Code: Select all

System:
  Kernel: 5.15.0-43-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: Cinnamon 5.4.9
    tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME Q370M-C v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 2811 date: 05/27/2020
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard ERGO K860 serial: <filter>
    charge: 100% (should be ignored) status: Discharging
  Device-2: hidpp_battery_1 model: Logitech MX Ergo Multi-Device Trackball serial: <filter>
    charge: 50% (should be ignored) status: N/A
CPU:
  Info: 6-core model: Intel Core i5-9600K bits: 64 type: MCP arch: Coffee Lake rev: D cache:
    L1: 384 KiB L2: 1.5 MiB L3: 9 MiB
  Speed (MHz): avg: 4397 high: 4406 min/max: 800/4600 cores: 1: 4406 2: 4380 3: 4400 4: 4397
    5: 4400 6: 4399 bogomips: 44398
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK driver: i915 v: kernel
    ports: active: DP-1,DP-2 empty: DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0
    chip-ID: 8086:3e98
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5120x1440 s-dpi: 96
  Monitor-1: DP-1 pos: primary,right model: PA278QV res: 2560x1440 dpi: 109 diag: 685mm (27")
  Monitor-2: DP-2 pos: primary,left model: PA278QV res: 2560x1440 dpi: 109 diag: 685mm (27")
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 22.0.5 direct render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:a348
  Device-2: Thesycon System & Consulting GmbH D10s type: USB driver: snd-usb-audio bus-ID: 1-9:4
    chip-ID: 152a:8750
  Sound Server-1: ALSA v: k5.15.0-43-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: no
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Ethernet I219-LM vendor: ASUSTeK driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15bb
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: ASUSTek ASUS USB-BT500 type: USB driver: btusb v: 0.8 bus-ID: 1-3:2 chip-ID: 0b05:190e
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1
    sub-v: 8a6b
Drives:
  Local Storage: total: 698.65 GiB used: 254.48 GiB (36.4%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB size: 465.76 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 48.9 C
  ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s
    serial: <filter>
Partition:
  ID-1: / size: 465.26 GiB used: 254.47 GiB (54.7%) fs: btrfs dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat dev: /dev/nvme0n1p1
  ID-3: /home size: 465.26 GiB used: 254.47 GiB (54.7%) fs: btrfs dev: /dev/nvme0n1p2
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swapfile
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 16 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002
  Device-1: 1-3:2 info: ASUSTek ASUS USB-BT500 type: Bluetooth driver: btusb rev: 1.1
    speed: 12 Mb/s chip-ID: 0b05:190e
  Device-2: 1-7:3 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID
    driver: logitech-djreceiver,usbhid rev: 2.0 speed: 12 Mb/s chip-ID: 046d:c52b
  Device-3: 1-9:4 info: Thesycon System & Consulting GmbH D10s type: Audio driver: snd-usb-audio
    rev: 2.0 speed: 480 Mb/s chip-ID: 152a:8750
  Hub-2: 1-10:5 info: VIA Labs USB2.0 Hub ports: 4 rev: 2.1 speed: 480 Mb/s chip-ID: 2109:2815
  Device-1: 1-11:6 info: Alcor Micro Multi Flash Reader type: Mass Storage driver: usb-storage
    rev: 2.0 speed: 480 Mb/s chip-ID: 058f:6366
  Hub-3: 2-0:1 info: Super-speed hub ports: 10 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: apt: 2264
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/docker.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https: //download.docker.com/linux/ubuntu jammy stable
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https: //dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/insync.list
    1: deb http: //apt.insync.io/ubuntu jammy non-free contrib
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //ftp.energotel.sk/pub/linux/linuxmint-packages vanessa main upstream import backport
    2: deb http: //ftp.energotel.sk/pub/linux/ubuntu jammy main restricted universe multiverse
    3: deb http: //ftp.energotel.sk/pub/linux/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //ftp.energotel.sk/pub/linux/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 369 Uptime: 37m Memory: 62.56 GiB used: 4.36 GiB (7.0%) Init: systemd v: 249
  runlevel: 5 Compilers: gcc: 11.2.0 alt: 11 Client: Unknown python3.10 client inxi: 3.3.13

[Termy]

I find a swift bang from a sledgehammer to be a solid solution for turning them off, but getting them back on again can be a bit tricky.

[slano]

Some further info from the moment the monitors turned back on (after sleeping for a couple of seconds):

jounralctl --user -f

Code: Select all

Aug 07 21:32:22 dextop cinnamon-screensaver-pam-helper[40604]: pam_unix(cinnamon-screensaver:auth): conversation failed
Aug 07 21:32:22 dextop cinnamon-screensaver-pam-helper[40604]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [slano]
Aug 07 21:32:23 dextop dbus-daemon[1521]: [session uid=1000 pid=1521] Activating service name='org.cinnamon.CalendarServer' requested by ':1.364' (uid=1000 pid=29472 comm="cinnamon --replace " label="unconfined")
Aug 07 21:32:23 dextop dbus-daemon[1521]: [session uid=1000 pid=1521] Successfully activated service 'org.cinnamon.CalendarServer'

.xsession-errors

Code: Select all

(cinnamon:29472): Gjs-WARNING **: 21:32:21.470: JS ERROR: Exception in callback for signal: monitors-changed: TypeError: this.findMonitorForActor(...) is undefined
_updateVisibility@/usr/share/cinnamon/js/ui/layout.js:589:27
_relayout@/usr/share/cinnamon/js/ui/layout.js:612:14
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
_monitorsChanged@/usr/share/cinnamon/js/ui/layout.js:157:14

(cinnamon:29472): Gjs-WARNING **: 21:32:21.601: JS ERROR: Exception in callback for signal: monitors-changed: TypeError: this.findMonitorForActor(...) is undefined
_updateVisibility@/usr/share/cinnamon/js/ui/layout.js:589:27
_relayout@/usr/share/cinnamon/js/ui/layout.js:612:14
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
_monitorsChanged@/usr/share/cinnamon/js/ui/layout.js:157:14

** (csd-color:6585): WARNING **: 21:32:21.965: failed to reset xrandr-ASUSTek COMPUTER INC-PA278QV-M5LMQS147719 gamma tables: gamma size is zero
** (csd-color:6585): WARNING **: 21:32:21.965: failed to reset xrandr-ASUSTek COMPUTER INC-PA278QV-L8LMQS127897 gamma tables: gamma size is zero
** (csd-color:6585): WARNING **: 21:32:21.965: failed to reset xrandr-ASUSTek COMPUTER INC-PA278QV-M5LMQS147719 gamma tables: gamma size is zero
** (csd-color:6585): WARNING **: 21:32:21.965: failed to reset xrandr-ASUSTek COMPUTER INC-PA278QV-L8LMQS127897 gamma tables: gamma size is zero
** (cinnamon:29472): CRITICAL **: 21:32:22.836: na_tray_manager_manage_screen: assertion 'manager->screen == NULL' failed
...

Xorg.0.log

Code: Select all

[ 11532.208] (EE) modeset(0): failed to set mode: No such file or directory
[ 11532.208] (WW) modeset(0): hotplug event: connector 112's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...
[ 11532.926] (II) modeset(0): EDID vendor "AUS", prod id 9984
[ 11532.926] (II) modeset(0): Using hsync ranges from config file
[ 11532.926] (II) modeset(0): Using vrefresh ranges from config file
[ 11532.926] (II) modeset(0): Printing DDC gathered Modelines:
[ 11532.926] (II) modeset(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
[ 11532.926] (II) modeset(0): Modeline "1280x768"x0.0   79.50  1280 1344 1472 1664  768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 11532.926] (II) modeset(0): Modeline "2560x1440"x0.0  298.47  2560 2583 2615 2670  1440 1478 1486 1492 +hsync -vsync (111.8 kHz e)
...

also dmesg, each wakeup is this error:

Code: Select all

[Sun Aug  7 22:24:17 2022] i915 0000:00:02.0: [drm] *ERROR* failed to enable link training
[Sun Aug  7 22:25:22 2022] i915 0000:00:02.0: [drm] *ERROR* failed to enable link training
[Sun Aug  7 22:26:13 2022] i915 0000:00:02.0: [drm] *ERROR* failed to enable link training
[Sun Aug  7 22:27:05 2022] i915 0000:00:02.0: [drm] *ERROR* failed to enable link training

[SMG]

The below is a problem.

Code: Select all

[ 11532.208] (EE) modeset(0): failed to set mode: No such file or directory

Please use this command in a terminal to upload the X Server log file to termbin:

Code: Select all

cat /var/log/Xorg.0.log | nc termbin.com 9999

It will return with a url address that you can post in your next reply.

[slano]

Here is the log: https://termbin.com/azfl

btw I tried the same with Live Mint 21 and it's the same behavior and error message

[SMG]

Everything is setting up fine. The error messages are later in the file and relate to specific modelines. That's the first time I've seen something like that and am not sure what might cause it. I included the line before the errors because I've also never seen "(null)" as a resolution.

Code: Select all

[    31.656] (II) modeset(0): Modeline "(null)"x59.9  197.00  2048 2184 2400 2752  1152 1155 1160 1195 -hsync +vsync (71.6 kHz e)
[    73.361] (EE) modeset(0): failed to set mode: No such file or directory
[    73.401] (EE) modeset(0): failed to set mode: No such file or directory
[    73.455] (EE) modeset(0): failed to set mode: No such file or directory
[    73.455] (WW) modeset(0): hotplug event: connector 112's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...

Considering there is only one set of these, I would guess it might relate to one of your monitors. Both your monitors appear to have the same 'prod id' so I do not know which one is generating the error messages.

I did find a bug modeset(0): failed to set mode: No such file or directory, but it was filed against an older kernel (5.0) and is now listed as closed.

Both monitors show DPMS capabilities: Off.

What is the output of

Code: Select all

xset -q

You indicated you didn't have any problems with LM20.3. What kernel were you using with it?

[slano]

This is getting really strange.. I tried booting with monitors disconnected one by one, the monitor still wakes up from sleep after issuing xset dpms force off, but the error from Xorg.0.log, as well as the dmesg error "failed to enable link training" is not present..


only right - https://termbin.com/m3n0
only left - https://termbin.com/jrht


xset q (with both monitors on):

Code: Select all

Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000002
  XKB indicators:
    00: Caps Lock:   off    01: Num Lock:    on     02: Scroll Lock: off
    03: Compose:     off    04: Kana:        off    05: Sleep:       off
    06: Suspend:     off    07: Mute:        off    08: Misc:        off
    09: Mail:        off    10: Charging:    off    11: Shift Lock:  off
    12: Group 2:     off    13: Mouse Keys:  off
  auto repeat delay:  228    repeat rate:  52
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  0
Colors:
  default colormap:  0x20    BlackPixel:  0x0    WhitePixel:  0xffffff
Font Path:
  /usr/share/fonts/X11/misc,/usr/share/fonts/X11/Type1,built-ins
DPMS (Energy Star):
  Standby: 0    Suspend: 0    Off: 0
  DPMS is Enabled
  Monitor is On

I was running linux-xanmod kernel on 20.3, I'll try it later on today on 21 as well and report back.

[slano]

I did some further digging as this issue is driving me crazy

I completely restored my disk with Una 20.3, running 5.18.16-xanmod1, monitor stays in sleep.. Here's the Xorg.0.log:
https://termbin.com/yz2o

Right now I have only one monitor connected (for easier troubleshooting), running Vanessa with 5.18.16-xanmod1 as well, monitor wakes up a couple of seconds after sleeping, here's the Xorg.0.log:
https://termbin.com/5agrj

the only notable difference is that "null" resolution is not present on Una, but proper resolution is reported:
Vanessa:

Code: Select all

[    16.379] (II) modeset(0): Modeline "(null)"x59.9  197.00  2048 2184 2400 2752  1152 1155 1160 1195 -hsync +vsync (71.6 kHz e)

Una:

Code: Select all

[    17.906] (II) modeset(0): Modeline "2048x1152"x59.9  197.00  2048 2184 2400 2752  1152 1155 1160 1195 -hsync +vsync (71.6 kHz e)

[slano]

A major breakthrough!!!

The issue is only present when connecting the monitor using display port connector. I've connected the monitor using HDMI and now it sleeps properly, also "null" modeline is gone. However, it's a bummer, since my motherboard only has one HDMI output, so it leaves me basically with one monitor only (if I connect the second monitor using display port, the issue is back). I don't think it's issue with cables, since I'm using cables that came with the monitor, and sleeping over display port worked without any issues in past on Una (as well as on windows 10/11).

log from Vanessa, xanmod-kernel and one monitor over HDMI, no issue present:
https://termbin.com/i9wh8

Any idea what to try next?

[SMG]

A major breakthrough!!!

The person in the other topic just posted the reverse. Fine with DP, but not with HDMI.

I'm in a different time zone than both of you and it will take some time to go through the logs you posted. I will see if I can figure out what might be the cause. The fact you used the same kernel in both versions should mean it's not a driver issue, but maybe driver interaction with some other code is? I don't really know just yet.

[slano]

No worries, take your time, and thanks for all the help so far! I somehow feel its not going to be a easy to find the root cause on this one..

Meanwhile I'll create a bootable persistent Una USB stick with xanmod kernel, so I don't have to go through disk image/backup restore procedure every time, since it takes me ~4 hours to do so.

[roblm]

What is the output of xset dpms q with both monitors connected?

[slano]

one monitor over HDMI:

Code: Select all

Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000002
  XKB indicators:
    00: Caps Lock:   off    01: Num Lock:    on     02: Scroll Lock: off
    03: Compose:     off    04: Kana:        off    05: Sleep:       off
    06: Suspend:     off    07: Mute:        off    08: Misc:        off
    09: Mail:        off    10: Charging:    off    11: Shift Lock:  off
    12: Group 2:     off    13: Mouse Keys:  off
  auto repeat delay:  228    repeat rate:  52
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  0
Colors:
  default colormap:  0x20    BlackPixel:  0x0    WhitePixel:  0xffffff
Font Path:
  /usr/share/fonts/X11/misc,/usr/share/fonts/X11/Type1,built-ins
DPMS (Energy Star):
  Standby: 0    Suspend: 0    Off: 0
  DPMS is Enabled
  Monitor is On

one monitor over HDMI, second over display port:

Code: Select all

Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000002
  XKB indicators:
    00: Caps Lock:   off    01: Num Lock:    on     02: Scroll Lock: off
    03: Compose:     off    04: Kana:        off    05: Sleep:       off
    06: Suspend:     off    07: Mute:        off    08: Misc:        off
    09: Mail:        off    10: Charging:    off    11: Shift Lock:  off
    12: Group 2:     off    13: Mouse Keys:  off
  auto repeat delay:  228    repeat rate:  52
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  600    cycle:  600
Colors:
  default colormap:  0x20    BlackPixel:  0x0    WhitePixel:  0xffffff
Font Path:
  /usr/share/fonts/X11/misc,/usr/share/fonts/X11/Type1,built-ins
DPMS (Energy Star):
  Standby: 0    Suspend: 0    Off: 0
  DPMS is Enabled
  Monitor is On

diff

Code: Select all

19c19
<   timeout:  600    cycle:  600
---
>   timeout:  0    cycle:  0

[roblm]

I see the xset dpms q command gives the same info as xset q, which you previously used.

I think a timeout value of 0 would disable the screensaver.

Would you try using xset s 0 and then try to suspend.

If that doesn’t help, then try xset s off


EDITED: also try xset s 0 0

[slano]

same issue with xset s 0 as well as with xset s off, together with line in dmesg:

Code: Select all

i915 0000:00:02.0: [drm] *ERROR* [ENCODER:111:DDI C/PHY C][DPRX] Failed to enable link training

once I turn off the DP monitor, issue is gone, and primary monitor connected via HDMI doesn't automatically wake up from the sleep

EDITED: same issue with xset s 0 0

[roblm]

Can you force a suspend with xset dpms force suspend

[slano]

it behaves the same for off, suspend and standby :/

[SMG]

So I guess the good news is LM20.3 does work for you and it is supported until April 2025.

I compared the logs and compared to the one from the other topic and both the modesetting driver in your case and the admgpu driver in the other person's case are using the ABI class: X.Org Video Driver, version 25.2. In LM20.3, version 24.1 was used.

The Xorg version between the two also differs (1.21.1.3 versus 1.20.13), but not all the display driver versions differ between the two Xorg versions. For example, the glamoregl version (dealing with X acceleration in your case) is the same for both. That gives me the impression whatever is in version 25.2 might be the issue, but I have not yet been able to figure out exactly what that is and where the code/bug reports might be located.

Code: Select all

i915 0000:00:02.0: [drm] *ERROR* [ENCODER:111:DDI C/PHY C][DPRX] Failed to enable link training

While hunting for version 25.2, I did come across this bug report for a laptop No external video output after suspend on Intel Xe Graphics (TGL GT2) where someone posted that error message, but without the [ENCODER:111:DDI C/PHY C][DPRX] in the middle. The person responding to their bug indicated, "This is a firmware or kernel issue. The error failed to enable link training effectively means that the video output is unlikely to be usable. Nowadays the data rates are so high that the digital transceivers need training for the specific cable that is attached. If link training is not done the receiver side will get garbage data."

I do not how that type of explanation might relate to your situation. I do not have an LM21 install to know if the linux-firmware version is different or if that is even to what he was referring. There is also i915 firmware which is part of a Linux-based distro install, but usually there are errors if the necessary packages are not there and your hardware has been available for several years (ie. not brand new).

I had checked earlier and your desktop does have the latest UEFI version so there is nothing more to be done in that regard. And you tried the same kernel with both LM20.3 and LM21 and the problem did not happen on both so that would seem to rule out the kernel version.

I did a search on [ENCODER:111:DDI C/PHY C][DPRX] the results are, for me, deep in the weeds of electronic signalling so I do not know to what it specifically relates.

Is there anything else in dmesg after the wakeup which might related to graphics or even usb ports? (You both have Logitech MX mice, but different versions.)