search

flathub / org.darktable.Darktable

https://flathub.org/apps/details/org.darktable.Darktable
5 stars 14 forks source link

RustiCL not working #122

Closed Eckoa closed 6 months ago

Eckoa commented 6 months ago

Seeing as the current Flatpak Mesa looks to be built with RustiCL support https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/blob/master/elements/extensions/mesa/mesa.yml?ref_type=heads i figured i would give it a try.

Unfortunately there doesnt seem to be any way to get this flatpak to recognize it being there. Using RUSTICL_ENABLE=radeonsi or OCL_ICD_VENDORS environment variables does nothing to help the situation. In theory the inclusion of RustiCL should allow at least experimental OpenCL for AMD users.

Im not very familiar with how exactly flatpak runtimes all work but maybe the org.gnome.Sdk used here doesnt expose RustiCL? I would think the default mesa having it would be enough.

paperdigits commented 6 months ago

I believe you need the same mesa version installed on your system, I might be wrong tho.

On February 25, 2024 11:20:23 AM PST, Echoa @.***> wrote:

Seeing as the current Flatpak Mesa looks to be built with RustiCL support https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/blob/master/elements/extensions/mesa/mesa.yml?ref_type=heads i figured i would give it a try.

Unfortunately there doesnt seem to be any way to get this flatpak to recognize it being there. Using RUSTICL_ENABLE=radeonsi or OCL_ICD_VENDORS environment variables does nothing to help the situation. In theory the inclusion of RustiCL should allow at least experimental OpenCL for AMD users.

Im not very familiar with how exactly flatpak runtimes all work but maybe the org.gnome.Sdk used here doesnt expose RustiCL? I would think the default mesa having it would be enough.

-- Reply to this email directly or view it on GitHub: https://github.com/flathub/org.darktable.Darktable/issues/122 You are receiving this because you are subscribed to this thread.

Message ID: @.***>

Eckoa commented 6 months ago

I wouldnt think you would need both Mesa to match, afaik the flatpak mesa is completely separate from system mesa and shouldnt require either to match as flatpak provides everything itself in this case to the application.

I know Nvidia requires this but i believe thats due to the Nvidia kernel driver which mesa doesnt need a matching one to function properly as Mesa itself is userspace and doesnt provide the kernel driver.

paperdigits commented 6 months ago

What does darktable -d opencl say?

On February 25, 2024 11:31:08 AM PST, Echoa @.***> wrote:

I wouldnt think you would need both Mesa to match, afaik the flatpak mesa is completely separate from system mesa and shouldnt require either to match as flatpak provides everything itself in this case

-- Reply to this email directly or view it on GitHub: https://github.com/flathub/org.darktable.Darktable/issues/122#issuecomment-1963037744 You are receiving this because you commented.

Message ID: @.***>

Eckoa commented 6 months ago

After a little more testing Ive found that even though RustiCL is built in even org.freedesktop.Platform.ClInfo cant be made to see it, i dont think this is something that can be remedied here but might be something runtime related.

Eckoa commented 6 months ago

What does darktable -d opencl say?

flatpak run --env=RUSTICL_ENABLE=radeonsi org.darktable.Darktable -d opencl

reports 0 platforms detected when in "theory" it should see my rx6800 with opencl 3.0 through rusticl but i tried with flatpak clinfo and that doesnt work either so i think ill close this as i dont think anything can be done here

apologize for the unnecessary issue, i forgot that flatpak clinfo existed and i couldve done other testing before making this. Im going to dig a bit more then see about making an issue elsewhere.