From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198745] Blank screen on RX 580 with AMDGPU Display Core enabled
Date: Tue, 31 Jul 2018 18:08:00 +0000 [thread overview]
Message-ID: <bug-198745-2300-3evZ6cTxk4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198745-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198745
Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nicholas.kazlauskas@amd.com
--- Comment #23 from Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) ---
(In reply to Claude Heiland-Allen from comment #22)
> I think I have this exact same issue with my RX 580. When amdgpu.dc=1 is
> initialized at boot, the console goes blank as it thinks all displays are
> disconnected. Xorg is not able to enable the display either. With
> amdgpu.dc=0 all is fine. Tried with various (mostly Debian) kernels from
> 4.16 through 4.18~rc4, all have the issue. I'm building a 4.18~rc7 from
> kernel.org now to rule out Debian patches being the issue and will be able
> to provide logs.
>
> Should I open a new issue as this one has been closed? Or can this one be
> reopened?
Feel free to create a new ticket and include your dmesg and Xorg logs.
--
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
prev parent reply other threads:[~2018-07-31 18:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 17:49 [Bug 198745] New: Blank screen on RX 580 with AMDGPU Display Core enabled bugzilla-daemon
2018-02-10 17:50 ` [Bug 198745] " bugzilla-daemon
2018-02-10 17:51 ` bugzilla-daemon
2018-02-10 20:07 ` bugzilla-daemon
2018-02-11 16:57 ` bugzilla-daemon
2018-02-11 18:29 ` bugzilla-daemon
2018-02-11 18:29 ` bugzilla-daemon
2018-02-12 15:47 ` bugzilla-daemon
2018-02-12 16:58 ` bugzilla-daemon
2018-02-12 16:59 ` bugzilla-daemon
2018-02-12 17:03 ` bugzilla-daemon
2018-02-23 13:02 ` bugzilla-daemon
2018-02-23 14:37 ` bugzilla-daemon
2018-02-24 1:23 ` bugzilla-daemon
2018-02-27 20:21 ` bugzilla-daemon
2018-02-28 9:15 ` bugzilla-daemon
2018-02-28 11:03 ` bugzilla-daemon
2018-02-28 15:26 ` bugzilla-daemon
2018-02-28 16:01 ` bugzilla-daemon
2018-02-28 16:17 ` bugzilla-daemon
2018-02-28 16:40 ` bugzilla-daemon
2018-02-28 16:47 ` bugzilla-daemon
2018-03-21 7:12 ` bugzilla-daemon
2018-07-31 18:04 ` bugzilla-daemon
2018-07-31 18:08 ` bugzilla-daemon [this message]
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-198745-2300-3evZ6cTxk4@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.