Opencl support Darktable

Different distros have different policies on how many kernels they package. In Arch, there is the linux-lts package if you need to downgrade (which along nvidia-lts are the recommended way to handle the openCL problems until the fix in November).

3 Likes

In Arch Linux, openCL is again working for me with nvidia driver 455.38. Other people on reddit are saying it is not fixed for them, though. But if it works for me, I can’t understand why it wouldn’t work, generally.

I have updated my Manjaro Linux (Rolling Release, Long Term Support) today. The update includes the recent Nvidia driver for my hardware and the libraries related to openCL.
Below are the outputs of test commands (the last one does not seem to tell much about the nature of the problem, except for the “opencl_library” line):

[bulent@bulent-pc ~]$ darktable-cmstest
darktable-cmstest version 3.2.1
this executable was built with colord support enabled
darktable itself was built with colord support enabled

primary CRTC is at CRTC 0
CRTC for screen 0 CRTC 1 has no mode or no output, skipping
CRTC for screen 0 CRTC 2 has no mode or no output, skipping
CRTC for screen 0 CRTC 3 has no mode or no output, skipping

DVI-D-0 the X atom and colord returned the same profile
X atom: _ICC_PROFILE (1492 bytes)
description: DELL 2209WA
colord: “/var/lib/colord/icc/edid-4e5f32af7c2c9b0aea4e77b987788fbb.icc”
description: DELL 2209WA

Your system seems to be correctly configured

[bulent@bulent-pc ~]$ darktable-cmstest
darktable-cmstest version 3.2.1
this executable was built with colord support enabled
darktable itself was built with colord support enabled

primary CRTC is at CRTC 0
CRTC for screen 0 CRTC 1 has no mode or no output, skipping
CRTC for screen 0 CRTC 2 has no mode or no output, skipping
CRTC for screen 0 CRTC 3 has no mode or no output, skipping

DVI-D-0 the X atom and colord returned the same profile
X atom: _ICC_PROFILE (1492 bytes)
description: DELL 2209WA
colord: “/var/lib/colord/icc/edid-4e5f32af7c2c9b0aea4e77b987788fbb.icc”
description: DELL 2209WA

Your system seems to be correctly configured

[bulent@bulent-pc ~]$ darktable-cltest
0.023719 [opencl_init] opencl related configuration options:
0.023727 [opencl_init]
0.023729 [opencl_init] opencl: 1
0.023731 [opencl_init] opencl_scheduling_profile: ‘default’
0.023733 [opencl_init] opencl_library: ‘’
0.023735 [opencl_init] opencl_memory_requirement: 768
0.023737 [opencl_init] opencl_memory_headroom: 200
0.023739 [opencl_init] opencl_device_priority: ‘/!0,//’
0.023741 [opencl_init] opencl_mandatory_timeout: 200
0.023744 [opencl_init] opencl_size_roundup: 16
0.023746 [opencl_init] opencl_async_pixelpipe: 0
0.023747 [opencl_init] opencl_synch_cache: false
0.023749 [opencl_init] opencl_number_event_handles: 200
0.023751 [opencl_init] opencl_micro_nap: 500
0.023753 [opencl_init] opencl_use_pinned_memory: 0
0.023755 [opencl_init] opencl_use_cpu_devices: 0
0.023780 [opencl_init] opencl_avoid_atomics: 0
0.023781 [opencl_init]
0.023903 [opencl_init] found opencl runtime library ‘libOpenCL’
0.023915 [opencl_init] opencl library ‘libOpenCL’ found on your system and loaded
0.023922 [opencl_init] could not get platforms: -1001
0.023925 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
0.023926 [opencl_init] initial status of opencl enabled flag is OFF.


Strangely, I was able to use darktable “with” openCL support about a month or so ago.

Any ideas?

@bc_the-path
Step 1: Dump of your Manjaro settings/Hardware config/mhwd?

Oh, thanks Claes!
I have just finished updating my kernel version to 5.4 and Nvidia driver version to 455.38. Then, I re-installed opencl… (with the help of my son) The problem, whatever it was, is gone.
Now, everything is fine and darktable runs smoothly and saves an ordinary image file in no time!

Thanks very much for paying attention.

2 Likes

OK. that’s the LTS variety of the kernel.
Nvidia 455.38 is modern.

Be grateful to your son.
Good to have them in cases such as this.

1 Like