You are not logged in.
I have always used "opencl-amd" from the AUR to be able to use software like Blender and DaVinci Resolve. Lately I wanted to try ROCm and cleaned up the system from the old drivers and installed "rocm-hip-sdk" and "rocm-opencl-sdk" from the repository.
In the tests done in previous months (years) I always had problems, partly because my video card has no official support for ROCm. Instead, everything worked this time: clinfo and the various graphics programs worked fine, as did the benchmarks ("geekbench --compute opencl"). I even tried PyTorch (which I don't use and don't know about) because I knew its support with my board was problematic, but pytorch also worked fine.
This week, however, it no longer works! Trying to start programs that use OpenCL (Blender; DVR; clinfo; LibreOffice with OpenCL; etc.) these do not start, they hang and do not move forward. I have to terminate them or even do a kill. There are no error messages on the terminal and I can't find any in the journal either. Simply if something invokes OpenCL it stays on hold with no other signs.
I thought of a problem with ROCm and went back to "opencl-amd" from AUR, but the problem remains and OpenCL is no longer recognized.
I have looked for some solutions but no one has ever reported such a problem. From this I would say it's my video card only, but it's strange because for every other task it works regularly: "geekbench --compute vulkan", it works; "glmark2", it works; games, they works; etc...
I really don't know how to proceed to figure out the problem. Do you have any suggestions?
I put the links to the files: Xorg.0.log; pacman.log e journal.txt
https://pastebin.com/6x73HEZw
https://pastebin.com/0RQuxvE9
https://pastebin.com/ESy4UN54
Last edited by apaz (2023-03-24 13:18:29)
Offline
Output of a clinfo command? A likely guess, for one version blender hard installed the intel compute stack because it wasn't dynamically loadable, that should be fixed on the current versions, try uninstalling
[2023-03-11T09:18:09+0100] [ALPM] installed intel-oneapi-common (2023.0.0-3)
[2023-03-11T09:18:09+0100] [ALPM] installed intel-oneapi-compiler-dpcpp-cpp-runtime (2023.0.0-2)
[2023-03-11T09:18:09+0100] [ALPM] installed intel-oneapi-openmp (2023.0.0-1)
[2023-03-11T09:18:11+0100] [ALPM] installed intel-oneapi-compiler-shared-runtime
intel-oneapi-compiler-shared-opencl-cpu
Last edited by V1del (2023-03-24 09:32:58)
Offline
Thank you!!! By removing intel-oneapi (pacman -Rs intel-oneapi-compiler-shared-opencl-cpu), my AMD's OpenCL is back up and running.
Offline
It's kinda funny, because I tried to add similar packages to `opencl-amd` conflicts in the last version, and people started complaining, so I had to remove them again. You just can't please everyone
Offline
I can confirm that `sudo pacman -Rs intel-oneapi-compiler-shared-opencl-cpu` resolves the issue.
Last edited by melthsked (2023-04-26 20:05:59)
Offline