You are not logged in.
Pages: 1
Hello,
I'm trying to turn on OpenCL - using this guide:
https://wiki.archlinux.org/title/GPGPU
so, I installed rocm-opencl-runtime (using open source AMD drivers with my RX590 graphic card). After installing this package, rebooting computer, I still get:
clinfo | grep -i "image support"
Image support Noand also Darktable is not turning on anymore - I cannot open the app. Could anyone help me with this?
Offline
To support cards older than Vega, you need to set the runtime variable ROC_ENABLE_PRE_VEGA=1
Your RX 590 is GCN 4 and predates Vega which is GCN 5 .
Please post the outputs of
$ ROC_ENABLE_PRE_VEGA=1 clinfo --list
$ ROC_ENABLE_PRE_VEGA=1 clinfo -| grep -i "image support"Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online
I thought that I've modern graphic card... time flies ![]()
$ ROC_ENABLE_PRE_VEGA=1 clinfo --list
Platform #0: rusticl
Platform #1: AMD Accelerated Parallel Processing
`-- Device #0: gfx803
Platform #2: Clover
`-- Device #0: AMD Radeon RX 590 Series (polaris10, LLVM 15.0.7, DRM 3.52, 6.3.1-arch1-1)
$ ROC_ENABLE_PRE_VEGA=1 clinfo -| grep -i "image support"
ignoring unknown command-line parameter -
Image support Yes
Image support NoOffline
rusticl & clover come with opencl-mesa .
Clover doesn't have image support and is unlikely to ever get it.
Rusticl does have image support , but needs mesa 23.1 (now in release candidate stage) or later to support amd cards .
For now I suggest you remove opencl-mesa and try running ROC_ENABLE_PRE_VEGA=1 darktable .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online
Thank you! It's running it for now. So after Mesa 23.1 I should do what? Remove rocm-opencl-runtime and install opencl-mesa?
Offline
You should test which works better for you, removal of rocm may not be necessary (it does make things simpler though).
DT appears to be able to select between multiple opencl devices, https://docs.darktable.org/usermanual/4 … cs/opencl/ .
RUSTICL support in mesa is disabled by default, so you'd need to enable it when starting darktable.
$ RUSTICL_ENABLE=radeonsi darktable -d opencladding -d opencl makes darktable show details about opencl devices it sees and whether it can use them.
There are more env vars that control rusticl behavior, see https://docs.mesa3d.org/envvars.html#ru … -variables .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online
Pages: 1