https://bugzilla.kernel.org/show_bug.cgi?id=205069
Bug ID: 205069 Summary: Black screen when starting graphical environment Product: Drivers Version: 2.5 Kernel Version: 5.3.1, 5.4.0-rc1, latest Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri@kernel-bugs.osdl.org Reporter: freddyreimer@comcast.net Regression: No
Created attachment 285285 --> https://bugzilla.kernel.org/attachment.cgi?id=285285&action=edit kernel .config 5.4.0-rc1
Hello there
On kernels 5.3.1 and 5.4.0-rc1, I get a black screen with a white underscore cursor in the upper left. The display gets stuck in this state, with no way to switch to a different TTY or leave this aside from hitting the reset button. I can secure-shell into the box and get a login at this time, but killing the process does not fix the display. Sway WM also does this, with it just getting stuck at the prompt entry.
I have an AMD RX 5700 graphics card, using the amdgpu driver. When I do some manual configuration by blacklisting amdgpu and writing a stanza in xorg conf for vesa, I am able to get X running using vesa.
uname -a output: Linux gentoo 5.4.0-rc1 #1 SMP Tue Oct 1 14:24:57 EDT 2019 x86_64 AMD Ryzen 5 3600 6-Core Processor AuthenticAMD GNU/Linux
https://bugzilla.kernel.org/show_bug.cgi?id=205069
--- Comment #1 from freddyreimer@comcast.net --- Created attachment 285287 --> https://bugzilla.kernel.org/attachment.cgi?id=285287&action=edit dmesg
https://bugzilla.kernel.org/show_bug.cgi?id=205069
--- Comment #2 from freddyreimer@comcast.net --- Created attachment 285289 --> https://bugzilla.kernel.org/attachment.cgi?id=285289&action=edit lsmod
https://bugzilla.kernel.org/show_bug.cgi?id=205069
--- Comment #3 from freddyreimer@comcast.net --- Created attachment 285291 --> https://bugzilla.kernel.org/attachment.cgi?id=285291&action=edit lspci -vv
https://bugzilla.kernel.org/show_bug.cgi?id=205069
--- Comment #4 from freddyreimer@comcast.net --- Created attachment 285293 --> https://bugzilla.kernel.org/attachment.cgi?id=285293&action=edit Xorg log from amdgpu freeze startx
https://bugzilla.kernel.org/show_bug.cgi?id=205069
--- Comment #5 from freddyreimer@comcast.net --- I've seen another report on a similar issue, where the suggestion (solution?) was to be using a newer mesa and llvm. I am on llvm 9 and mesa 19.2.0
* media-libs/mesa Latest version available: 19.2.0 Latest version installed: 19.2.0_rc4
* sys-devel/llvm Latest version available: 9.0.0 Latest version installed: 9.0.0
https://bugzilla.kernel.org/show_bug.cgi?id=205069
--- Comment #6 from Michel Dänzer (michel@daenzer.net) --- Was Mesa built against LLVM 9, not an older version?
It looks like the problem occurs when the Xorg driver tries loading glamor, so a Mesa/LLVM issue is most likely.
https://bugzilla.kernel.org/show_bug.cgi?id=205069
freddyreimer@comcast.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |PATCH_ALREADY_AVAILABLE
--- Comment #7 from freddyreimer@comcast.net --- Gotcha. I did not know until very recently that the graphics output for this kernel navi driver required a specific set of userland libraries to exist. I recompiled mesa and also got onto a new version of llvm-common for good measure.
This worked! Thank you for your help! I am able to launch Xorg on AMDGPU driver, without resorting to vesa, and can also run Sway wm. No display freezing or anything like that. I'll set this as resolved.
Reminder for future reference if someone comes across this with the same issue. You need at minimum LLVM 9 and Mesa 19.2.0. The LLVM has to be installed first.
Thank you again.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠bugzilla.kernel.org