If I understand properly, that just implements the opencl part and therefore keeps the system interdependent from snapshot (Kernel/driver) updates.
The next days I might find some time to install Tumbleweed and Leap on an external drive to try it out on a “real” system. Still undecided whether I wanna “roll” or not
@asn Thanks for your comments. Before I asked this question here, I tried many days and installed all I can find (about opencl) on “https://software.opensuse.org/” (even I don’t waht it is…).
If I let you and @darix feel I run away, I apology.
Actually, I still keep openSUSE tumbleweed on my laptop not switch to Linuxmint and try to find how to use opencl (I really like this OS) and using darktable on another PC with Win10 temporarily.
If you and @darix have any new idea of fix opencl issue, pleae let me know.
Hi All~ good news!
After reinstall the driver, opencl-headers and libopencl1 it works!! Thanks you all.
But there are a very weird problem.
Opencl worked only if I run darktable-cltest first.
Once I reboot my system, it wouldn’t work untill I run “darktable-cltest” again. Any ideas?
Hi @asn
After I run "sudo darktable-cltest ".
I can just use “darktable-cltest”, then opencl works.
It looks like I need to run a “sudo darktable-cltest” first, anyway.
kelvin@localhost:~> darktable-cltest
0.020404 [opencl_init] opencl related configuration options:
0.020414 [opencl_init]
0.020416 [opencl_init] opencl: 1
0.020428 [opencl_init] opencl_scheduling_profile: ‘default’
0.020430 [opencl_init] opencl_library: ‘’
0.020432 [opencl_init] opencl_memory_requirement: 768
0.020433 [opencl_init] opencl_memory_headroom: 400
0.020436 [opencl_init] opencl_device_priority: ‘/!0,///!0,*’
0.020450 [opencl_init] opencl_mandatory_timeout: 200
0.020453 [opencl_init] opencl_size_roundup: 16
0.020454 [opencl_init] opencl_async_pixelpipe: 0
0.020456 [opencl_init] opencl_synch_cache: active module
0.020459 [opencl_init] opencl_number_event_handles: 25
0.020462 [opencl_init] opencl_micro_nap: 1000
0.020464 [opencl_init] opencl_use_pinned_memory: 0
0.020466 [opencl_init] opencl_use_cpu_devices: 0
0.020468 [opencl_init] opencl_avoid_atomics: 0
0.020470 [opencl_init]
0.020547 [opencl_init] could not find opencl runtime library ‘libOpenCL’
0.020612 [opencl_init] could not find opencl runtime library ‘libOpenCL.so’
0.020715 [opencl_init] found opencl runtime library ‘libOpenCL.so.1’
0.020747 [opencl_init] opencl library ‘libOpenCL.so.1’ found on your system and loaded
0.030686 [opencl_init] found 1 platform
0.030701 [opencl_init] found 1 device
0.030869 [opencl_init] device 0 Quadro K2100M' has sm_20 support. 0.030987 [opencl_init] device 0 Quadro K2100M’ supports image sizes of 16384 x 16384
0.030990 [opencl_init] device 0 `Quadro K2100M’ allows GPU memory allocations of up to 498MB
[opencl_init] device 0: Quadro K2100M
GLOBAL_MEM_SIZE: 1995MB
MAX_WORK_GROUP_SIZE: 1024
MAX_WORK_ITEM_DIMENSIONS: 3
MAX_WORK_ITEM_SIZES: [ 1024 1024 64 ]
DRIVER_VERSION: 440.44
DEVICE_VERSION: OpenCL 1.2 CUD
Okay, again the combination of tumbleweed, opencl and in my case AMD graphics card, which is older and belongs to the polaris line. That line has no longer been supported by rocm since rocm 4.5.
On supported OSs, which tumbleweed is not, the official AMD driver works unobtrusively.
I cannot get the official driver to work under tumbleweed. Because of the line of my graphics card, I should call up the installer with --opencl=legacy which enforces dkms to be installed by the setup script.
Does anyone of you use the same combination (tumbleweed, AMD and opencl) and can point me in the right direction?