There is a bug staring with NVidia 520.x driver and not yet fixed in 525.x that breaks the OpenCL compiler. So, if you upgrade to this NVidia version you won’t be able to have OpenCL working in darktable. At the moment the issue is unknown…
Hm. I have 525.85.05 yet it appears to be working:
[colinadams@fedora ~]$ darktable -debug opencl
[dt_get_sysresource_level] switched to 2 as `large’
total mem: 32007MB
mipmap cache: 4000MB
available mem: 21880MB
singlebuff: 500MB
OpenCL tune mem: OFF
OpenCL pinned: OFF
[opencl_init] opencl related configuration options:
[opencl_init] opencl: ON
[opencl_init] opencl_scheduling_profile: ‘very fast GPU’
[opencl_init] opencl_library: ‘default path’
[opencl_init] opencl_device_priority: ‘/!0,///!0,*’
[opencl_init] opencl_mandatory_timeout: 400
[opencl_init] opencl library ‘libOpenCL.so.1’ found on your system and loaded
[opencl_init] found 1 platform
[opencl_init] found 1 device
[dt_opencl_device_init]
DEVICE: 0: ‘NVIDIA GeForce RTX 3050’
CANONICAL NAME: nvidiageforcertx3050
PLATFORM NAME & VENDOR: NVIDIA CUDA, NVIDIA Corporation
DRIVER VERSION: 525.85.05
DEVICE VERSION: OpenCL 3.0 CUDA, SM_20 SUPPORT
DEVICE_TYPE: GPU
GLOBAL MEM SIZE: 7971 MB
MAX MEM ALLOC: 1993 MB
MAX IMAGE SIZE: 32768 x 32768
MAX WORK GROUP SIZE: 1024
MAX WORK ITEM DIMENSIONS: 3
MAX WORK ITEM SIZES: [ 1024 1024 64 ]
ASYNC PIXELPIPE: NO
PINNED MEMORY TRANSFER: NO
MEMORY TUNING: NO
FORCED HEADROOM: 400
AVOID ATOMICS: NO
MICRO NAP: 250
ROUNDUP WIDTH: 16
ROUNDUP HEIGHT: 16
CHECK EVENT HANDLES: 128
PERFORMANCE: 4.213
TILING ADVANTAGE: 0.000
DEFAULT DEVICE: NO
KERNEL DIRECTORY: /usr/share/darktable/kernels
CL COMPILER OPTION: -cl-fast-relaxed-math
KERNEL LOADING TIME: 0.0525 sec
[opencl_init] OpenCL successfully initialized.
[opencl_init] here are the internal numbers and names of OpenCL devices available to darktable:
[opencl_init] 0 ‘NVIDIA GeForce RTX 3050’
[opencl_init] FINALLY: opencl is AVAILABLE on this system.
[opencl_init] initial status of opencl enabled flag is ON.
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 0 0 0 0 0
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 1 1 1 1 1
[opencl_synchronization_timeout] synchronization timeout set to 0
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 0 0 0 0 0
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 1 1 1 1 1
[opencl_synchronization_timeout] synchronization timeout set to 0
1.737845 [dt_opencl_check_tuning] use 6653MB (tunemem=OFF, pinning=OFF) on device `NVIDIA GeForce RTX 3050’ id=0
[opencl_summary_statistics] device ‘NVIDIA GeForce RTX 3050’ (0): 2271 out of 2271 events were successful and 0 events lost. max event=818
Note: while investigating Frequent crashes · Issue #13893 · darktable-org/darktable · GitHub, we have discovered that 525.85 caused some crashes with NVidia 1060 on Ubuntu 22.10 that cannot be reproduced with either 470 (on Ubuntu) or 525.89 (on Debian). This is distinct from the compiler issue: OpenCL is available, but sometimes causes crashes.