http://bugzilla.opensuse.org/show_bug.cgi?id=1188954 http://bugzilla.opensuse.org/show_bug.cgi?id=1188954#c8 --- Comment #8 from Felix Miata <mrmazda@earthlink.net> --- (In reply to Stefan Dirsch from comment #7)
Ok. If it fails only during initial X startup, this looks like a timing issue, i.e. kernel module is not being initialized in time before X gets started. Maybe amdgpu kernel module is missing from initrd, but radeon is (since it's the default driver), i.e. adding amdgpu to initrd may help (if it's really missing).
asa88:/boot # head -n2 /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20210730" asa88:/boot # lsinitrd initrd-5.13.4-1-default | grep AMD -rw-r--r-- 1 root root 7876 Aug 1 02:08 kernel/x86/microcode/AuthenticAMD.bin asa88:/boot # lsinitrd initrd-5.13.4-1-default | grep -i radeon asa88:/boot # lsinitrd initrd-5.13.4-1-default | grep -i amdgpu asa88:/boot # lsinitrd initrd-5.12.13-1-default | grep -i amdgpu asa88:/boot # lsinitrd initrd-5.11.16-1-default | grep -i amdgpu asa88:/boot # lsinitrd initrd-5.10.16-1-default | grep -i amdgpu asa88:/boot # lsinitrd initrd-5.9.14-1-default | grep -i amdgpu asa88:/boot # lsinitrd initrd-5.8.15-1-default | grep -i amdgpu asa88:/boot # lsinitrd initrd-5.7.11-1-default | grep -i amdgpu asa88:/boot # On Intel Haswell lsinitrd /boot/initrd | grep i915 returns null too.
I still don't understand why you want to use "amdgpu" drvier with your hardware though.
I started to when I learned it was possible. Until this, I had only seen one reason not to (unique set of connector names is a nuisance). I have to wonder how much testing following refactoring the radeon gets by developers, given how old the hardware is that isn't supported by the modesetting DIX. -- You are receiving this mail because: You are on the CC list for the bug.