OpenCL disabled on Intel GPUs with compute-runtime 26.35 (platform renamed)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
Research direction
Start in src/common/opencl.c around lines 1365-1369, where platform names are converted to keys and checked against the Intel alias list. Reproduce with darktable-cltest --configdir /tmp/dt-empty using the reported Intel compute-runtime, then add support for the integrated and discrete platform keys and verify that the Intel GPU is found and active.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this?
- I checked and did not find my issue in the already reported ones
Describe the bug
With intel-compute-runtime 26.35.39758.10, darktable no longer uses the Intel GPU. At startup it shows:
OpenCL initializing problem:
no OpenCL devices found
disabling OpenCL for now
darktable then sets opencl=FALSE, so later starts run without OpenCL and show no message.
Intel renamed the OpenCL platform in intel/compute-runtime@0522836c43fc4a556dfd011bc36aab3d5ba99a6b ("feature: distinguish discrete and integrated platforms by name"). The first release with this change is 26.35.39758.10. The platform is now called Intel(R) OpenCL Graphics (integrated) or Intel(R) OpenCL Graphics (discrete).
darktable turns the new name into the key clplatform_intelropenclgraphicsintegrated (or clplatform_intelropenclgraphicsdiscrete). This key is not in the Intel alias list, so darktable falls back to clplatform_other, which is false by default, and skips the platform:
Adding the two new keys to that list should fix it. I could only test an integrated GPU, but discrete Intel GPUs get the (discrete) name from the same change and should be affected as well.
Steps to reproduce
- Install intel-compute-runtime 26.35.39758.10 on a system with an Intel GPU
- Run
darktable-cltest --configdir /tmp/dt-empty - The Intel platform is reported as "NOT active" and no device is found
Expected behavior
darktable should find and use the Intel GPU for OpenCL, as with older drivers.
Logfile | Screenshot | Screencast
darktable-cltest 5.6.1 with an empty config dir:
[opencl_init] opencl library 'libOpenCL' found on your system and loaded, preference 'default path'
[opencl_init] found 1 platform
[check platform] platform 'Intel(R) OpenCL Graphics (integrated)' with key 'clplatform_intelropenclgraphicsintegrated' is NOT active
[opencl_init] found 0 device
[opencl_init] FINALLY: opencl PREFERENCE=YES is NOT AVAILABLE and NOT ENABLED
Commit
No response
Where did you obtain darktable from?
distro packaging
darktable version
5.6.1
What OS are you using?
Linux
What is the version of your OS?
Arch Linux (kernel 7.2.6)
Describe your system
Wayland, 32 GB RAM
Are you using OpenCL GPU in darktable?
Yes
If yes, what is the GPU card and driver?
Intel Iris Xe (Alder Lake-P GT2, integrated), intel-compute-runtime 26.35.39758.10, intel-graphics-compiler 2.41.5, ocl-icd 2.3.5
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
- Reproducible with another darktable version: yes, with self-compiled master (8e756aa23f)
- Still present with an empty config dir: yes
- Dominant language
- C
- Stars
- 13.3k
- Forks
- 1.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 182
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from darktable-org/darktable
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
darktable-org/darktable#22674 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
darktable-org/darktable#22658 ·
Maintainers usually reply within 1 day
-
bug: upstream
Difficulty 1/5 Under an hour Newbie friendliness 72/100
darktable-org/darktable#22521 · 1 comment ·
Maintainers usually reply within 1 day
-
_auto_set_exposure() is manual-mode logic kept out of automatic mode by a reset call, not a guardOpenpriority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
darktable-org/darktable#22184 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
darktable-org/darktable#22135 ·
Maintainers usually reply within 1 day
All issues in darktable-org/darktable
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
awslabs/aws-checksums#121 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug low priority rt_lib wasm
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day