[Installation] Monitor does not wake up after entering power saving

[HungryIAm]

Hi, new install of Debian 12 on a NUC13VYKi5 (NUC with Intel Iris Xe graphics). Installation going pretty well so far - a few dumb-user-errors, but what can you expect...?

Now, one issue that I fail to resolve by googling: Debian sends my monitor to sleep during inactivity. But the wake-up (moving mouse, pressing key) doesn't work. Switching the monitor off and on after pressing a key does work, though. Looks like Debian thinks the monitor would have been woken up while actually it isn't.

I looked at the journal (screen softly fading out around 18:31, screen then complaining about no signal & going dark, finally me pressing keys at 18:32, and then switching the monitor off and on again to get a picture), but cannot see anything helpful:

Code: Select all

Feb 12 18:31:23 homenuc gsd-media-keys[1815]: Unable to get default sink
Feb 12 18:32:02 homenuc gsd-media-keys[1815]: Unable to get default sink
Feb 12 18:32:02 homenuc gsd-media-keys[1815]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Feb 12 18:32:02 homenuc gsd-media-keys[1815]: Unable to get default source
Feb 12 18:32:16 homenuc gdm-password][170816]: gkr-pam: unlocked login keyring
Feb 12 18:32:16 homenuc dbus-daemon[1434]: [session uid=1000 pid=1434] Activating service name='org.freedesktop.FileManager1' requested by ':1.37' (uid=1000 pid=1600 comm="/usr/bin/gnome-shell")
Feb 12 18:32:16 homenuc NetworkManager[803]: <info>  [1707759136.8266] agent-manager: agent[9987814d0ec9d79c,:1.68/org.gnome.Shell.NetworkAgent/1000]: agent registered
Feb 12 18:32:16 homenuc nautilus[171708]: Connecting to org.freedesktop.Tracker3.Miner.Files
Feb 12 18:32:16 homenuc nautilus[171708]: g_hash_table_foreach: assertion 'hash_table != NULL' failed
Feb 12 18:32:16 homenuc dbus-daemon[1434]: [session uid=1000 pid=1434] Successfully activated service 'org.freedesktop.FileManager1'
Feb 12 18:32:16 homenuc dbus-daemon[1434]: [session uid=1000 pid=1434] Activating service name='org.gnome.DiskUtility' requested by ':1.202' (uid=1000 pid=171708 comm="/usr/bin/nautilus --gapplication-service")
Feb 12 18:32:16 homenuc dbus-daemon[1434]: [session uid=1000 pid=1434] Successfully activated service 'org.gnome.DiskUtility'
Feb 12 18:32:16 homenuc gnome-shell[1600]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Feb 12 18:32:16 homenuc gnome-shell[1600]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Feb 12 18:32:16 homenuc gnome-shell[1600]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Feb 12 18:32:16 homenuc gnome-shell[1600]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Feb 12 18:32:16 homenuc gnome-shell[1600]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Feb 12 18:32:16 homenuc gnome-shell[1600]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Feb 12 18:32:16 homenuc gnome-shell[1600]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Feb 12 18:32:16 homenuc gnome-shell[1600]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Feb 12 18:32:16 homenuc gnome-shell[1600]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).

Any pointer on what I could do/try to investigate would be helpful. Thanks.

Edit: The same problem applies when the machine wakes up from suspend. If the monitor is already on, a picture is shown. If the monitor is sleeping, I have to wake it manually.

[Aki]

Hello,

Log in previous messages do not capture relevant messages.

What is the type of cable that connects the monitor to the computer ?

What is your desktop environment (if any) ?

It would be useful to report your general hardware/software configuration; you can use the following command (the package inxi must be installed):

Code: Select all

inxi -Fz

[HungryIAm]

Apologies for not providing more helpful logging. I couldn't find anything relevant in the present logging, either, and just provided it as I didn't have anything else.

The monitor is connected with a HDMI cable. Desktop environment is Gnome, which was installed by default.

I hope the below output from inxi is helpful:

Code: Select all

# inxi -Fz
System:
  Kernel: 6.1.0-18-amd64 arch: x86_64 bits: 64 Desktop: GNOME v: 43.9
    Distro: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Mini-pc System: Intel Client Systems product: NUC13VYKi5 v: M98770-303
    serial: <filter>
  Mobo: Intel model: NUC13ANBi5 v: M89647-203 serial: <filter> UEFI: Intel
    v: ANRPL357.0027.2023.0607.1754 date: 06/07/2023
