Open okaestne opened 2 years ago
Just tested this on bullseye.
With video=HDMI-A-1:2560x1440@70D
in cmdline.txt I get an image and:
pi@pi4:~ $ kmsprint
Connector 0 (32) HDMI-A-1 (connected)
Encoder 0 (31) TMDS
Crtc 3 (96) 2560x1440@69.99 369.276 2560/200/280/480/- 1440/1/3/55/+ 70 (69.99) U
Plane 3 (86) fb-id: 339 (crtcs: 3) 0,0 2560x1440 -> 0,0 2560x1440 (XR24 AR24 AB24 XB24 RG16 BG16 AR15 XR15 RG24 BG24 YU16 YV16 YU12 YV12 NV12 NV21 NV16 NV61 P030 XR30 AR30 AB30 XB30 RGB8 BGR8 XR12 AR12 XB12 AB12 BX12 BA12 RX12 RA12)
FB 339 2560x1440 RG16
With video=HDMI-A-1:2560x1440@120D
in cmdline.txt I get an image it rejects the mode with:
vc4-drm gpu: [drm] User-defined mode not supported: "2560x1440": 120 661598 2560 2784 3064 3568 1440 1443 1448 1545 0x20 0x6
because the pixel clock (661MHz) is higher than we support (600MHz).
So it seems to be working as intended here. Are you seeing the same with a recent bullseye RPiOS image and kms?
It really has gotten better. I can now use 2560x1440@70Hz and even 120 Hz without issues! I used the exact timings listed in the EDID table I initially posted, which use the CVT 1.2 reduced blanking timings:
$ ./cvt12 2560 1440 120 -b
# 2560x1440 @ 120.000 Hz Reduced Blank (CVT) field rate 120.000 Hz; hsync: 183.000 kHz; pclk: 483.12 MHz
Modeline "2560x1440_120.00_rb2" 483.12 2560 2568 2600 2640 1440 1511 1519 1525 +hsync -vsync
This way the pixel clock stays far below HDMI 2.0's 600 MHz limit. But I had no luck getting the 144 Hz mode work, which my monitor SHOULD officially support via HDMI (got no other device to verify). It is just below 600 MHz:
$ ./cvt12 2560 1440 143.856 -b
# 2560x1440 @ 143.856 Hz Reduced Blank (CVT) field rate 143.856 Hz; hsync: 221.970 kHz; pclk: 586.00 MHz
Modeline "2560x1440_143.86_rb2" 586.00 2560 2568 2600 2640 1440 1529 1537 1543 +hsync -vsync
I do still get freezes though, when trying to use the 144 Hz mode that is listed in xrandr
without manual action. Here some info:
$ vcgencmd version
Jan 5 2023 10:46:54
Copyright (c) 2012 Broadcom
version 8ba17717fbcedd4c3b6d4bce7e50c7af4155cba9 (clean) (release) (start)
$ uname -a
Linux raspberrypi 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
So overall: good job! I can use 2560x1440@120Hz on my Pi4 :tada: I would still ask you leave this issue open as long as the kernel mod crashes, rather than kindly rejecting unsupported modes.
Thanks for your efforts!
Hi, I tried all day to get a higher refresh rate on my 1440p monitor running without success. When trying to switch to an higher rate (70/120/144 Hz), the screen goes black. 4k60 and 1080p120 do work on my TV (but not 1440p120). When choosing 70Hz, the screen seems gets a signal for a short time (<0.5 sec) before it looses it. I wasn't successful with custom xrandr modes either.
With the FKMS driver xrandr doesn't list the 144 Hz mode, but the 70 Hz mode. Here the same issue (no signal) occurs when choosing 70Hz.
The OS keeps running, but sometimes my whole desktop (Cinnamon, compiled from git) is frozen after restoring the old setting (2560x1440 @60Hz). Mouse cursor can still be moved though. In this case dmesg prints:
System Raspberry Pi 4 Model B Rev 1.4 4GB Raspberry Pi reference 2021-10-30 Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, c12b1df4ed6416fb0df33ba1731c5b13c1bdbdf8, stage4 Linux raspberrypi 5.10.63-v8+ #1459 SMP PREEMPT Wed Oct 6 16:42:49 BST 2021 aarch64 GNU/Linux
EDID of my monitor (binary): edid.zip EDID decoded: