[Bug] RTX 5090 FE + KDE Wayland: DisplayPort fails to wake after DPMS, outputs become unusable until VT/session reactivation – 615.71.09

System

  • GPU: NVIDIA GeForce RTX 5090 Founders Edition
  • Driver: 615.71.09
  • Distribution: CachyOS
  • Kernel: 7.2.6
  • Desktop: KDE Plasma / KWin
  • Session: Wayland
  • Monitor: Samsung Odyssey Neo G9 57"
  • Resolution: 7680×2160
  • Refresh rate during latest reproduction: 240 Hz
  • Connection: DisplayPort
  • nvidia_drm modeset enabled

Problem

When KDE turns the monitor off through display power management and the display remains off for a long period (for example overnight), moving the mouse or pressing the keyboard does not restore the display.

The computer itself remains running and responsive. The KDE/Wayland session and kwin_wayland remain running.

I reproduced the problem on September 24, 2026. The first wake attempt was approximately 07:43 local time.

During/after the failure, the logs show KDE losing the physical output and creating a placeholder output. During subsequent DisplayPort recovery attempts, the kernel logged an NVIDIA modeset error including:

nvHandleCpEventDeferredWork: displayId 0x8000 invalid

KWin subsequently logged:

Applying output configuration failed!

and later:

Failed to open drm device

DisplayPort connector behavior

There is another unusual behavior during the same boot.

Initially the monitor was connected to one of the RTX 5090 FE DisplayPort connectors. After the failure, moving it to another DP connector could restore an output.

During subsequent testing in the same boot, previously used DP connectors stopped producing an image. Eventually DP1 and DP2 produced a black screen while DP3 could be used to obtain a TTY.

After additional connector testing, DP3 also produced a black screen.

I was able to recover without rebooting using the following sequence:

  1. Switch to a TTY with Ctrl+Alt+F4.
  2. If the TTY was still not visible, unplug/replug DisplayPort on DP3 while the TTY VT was selected.
  3. The TTY login screen then appeared.
  4. Log in and check loginctl list-sessions.
  5. The original KDE Wayland session was still online on tty1.
  6. Run loginctl activate 1.
  7. The existing KDE Wayland desktop immediately became visible again.

No reboot or KWin restart was required.

nvidia-smi continued to work during the problem and showed kwin_wayland still running.

Refresh-rate observation

I have also experienced the wake problem at 60 Hz. On that occasion, unplugging/replugging DisplayPort restored the display more easily. The latest reproduction was at 7680×2160 @ 240 Hz and was substantially harder to recover.

I do not yet know whether refresh rate is causal.

Expected behavior

The DisplayPort monitor should restore normally when keyboard or mouse input wakes a display that KDE has turned off.

Actual behavior

The monitor remains black/no-signal while the computer and Wayland session remain operational. DisplayPort connector/output state appears to become unusable until the VT/display link is recovered and the existing graphical session is explicitly reactivated.

I generated nvidia-bug-report.log.gz after reproducing and recovering from the problem, without rebooting, and have attached it.

kernel-live.log (27.1 KB)

nvidia-bug-report.log.gz (741.3 KB)

full-journal-after-failure.txt (578.9 KB)

user-live-snapshot-2026-09-24.txt (562.5 KB)

RTX 5080 + KDE Plasma Wayland: DisplayPort outputs fail to wake after monitor power-off / DPMS

I am seeing a DisplayPort wake failure on a CachyOS system with an NVIDIA GeForce RTX 5080, KDE Plasma/KWin Wayland, and multiple active monitors.

System

  • GPU: NVIDIA GeForce RTX 5080 (Blackwell)
  • Driver: 615.78.08 (nvidia-open-dkms, nvidia-utils)
  • Distribution: CachyOS Linux rolling
  • Kernel: 7.2.9-2-cachyos, PREEMPT_DYNAMIC
  • KDE/KWin: 6.7.5
  • Qt: 6.12.0
  • Session: KDE Plasma Wayland
  • Outputs involved: NVIDIA card1-DP-1, card1-DP-2, and card1-DP-3
  • One active display is a 3440x1440 OLED; additional monitors are also connected.

Problem

When KDE turns the displays off through its normal display power-management path, the system can fail to restore one or more DisplayPort outputs after the displays have been off for an extended period, including overnight.

The computer remains running and responsive, and the KDE/Wayland session remains active. The affected monitor/output remains black or has no signal. This is not ordinary system suspend or hibernate.

A visual fullscreen screensaver that keeps the display links active avoids the wake failure, which points toward the DisplayPort/DPMS wake path.

The behavior was originally observed on 615.71.09 and remains relevant on 615.78.08. The 615.78.08 release notes do not mention a fix for this DisplayPort/DPMS wake behavior.

Previous testing also showed that the failure was not dependent on LACT being active and could be reproduced with VRR disabled.

Expected behavior

All DisplayPort monitors should restore their signal and KDE should reapply the existing output configuration after the display power-off timeout expires and the user moves the mouse or presses a key.

Related report

This appears closely related to the following report involving an RTX 5090, CachyOS, KDE Wayland, and the 615 driver branch:

I have attached nvidia-bug-report-rtx5080-dp-wake-sanitized.log.gz and a short system summary. The NVIDIA report has been sanitized to remove private network addresses, MAC addresses, usernames/hostnames, email addresses, and credential-like data. Please let me know if additional DRM/KWin tracing or a specific test driver is needed.

rtx5080-kde-wayland-dp-wake-sanitized-package.zip (196.8 KB)

nvidia-bug-report-rtx5080-dp-wake-sanitized.log.gz (201.0 KB)