Bug 111412 - 4k 60hz unavailable RX 560 over HDMI
Summary: 4k 60hz unavailable RX 560 over HDMI
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-16 21:37 UTC by Alfie Day
Modified: 2019-08-16 22:03 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg log (34.42 KB, text/x-log)
2019-08-16 21:37 UTC, Alfie Day
no flags Details
lspci (6.23 KB, text/plain)
2019-08-16 22:03 UTC, Alfie Day
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alfie Day 2019-08-16 21:37:23 UTC
Created attachment 145078 [details]
xorg log

Hi,

My RX 560 won't do 4k 60hz over HDMI. I have tested the cable/display with a different PC (that has a 1080Ti) and it works fine, so I can confirm that both the cable and the TV are capable of displaying a 4k 60hz signal. I have also tested with a monitor that is capable of doing 4k 60hz over HDMI.

xrandr only shows 30hz as an option on both the TV and the monitor.
Comment 1 Alfie Day 2019-08-16 21:39:50 UTC
Someone on IRC said I should mention I was able to achieve 4k 60hz with a DisplayPort cable to the monitor (sadly this doesn't get me 4k 60hz on my TV, which only has HDMI)
Comment 2 Alfie Day 2019-08-16 21:58:44 UTC
trek00 from IRC found this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=104412#c14

which mentions running these commands, which seems to work and enable 4k60 over HDMI.

xrandr --newmode "mymode" 594  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync
xrandr --addmode HDMI-A-0 mymode
xrandr --output HDMI-A-0 --mode mymode
Comment 3 Alfie Day 2019-08-16 22:03:37 UTC
Created attachment 145079 [details]
lspci


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.