RTX 5070 + Samsung G95NC: DP 2.1 wake and initialization take 27–30 seconds on driver 610.43.03

Graphics / Linux Linux
, , , ,
1

System

  • GPU: NVIDIA GeForce RTX 5070, GB205

  • NVIDIA driver: 610.43.03

  • Driver package: NVIDIA open kernel modules

  • Distribution: Arch Linux

  • Kernel: 7.1.4-arch1-1

  • Desktop: KDE Plasma on Wayland

  • Monitor: Samsung Odyssey Neo G9 57-inch G95NC

  • Connection: DisplayPort 2.1

  • Operating mode: 7680×2160 at 240 Hz

Problem

When the Samsung G95NC enters DPMS sleep, waking it over DisplayPort 2.1 usually takes approximately 30 seconds.

The kscreen-doctor --dpms on command returns immediately, but the physical display remains black and the DRM connector remains disabled/off for about 30 seconds. The connector then becomes enabled, followed by a disconnect/reconnect sequence.

The problem is not specific to KDE or Wayland. Similar behavior occurs before Plasma starts, in SDDM, and under X11.

It can also cause the login manager to display a blank or incomplete screen, and occasionally login becomes unusable or hangs.

Important kernel-log evidence

The attached NVIDIA bug report contains this initialization sequence:

[    5.396773] [nvidia-drm] Loading driver
[   32.396546] [nvidia-drm] Failed to get dynamic displays during device registration.
[   32.453086] Initialized nvidia-drm

The delay between loading nvidia-drm and the failure message is almost exactly 27 seconds. This closely matches the approximately 30-second delay observed during DPMS wake.

The driver reports:

[nvidia-drm] Failed to get dynamic displays during device registration.
Dynamic displays may be probed in non-deterministic order.

No NVIDIA Xid errors, PCIe AER errors, GPU initialization failures, or compositor crashes were observed.

Reproduction steps

  1. Configure the Samsung G95NC monitor’s DisplayPort version as DP 2.1.

  2. Run the display at 7680×2160 and 240 Hz.

  3. Enter display sleep:

kscreen-doctor --dpms off

  1. Wait until the monitor is fully asleep.

  2. Wake the display:

kscreen-doctor --dpms on
  1. The command returns immediately, but the monitor remains black for approximately 30 seconds before displaying an image.

The issue reproduces reliably.

Comparison tests

  • DisplayPort 2.1: approximately 30-second wake delay.

  • DisplayPort 1.4 selected through the monitor OSD: wakes essentially immediately.

  • HDMI: wakes normally in approximately 3–5 seconds.

  • Reducing resolution or refresh rate while remaining in the monitor’s DP 2.1 mode does not eliminate the behavior.

  • The issue occurs during early display initialization as well as during a graphical desktop session.

  • PCIe ASPM is disabled and does not appear related.

Changing the monitor from DP 2.1 to DP 1.4 also changes its advertised EDID, but both EDIDs decode successfully without checksum or structural errors.

Windows comparison

This monitor previously exhibited effectively the same slow DP 2.1 wake behavior under Windows with an older NVIDIA driver.

Rolling Windows back to driver 581.80 resolved it at that time. Current Windows NVIDIA drivers no longer reproduce the problem.

This suggests Windows may already contain a monitor-specific or DP 2.1 link-training workaround that is not present in the current Linux driver.

Expected behavior

The monitor should wake within a few seconds, comparable to its behavior under DP 1.4, HDMI, and current Windows drivers.

Attachment

I have attached nvidia-bug-report-rtx5070-g95nc-dp21-wake.log.gz, generated immediately after reproducing the problem.

nvidia-bug-report-rtx5070-g95nc-dp21-wake.log.gz (487.5 KB)