dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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, 04 Jan 2017 11:30:04 +0000	[thread overview]
Message-ID: <bug-98333-502-IGh2avP7Z7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98333-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1678 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=98333

--- Comment #9 from wiak@nwgat.net ---
Hey i got the exact same issue with a Samsung HU7505 4k60 television using
amdgpu on xubuntu 16.04.1/16.10, amdgpu-pro-16.50-362463 drivers work in 4k60
until the display is turned off and then it gives "mode not supported"


both the bios and the edid from the display while on crimson 16.12
https://f001.backblazeb2.com/file/nwgat-cdn/misc/xfx-rx460-Baffin-bios.rom
https://f001.backblazeb2.com/file/nwgat-cdn/misc/samsung_uhd_colour_YCbCr444-4k60_edid.bin

amd-staging-4.7 kernel, made no difference (git pull today)
ubuntu 4.10 from kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc2/

might also be related to black screen on 4k60 issue i have on windows 
https://www.reddit.com/r/Amd/comments/5fyy7c/december_tech_support_megathread/dbwa536/?context=3

System Configuration:
Motherboard: FM2A88X-ITX+ AMD A88X
CPU: AMD A10-7800
Memory: 16GB DDR3
GPU: XFX RX 460 2GB (RX-460P2SFG5)
GPU-Z Report: https://www.techpowerup.com/gpuz/details/4qq9n
VBIOS: 015.050.000.000.000000
Driver: amdgpu
OS: xubuntu 16.04.1 LTS AMD64 or 16.10 AMD64
Display: Samsung UE55HU7505 55" UltraHD (in UHD Colour Mode)
Display Cable: Startech Pro Series Metal High Speed HDMI Cable 2M (HDPSMM2M)

from samsung manual
http://downloadcenter.samsung.com/content/UM/201411/20141127124859330/[ENG]NUDVBEUH-1.111-1015.pdf

CEA-861
3840x2160 50Hz 112.500 50.000 594.000 +/+
3840x2160 60Hz 135.000 60.000 594.000 +/+
4096x2160 50Hz 112.500 50.000 594.000 +/+
4096x2160 60Hz 135.000 60.000 594.000 +/+

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2935 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

  parent reply	other threads:[~2017-01-04 11:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 21:04 [Bug 98333] 4K @ 60Hz over HDMI 2.0 not working with AMDGPU-DAL bugzilla-daemon
2016-10-20  3:44 ` 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 [this message]
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-IGh2avP7Z7@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).