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: Tue, 27 Mar 2018 19:04:22 +0000	[thread overview]
Message-ID: <bug-104412-502-w6Yc4wP21e@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104412-502@http.bugs.freedesktop.org/>


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

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

--- Comment #14 from S.H. <anaxi@aikq.org> ---
(In reply to Alfe from comment #12)
> (In reply to S.H. from comment #6)
> > Hello,
> > Last night I was able to get my hands on a Gigabyte RX460 and did some
> > testing.
> > Booting and normal startup with the Gigabyte also only used 4k@30Hz but I
> > was able to reach 4k@60Hz by adding a modeline via xrandr.
> > With the Saphhire I am not able to get 4k@60Hz even with a custom modeline
> > set via xrandr.
> > Something seems broken here and I don't think both vendors messed up their
> > cards.
> 
> Hi!  Since I'm also trying around with this, it would be really helpful if
> you shared your modeline with which you were able to achieve 4k@60Hz ;-)
> 
> Cheers, Alfe

Hi,
I use these three lines to achieve 60Hz output:
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

Cheers,
Sven

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

[-- Attachment #1.2: Type: text/html, Size: 2085 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-03-27 19:04 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
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 [this message]
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-w6Yc4wP21e@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