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: Tue, 07 Aug 2018 23:50:26 +0000 [thread overview]
Message-ID: <bug-200645-2300-XIDVvQlZSQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200645-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200645
Duncan (1i5t5.duncan@cox.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #277491|0 |1
is obsolete| |
--- Comment #6 from Duncan (1i5t5.duncan@cox.net) ---
Created attachment 277749
--> https://bugzilla.kernel.org/attachment.cgi?id=277749&action=edit
xrandr output (working at 60 Hz)
The previous xrandr working output was with a setting on the 4K TV hooked up to
HDMI-A-0 set wrong, so @3840x2160 it'd only give me 30 Hz (tho that shouldn't
have mattered for this bug, since the problem is with DVI-D-0, not HDMI-A-0).
This one has the TV set correctly so HDMI-A-0 will do 3840x2160 at full 60 Hz.
The bug's still there on rc8, with a revert of the commit to once again force
bpc <= 8 still fixing it (it's what I used to get this xrandr). So at this
point it seems release will still be bugged.
Comparing to the tested-fixed bug @ freedesktop that bisected to the same
commit, the problem there was with the HDMI forced to 30 Hz @3840x2160, while
here it's with no display on a 1920x1080 DVI-D, with the 3840x2160 HDMI-A
behaving normally -- early-boot displays on the DVI-D and the HDMI-A at the
usual low res, but the DVI-D goes blank as soon as it switches to DRM/hi-res,
while the HDMI-A behaves entirely normally. And once in X, xrandr says there's
no modes available for the (1920x1080-resolution) DVI-D, while again the
3840x2160 HDMI-A behaves entirely normally.
So perhaps a similar fix to the one on that bug (and now in tree) for HDMI, is
needed for DVI-D, tho it could be more than that as well, since (unlike the
freedesktop bug) the DVI-D is entirely blank and xrandr says it has no modes,
not even the low resolutions it was working with just fine in grub and early
boot.
--
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-07 23:50 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 [this message]
2018-08-11 8:58 ` bugzilla-daemon
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-XIDVvQlZSQ@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).