Yes, it’s the same on both editions.
This is assuming you have fpaste and libdisplay-info-tools installed.. if you don’t ..
sudo dnf install fpaste libdisplay-info-tools
Can you run:
find /sys/class/drm/card[0-9]/ -iname edid -exec di-edid-decode {} \; | tee -a /tmp/edidinfo.txt; cat /tmp/edidinfo.txt | fpaste
and give us the link to the URL.
Thanks
Here you go:
That looks like a bug …
EDIT: Apologies for the confusion, I misread this.
Cut/Paste from the pastebin:
Block 0, Base EDID:
EDID Structure Version & Revision: 1.3
Vendor & Product Identification:
Manufacturer: HEC
Model: 0
Serial Number: 2460 (0x0000099c)
Made in: 2021
Basic Display Parameters & Features:
Digital display
Maximum image size: 128 cm x 72 cm
Gamma: 2.20
RGB color display
First detailed timing is the preferred timing
Color Characteristics:
Red : 0.6347, 0.3271
Green: 0.3066, 0.6083
Blue : 0.1503, 0.0468
White: 0.3125, 0.3291
Established Timings I & II:
IBM : 720x400 70.081663 Hz 9:5 31.467 kHz 28.320000 MHz
DMT 0x04: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz
DMT 0x05: 640x480 72.808802 Hz 4:3 37.861 kHz 31.500000 MHz
DMT 0x06: 640x480 75.000000 Hz 4:3 37.500 kHz 31.500000 MHz
DMT 0x09: 800x600 60.316541 Hz 4:3 37.879 kHz 40.000000 MHz
DMT 0x0a: 800x600 72.187572 Hz 4:3 48.077 kHz 50.000000 MHz
DMT 0x0b: 800x600 75.000000 Hz 4:3 46.875 kHz 49.500000 MHz
DMT 0x10: 1024x768 60.003840 Hz 4:3 48.363 kHz 65.000000 MHz
DMT 0x11: 1024x768 70.069359 Hz 4:3 56.476 kHz 75.000000 MHz
DMT 0x12: 1024x768 75.028582 Hz 4:3 60.023 kHz 78.750000 MHz
DMT 0x24: 1280x1024 75.024675 Hz 5:4 79.976 kHz 135.000000 MHz
Standard Timings:
DMT 0x15: 1152x864 75.000000 Hz 4:3 67.500 kHz 108.000000 MHz
DMT 0x20: 1280x960 60.000000 Hz 4:3 60.000 kHz 108.000000 MHz
DMT 0x23: 1280x1024 60.019740 Hz 5:4 63.981 kHz 108.000000 MHz
DMT 0x1c: 1280x800 59.810326 Hz 16:10 49.702 kHz 83.500000 MHz
DMT 0x2f: 1440x900 59.887445 Hz 16:10 55.935 kHz 106.500000 MHz
DMT 0x3a: 1680x1050 59.954250 Hz 16:10 65.290 kHz 146.250000 MHz
DMT 0x52: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz
DMT 0x55: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz
Detailed Timing Descriptors:
DTD 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz (800 mm x 450 mm)
Hfront 176 Hsync 88 Hback 296 Hpol P
Vfront 8 Vsync 10 Vback 72 Vpol P
DTD 2: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz (800 mm x 450 mm)
Hfront 88 Hsync 44 Hback 148 Hpol P
Vfront 4 Vsync 5 Vback 36 Vpol P
Display Product Name: '6Series58'
Display Range Limits:
Monitor ranges (GTF): 23-76 Hz V, 15-81 kHz H, max dotclock 340 MHz
Extension blocks: 1
Checksum: 0x7c
----------------
Block 1, CTA-861 Extension Block:
Revision: 3
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
Native detailed modes: 1
Video Data Block:
VIC 95: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz
VIC 93: 3840x2160 24.000000 Hz 16:9 54.000 kHz 297.000000 MHz
VIC 100: 4096x2160 30.000000 Hz 256:135 67.500 kHz 297.000000 MHz
VIC 98: 4096x2160 24.000000 Hz 256:135 54.000 kHz 297.000000 MHz
VIC 16: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz
VIC 34: 1920x1080 30.000000 Hz 16:9 33.750 kHz 74.250000 MHz
VIC 32: 1920x1080 24.000000 Hz 16:9 27.000 kHz 74.250000 MHz
VIC 5: 1920x1080i 60.000000 Hz 16:9 33.750 kHz 74.250000 MHz
VIC 4: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz
VIC 62: 1280x720 30.000000 Hz 16:9 22.500 kHz 74.250000 MHz
VIC 60: 1280x720 24.000000 Hz 16:9 18.000 kHz 59.400000 MHz
VIC 2: 720x480 59.940060 Hz 4:3 31.469 kHz 27.000000 MHz
VIC 1: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz
VIC 6: 1440x480i 59.940060 Hz 4:3 15.734 kHz 27.000000 MHz
Audio Data Block:
Linear PCM:
Max channels: 2
Supported sample rates (kHz): 48 44.1 32
Supported sample sizes (bits): 24 20 16
AC-3:
Max channels: 6
Supported sample rates (kHz): 48 44.1 32
Maximum bit rate: 640 kb/s
Enhanced AC-3 (DD+):
Max channels: 8
Supported sample rates (kHz): 48 44.1 32
MAT (MLP):
Max channels: 8
Supported sample rates (kHz): 48
Supports only Dolby TrueHD
Video Capability Data Block:
YCbCr quantization: Selectable (via AVI YQ)
RGB quantization: Selectable (via AVI Q)
PT scan behavior: No Data
IT scan behavior: Supports both over- and underscan
CE scan behavior: Supports both over- and underscan
YCbCr 4:2:0 Video Data Block:
VIC 97: 3840x2160 60.000000 Hz 16:9 135.000 kHz 594.000000 MHz
VIC 102: 4096x2160 60.000000 Hz 256:135 135.000 kHz 594.000000 MHz
Detailed Timing Descriptors:
DTD 3: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz (800 mm x 450 mm)
Hfront 110 Hsync 40 Hback 220 Hpol P
Vfront 5 Vsync 5 Vback 20 Vpol P
DTD 4: 1360x768 60.015162 Hz 85:48 47.712 kHz 85.500000 MHz
Hfront 64 Hsync 112 Hback 256 Hpol N
Vfront 3 Vsync 6 Vback 18 Vpol N
Checksum: 0x34
----------------
EDID conformity: PASS
Block 0, Base EDID:
EDID Structure Version & Revision: 1.4
Vendor & Product Identification:
Manufacturer: AUO
Model: 17565
Made in: 2018
Basic Display Parameters & Features:
Digital display
Bits per primary color channel: 8
DisplayPort interface
Maximum image size: 38 cm x 22 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4
First detailed timing includes the native pixel format and preferred refresh rate
Color Characteristics:
Red : 0.6425, 0.3320
Green: 0.3066, 0.6259
Blue : 0.1562, 0.0517
White: 0.3134, 0.3291
Established Timings I & II: none
Standard Timings: none
Detailed Timing Descriptors:
DTD 1: 1920x1080 144.027931 Hz 16:9 175.138 kHz 368.140000 MHz (382 mm x 215 mm)
Hfront 48 Hsync 32 Hback 102 Hpol N
Vfront 10 Vsync 5 Vback 121 Vpol N
Alphanumeric Data String: 'AUO'
Alphanumeric Data String: 'B173HAN04.4 '
Checksum: 0x33
----------------
Hmm…
This is only with Wayland. I have no problems with other display managers. Only Wayland. I wonder if the bug is in Wayland itself.
Out of curiosity does: gnome-control-center --verbose display show anything interesting?
wayland is a protocol spec not an implementation as such.
The implementation is in the display managers, kde, gnome etc.
A screenshot of straight text… sigh.
Just paste the text Torry - we can’t search this, copy any of it, reply with specific parts of it to highlight it and so on. No-one else can find it via search either.
When this happens, usually it’s because either (1) the HDMI cable or (2) laptop HDMI port or (3) the monitor does not support HDMI 2.0.
old cables and inexpensive laptops/monitors will only give you 30 hz.
Are you sure you’re using the right cable and 60hz works with other distros?
I don’t think this is a bug. It’s advertising correctly that for full RGB8 or YCbCr 4:4:4 max supported resolution is 4k @30Hz
Looks like the HDMI interface is limited to HDMI1.4
etailed Timing Descriptors:
DTD 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz (800 mm x 450 mm)
Hfront 176 Hsync 88 Hback 296 Hpol P
Vfront 8 Vsync 10 Vback 72 Vpol P
60Hz is only supported with a reduced color space
YCbCr 4:2:0 Video Data Block:
VIC 97: 3840x2160 60.000000 Hz 16:9 135.000 kHz 594.000000 MHz
VIC 102: 4096x2160 60.000000 Hz 256:135 135.000 kHz 594.000000 MHz
Yes, when I choose 1900x1080, I’m it gives me the option of 60hz vs 3840x2160 with the highest refresh rate option of 30hz.
Good question. I didn’t even bother to check the HDMI cable version. I’ll check when I get back home from work and if it isn’t 2.0, then I’ll have to invest in an HDMI 2.0 cable. And perhaps it could be the flatscreen I have may not support I don’t know.
That flatscreen I bought is 3 years old and the laptop I have is 5 years old. It’s a gaming laptop lenovo legion 5.
60hz only works if I have either x11 as the protocol or xWayland or if I reduce the resolution to 1900x1080
This only applies to the Wayland protocol/display manager server. With x11, I can use 4k with 60hz and it works wonderfully and you can clearly tell the difference in resolution which is what I’ve said from the beginning that’s it’s the Wayland protocal/display manager server that is flawed.
No, Wayland is also a display manager server as well.
I can achieve 4k with 60hz with x11. So it’s nothing to do with HDMI, it’s the Wayland protocol/display manager server that’s the culprit.
I’ve decided to switch from Gnome to another display manager. Wayland still needs some work and time to mature. It may reduce screen tearing, be more secure, etc. but it still needs some attention to be more compatible with softwares that work well like they do with x11. Thanx all for the inputs.
1 Like
Wayland is not a desktop environment, it’s a display protocol.
Would suggest you a quick test: download Fedora 43 KDE iso (it’s on wayland too), and live boot it. see if it works?
That’s the one i’m using and tested it on several different laptops with HiDPI screens, never a problem with high resolutions.
I’ll give that a try. Yes, I know that Wayland isn’t a display manager. It’s a protocol but it’s also a display manager server like x11.
There is a reference implementation of the protocol, Weston, I think.
Other than that I don’t think you will find wayland as a server.