# Mode is rejected: PixelClock (533.2 MHz) too high for Display Device
**URL:** https://forums.developer.nvidia.com/t/mode-is-rejected-pixelclock-533-2-mhz-too-high-for-display-device/290357
**Category:** Linux
**Created:** [April 21, 2024, 11:32am UTC](https://forums.developer.nvidia.com/t/mode-is-rejected-pixelclock-533-2-mhz-too-high-for-display-device/290357 "2024-04-21T11:32:33Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@leszek3](https://forums.developer.nvidia.com/u/leszek3)
#### Post date: [April 21, 2024, 11:32am UTC](https://forums.developer.nvidia.com/t/mode-is-rejected-pixelclock-533-2-mhz-too-high-for-display-device/290357/1 "2024-04-21T11:32:33Z")
I’ve got a Lenovo D32u-40 monitor, which can do 3840x2160 (under Windows this works)
GPU: NVidia Quadro P400, OS: Debian testing.
Driver version: 550.76
Problem: the top resolution, the 3840x2160, is not detected - the driver uses 1920x1080 instead.
I have set “ModeDebug” to “true” in the nvidia driver settings, and rebooted the system. Now in xorg.log I can see the following:
```auto
[6.651] (WW) NVIDIA(GPU-0): Validating Mode "3840x2160_60":
[6.651] (WW) NVIDIA(GPU-0): Mode Source: EDID
[6.651] (WW) NVIDIA(GPU-0): 3840 x 2160 @ 60 Hz
[6.651] (WW) NVIDIA(GPU-0): Pixel Clock : 533.25 MHz
[6.651] (WW) NVIDIA(GPU-0): HRes, HSyncStart : 3840, 3888
[6.651] (WW) NVIDIA(GPU-0): HSyncEnd, HTotal : 3920, 4000
[6.651] (WW) NVIDIA(GPU-0): VRes, VSyncStart : 2160, 2163
[6.651] (WW) NVIDIA(GPU-0): VSyncEnd, VTotal : 2168, 2222
[6.651] (WW) NVIDIA(GPU-0): Sync Polarity : +H -V
[6.651] (WW) NVIDIA(GPU-0): Mode is rejected: PixelClock (533.2 MHz) too high for
[6.651] (WW) NVIDIA(GPU-0): Display Device (Max: 165.0 MHz).
[6.651] (WW) NVIDIA(GPU-0): GPU extended capability check failed.
[6.651] (WW) NVIDIA(GPU-0): Mode "3840x2160_60" is invalid.
```
If I add the following to the ‘Device’ section
```auto
Option "ModeValidation" "NoMaxPClkCheck"
```
then I get
```auto
[6.648] (**) NVIDIA(GPU-0): (DFP-3):
[6.648] (**) NVIDIA(GPU-0): NoMaxPClkCheck
[6.648] (WW) NVIDIA(GPU-0): Validating Mode "3840x2160_60":
[6.648] (WW) NVIDIA(GPU-0): Mode Source: EDID
[6.648] (WW) NVIDIA(GPU-0): 3840 x 2160 @ 60 Hz
[6.648] (WW) NVIDIA(GPU-0): Pixel Clock : 533.25 MHz
[6.648] (WW) NVIDIA(GPU-0): HRes, HSyncStart : 3840, 3888
[6.648] (WW) NVIDIA(GPU-0): HSyncEnd, HTotal : 3920, 4000
[6.648] (WW) NVIDIA(GPU-0): VRes, VSyncStart : 2160, 2163
[6.648] (WW) NVIDIA(GPU-0): VSyncEnd, VTotal : 2168, 2222
[6.648] (WW) NVIDIA(GPU-0): Sync Polarity : +H -V
[6.648] (WW) NVIDIA(GPU-0): ViewPort 3840x2160 exceeds hardware capabilities.
[6.648] (WW) NVIDIA(GPU-0): Mode is rejected: GPU extended capability check failed.
[6.648] (WW) NVIDIA(GPU-0): GPU extended capability check failed.
[6.648] (WW) NVIDIA(GPU-0): Mode "3840x2160_60" is invalid.
```
and again it doesn’t work. Then I tried adding the following
```auto
Option "ModeValidation" "NoMaxPClkCheck,NoExtendedGpuCapabilitiesCheck"
```
after which I get a black screen on bootup.
[nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/sGAvdVJJ5VmLT7V7m8wkTlW4X5i.gz) (549.4 KB)
---
### Author:  [@generix](https://forums.developer.nvidia.com/u/generix)
#### Post date: [April 21, 2024, 8:22pm UTC](https://forums.developer.nvidia.com/t/mode-is-rejected-pixelclock-533-2-mhz-too-high-for-display-device/290357/2 "2024-04-21T20:22:17Z")
The adapter you’re using is a passive adapter so you can’t achieve more than 4k@30Hz.
---
### Author:  [@leszek3](https://forums.developer.nvidia.com/u/leszek3)
#### Post date: [April 21, 2024, 9:22pm UTC](https://forums.developer.nvidia.com/t/mode-is-rejected-pixelclock-533-2-mhz-too-high-for-display-device/290357/3 "2024-04-21T21:22:30Z")
By ‘adapter’ you mean the GPU?
How can I then manually force the driver to do 4k@30Hz ?
Here’s what I tried:
```auto
> cvt 3840 2160 30
# 3840x2160 29.98 Hz (CVT) hsync: 65.96 kHz; pclk: 338.75 MHz
Modeline "3840x2160_30.00" 338.75 3840 4080 4488 5136 2160 2163 2168 2200 -hsync +vsync
> xrandr --newmode "3840x2160_30.00" 338.75 3840 4080 4488 5136 2160 2163 2168 2200 -hsync +vsync
> xrandr --addmode DP-3 3840x2160_30.00
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 39
Current serial number in output stream: 40
```
---
### Author:  [@generix](https://forums.developer.nvidia.com/u/generix)
#### Post date: [April 21, 2024, 10:29pm UTC](https://forums.developer.nvidia.com/t/mode-is-rejected-pixelclock-533-2-mhz-too-high-for-display-device/290357/4 "2024-04-21T22:29:29Z")
Adapter=DP2HDMI cable.
---
### Author:  [@leszek3](https://forums.developer.nvidia.com/u/leszek3)
#### Post date: [April 22, 2024, 8:08am UTC](https://forums.developer.nvidia.com/t/mode-is-rejected-pixelclock-533-2-mhz-too-high-for-display-device/290357/5 "2024-04-22T08:08:24Z")
Ok. So If I use a mDP2DP 1.2 ( the monitor has a DP input) cable instead, is 3840x2160@60Hz going to work?
And how do I come up with a working 3840x2160@30Hz modeline now? Under Windows, 3840x2160 works with the very same hardware.
---
### Author:  [@generix](https://forums.developer.nvidia.com/u/generix)
#### Post date: [April 22, 2024, 8:31am UTC](https://forums.developer.nvidia.com/t/mode-is-rejected-pixelclock-533-2-mhz-too-high-for-display-device/290357/6 "2024-04-22T08:31:57Z")
> [@leszek3](#):
>
> If I use a mDP2DP 1.2 ( the monitor has a DP input) cable instead, is 3840x2160@60Hz going to work?
Yes.
You’re currently using a passive DP2HDMI cable which is in general limited to HDMI 1.3 speeds (300/340MHz) so only supports 4k@30Hz. In your case, only HDMI 1.0 speeds (165MHz) are detected, only supporting FHD. I don’t know why it only detects low speeds, might be a bad cable, just barely working on Windows due to different connection threshholds in the Windows driver opposed to the Linux driver. Or there might be a driver bug limiting it. In any case, a real DisplayPort connection is preferable.
---
### Author:  [@leszek3](https://forums.developer.nvidia.com/u/leszek3)
#### Post date: [April 25, 2024, 2:30pm UTC](https://forums.developer.nvidia.com/t/mode-is-rejected-pixelclock-533-2-mhz-too-high-for-display-device/290357/7 "2024-04-25T14:30:30Z")
Indeed, thanks generix. The cable has just arrived and 3840x2160 started working automagically.
---
### Author:  [@system](https://forums.developer.nvidia.com/u/system)
#### Post date: [May 9, 2024, 2:30pm UTC](https://forums.developer.nvidia.com/t/mode-is-rejected-pixelclock-533-2-mhz-too-high-for-display-device/290357/8 "2024-05-09T14:30:38Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.