Battery:
  ID-1: hidpp_battery_0 charge: 100% condition: N/A
CPU:
  Info: 12-core (4-mt/8-st) model: 13th Gen Intel Core i5-1340P bits: 64
    type: MST AMCP cache: L2: 9 MiB
  Speed (MHz): avg: 434 min/max: 400/4600:3400 cores: 1: 435 2: 400 3: 400
    4: 400 5: 434 6: 400 7: 400 8: 400 9: 445 10: 555 11: 400 12: 400 13: 400
    14: 634 15: 400 16: 445
Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] driver: i915 v: kernel
  Display: server: X.Org v: 1.22.1.9 with: Xwayland v: 22.1.9 driver:
    dri: iris gpu: i915 note: X driver n/a resolution: 2560x1440~60Hz
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel Graphics (RPL-P)
Audio:
  Device-1: Intel Raptor Lake-P/U/H cAVS driver: snd_hda_intel
  API: ALSA v: k6.1.0-18-amd64 status: kernel-api
Network:
  Device-1: Intel Raptor Lake PCH CNVi WiFi driver: iwlwifi
  IF: wlo1 state: down mac: <filter>
  Device-2: Intel Ethernet I226-V driver: igc
  IF: enp86s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX211 Bluetooth type: USB driver: btusb
  Report: hciconfig ID: hci0 state: up address: <filter>
