[Bug/DSC Limitation] NVIDIA driver cannot set 6016×3384 (6K) on Apple Pro Display XDR (RTX 3070 / Linux)

Can’t force the proprietary NVIDIA driver (tried 565.77 for both nvidia and nvidia-open) to drive Apple Pro Display XDR at its native 6016×3384 @ 60 Hz resolution. The monitor’s EDID does advertise 6K (via DisplayID), and 6K works correctly under Windows (tested myself) and on AMD GPUs in Linux (based on user reports). However on Linux+NVIDIA the driver only enumerates fallback modes (5120×2880, 3840×2160, etc.) and rejects all attempts to force 6016×3384 with -22 during atomic commits (Wayland). Maybe the driver is not enabling or is failing to negotiate Display Stream Compression (DSC) even though the driver is capable since 535.xx.

  • Display: Apple Pro Display XDR (native resolution 6016×3384 @ 60 Hz with 3008x3384 2x1 tiles) works at full 6K on Windows (same GPU + cable).
  • Cable: Belkin Charge and Sync Cable for Huawei VR Glass (CAZ001) (DisplayPort to USB-C supporting both DisplayPort Alternate Mode and USB 2.0 channel)
  • GPU: NVIDIA GeForce RTX 3070 (PCI ID 10de:2488)
  • Driver Version: 565.77
  • Kernel: 6.12.10-arch1-1 (Arch Linux)
  • Wayland Compositor
  • nvidia-drm.modeset=1 is enabled (kernel parameters + modprobe.d + mkinitcpio MODULES).
  • All other modes (e.g. 5120×2880@60) work without issue as they don’t need DSC.

EDID Parsing
Parsed via edid-decode:

  • DisplayID extension block includes:
    DTD:  6016x3384   59.999899 Hz  16:9    210.960 kHz   1286.010000 MHz (aspect 16:9, no 3D stereo, preferred)
  • Tiled display topology: 2 horizontal tiles at 3008×3384 each.
  • The CTA block does not show 6016×3384 as a preferred mode, but the DisplayID block does.
  • The driver reads the EDID but omits 6016×3384 from the probed modes list.

Forcing 6K
Attempting monitor=DP-2,modeline 1286.01 6016 6024 6056 6096 3384 3502 3510 3516 +hsync -vsync,0x0,1 or monitor=DP-2,6016x3384@60,0x0,1.0 or a Hyprland config line triggers an “[drm:drm_atomic_check_only] atomic driver check for 00000000cc4f4637 failed: -22”

No DSC Negotiation

  • drm_info / modetest do not show any DSC property or “Enabled DSC” indicator for DP-2.
  • Driver’s DSC handshake failure?

Relevant dmesg and DRM Logs
Below is an excerpt showing the driver enumerates 5120×2880, 3840×2160, etc. but not 6016×3384. When Hyprland tries an atomic commit with that mode, the driver returns -22:

[drm:update_display_info.part.0] [CONNECTOR:110:DP-2] DisplayID extension version 0x12, primary use 0x00
[drm:update_display_info.part.0] [CONNECTOR:110:DP-2] Assigning EDID-1.4 digital sink color depth as 12 bpc.
[drm:update_display_info.part.0] [CONNECTOR:110:DP-2] ELD monitor ProDisplayXDR
[drm:update_display_info.part.0] [CONNECTOR:110:DP-2] ELD size 36, SAD count 0
[drm:drm_edid_connector_update] [CONNECTOR:110:DP-2] tile cap 0x82, size 3008x3384, num tiles 2x1, location 0x0, vend APP
[drm:drm_helper_probe_single_connector_modes] [CONNECTOR:110:DP-2] probed modes:
[drm:drm_helper_probe_single_connector_modes] Probed mode: "5120x2880": 60 933810 5120 5128 5160 5200 2880 2979 2987 2993 0x20 0x9
...
[drm:drm_atomic_check_only] atomic driver check for 00000000cc4f4637 failed: -22

Attaching all relevant command outputs and logs. This display is my daily driver, so I can quickly test anything to debug this.

nvidia-bug-report.log.gz (309.8 KB)
drm_info.txt (119.5 KB)
hyprlandCrashReport10597.txt (8.0 KB)
edid-decode.txt (11.9 KB)

1 Like

bumping the above as i’m also daily driving a Pro Display XDR and can also help with more info if needed.

1 Like

No change on 570.86.16 driver version.