From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102985] HDMI 2.0 4k EDIDs not available (Radeon RX Vega 56)
Date: Mon, 25 Sep 2017 21:16:33 +0000 [thread overview]
Message-ID: <bug-102985-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2587 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102985
Bug ID: 102985
Summary: HDMI 2.0 4k EDIDs not available (Radeon RX Vega 56)
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: bicom@invergo.net
Created attachment 134476
--> https://bugs.freedesktop.org/attachment.cgi?id=134476&action=edit
DRM/AMDGPU logs (journalctl)
I have a Radeon RX Vega 56 connected to a Sony 4K TV (kd-49x8305c) via a
"Premium" (certified) HDMI 2.0 cable. The TV's HDMI input is set to "Enhanced
Format". Thus, on the hardware side, everything's ready to go for 4k@60Hz. On
the software side, I'm running Arch Linux with mesa-git (rev. 066d1dc951),
llvm-svn (rev. 313470), and Linux branch amd-staging-drm-next (4.13 rev.
dcae401d1113). I'm running Gnome and I've tested both Wayland and Xorg.
While other functionality such as rendering and acceleration work with this
setup, I have been unable to access any 4k resolutions.
As you'll see in the attached logs, the maximum resolution detected from the
TV's EDID is 1920x1080. However, using the program edid-decode (output
attached), one can see that the EDID clearly advertises 4k modes, however,
they're in the Extension block at VIC indexes higher than 64.
Until recently, 64 was the highest supported by drivers/gpu/drm/drm_edid.c in
the kernel. However, that has been fixed:
https://github.com/torvalds/linux/commit/8ec6e0755565192b328059b64f982adabbecda78#diff-f1b0089a97dd0195eb24305ab63a79e3
That commit has been merged into the amd-staging-drm-next kernel (but not
amd-staging), and the revision that I have built and installed includes that
code. Nevertheless, I haven't had any luck in getting the computer to
recognize any of those extended modes.
I have tried adding the mode manually via xrandr, however when I try to switch
to that mode, I get the error "xrandr: Configure crtc 0 failed". Trying to set
it in a conf file in /etc/X11/xorg.conf.d also didn't work (I no longer have a
configuration file in there). I've also tried forcing it from the kernel
command line (video=3840x2160@60) to no avail. Still, all of those seem like
workarounds when I think the problem is pretty clearly that the VIC 65+ modes
are not detected.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4206 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:[~2017-09-25 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 21:16 bugzilla-daemon [this message]
2017-09-25 21:17 ` [Bug 102985] HDMI 2.0 4k EDIDs not available (Radeon RX Vega 56) bugzilla-daemon
2017-09-25 21:17 ` bugzilla-daemon
2017-11-16 21:35 ` bugzilla-daemon
2017-11-16 21:40 ` bugzilla-daemon
2017-12-09 9:12 ` bugzilla-daemon
2017-12-11 11:52 ` 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-102985-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