From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200695] Blank screen on RX 580 with amdgpu.dc=1 enabled (no displays detected)
Date: Tue, 16 Jun 2020 23:39:32 +0000 [thread overview]
Message-ID: <bug-200695-2300-hlnXkbEimI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200695-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200695
Lukas Fink (lukas.fink1@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lukas.fink1@gmail.com
--- Comment #43 from Lukas Fink (lukas.fink1@gmail.com) ---
(In reply to babgozd from comment #38)
> I am following this thread since it has created. My R9 380 with DVI-I output
> is connected to my VGA monitor with DVI-I male to VGA female adapter and I
> am getting black/blank screen while booting with amdgpu.dc=1 which is
> default since kernel 4.17. It is fine with amdgpu.dc=0. I can provide logs
> too if any kernel contributor wants to investigate the problem any further.
To me it seems, as if the DVI-I port is somehow misdetected/misconfigured as a
DVI-D port. With dc=0 I find the files "card1-DVI-I-1" and "card1-DVI-D-1" in
"/sys/class/drm/card1". With dc=1 there are "card1-DVI-D-1" and
"card1-DVI-D-2".
It appears to correctly negotiate resolution and refresh rate over DDC, but
because it only outputs the digital signal, a display connected over VGA
receives nothing and turns off.
--
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:[~2020-06-16 23:39 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 18:32 [Bug 200695] New: Blank screen on RX 580 with amdgpu.dc=1 enabled (no displays detected) bugzilla-daemon
2018-07-31 18:33 ` [Bug 200695] " bugzilla-daemon
2018-07-31 18:34 ` bugzilla-daemon
2018-07-31 18:37 ` bugzilla-daemon
2018-07-31 18:37 ` bugzilla-daemon
2018-07-31 18:38 ` bugzilla-daemon
2018-08-28 15:40 ` bugzilla-daemon
2018-08-28 15:42 ` bugzilla-daemon
2018-09-06 6:51 ` bugzilla-daemon
2018-09-10 13:45 ` bugzilla-daemon
2018-09-17 17:46 ` bugzilla-daemon
2018-09-17 18:09 ` bugzilla-daemon
2018-09-18 2:10 ` bugzilla-daemon
2018-09-18 13:43 ` bugzilla-daemon
2018-09-18 15:02 ` bugzilla-daemon
2018-10-01 17:30 ` bugzilla-daemon
2018-10-10 21:16 ` bugzilla-daemon
2018-10-22 18:52 ` bugzilla-daemon
2018-11-06 16:13 ` bugzilla-daemon
2018-11-13 19:54 ` bugzilla-daemon
2018-11-19 18:15 ` bugzilla-daemon
2018-12-04 23:12 ` bugzilla-daemon
2018-12-28 6:07 ` bugzilla-daemon
2019-01-12 11:18 ` bugzilla-daemon
2019-01-13 19:35 ` bugzilla-daemon
2019-02-25 17:51 ` bugzilla-daemon
2019-02-26 16:43 ` bugzilla-daemon
2019-02-27 12:42 ` bugzilla-daemon
2019-03-07 15:42 ` bugzilla-daemon
2019-03-07 16:26 ` bugzilla-daemon
2019-03-07 16:57 ` bugzilla-daemon
2019-04-02 16:38 ` bugzilla-daemon
2019-04-02 16:39 ` bugzilla-daemon
2019-09-20 11:22 ` bugzilla-daemon
2019-11-05 14:07 ` bugzilla-daemon
2019-12-16 21:43 ` bugzilla-daemon
2019-12-16 23:52 ` bugzilla-daemon
2020-02-15 14:42 ` bugzilla-daemon
2020-02-16 13:47 ` bugzilla-daemon
2020-02-16 21:12 ` bugzilla-daemon
2020-05-08 10:55 ` bugzilla-daemon
2020-05-08 15:12 ` bugzilla-daemon
2020-05-08 18:20 ` bugzilla-daemon
2020-05-30 19:22 ` bugzilla-daemon
2020-06-16 23:39 ` bugzilla-daemon [this message]
2020-06-17 2:24 ` bugzilla-daemon
2020-06-17 3:11 ` bugzilla-daemon
2020-06-28 9:25 ` bugzilla-daemon
2020-06-28 9:26 ` bugzilla-daemon
2020-06-28 9:27 ` bugzilla-daemon
2021-04-06 7:51 ` 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-200695-2300-hlnXkbEimI@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.