OpenCL stopped functioning

@Tumblebatch For your sound issue, start a new thread for the likes of @deano_ferrari or @oldcpu can likely advise.

@Tumbleweed:zypper se --provides libOpenCL.so.1
Loading repository data...
Reading installed packages...

S  | Name             | Summary             | Type
---+------------------+---------------------+--------
i+ | libOpenCL1       | OpenCL ICD Bindings | package
   | libOpenCL1-32bit | OpenCL ICD Bindings | package
@Tumbleweed:zypper se --provides libOpenCL.so
Loading repository data...
Reading installed packages...

S  | Name             | Summary             | Type
---+------------------+---------------------+--------
i+ | libOpenCL1       | OpenCL ICD Bindings | package
   | libOpenCL1-32bit | OpenCL ICD Bindings | package
@Tumbleweed:zypper se --provides libigdrcl.so
Loading repository data...
Reading installed packages...

S  | Name         | Summary                                   | Type
---+--------------+-------------------------------------------+--------
i+ | intel-opencl | Intel Graphics Compute Runtime for OpenCL | package
@Tumbleweed:zypper se --provides /usr/share/OpenCL/vendors/intel.icd
Loading repository data...
Reading installed packages...

S  | Name         | Summary                                   | Type
---+--------------+-------------------------------------------+--------
i+ | intel-opencl | Intel Graphics Compute Runtime for OpenCL | package

Assuming the 32bit packages are not required, this looks alright, no?

Something odd just did occur though. Yesterday after installing the packages previously mentioned by @FreddyFH in this thread, the output from clinfo showed it had found 1 platform, but 0 devices.
I figured that was the result of installing mesa-libOpenCL which is meant for AMD/ATI, right?

Nevertheless the OpenCL Loader did register the platform while it completely misses anything relating to the Intel drivers/GPU.

About an hour ago something similar happened after I installed Mesa-libRusticlOpenCL. Thought I might as well give it a go as it’s sort of supported by darktable.
Sure enough running clinfo' showed 1 platform, but again 0 devices.

Two implementations for which I have no actual hardware are detected but the drivers/GPU it needs to detect get ignored.
Starting to look like the problem could be the Intel drivers or GPU, would’t you agree?

clinfo
Number of platforms                               1
  Platform Name                                   rusticl
  Platform Vendor                                 Mesa/X.org
  Platform Version                                OpenCL 3.0 
  Platform Profile                                FULL_PROFILE
  Platform Extensions                             cl_khr_byte_addressable_store cl_khr_create_command_queue cl_khr_expect_assume cl_khr_extended_versioning cl_khr_icd cl_khr_il_program cl_khr_spirv_no_integer_wrap_decoration cl_khr_suggested_local_work_size
  Platform Extensions with Version                cl_khr_byte_addressable_store                                    0x400000 (1.0.0)
                                                  cl_khr_create_command_queue                                      0x400000 (1.0.0)
                                                  cl_khr_expect_assume                                             0x400000 (1.0.0)
                                                  cl_khr_extended_versioning                                       0x400000 (1.0.0)
                                                  cl_khr_icd                                                       0x400000 (1.0.0)
                                                  cl_khr_il_program                                                0x400000 (1.0.0)
                                                  cl_khr_spirv_no_integer_wrap_decoration                          0x400000 (1.0.0)
                                                  cl_khr_suggested_local_work_size                                 0x400000 (1.0.0)
  Platform Numeric Version                        0xc00000 (3.0.0)
  Platform Extensions function suffix             MESA
  Platform Host timer resolution                  1ns

  Platform Name                                   rusticl
Number of devices                                 0

NULL platform behavior
  clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...)  rusticl
  clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...)   No devices found in platform [rusticl?]
  clCreateContext(NULL, ...) [default]            No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL)  No devices found in platform

ICD loader properties
  ICD loader Name                                 OpenCL ICD Loaderns
  ICD loader Vendor                               OCL Icd free softwarens
  ICD loader Version                              2.3.1ns
  ICD loader Profile                              OpenCL 3.0ns

