Bug 1956315 - 3840x2160@60hz unavailable in Wayland, works fine in XOrg
Summary: 3840x2160@60hz unavailable in Wayland, works fine in XOrg
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: wayland
Version: 34
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-03 13:15 UTC by Jeff Tickle
Modified: 2021-05-03 13:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Last Closed:
Type: ---

Attachments (Terms of Use)

Description Jeff Tickle 2021-05-03 13:15:01 UTC
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0
Build Identifier: 

The resolution 3840x2160 at 60hz is not available in Wayland.  I can only run at 30hz in that resolution, or 60hz in lower resolutions.  In XOrg, it is not automatically detected.  But, I can generate my own modeline and it works just fine.

I attempted this procedure, with my own mode line, which was not successful: https://blogs.nologin.es/rickyepoderi/index.php?/archives/149-Custom-mode-lines-in-Wayland.html

Other details, I am using NVIDIA non-Free drivers from package management.  Display is a Samsung Smart TV model number UN43NU7100, and I just updated its software to the latest T-KTM2LAKUC-1310.4.

I am happy to try any patches or configurations, or give you any requested information.

Reproducible: Always

Steps to Reproduce:
1. Install Fedora 34
2. Configure displays
3. Try to select 3840x2160 60hz.  Unavailable in the list.
Actual Results:  
Can only select 30hz in Wayland.  60hz works with some manual Modeline config in Xorg.

Expected Results:  
Present 60hz as available to select for a 4k refresh rate.  Perhaps an "advanced" mode in the display config would allow us to try to force modes that the application for whatever reason does not think are available.  I know how to do this in Xorg, but not in Wayland.

Note You need to log in before you can comment on or make changes to this bug.