From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter
Date: Thu, 22 Sep 2016 13:51:32 +0000 [thread overview]
Message-ID: <bug-172421-2300-oe4qPpKGxj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-172421-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=172421
--- Comment #12 from Elmar Stellnberger <estellnb@elstel.org> ---
Today I approached to try out the dual-link feature of the DVI-port. First I
had verified with AOC that my u2868pqu monitor in deed supports dual-link over
DVI. Then I connected the DVI output of my R5 230 (comment #6) with the
u2868pqu monitor over DVI. Trying to boot with a vanilla/hdmimhz=0 I just ended
up with a black screen. Finally I did succeed to get a picture by setting
hdmimhz=165. Firstly amazed I then noticed that hdmimhz does also disable the
duallink feature which was obviously the cause why it worked with hdmimhz. My
explanation for this is that the radeon driver detected both the display and
the card to support dual-link DVI. However the cable does not.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-22 13:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 18:15 [Bug 172421] New: radeon: allow to set the TMDS frequency by a special kernel parameter bugzilla-daemon
2016-09-21 18:16 ` [Bug 172421] " bugzilla-daemon
2016-09-21 18:17 ` bugzilla-daemon
2016-09-21 18:30 ` bugzilla-daemon
2016-09-21 18:37 ` bugzilla-daemon
2016-09-21 18:38 ` bugzilla-daemon
2016-09-21 18:49 ` bugzilla-daemon
2016-09-21 19:59 ` bugzilla-daemon
2016-09-21 20:16 ` bugzilla-daemon
2016-09-21 20:20 ` bugzilla-daemon
2016-09-22 7:07 ` bugzilla-daemon
2016-09-22 7:24 ` bugzilla-daemon
2016-09-22 13:51 ` bugzilla-daemon [this message]
2016-09-23 2:53 ` bugzilla-daemon
2016-09-23 7:36 ` bugzilla-daemon
2016-09-23 16:22 ` bugzilla-daemon
2016-09-23 17:27 ` bugzilla-daemon
2016-09-24 18:08 ` bugzilla-daemon
2017-12-16 18:52 ` bugzilla-daemon
2018-11-27 3:33 ` bugzilla-daemon
2018-11-27 12:28 ` bugzilla-daemon
2019-02-23 12:44 ` bugzilla-daemon
2022-06-19 15:33 ` bugzilla-daemon
2022-06-19 15:43 ` bugzilla-daemon
2023-01-03 12:16 ` bugzilla-daemon
2023-04-04 8:21 ` 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-172421-2300-oe4qPpKGxj@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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).