Drives:
  Local Storage: total: 1.82 TiB used: 28.72 GiB (1.5%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 990 PRO 2TB size: 1.82 TiB
Partition:
  ID-1: / size: 239.25 GiB used: 10.06 GiB (4.2%) fs: ext4 dev: /dev/nvme0n1p5
  ID-2: /boot/efi size: 96 MiB used: 70.7 MiB (73.7%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 41.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 350 Uptime: 2h 18m Memory: 30.9 GiB used: 3.65 GiB (11.8%)
  Shell: Bash inxi: 3.3.26

Thanks.

[mrmazda]

Inxi -Fz didn't say quite enough. It appears there is no X display driver loading. Please copy and paste input/output from inxi -GSaz --vs. Also, if you can find Xorg.0.log in /var/log/ or ~/.local/share/xorg/, please attach it or pastebin it.

[HungryIAm]

Sure, here you go for the inxi output:

Code: Select all

# inxi -GSaz --vs
inxi 3.3.26-00 (2023-03-28)
System:
  Kernel: 6.1.0-18-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-amd64
    root=UUID=a44066df-be2d-4d91-9ca9-358b225eceb1 ro quiet
  Desktop: GNOME v: 43.9 tk: GTK v: 3.24.38 wm: gnome-shell dm: GDM3 v: 43.0
    Distro: Debian GNU/Linux 12 (bookworm)
Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] driver: i915 v: kernel
    arch: Gen-13 process: Intel 7 (10nm) built: 2022+ ports: active: HDMI-A-1
    empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:a7a0
    class-ID: 0300
  Display: server: X.Org v: 1.22.1.9 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: dri: iris gpu: i915 note: X driver n/a
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
    s-diag: 777mm (30.58")
  Monitor-1: HDMI-A-1 mapped: XWAYLAND0 model: Asus ROG PG279Q
    serial: <filter> built: 2015 res: 2560x1440 hz: 60 dpi: 108 gamma: 1.2
    size: 600x340mm (23.62x13.39") diag: 686mm (27") ratio: 16:9 modes:
    max: 2560x1440 min: 640x480
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel Graphics (RPL-P)
    direct-render: Yes

The Xorg.0.log from /var/log/installer can be found in Pastebin

[mrmazda]

The installer log tells us that a generic driver was used to install; nothing more that is useful. The fresh inxi output somewhat reinforces that there is an X driver problem by (1) the whitespace between "driver:" and "dri:" and (2) "X driver n/a". This may reflect brokenness of inxi in v3.3.26. Upgrading of inxi to current 3.3.33 may tell a slightly different picture. You may upgrade inxi by editing /etc/inxi.conf to say B_ALLOW_UPDATE=true instead of false, then running sudo inxi -U to update[1], and then run inxi -GSaz --vs again to see if drivers remain missing. I suspect what you actually need are a backport kernel and/or server software, because your Q1'23 CPU/GPU is only some months older than Bookworm's release, so likely either Bookworm's 6.1 kernel provides incomplete i915 support, and/or its Modesetting DIX or Iris DRI lack or provide incomplete support. Alternatively, consider upgrading to Trixie.

Have you checked to see if your NUC has an available firmware update?

[1] as alternative to updating the installed inxi, you may add the upstream version to /usr/local/bin/ by following the instructions here.

[HungryIAm]

No pending firmware updates for the NUC I'm aware of.

Please see below for the output from updated inxi:

Code: Select all

# inxi -GSaz --vs
inxi 3.3.31-00 (2023-11-02)
System:
  Kernel: 6.1.0-18-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-amd64
    root=UUID=a44066df-be2d-4d91-9ca9-358b225eceb1 ro quiet
  Desktop: GNOME v: 43.9 tk: GTK v: 3.24.38 wm: gnome-shell dm: GDM3 v: 43.0
    Distro: Debian GNU/Linux 12 (bookworm)
Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] driver: i915 v: kernel
    arch: Gen-13 process: Intel 7 (10nm) built: 2022+ ports: active: HDMI-A-1
    empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:a7a0
    class-ID: 0300
  Display: server: X.Org v: 1.22.1.9 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: dri: iris gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
    s-diag: 777mm (30.58")
  Monitor-1: HDMI-A-1 mapped: XWAYLAND0 model: Asus ROG PG279Q
    serial: <filter> built: 2015 res: 2560x1440 hz: 60 dpi: 108 gamma: 1.2
    size: 600x340mm (23.62x13.39") diag: 686mm (27") ratio: 16:9 modes:
    max: 2560x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
    inactive: wayland
  API: OpenGL v: 4.6 vendor: intel mesa v: 22.3.6 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel Graphics (RPL-P)
    device-ID: 8086:a7a0 memory: 30.18 GiB unified: yes

Looks a bit better on the X driver, at least the "note: X driver n/a" is gone.

But if this is because the machine is too new, then I guess I will have to live with this for the time being. Bookworm is too stable otherwise for me to go lightheartedly to a different release.

[mrmazda]

FYI, https://smxi.org/docs/inxi-changelog.htm is the inxi changelog.

You still have a gap between "driver:" and "dri: iris gpu: i915". Compare to mine (about 2 years older):

# inxi -GSaz --vs
inxi 3.3.33-00 (2024-02-06)
System:
  Kernel: 6.1.0-18-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/vmlinuz
    root=LABEL=tm8p10deb12 noresume ipv6.disable=1 net.ifnames=0
    consoleblank=0 preempt=full mitigations=off
  Desktop: TDE (Trinity) v: R14.1.1 tk: Qt v: 3.5.0 wm: Twin v: 3.0
    with: kicker vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 12 (bookworm)
Graphics:
  Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
    ports: active: DP-1,HDMI-A-1,HDMI-A-2 empty: HDMI-A-3 bus-ID: 00:02.0
    chip-ID: 8086:4c8b class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: Twin v: 3.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0
    screens: 1
...
#

[HungryIAm]

Ok, so I guess this means that I will have to live with this if I want to stay on stable Bookworm for now. I will survive - thanks for your help with looking into this!

[Aki]

Hello,

The monitor is connected with a HDMI cable

Can you test a different HDMI cable ?

Can you test monitor power saving with a Debian Testing Live ISO (because it uses a newer kernel) ?

• https://cdimage.debian.org/cdimage/weekly-live-builds/amd64/iso-hybrid/

If it would be useful to rename the subject of the first post to make it more understandable to other users and readers with the same problem, or that might help you; i.e.:

Monitor does not wake up after entering power saving

Hope this helps.

[HungryIAm]

The monitor is connected with a HDMI cable

Can you test a different HDMI cable ?

I don't have a different cable. If I went to buy one for testing purposes, any specs or anything I should watch out for rather than just buying the cheapest one?

Can you test monitor power saving with a Debian Testing Live ISO (because it uses a newer kernel) ?

• https://cdimage.debian.org/cdimage/weekly-live-builds/amd64/iso-hybrid/

Same behavior, unfortunately.

[HungryIAm]

Ok, it took a while, but I finally gave up and bought a different HDMI cable. Went for a HDMI 2.1 one from KabelDirekt, allegedly certified. No change in the behavior.