You are not logged in.
On a system with the latest kernel (5.12.1 as of writing this post) and an rx 480, booting into a graphical environment on Wayland or Xorg causes a system crash. Blacklisting the amdgpu kernel module fixes the issue (temporary fix for now).
N.B. while it was working on kernel 5.11.16.arch1-1, the gpu is not outputting video after the update to 5.12.1.
Addendum
GPU is working on kernel 5.12.5.
Last edited by keiichiiownsu12 (2021-05-23 03:20:29)
I, uh, nevermind
Offline
Please boot with systemd.unit=multi-user.target added as kernel parameter and amdgpu non-blacklisted.
If that works you'll get to a text console.
login as root and post dmesg plus journalclt -b .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Would like to apologize for the delayed response! Amdgpu is working on kernel 5.12.5.
Unfortunately I do not know how to access previous dmesg logs, but here is journalctl -b output from a boot when the kernel panic happened. (I assume `BUG: kernel NULL pointer dereference, address: 0000000000000028 refers` refers to a kernel panic...)
https://pastebin.com/YKwLnFsE
I, uh, nevermind
Offline