Discussion:
[Bug 108981] Kernel 4.19 won't boot with amdgpu (black screen) for some video cards
b***@freedesktop.org
2018-12-10 13:43:15 UTC
Permalink
https://bugs.freedesktop.org/show_bug.cgi?id=108981

--- Comment #2 from MirceaKitsune <***@yahoo.com> ---
It seems further debugging might not be needed: As of kernel 4.19.7 the issue
appears to go away, I'm able to boot with amdgpu normally like before. The last
kernel I still saw the problem with is 4.19.5. Anyone know what could have
changed in between them, so perhaps we can keep a lookout for such an issue in
the future and prevent it?

Perhaps this might have been a package issue in openSUSE: Michel DÀnzer
suggested that as of 4.19, the kernel loads all firmware from
"path/firmware/amdgpu/" instead of falling back to "path/firmware/radeon/" when
something is missing. Did the Tumbleweed snapshot 20181208 make any updates in
this regard? In any case, I'll mark this as resolved and reopen in case the
issue ever returns.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freedesktop.org
2018-12-10 11:27:40 UTC
Permalink
https://bugs.freedesktop.org/show_bug.cgi?id=108981

Michel DÀnzer <***@daenzer.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
Assignee|xorg-driver-***@lists.x.org |dri-***@lists.freedesktop
| |.org
Component|Driver/AMDgpu |DRM/AMDgpu
Product|xorg |DRI
QA Contact|xorg-***@lists.x.org |

--- Comment #1 from Michel DÀnzer <***@daenzer.net> ---
Sounds like it's probably failing to load some microcode files. The amdgpu
driver in 4.19 started loading some of them from .../firmware/amdgpu/ instead
of .../firmware/radeon/. If you don't have the former files yet, you can create
symlinks for them pointing to the radeon directory for now.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freedesktop.org
2018-12-10 13:44:05 UTC
Permalink
https://bugs.freedesktop.org/show_bug.cgi?id=108981

MirceaKitsune <***@yahoo.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED

--- Comment #3 from MirceaKitsune <***@yahoo.com> ---
Seems to be resolved in openSUSE Tumbleweed snapshot 20181208.
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...