All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204725] black screen
Date: Sat, 31 Aug 2019 20:39:04 +0000	[thread overview]
Message-ID: <bug-204725-2300-TjhTE0hVWg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204725-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=204725

--- Comment #13 from Ant (untaintableangel@hotmail.co.uk) ---
I've got an RX5700 myself, so lets see if we can't get this sorted.

Can I just check something - the .config file you attached (comment 1)
for the kernel has 

# Display Engine Configuration
#
CONFIG_DRM_AMD_DC=y
CONFIG_DRM_AMD_DC_DCN1_0=y
CONFIG_DRM_AMD_DC_DCN1_01=y
# CONFIG_DEBUG_KERNEL_DC is not set
# end of Display Engine Configuration

whereas mine has 

# Display Engine Configuration
#
CONFIG_DRM_AMD_DC=y
CONFIG_DRM_AMD_DC_DCN1_0=y
CONFIG_DRM_AMD_DC_DCN2_0=y
CONFIG_DRM_AMD_DC_DSC_SUPPORT=y
# CONFIG_DEBUG_KERNEL_DC is not set
# end of Display Engine Configuration

I think CONFIG_DRM_AMD_DC_DCN1_01 was an option back in kernel 5.2 and the new
option comes in in 5.3(rc). Kernel 5.3 is a necessity for this reason. You've
got the latest mesa etc, can I just check you also have the latest mesa drm
code too? 

If there is insistence to use amdgpu as a module, let's try setting a config
file to force it to be used. How about you create this file with a text editor
(or otherwise like nano/vim etc):

/usr/local/share/X11/xorg.conf.d/10-amdgpu.conf

and fill it with this (tab an indentation for lines 2 - 4):

Section "OutputClass"
        Identifier "AMDgpu"
        MatchDriver "amdgpu"
        Driver "amdgpu"
EndSection

After restarting, it should find the card and force it to use the amdgpu
module?

-- 
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

  parent reply	other threads:[~2019-08-31 20:39 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 22:23 [Bug 204725] New: black screen bugzilla-daemon
2019-08-28 22:25 ` [Bug 204725] " bugzilla-daemon
2019-08-28 22:34 ` bugzilla-daemon
2019-08-28 22:35 ` bugzilla-daemon
2019-08-28 22:35 ` bugzilla-daemon
2019-08-29  2:36 ` bugzilla-daemon
2019-08-30 16:27 ` bugzilla-daemon
2019-08-31  4:31 ` bugzilla-daemon
2019-08-31  4:55 ` bugzilla-daemon
2019-08-31 17:58 ` bugzilla-daemon
2019-08-31 19:52 ` bugzilla-daemon
2019-08-31 19:56 ` bugzilla-daemon
2019-08-31 19:57 ` bugzilla-daemon
2019-08-31 20:39 ` bugzilla-daemon [this message]
2019-08-31 20:53 ` bugzilla-daemon
2019-08-31 20:55 ` bugzilla-daemon
2019-08-31 20:56 ` bugzilla-daemon
2019-08-31 20:56 ` bugzilla-daemon
2019-08-31 20:57 ` bugzilla-daemon
2019-08-31 21:09 ` bugzilla-daemon
2019-08-31 21:11 ` bugzilla-daemon
2019-08-31 21:13 ` bugzilla-daemon
2019-08-31 21:38 ` bugzilla-daemon
2019-08-31 22:03 ` bugzilla-daemon
2019-08-31 22:07 ` bugzilla-daemon
2019-08-31 22:08 ` bugzilla-daemon
2019-09-01  0:43 ` bugzilla-daemon
2019-09-01  0:48 ` bugzilla-daemon
2019-09-01  7:17 ` bugzilla-daemon
2019-09-01  7:20 ` bugzilla-daemon
2019-09-01  7:22 ` bugzilla-daemon
2019-09-01  7:25 ` bugzilla-daemon
2019-09-01  7:30 ` bugzilla-daemon
2019-09-01  7:35 ` bugzilla-daemon
2019-09-01  7:40 ` bugzilla-daemon
2019-09-01  8:53 ` bugzilla-daemon
2019-09-01  8:59 ` bugzilla-daemon
2019-09-01  9:04 ` bugzilla-daemon
2019-09-01  9:04 ` bugzilla-daemon
2019-09-01  9:20 ` bugzilla-daemon
2019-09-01  9:29 ` bugzilla-daemon
2019-09-01  9:29 ` bugzilla-daemon
2019-09-01 17:08 ` bugzilla-daemon
2019-09-01 18:28 ` bugzilla-daemon
2019-09-02 10:42 ` bugzilla-daemon
2019-09-02 17:26 ` bugzilla-daemon
2019-09-02 18:06 ` bugzilla-daemon
2019-09-02 20:37 ` bugzilla-daemon
2019-09-03 21:17 ` bugzilla-daemon
2019-09-03 21:23 ` bugzilla-daemon
2019-09-03 21:25 ` bugzilla-daemon
2019-09-03 21:28 ` bugzilla-daemon
2019-09-03 21:30 ` bugzilla-daemon
2019-09-04 16:20 ` bugzilla-daemon
2019-10-05 11:49 ` bugzilla-daemon
2019-10-07 14:24 ` bugzilla-daemon
2019-10-07 16:11 ` bugzilla-daemon
2019-10-14 20:57 ` bugzilla-daemon
2019-10-14 20:58 ` 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-204725-2300-TjhTE0hVWg@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.