Monitor not working after switching off

Issues & Assistance
, ,
1

Hello,
I am using Garuda (and KDE) since a few days.
I absolutely love it so far, but I am experiencing one issue.

If I switch on my PC and switch on the monitor a bit later than the PC
OR
if the monitor is automatically switching off for energy saving
the screen won’t work again until I reboot the PC.
Restarting the screen, unpluggin and replugging it, plugging it into another port,… all won’t help.

Switching the monitor off and back on later or switching it to another input channel and switching back later all works fine and it is coming back on with no issues.

Here is my garuda-inxi:

System:
Kernel: 6.17.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=041e63c0-043f-453d-88a1-1bade9d8c7d6 rw rootflags=subvol=@
quiet loglevel=3
Desktop: KDE Plasma v: 6.5.3 tk: Qt v: N/A info: frameworks v: 6.20.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX Z590-E GAMING WIFI v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
Firmware: UEFI vendor: American Megatrends v: 0902 date: 05/18/2021
CPU:
Info: model: 11th Gen Intel Core i9-11900K bits: 64 type: MT MCP
arch: Rocket Lake gen: core 11 level: v4 note: check built: 2021+
process: Intel 14nm family: 6 model-id: 0xA7 (167) stepping: 1
microcode: 0x64
Topology: cpus: 1x dies: 1 clusters: 8 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 4 MiB
desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 800 min/max: 800/5100:5300 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800
bogomips: 112128
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: EVGA
driver: nvidia v: 580.105.08 alternate: nouveau,nvidia_drm
non-free: 550-580.xx+ status: current (as of 2025-11; EOL~2026-12-xx)
arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
gen: 2 speed: 5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
active: HDMI-A-1 empty: DP-1, DP-2, DP-3, Unknown-2 bus-ID: 01:00.0
chip-ID: 10de:1e07 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
display-ID: 0
Monitor-1: HDMI-A-1 model: Panasonic Panasonic-TV serial: <filter>
built: 2021 res: mode: 3840x2160 hz: 60 scale: 145% (1.45) to: 2648x1490
dpi: 76 gamma: 1.2 size: 698x392mm (27.48x15.43") diag: 1469mm (57.8")
ratio: 16:9 modes: max: 3840x2160 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: nvidia inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.105.08
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
memory: 10.74 GiB display-ID: :1.0
API: Vulkan v: 1.4.328 layers: 15 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 2080 Ti driver: nvidia v: 580.105.08 device-ID: 10de:1e07
surfaces: N/A device: 1 type: cpu name: llvmpipe (LLVM 21.1.5 256 bits)
driver: mesa llvmpipe v: 25.2.7-arch1.1 (LLVM 21.1.5)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl,nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Tiger Lake-H HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:43c8 class-ID: 0403
Device-2: NVIDIA TU102 High Definition Audio vendor: EVGA
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:10f7 class-ID: 0403
Device-3: C-Media CM106 Like Sound Device
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-11:11 chip-ID: 0d8c:0102 class-ID: 0300
Device-4: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-14:9
chip-ID: 0b05:1996 class-ID: 0300
API: ALSA v: k6.17.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 04:00.0 chip-ID: 8086:15f3
class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 05:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp5s0 state: down mac: <filter>
Device-3: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 06:00.0
chip-ID: 8086:2725 class-ID: 0280
IF: wlp6s0 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:2 chip-ID: 8087:0032
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.4
lmp-v: 13 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 1.82 TiB used: 342.28 GiB (18.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 232.96 GiB (25.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 664 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 232.96 GiB (25.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 232.96 GiB (25.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 232.96 GiB (25.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.62 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 45.8 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 64 GiB note: est. available: 62.62 GiB used: 5.16 GiB (8.2%)
Processes: 422 Power: uptime: 2h 18m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 25 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
tool: systemctl
Packages: 1712 pm: pacman pkgs: 1706 libs: 503 tools: octopi,paru
pm: flatpak pkgs: 6 Compilers: gcc: 15.2.1 Shell: Bash v: 5.3.8
default: fish v: 4.2.1 running-in: konsole inxi: 3.3.40
Garuda (2.11.1-1):
System install date:     2025-11-29
Garuda release:          251103
Last full system update: 2025-12-05
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-utils nvidia-open-dkms garuda-hardware-profile-nvidia garuda-hardware-profile-standard
Windows dual boot:       No/Undetected
Failed units:
--- System Health Check Report ---
25/26 checks run in 0.72 seconds ⌛
Powered by garuda-health 🦅

✅ System health check passed. No issues found.

I am on KDE, plasma, wayland.
My screen is a Panasonic TX-40JXN888 (yes, that is sold as a TV, but works well for me).
The screen is connected to a port of my Nvidia card via HDMI.

I switched off all energy saving options whatsover on my PC, so it is not going into standby, only thing switching off is the screen.

I found online that it could be connected to DPMS, so I checked:

╰─λ xset -dpms
server does not have extension for -dpms option

I also found the advice to switch to wayland and learned that this is the default already.

Any ideas?
Thanks in advance, any help is greatly appreciated!

2

The following thread is about system sleep/hibernate rather than monitor sleep, but maybe the services mentioned there are needed both ways:

1 Like
3

Hello and Welcome :wink:

If I switch on my PC and "switch on" the monitor a bit ""later"" than the PC

This is a security normal behavior because of the POST ( Power On Self Test ) startup from the Mainboard. There is mostly not a way to disable it on newer Mainboards, because it is a part of the Boot Progress. ( Didnt find it on my Asus Bios because older PCs dont cares)

You should have 4 LED Lights/Indicator on the Mainboard and if its not detecting a Display output ala Monitor/TV it will not Boot (stopped on VGA) in my case a white light. This is written in the Manual :wink: ( If you dont installed the little SPEAKER to give the BEEP BEEP BEEP indicator :wink: .

If the Power Safe from the Monitor/Display is to short itself in their Settings before same behavior ( check the power Safe Settings not on 10 Seconds) if its after the Boot you should check the other Reply with Nvidia Settings.

grafik
grafik170×133 3.92 KB

grafik
grafik863×626 118 KB

Just as a Info beside its outdated too if you have any other trouble update it . Read the Website may you can update until before you need those Intel update ME Tool. ( May work with a WinPe iso and Ventoy) I dont need this on my Asus Mainboard with Amd .

3 Likes
4

Btw…
The cause of your problems could also lie elsewhere. It is not uncommon for some TVs to have a faulty EDID implementation. Search for EDID handshake online for more information.
Last but not least, the HDMI cable you use also plays a major role. Many high-speed cables on the market don´t deliver what they promise.

5 Likes
5

Tested, did not fix the issue unfortunately.
Thank you anyway, your help is much appreciated.

1 Like
6

Yes i used to have this an had to write a script to restart the monitor. However this will also kill all open apps.

~~~

#!/usr/bin/bash

eval ‘kwin_wayland --replace &’;sleep 2;pkill -9 plasmashell;sleep 1;eval ‘plasmashell &’

~~~

make the code above an executable script and hotkey it for when you need it.

hope it works for you

3 Likes
7

Excuse my late reply, I needed to make time to read and comprehend all the things you wrote.
Thank you very much for your assistance.
Also, for pointing out that I should take the BIOS version to a museum :smiley: Since it is not giving me trouble, I never considered updating it. If it starts to do so, I will update it.

I wasn’t aware of that BIOS function but I understand that this part of the issue is not fixable than.. I found an option in the TV configuration tho to power it on automatically if the connected PC is powered on.
So I will use that option to fix part of the problem.
Thank you :slight_smile:

1 Like
8

Thank you, very interesting point. I wasn’t aware of this.
On the other hand, I used the same cables, monitor, graphics card,… before.
The only thing I switched out is the operating system of my pc. So I do not consider the cable to be a problem… I shall still check the settings of my screen and maybe try a different cable.
Thank you for your assistance.

2 Likes
9

Thank you very much.
I copied the script and hotkeyed it.
I shall brainlessly watch videos online until my screen powers off for power saving to test it :smiley:

2 Likes
10

Thank you all very much for your help.
I ended up configuring an “auto switch on” on my screen, which is solving my issue at boot.
Besides that I disabled the auto standby and left on the auto power off.
This is not solving whatever caused the behaviour in the first place, but now it is not occuring anymore, which is good enough for me.
Thank you everyone :slight_smile: