http://bugzilla.opensuse.org/show_bug.cgi?id=1116611 http://bugzilla.opensuse.org/show_bug.cgi?id=1116611#c2 --- Comment #2 from Stefan Dirsch <sndirsch@suse.com> --- Well. You're setting these kernel module options manually. radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 Which means that you're forcing the system to use amdgpu kernel module (experimental status on these GPUs) instead of radeon one (default). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1116611 http://bugzilla.opensuse.org/show_bug.cgi?id=1116611#c4 --- Comment #4 from Ülo Parri <yltsparri@gmail.com> --- Everything else seems to work with amdgpu kernel module. Only xf86-video-amdgpu has problems. Modesetting driver works with amdgpu kernel module. And also vulkan examples with radv and startplasmacompositor command. It is not high priority problem, but there is a bug in either xf86-video-amdgpu or xf86-video-ati driver. Problem may be using radeon and amdgpu simultaneously or using HAINAN GPU with xf86-video-amdgpu. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1116611 http://bugzilla.opensuse.org/show_bug.cgi?id=1116611#c6 Michal Srb <msrb@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msrb@suse.com --- Comment #6 from Michal Srb <msrb@suse.com> ---

From the log in comment 0:

(II) xfree86: Adding drm device (/dev/dri/card0) (II) xfree86: Adding drm device (/dev/dri/card1) (--) PCI:*(0@0:1:0) 1002:990b:103c:1983 rev 0, Mem @ 0xd0000000/268435456, 0xf0400000/262144, I/O @ 0x00005000/256, BIOS @ 0x????????/131072 (--) PCI: (1@0:0:0) 1002:6660:103c:1983 rev 0, Mem @ 0xe0000000/268435456, 0xf0300000/262144, I/O @ 0x00004000/256, BIOS @ 0x????????/131072 ... (II) Applying OutputClass "Radeon" to /dev/dri/card0 ... (II) Applying OutputClass "AMDgpu" to /dev/dri/card1 ... (II) RADEON(0): glamor X acceleration enabled on AMD ARUBA (DRM 2.50.0 / 4.19.1-1-default, LLVM 6.0.1) ... (II) RADEON(G0): glamor X acceleration enabled on AMD Radeon HD 8600M Series (HAINAN, DRM 3.27.0, 4.19.1-1-default, LLVM 6.0.1) This looks like you have two AMD GPUs in your machine. The initialization of the second fails as a GPU screen fails. Can you please clarify, do you have two GPUs and do you intend to use them both (e.g. for additional outputs or render offloading)? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1116611 http://bugzilla.opensuse.org/show_bug.cgi?id=1116611#c7 --- Comment #7 from Stefan Dirsch <sndirsch@suse.com> --- FWIW, Aruba (0x000b) is still Northern Islands from 2010. Only supported by radeon kernel module. Whereas Hainan (0x6660) is already Southern Islands from 2012. Experimental support in amdgpu driver, when setting the module options I mentioned above. So you're now mixing radeon and amdgpu driver here ... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1116611 http://bugzilla.opensuse.org/show_bug.cgi?id=1116611#c9 --- Comment #9 from Michal Srb <msrb@suse.com> --- In the Xorg.0.log in comment 0 the xf86-video-amdgpu is not even used. The Aruba GPU is primary, which causes the xf86-video-radeon driver to load for it. Once it is loaded, it seems to take over the second card as well instead of xf86-video-amdgpu. It tries to initialize the surface manager, which uses ioctl for the *radeon kernel* driver, but the device actually uses the *amdgpu kernel* driver, so it fails. Now strictly speaking it is a bug in X server's matching of user-side to kernel-side drivers. But you do have quite unusual configuration - two AMD GPUs, where both would normally use radeon, but you forced one of them to use amdgpu. I think your best bet is to fix/workaround it using some configuration. The point of my question was whether you actually intend to use *both* GPUs or just one of them. If for example you want to use just the Radeon HD 8600M, you could disable the Aruba one. You could: 1) Disable the APU in bios. (If that is possible. I don't know.) 2) Blacklist the radeon driver. 3) Configure X to use only the one card: Section "ServerFlags" Option "AutoAddGPU" "False" EndSection Section "Device" Identifier "Default Device" Driver "amdgpu" BusId "PCI:0:0:0" EndSection In case you really want to use both, then maybe some X configuration would be enough to match the cards to the proper drivers. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1116611 http://bugzilla.opensuse.org/show_bug.cgi?id=1116611#c12 --- Comment #12 from Ülo Parri <yltsparri@gmail.com> --- I did not get any hints here. I knew that using xf86-video-amdgpu does not work if SI GPU is using amdgpu module and radeon module is also loaded. It has not changed as far as i know. If modesetting Xorg drivers is used or amdgpu kernel module is not used, then X starts. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1116611 http://bugzilla.opensuse.org/show_bug.cgi?id=1116611#c14 --- Comment #14 from Ülo Parri <yltsparri@gmail.com> --- Both cards are usable with modesetting X driver. No need to disable anything. Maybe i could try X configuration to get xf86-video-amdgpu and xf86-video-ati to load correctly. Correct solution would be to fix choosing xf86-video-amdgpu and xf86-video-ati X drivers, but i have a solution that works for me. It is not very common configuration and this problem is not a high priority for me. -- You are receiving this mail because: You are on the CC list for the bug.