Maybe later, thanks for the suggestion. :slightly_smiling_face:

I have the same issue with my Intel 620, I actually reported my issue here 1236716 – intel 620 gpu opencl support disabled
It is not an AMD (ATI) or Nvidia but if 620 loses hardware OpenCL support, I won’t be able to use digikam etc at all, I have hundreds of thousands of images to deal with here.

Right, so Intel dropped driver support for older CPUs (Gen8, Gen9 and Gen11).

Unfortunate but these things happen. Had the same problem with older ATI/AMD and Nvidia GPU’s that I tried to use for OpenCL.

It is indeed depreciation issue, but the situation isn’t that bad. They basically froze a specific tree, and it can be built as -legacy1 (or something similar) package. So, no new features, big fixes but security updates only. It is the same deal on Windows 11 side.
Trying to build it locally (that tree) isn’t a trivial job. It can’t find some installed tools etc.

@ilgazcl

I’ve decided to use this as an excuse to finally buy some new hardware as my system was getting a bit old and tired anyway.
Hope you can work out a way to get around this issue as well seeing as you have ‘slightly’ more images to deal with. It would take a good chunk of time with that iGPU and OpenCL support but it’d be an absolute nightmare without the latter…

Good luck!

1 Like

I disagree.

Clover doesn’t support Darktable because it lacks Image support.

For Rusticl you need to enable it:

https://en.opensuse.org/SDB:AMD_GPGPU#Enabling_Rusticl

Of course you’re free to disagree, but regarding the Intel drivers it seems clear that OpenCL is no longer supported in the latest version for 8th, 9th and 11th gen CPUs.

Yesterday I booted into (K)Ubuntu with slightly older Intel drivers on the same system and lo and behold, it still had OpenCL support.

As for AMD and RustiCL, I have absolutely no idea as I have no AMD hardware and wasn’t sure at all what I was doing anyway.

But, as of today this issue is no longer relevant for me. Just installed a new Intel ARC B580 in my current system. Wasn’t sure if it was going to work at all, but it does, and OpenCL support was back without me having to do anything at all.

And although it’s a bit offtopic - the difference this discrete GPU alone makes is worth the money. I’m still waiting for some other parts, but at first glance they may not even be needed to run darktable smoothly.
I hope this information may be of some use to others facing the same issue.

https://bugzilla.opensuse.org/show_bug.cgi?id=1236716#c10

Intel-opencl v. 21.36.20889 is available for Tumbleweed: https://download.opensuse.org/repositories/science:/GPU:/Intel-OpenCL/openSUSE_Tumbleweed/x86_64/

Installing:

zypper addrepo https://download.opensuse.org/repositories/science:GPU:Intel-OpenCL/openSUSE_Tumbleweed/science:GPU:Intel-OpenCL.repo
zypper refresh
zypper install intel-opencl

Leap 15.6 uses old intel-opencl package with 21.39.21127 version and it works with my Intel Gen 7 iGPU:

https://download.opensuse.org/distribution/leap/15.6/repo/oss/x86_64/intel-opencl-21.39.21127-150500.7.5.1.x86_64.rpm

There is work in progress ( intel-opencl-legacy1 ) which will simply enable the openCL for pre gen 8 Intels. I branched the original WIP to enable Tumbleweed&Leap binaries for testing. It is here: Show home:ilgazcl:branches:home:patrikjakobsson:branches:X11:XOrg / intel-opencl-legacy1 - openSUSE Build Service

Patrik Jacobsson enabled binaries so here is the original WIP for testing: Show home:patrikjakobsson:branches:X11:XOrg / intel-opencl-legacy1 - openSUSE Build Service

I have a similar problem. I’m not having it load in wayland.

After installing this package, I was able to switch to wayland with a long wait on a black screen and only after running plasmashell --replace &, but only 1 moniton out of two worked, frame rate dropped from 144 to 60, system was slow.