@apaz commented. I also get that error in clinfo and darktable (starting from terminal)
dlerror: libamdocl-orca64.so: cannot open shared object file: No such file or directory arch
However, darktable works fine.
Git Clone URL: | https://aur.archlinux.org/opencl-amd.git (read-only, click to copy) |
---|---|
Package Base: | opencl-amd |
Description: | ROCm components repackaged from AMD's Ubuntu releases (ROCr runtime, ROCm runtime, HIP runtime) - This package is intended to work along with the free amdgpu stack. |
Upstream URL: | http://www.amd.com |
Keywords: | amd amdgpu computing gpgpu opencl radeon |
Licenses: | custom:AMD |
Conflicts: | amd-smi-lib, comgr, hip, hip-dev, hip-doc, hip-runtime-amd, hip-samples, hipcc, hsa-amd-aqlprofile, hsa-rocr, hsa-rocr-dev, libdrm-amdgpu-amdgpu1, openmp-extras-runtime, rocdecode, rocdecode-dev, rocjpeg, rocjpeg-dev, rocm-cmake, rocm-core, rocm-dbgapi, rocm-debug-agent, rocm-device-libs, rocm-gdb, rocm-hip-runtime, rocm-language-runtime, rocm-ocl-icd, rocm-opencl, rocm-opencl-dev, rocm-opencl-icd-loader, rocm-opencl-runtime, rocm-smi-lib, rocm-utils, rocminfo, rocprofiler, rocprofiler-dev, rocprofiler-plugins, rocprofiler-register, roctracer, roctracer-dev |
Provides: | amd-smi-lib, comgr, hip, hip-dev, hip-doc, hip-runtime-amd, hip-samples, hipcc, hsa-amd-aqlprofile, hsa-rocr, hsa-rocr-dev, libdrm-amdgpu-amdgpu1, opencl-driver, openmp-extras-runtime, rocdecode, rocdecode-dev, rocjpeg, rocjpeg-dev, rocm-cmake, rocm-core, rocm-dbgapi, rocm-debug-agent, rocm-device-libs, rocm-gdb, rocm-hip-runtime, rocm-language-runtime, rocm-ocl-icd, rocm-opencl, rocm-opencl-dev, rocm-opencl-icd-loader, rocm-opencl-runtime, rocm-smi-lib, rocm-utils, rocminfo, rocprofiler, rocprofiler-dev, rocprofiler-plugins, rocprofiler-register, roctracer, roctracer-dev |
Submitter: | grmat |
Maintainer: | sperg512 (luciddream) |
Last Packager: | luciddream |
Votes: | 134 |
Popularity: | 0.74 |
First Submitted: | 2016-12-01 03:45 (UTC) |
Last Updated: | 2025-05-22 15:22 (UTC) |
« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 82 Next › Last »
@apaz commented. I also get that error in clinfo and darktable (starting from terminal)
dlerror: libamdocl-orca64.so: cannot open shared object file: No such file or directory arch
However, darktable works fine.
@luciddream: Looking through Arch Linux's packages website, ffmpeg required a package called opencl-headers which I believe is associated with opencl-mesa. I believe I tried to remove that package as well because I thought it was associated with opencl-mesa (since opencl-amd is self-contained) and couldn't without also removing ffmpeg. That's when I concluded that ffmpeg is linked to opencl-mesa.
In any case, the latest update that solves the issue for @keilmillerjr has also solved my problem so I'm satisfied.
@keilmillerjr thanks, I don't know much about opencl-nvidia
, I will make a new release later tonight so it doesn't break for you.
Preparing...
Synchronizing package databases...
Refreshing AUR...
Cloning opencl-amd build files...
Generating opencl-amd information...
Checking opencl-amd dependencies...
Resolving dependencies...
Checking inter-conflicts...
Failed to prepare transaction:
could not satisfy dependencies:
- removing opencl-nvidia breaks dependency 'opencl-nvidia' required by cuda
Transaction cancelled.
Sorry but I'm not convinced. ffmpeg has no dependency on opencl-mesa
and it should be able to run with opencl-amd
instead.
Indeed, several documentation I come across online suggests that both can be installed side by side
In theory, maybe, but in practice, as you can see in the comments of opencl-amd
aur page, it doesn't. There are open bugs about it in multiple places (ocl-icd, rocm, freedesktop)
I'm leaning towards reverting the change anyway, not because it's better, but because most users so far with this problem have reached out here and we provided them with a solution (by asking them to uninstall opencl-mesa
)
@luciddream: I may be an edge case, but in my case I use opencl-mesa for ffmpeg's OCL filters (indeed, when I try to uninstall opencl-mesa, I get an explicit error saying that it's needed by ffmpeg and the uninstallation aborts). However it appears that Blender needs opencl-amd instead for hardware rendering instead because it explicitly uses HIP for shader compilation. Makes no sense to me to set up two different boot environment or even two different boxes for separate tasks.
Indeed, several documentation I come across online suggests that both can be installed side by side and there is an environment variable to dictate which icd to load per-program. For example, even in the archwiki itself, the command
OCL_ICD_VENDORS=/etc/OpenCL/vendors/rusticl.icd
is given to select ICD per-program.
I've also did a cross-check between the files installed by the opencl-amd package and the opencl-mesa package and found no overwriting files, suggesting that it should be safe to install both side by side. I've also been running both side-by-side for a while now and have not seen any ill effects.
Trying to do a "clinfo" I get an error message:
dlerror: libamdocl-orca64.so: cannot open shared object file: No such file or directory
However, everything seems to work fine. DaVinci Resolve also reports this error but then continues to work without problems. "geekbench --compute opencl" works without error.
@RAMChYLD some people (and rightfully so) complained that the conflict section was missing, so I added that. I know for a fact that opencl-mesa
is conflicting with opencl-amd
because many people have problems running software with both installed. So your use case looks interesting, do you mind elaborating more? I don't mind reverting it to the old behaviour if there is a need for it but I would like to to know what that need is.
@Astrobald, I was sure I forgot something, I guess that was it. I will take care of it on next release. thanks
Why is installing the latest version of this package causing a warning that it is now conflicting with opencl-mesa? This was never an issue before. Please fix.
Pinned Comments
nho1ix commented on 2023-12-29 08:43 (UTC) (edited on 2024-02-10 07:13 (UTC) by nho1ix)
Note for anyone who has a Polaris GPU (Radeon RX 5xx) debugging issues with this package; Packages that use OpenCL like clinfo or davinci-resolve-studio will need you to downgrade opencl-amd to 1:5.7.1-1 as well as amdgpu-pro-oglp to 23.10_1620044-1 to avoid coredumps & segfaults.
DVR would not open unless these 2 packages were downgraded (along with their dependencies). Had to figure it out the hard way after hours using valgrind and rebooting over and over. Hopefully someone else will not have to pull their hair out trying to resolve their issue.