Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: OpenCL shown as not available, but it is #398

Open
2 tasks done
barathrm opened this issue Jan 9, 2025 · 1 comment
Open
2 tasks done

Bug: OpenCL shown as not available, but it is #398

barathrm opened this issue Jan 9, 2025 · 1 comment

Comments

@barathrm
Copy link

barathrm commented Jan 9, 2025

Code of Conduct

  • I have read this document and I accept the conditions

Search previous report

  • I have searched my issue

Computer's operating system

Linux

What GPU do you have ?

I don't know

Ansel version

0.0.0+992.gd44e3803

Type of binary

Pre-built packages provided by the Ansel project (.AppImage, .EXE)

What happened?

I realize this may be low priority atm, but I thought it would be good to have an issue ticket for others who come searching.


I have an AMD graphics card with mesa's rusticl installed. clinfo outputs a lot of stuff, and darktable seems to work with it as expected.

Starting ansel like this

export RUSTICL_ENABLE=radeonsi
./Ansel-0.0.0+992.gd44e3803-x86_64.AppImage

OpenCL is not available under processing:

image

However, with Darktable I can first activate rusticl support and then after a restart OpenCL becomes available:

image

Possibly relevant section from -d all:

[opencl_init] opencl library 'libOpenCL.so.1' found on your system and loaded
[opencl_init] could not get platforms: Unknown OpenCL error

Does your problem occur with OpenCL enabled ?

No

Does your problem occur with OpenCL disabled ?

No

Previous Ansel version that use to work

No response

Output of ansel -d all

debug.log

Backtrace

No response

@aurelienpierre
Copy link
Collaborator

That Unknown OpenCL error is not going to be very helpful, and if Darktable has it under the "experimental" flag, it's probably through some workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants