From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200645] 4.18-rc regression bisected to e03fd3f30: amdgpu polaris11/rx460 only activates on one output/monitor of two
Date: Sat, 11 Aug 2018 08:58:02 +0000 [thread overview]
Message-ID: <bug-200645-2300-k1KfTy60Zk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200645-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200645
--- Comment #7 from Duncan (1i5t5.duncan@cox.net) ---
So out of curiosity I found my old DVI-D/DisplayPort adapter and tried
switching outputs.
First thing I noticed is that the DVI/HDMI cable I'm using is only single-link
DVI, as is the DVI/DisplayPort adapter, so if I put the 4k monitor on it, it's
automatically limited to 1080p.
Which means that until I go buy a new cable, the only way I have to connect the
4k monitor and /get/ 4k is via the HDMI/HDMI cable and the card's HDMI
connector.
That leaves the DVI or DisplayPort card connector for the 1920x1080 TV. I can
connect it directly to the card DVI-D using the HDMI/DVI-D cable, as I had it
when I first filed this bug, or add the DVI-D/DisplayPort adaptor as well, and
connect it to the card's DisplayPort, as I have it now.
Either way, connecting the 1920x1080 via DVI-D or DisplayPort, the bug still
manifests -- without the cap to 8bpc, trying to boot 4.18-rc1+ blanks that
monitor as soon as the drmfb code takes over from the early-boot/VGA, while the
HDMI-connected 4k monitor continues to work normally (at 1080p until X starts
due to the video= kernel commandline option, at native 3840x2160 in X).
And the problem could also be partially due to the single-link cable I'm still
using for that monitor, enough for 8bpc 1920x1080, but perhaps not enough for
10bpc, even if both ends support it (I'm not actually sure whether the 1080p
limited TV does or 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:[~2018-08-11 8:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 6:00 [Bug 200645] New: 4.18-rc regression bisected to e03fd3f30: amdgpu polaris11/rx460 only activates on one output/monitor of two bugzilla-daemon
2018-07-25 6:06 ` [Bug 200645] " bugzilla-daemon
2018-07-25 6:10 ` bugzilla-daemon
2018-07-25 7:16 ` bugzilla-daemon
2018-07-25 14:02 ` bugzilla-daemon
2018-07-30 9:10 ` bugzilla-daemon
2018-08-07 23:50 ` bugzilla-daemon
2018-08-11 8:58 ` bugzilla-daemon [this message]
2018-09-01 5:21 ` bugzilla-daemon
2018-11-04 16:44 ` bugzilla-daemon
2018-11-05 12:18 ` bugzilla-daemon
2018-11-06 10:53 ` bugzilla-daemon
2018-11-06 11:09 ` bugzilla-daemon
2018-11-06 17:40 ` bugzilla-daemon
2018-11-25 6:29 ` 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-200645-2300-k1KfTy60Zk@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).