615.71.09: DisplayPort output on RTX 5060 Laptop GPU (GB206M) produces no signal, 610.57.04 works

NVIDIA Open GPU Kernel Modules Version

615.71.09-1

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.

• I confirm that this does not happen with the proprietary driver package.

Operating System and Version

Arch Linux (rolling). Wayland (niri 26.04). Hybrid graphics: supergfxctl "Hybrid", gpu_mux_mode=1, dgpu_disable=0.

Kernel Release

7.2.4-arch1-2

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.

• I am running on a stable kernel release.

Hardware: GPU

GPU 0: NVIDIA GeForce RTX 5060 Laptop GPU

Describe the bug

After upgrading nvidia-open-dkms/nvidia-utils from 610.57.04-1 to 615.71.09-1 and rebooting, the external
display on the dGPU DisplayPort output gets no signal at all: the monitor never leaves standby and its OSD
reports no input.

The driver side looks healthy - nvidia-drm initializes normally, the connector still reports connected,
the EDID is parsed correctly (HKC X3, 2560x1440, DSC-capable 180 Hz mode advertised), and the compositor
sets 2560x1440@180 on DP-2 with no errors. No Xid or NVRM errors are logged. The panel just receives
nothing. Unplug/replug does not help.

Reverting to 610.57.04-1 on the same kernel, cable, monitor and configuration restores the display
immediately. Reproduced on 3 consecutive boots with 615.71.09. The output is also dead at 2560x1440@60
(no DSC / low-bandwidth mode), so this is not limited to the high-refresh DSC path.

nvidia-smi -q gives a hint at where it stops:

610.57.04: Display Attached : Yes   Display Active : Enabled    <- external monitor works
615.71.09: Display Attached : Yes   Display Active : Disabled   <- monitor stays dark

The display engine never becomes active on 615 even though the connector is connected, the EDID is
parsed and the compositor sets a mode. (Caveat: the 615 sample was taken right after boot, before the
compositor came up - but the monitor also stayed dark after login on every 615 boot.)

Possibly related to the 615.71.09 DSC/EDID parsing changes reported for HDMI in #1348 (patch in #1352).
Here the failing output is DisplayPort, so it may be the same family of changes affecting a different path.

Note: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-2 appears at boot on BOTH
610.57.04 and 615.71.09 and is pre-existing, not part of this regression.

To Reproduce

• ASUS TUF Gaming FX608JMR, Raptor Lake-H platform.
• dGPU: NVIDIA GeForce RTX 5060 Laptop GPU (GB206M, 10de:2d59) - the GPU that owns the external output.
• iGPU: Intel Raptor Lake-S UHD (8086:a78b, i915) - drives the internal panel only.
• Hybrid (MSHybrid) graphics active, i.e. the external output is wired to the dGPU:
  supergfxctl -g = Hybrid, gpu_mux_mode=1, dgpu_disable=0.
• External display connected to the dGPU DisplayPort connector DP-2:
  HKC X3 ("HKC OVERSEAS LIMITED X3"), 24", 2560x1440, DSC-capable, advertises 180 Hz (preferred 60 Hz).
  Monitor powered on, OSD input source set to DP.
• Working baseline installed: nvidia-open-dkms + nvidia-utils 610.57.04-1, with the external display
  confirmed working at 2560x1440@180 before the upgrade.
• Nothing else differs between the working and the broken boot: same kernel, same initramfs setup, same
  cable, monitor, port and compositor configuration.

2. Boot with 610.57.04-1 and log into the Wayland session. Confirm the external display works at 2560x1440@180: cat /sys/class/drm/card0-DP-2/status = connected, and nvidia-smi -q reports
   Display Attached: Yes / Display Active: Enabled.
3. Upgrade only the driver packages to 615.71.09-1, e.g. pacman -U nvidia-utils-615.71.09-1 nvidia-open-dkms-615.71.09-1 lib32-nvidia-utils-615.71.09-1 nvidia-settings-615.71.09-1.
4. Rebuild the initramfs: mkinitcpio -P.
5. Reboot and log into the same Wayland session, with the external monitor still connected and powered on.
6. Observe the external monitor: it never leaves standby and its OSD reports no input. Nothing is ever
   displayed, not even a text console during boot.
7. From the internal display, check the driver state:
   • cat /sys/class/drm/card0-DP-2/status -> connected
   • nvidia-smi -q | grep -E "Display Attached|Display Active" -> Yes / Disabled
   • the compositor believes the output is live: niri msg outputs shows DP-2 at 2560x1440 @ 179.998 Hz
   • dmesg | grep -i nvidia shows a clean load with no Xid / NVRM errors
8. Force a mode that does not need DSC - e.g. niri msg output DP-2 mode "2560x1440@60.000" - still no signal.
9. Unplug/replug the DisplayPort cable and power-cycle the monitor - still no signal.
10. Roll the same four packages back to 610.57.04-1, run mkinitcpio -P, reboot: the monitor comes up
    immediately and nvidia-smi -q reports Display Active: Enabled.

Bug Incidence

Once

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

615-live-evidence.txt

More Info

No response

Start with nvidia-drm initialization and the DP-2 display path, comparing 615.71.09 with 610.57.04; review the related DSC/EDID changes in #1348 and patch #1352. Reproduce on the listed RTX 5060 setup at 180 Hz and 60 Hz, then verify Display Active becomes Enabled and the monitor shows a signal without Xid/NVRM errors.