Thanks for your time Šarūnas and Germano.

This has got me worried because my workstation has the OpenCL from the AMDGPU-PRO version installed (but nothing else from it) and I'm using the open source amdgpu driver package. My reading of the bug analyses done by the devs (https://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime/issues/103), is that I shouldn't be seeing the problem as it only affects the open source OpenCL package running with the open source amdgpu driver. Have I got this right? 
Is it possible I'm somehow using the open source OpenCL instead of the PRO?  The output from darktable and inxi are below - do the experts know if this proves what I'm running?

darktable -d opencl:
[opencl_init] device 0: gfx1012
     GLOBAL_MEM_SIZE:          8176MB
     MAX_WORK_GROUP_SIZE:      256
     MAX_WORK_ITEM_DIMENSIONS: 3
     MAX_WORK_ITEM_SIZES:      [ 1024 1024 1024 ]
     DRIVER_VERSION:           3075.10 (PAL,LC)
     DEVICE_VERSION:           OpenCL 2.0 AMD-APP (3075.10)

inxi -Gxx:
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M]
           vendor: Micro-Star MSI driver: amdgpu v: kernel bus ID: 0b:00.0 chip ID: 1002:7340


Thanks

On 14/08/2020 21:47, Šarūnas wrote:
On 8/14/20 2:37 PM, Dusenberg wrote:
Thanks for the prompt reply Andreas. 
What a pain, I use local laplacian a lot. The github threads say the
AMDGPU-PRO drivers don't have this problem, so I'm wondering if I should
replace the open source amdgpu driver with the PRO version as a
workaround for the time being. Do you know if this is a realistic option
for a non-dev user?
If this is a problem with the open source ROCm OpenCL library, you can
run open source amdgpu (present in Linux kernel) with OpenCL from
AMDGPU-PRO.

Here is for Ubuntu, but might be adaptable to others:
https://math.dartmouth.edu/~sarunas/amdgpu.html




On 14/08/2020 19:46, Germano Massullo wrote:
Il 14/08/20 20:37, Dusenberg ha scritto:
Thanks for the prompt reply Andreas. 
What a pain, I use local laplacian a lot. The github threads say the AMDGPU-PRO drivers don't have this problem, so I'm wondering if I should
replace the open source amdgpu driver with the PRO version as a workaround for the time being. Do you know if this is a realistic option for a non-dev user?

I everyday use amdgpu drivers, but when I use darktable, I use the proprietary amdgpu-pro OpenCL drivers. Here is my procedure:


Just download the drivers for the distro that is more similar to yours (example, RPM or Deb packages).
The example will follow RPM architecture, but for Debs the procedure is almost the same.
Unpack the tar.xz file in a folder let's call it
/home/user/unpacked
After that, you will have folder
/home/user/unpacked/amdgpu-pro
that contains subfolders
amdgpu-pro-install  repodata  RPMS  SRPMS
go in RPMS and take all RPM files that are in subfolder
/home/user/unpacked/amdgpu-pro/x86_64
and put them together someelsewhere, for example
/home/user/amd_opencl
then unpack them all.
You will get
/home/user/amd_opencl/etc/
/home/user/amd_opencl/lib/
/home/user/amd_opencl/opt/
/home/user/amd_opencl/usr/

Then to run darktable
OPENCL_VENDOR_PATH=/home/user/amd_opencl/etc/OpenCL/vendors/ LD_LIBRARY_PATH=/home/user/amd_opencl/opt/amdgpu-pro/lib64/ darktable

___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org


___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Reply via email to