From ArchWiki

Blender UI graphical corruption on AMDGPU driver

I found that compiling blender-git from the AUR completely removes this graphical corruption without needing to enable Triple Buffering, is this worthy of being noted in the wiki? Mycatfishsteve (talk) 21:58, 6 June 2017 (UTC)

I think this is valid info that should be noted if that is the case. Hopefully, this means that upstream has fixed the issue and that it will be eventually included in a later blender release.

Ase1590 (talk) 19:00, 7 June 2017 (UTC)

Experimental OpenCL support on AMDGPU

I will add an article either today or sometime during the week to describe how users with AMD GCN 2.0 cards can enable OpenCL support, since it isn't very well documented but is doable. Anyone with feedback to this addition can reply under me with the details. Thanks! Mycatfishsteve (talk) 08:38, 22 June 2018 (UTC)

How is the performance? When I used the open AMDGPU driver for OpenCL it performed much worse than the proprietary one for crypto usage about a year ago. That being said, I think it would be of interest to be added to the wiki how to do it anyway. That way those who want an open source stack can make use of it. I'm sure performance will only get better with time, if it hasn't already in the past year. So see if you can find out how to do it, then add it to the wiki. --Ase1590 (talk) 12:25, 31 August 2018 (UTC)
Have either of you got it working yet? I can't even figure out how to let Blender see my card as a compute device on open-source drivers. --Imyxh (talk) 01:37, 10 September 2018 (UTC)
I have an RadeonPro WX-5100 working with opencl-amd 18.30.641594-1 and libdrm 2.4.93-1. I'm going to investigate the Vulkan OpenCL implementation-- Mowley 25 Nov 2018
I have a Radeon RX 480, but it doesn't work with opencl-amd 18.30.641594-1 and libdrm 2.4.96-1, likely because I'm attempting to run it under GNOME Wayland. It emits the following error upon opening the System->General section of Preferences, then crashes:
amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-9)
Kode54 (talk) 01:42, 18 December 2018 (UTC)

Nope Kode54 you're getting that error because of an incompatible opencl-amd/libdrm driver, I reported this upstream to AMD and it was fixed in opencl-amd 18.50.708488-1 which works with libdrm 2.4.96-1 or later. If this doesn't fix your problem let me know.. Mowley