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 105534] amdgpu cannot set 2560x1440@60 mode even though monitor,gpu and motherboard support it
Date: Fri, 16 Mar 2018 19:50:54 +0000	[thread overview]
Message-ID: <bug-105534-502-EUnguxfMPG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105534-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Christian König from comment #3)
> What you can use is either an active DP to dual DVI converter (probably
> rather expensive if such a thing even exists) or native DP/HDMI (if the
> monitor has connectors for that).

They are actually relatively common for just these sorts of scenarios.  Not
sure about cost however.

(In reply to philipmorant from comment #4)
> Thanks for replies. My monitor is DVI DL only.
> 
> My old Haswell i5 4670 with HD4600 graphics was also single link DVI only
> (https://communities.intel.com/thread/44135), and it worked at 60Hz. Could
> somebody please explain why haswell can do it but raven can't ?

I'm not sure how the intel hw is designed.  I can't comment on exactly what is
happening.  I suspect what is happening is that the intel driver is not
validating the link requirements and treating the DVI port like HDMI and
sending the high bandwidth mode over a single TMDS link.  The monitor just
happens to accept it.

> 
> Otherwise I find myself assuming that the hardware is capable of DL DVI,
> just that the manufacturers aren't validating for it, ergo fixable in
> software.

No.  DL DVI requires two digital transmitters, one for each TMDS link.  We only
wire a single transmitter to each physical connector.  For DL DVI, you need two
transmitters connected to the physical connector.

> 
> I understand if AMD object to coding for something that hasn't been
> validated (I'd do the same myself).  Would it be possible alternatively to
> provide hints in log output or code comments or on a wiki somewhere, such
> that people in my position can hack the source themselves ?

You could try hacking the driver to treat the monitor as HDMI even through it's
DL DVI.  Maybe your monitor will accept the timing over a single TMDS link.

> 
> Secondly, even accepting the single link limitation, shouldn't it be
> possible to run at 33 refresh rate ?  I tried at 30 and got nothing.
> 

It depends on the hardware and the panel in the monitor.  The monitor hardware
may not like 30 Hz refresh rates.  

> Thirdly, why does amdgpu refer to the connection as HDMI-A-3 ?  There's no
> HDMI in the setup at all.

The display connectors are read from a table in the bios and are determined by
the OEM that designs the board.  It our case the OEM seems to have set it up as
3 HDMI connectors and a DP connector.  What physical connectors are actually on
the board?

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

[-- Attachment #1.2: Type: text/html, Size: 3958 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-16 19:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16  0:00 [Bug 105534] amdgpu cannot set 2560x1440@60 mode even though monitor,gpu and motherboard support it bugzilla-daemon
2018-03-16  1:38 ` bugzilla-daemon
2018-03-16 10:38 ` bugzilla-daemon
2018-03-16 10:50 ` bugzilla-daemon
2018-03-16 13:49 ` bugzilla-daemon
2018-03-16 19:50 ` bugzilla-daemon [this message]
2018-03-16 20:08 ` bugzilla-daemon
2018-03-16 20:34 ` bugzilla-daemon
2018-03-19 14:09 ` bugzilla-daemon
2018-03-19 15:14 ` bugzilla-daemon
2018-03-19 15:15 ` bugzilla-daemon
2018-03-19 15:17 ` bugzilla-daemon
2018-03-19 15:26 ` bugzilla-daemon
2018-03-19 16:02 ` bugzilla-daemon
2018-03-19 16:07 ` 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-105534-502-EUnguxfMPG@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