dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104412] RX 460 HDMI 4k 60fps not working, DisplayPort is.
Date: Fri, 19 Jan 2018 16:06:00 +0000	[thread overview]
Message-ID: <bug-104412-502-QntznydPCG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104412-502@http.bugs.freedesktop.org/>


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

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

--- Comment #10 from S.H. <anaxi@aikq.org> ---
(In reply to Peter Weber from comment #8)
> Hello!
> 
> I'm using a LG 27UD88-W, which featurese 1 x DP, 1 x USB-C (DP) and 2 x
> HDMI. In my desktop is a Radeon RX 560 which offers DP "1.4" and HDMI "2.0b"
> and I also use a ThinkPad X220 which offers DP "1.1".
> 
> USB-C -> No hardware available
> DP    -> Reserved for ThinkPad, so I can use 3480x2180@30 Hz (probably even
> 44 Hz [1])
> HDMI  -> RX 560
> 
> The DP of the RX 560 works fine at 3480x2180@60Hz, but via HDMI it fails
> with Fedora 27 and kernel "3.14". Only 1920x1***@30Hz is possible any higher
> resolution results in visual garbage on the screen or "NO SIGNAL". Finally I
> remembered, that kernel 3.15 will over the new graphics stack "AMDGPU DC". I
> booted a live ISO with kernel 3.15 and passed the requried option
> "amdgpu.dc=1" and got 3480x2180@30Hz. GNOME also offers 60Hz as option, but
> that fails and cannot be used, screen goes blank, until GNOME reverts the
> settings. I'm afraid the previous people are right, HDMI2.0b and 4K@60Hz are
> broken.
> 
> 
> 
> 
> HINT: Don't used "DEEP COLOR" (LG OPTION for 8/10BIT COLOR?) with HDMI or
> everything is busted, but that is a minor issue, as for now.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> [1]
> https://medium.com/@ValdikSS/how-to-use-high-resolutions-with-older-hardware-
> 58577d91b1f8

You need at least Kernel-4.15 which is in rc-state at the moment. Afaik, Kernel
3.14 is way too old for amdgpu and amdgpu-dc.

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

[-- Attachment #1.2: Type: text/html, Size: 2859 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:[~2018-01-19 16:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 13:33 [Bug 104412] RX 460 HDMI 4k 60fps not working, DisplayPort is bugzilla-daemon
2017-12-29 13:33 ` bugzilla-daemon
2017-12-29 13:34 ` bugzilla-daemon
2017-12-29 15:47 ` bugzilla-daemon
2017-12-29 20:08 ` bugzilla-daemon
2017-12-29 20:15 ` bugzilla-daemon
2017-12-30 12:10 ` bugzilla-daemon
2017-12-30 12:40 ` bugzilla-daemon
2018-01-18 21:51 ` bugzilla-daemon
2018-01-18 21:56 ` bugzilla-daemon
2018-01-19 16:06 ` bugzilla-daemon [this message]
2018-01-20  1:41 ` bugzilla-daemon
2018-03-27  2:12 ` bugzilla-daemon
2018-03-27 18:48 ` bugzilla-daemon
2018-03-27 19:04 ` bugzilla-daemon
2018-04-05 17:40 ` bugzilla-daemon
2018-04-05 21:43 ` bugzilla-daemon
2018-04-15 13:57 ` bugzilla-daemon
2018-04-17 18:13 ` bugzilla-daemon
2018-04-25 15:32 ` 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-104412-502-QntznydPCG@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