Giving full path names might help.ĭarktable states that a context could not be created. Often the required libraries cannot be found by your system’s dynamic loader. See if you can find something fishy in there and try to fix it. There is a structure of files in /etc/OpenCL on your system that libOpenCL.so consults to find these libraries. For the real work further vendor-specific libraries need to be loaded. This happens because libOpenCL.so is only a wrapper library. NVIDIA drivers will often give error code -1001 in this case. In that case you might need to buy a new card if you really want OpenCL support.ĭarktable finds your libOpenCL.so but then tell you that it couldn’t get a platform.

Here are a few cases that have been observed in the past:ĭarktable states that no OpenCL aware graphics card is detected or that the available memory on your GPU is too low and the device is discarded. Check if there is a hint about where it failed. If initialization failed, look at the messages above for anything that reads like could not be detected or could not be created. that should tell you whether OpenCL support is available for you or not. First, if you find a line that starts with FINALLY. This will give additional debugging output about the initialization and use of OpenCL.

In this case, the best thing to do is start darktable from a console with darktable -d opencl. your graphics driver – loaded as a kernel module – does not match the version of your libOpenCL.so) OpenCL support will likely not be available. In addition all these have to fit in terms of maker, model and revision number. OpenCL depends on hardware requirements and on the presence of certain drivers and libraries. There can be various reasons why OpenCL might fail during the initialization phase. While this will slow down processing it should not affect the end result. On detecting an error, it will then reprocess everything on the CPU. Darktable will detect OpenCL run-time errors automatically.

Instal darktable 4.4.2