dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204725] black screen
Date: Sun, 01 Sep 2019 07:17:03 +0000	[thread overview]
Message-ID: <bug-204725-2300-jqn7AIYWhJ@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 #28 from Dmitri Seletski (drjoms@gmail.com) ---
(In reply to Ant from comment #22)
> 2 things I notice are:
> 
> Xorg complains it can't find LLVM 9 or higher. I notice you said you have
> llvm trunk (10), could you try installing version 9 to see if that appeases
> it?
> 
> "radeonsi: Navi family support requires LLVM 9 or higher"
> 
> 
> Worryingly, I also notice some oddities about your card's information.
> 
> [    50.685] (--) AMDGPU(0): Chipset: "Unknown AMD Radeon GPU" (ChipID =
> 0x731f)
> 
> 
> You've not done any bios tweaking on the card have you? I wonder if the fix
> is to have your card's ID be accepted?
> 
> 
> What's the output of your
> /etc/X11/xorg.conf.d/20opengl.conf
> 
> file look like?
> 
> 
> For comparison, I have the sapphire pulse 5700 and my output looks like:
> 
> 0f:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
> [AMD/ATI] Navi 10 [1002:731f] (rev c4) (prog-if 00 [VGA controller])
>       Subsystem: Sapphire Technology Limited Navi 10 [1da2:e408]
>       Flags: bus master, fast devsel, latency 0, IRQ 90
>       Memory at e0000000 (64-bit, prefetchable) [size=256M]
>       Memory at f0000000 (64-bit, prefetchable) [size=2M]
>       I/O ports at f000 [size=256]
>       Memory at fcc00000 (32-bit, non-prefetchable) [size=512K]
>       Expansion ROM at 000c0000 [disabled] [size=128K]
>       Capabilities: <access denied>
>       Kernel driver in use: amdgpu
>       Kernel modules: amdgpu
> 
> 
> glxinfo | grep OpenGL
> OpenGL vendor string: X.Org
> OpenGL renderer string: AMD NAVI10 (DRM 3.33.0, 5.3.0-rc6-badidle+, LLVM
> 9.0.0)
> OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.3.0-devel
> (git-2023716 2019-08-31 eoan-oibaf-ppa)
> OpenGL core profile shading language version string: 4.50
> OpenGL core profile context flags: (none)
> OpenGL core profile profile mask: core profile
> OpenGL core profile extensions:
> OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.3.0-devel
> (git-2023716 2019-08-31 eoan-oibaf-ppa)
> OpenGL shading language version string: 4.50
> OpenGL context flags: (none)
> OpenGL profile mask: compatibility profile
> OpenGL extensions:
> OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.3.0-devel
> (git-2023716 2019-08-31 eoan-oibaf-ppa)
> OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
> OpenGL ES profile extensions:
> 
> 
> (My kernel's called 'badidle' cause there's a bug atm where the rx5700 is
> pulling ~30W at idle instead of 8W because the memory clocks are being maxed
> instead of changing dynamically because it is currently causing annoying
> flicker. The fix is probably upstream in agd5f's amd-staging branch, but I'm
> sticking to kernel.org)
> 
> 
> 
> I'm also beginning to consider the idea that you may have inadvertently set
> something in your .config that's interfering, so again for comparison and to
> save some grey hair, here is the relevent stuff from my .config apart from
> what you've seen so far.
> 
> 
> # CONFIG_DRM_RADEON is not set
> CONFIG_DRM_AMDGPU=m
> # CONFIG_DRM_AMDGPU_SI is not set
> # CONFIG_DRM_AMDGPU_CIK is not set
> CONFIG_DRM_AMDGPU_USERPTR=y
> 
> # Graphics support
> #
> # CONFIG_AGP is not set
> # CONFIG_VGA_ARB is not set
> # CONFIG_VGA_SWITCHEROO is not set
> CONFIG_DRM=y
> # CONFIG_DRM_DP_AUX_CHARDEV is not set
> # CONFIG_DRM_DEBUG_MM is not set
> # CONFIG_DRM_DEBUG_SELFTEST is not set
> CONFIG_DRM_KMS_HELPER=m
> # CONFIG_DRM_FBDEV_EMULATION is not set
> CONFIG_DRM_LOAD_EDID_FIRMWARE=y
> # CONFIG_DRM_DP_CEC is not set
> CONFIG_DRM_TTM=m
> CONFIG_DRM_SCHED=m
> 
> Critically, I have CONFIG_FB set to N (nothing for framebuffer devices and
> all adjacent options off so I don't put in any support for it.) I'm not sure
> why I stopped, but it works well without it and I assumed it was legacy
> stuff. As a last resort, you could try mimicing my file lol

0d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Device 731f (rev c1) (prog-if 00 [VGA controller])
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 0b36
        Flags: bus master, fast devsel, latency 0, IRQ 60
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at f0000000 (64-bit, prefetchable) [size=2M]
        I/O ports at f000 [size=256]
        Memory at fca00000 (32-bit, non-prefetchable) [size=512K]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [48] Vendor Specific Information: Len=08 <?>
        Capabilities: [50] Power Management version 3
        Capabilities: [64] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
        Capabilities: [150] Advanced Error Reporting
        Capabilities: [200] #15
        Capabilities: [240] Power Budgeting <?>
        Capabilities: [270] #19
        Capabilities: [2a0] Access Control Services
        Capabilities: [2b0] Address Translation Service (ATS)
        Capabilities: [2c0] Page Request Interface (PRI)
        Capabilities: [2d0] Process Address Space ID (PASID)
        Capabilities: [320] Latency Tolerance Reporting
        Capabilities: [400] #25
        Capabilities: [410] #26
        Capabilities: [440] #27
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu



look at my message at '2019-08-31 21:09:45 UTC'
for answer on whats in my config file

see Xorg output attached in next message.


'agd5f's amd-staging branch' - i will try to find it.
my next step is to compile LLVM 9(though message about version of LLVM seems
static, or so I suspect)


again, friendly remainder to everyone reading. Problems happens BEFORE xorg, it
happens at moment when amdgpu driver is loaded.

I have configured all entries to your config. all had to be disabled -
disabled. All not disabled is either mirror copy of yours or 'Y'.

-- 
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-09-01  7:17 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
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 [this message]
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-jqn7AIYWhJ@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).