From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98333] 4K @ 60Hz over HDMI 2.0 not working with AMDGPU-DAL
Date: Wed, 19 Oct 2016 21:04:24 +0000 [thread overview]
Message-ID: <bug-98333-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1664 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98333
Bug ID: 98333
Summary: 4K @ 60Hz over HDMI 2.0 not working with AMDGPU-DAL
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: dillondixon@gmail.com
So this is regarding AMDGPU DAL as it currently exists in
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-4.7, which from my
understanding contains the most up-to-date public-facing iteration of the DAL
patch.
So I have an HDMI 2.0 4K 60 Hz monitor (Vizio D40u-D1) as my main display
connected to an XFX RX 480. I'm using a kernel compiled from the branch listed
above.
Now the issue I'm having is that I'm stuck at 30 Hz. The RX 480 is capable of
driving this monitor at 60 Hz @ 4K, which works under Windows. Trying to switch
to 60 Hz either results in no signal, or just 30 Hz again.
I had the same issue in the past with the proprietary Linux Nvidia drivers on a
960 GTX I used to own, and after several months, the devs there were able to
figure out what the issue is, describe it in a forum post, and get a fix in.
See here:
https://devtalk.nvidia.com/default/topic/939971/linux/4k-60hz-works-in-windows-not-in-linux/
So what I'm hoping is that a similar fix would work in DAL.
I can provide logs on request (not sure to log right now).
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3161 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-10-19 21:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 21:04 bugzilla-daemon [this message]
2016-10-20 3:44 ` [Bug 98333] 4K @ 60Hz over HDMI 2.0 not working with AMDGPU-DAL bugzilla-daemon
2016-10-26 15:45 ` bugzilla-daemon
2016-11-03 2:54 ` bugzilla-daemon
2016-11-03 2:59 ` bugzilla-daemon
2016-11-03 4:46 ` bugzilla-daemon
2016-12-02 21:59 ` bugzilla-daemon
2016-12-02 22:02 ` bugzilla-daemon
2017-01-04 11:27 ` bugzilla-daemon
2017-01-04 11:30 ` bugzilla-daemon
2017-01-04 11:31 ` bugzilla-daemon
2017-01-04 11:32 ` bugzilla-daemon
2017-01-04 11:48 ` bugzilla-daemon
2017-01-04 11:49 ` bugzilla-daemon
2017-01-04 11:49 ` bugzilla-daemon
2017-01-05 1:34 ` bugzilla-daemon
2017-02-23 3:10 ` bugzilla-daemon
2017-02-23 3:11 ` bugzilla-daemon
2017-02-23 3:22 ` bugzilla-daemon
2019-11-19 8:11 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-98333-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).