Package Details: opencl-amd 1:6.1.0-2

Git Clone URL: https://aur.archlinux.org/opencl-amd.git (read-only, click to copy)
Package Base: opencl-amd
Description: ROCr OpenCL stack, supports Vega 10 and later products - Legacy OpenCL stack (Proprietary), supports legacy products older than Vega 10 - 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, hsakmt-roct, hsakmt-roct-dev, libdrm-amdgpu-amdgpu1, openmp-extras-runtime, rocdecode, rocdecode-dev, rocm-clang-ocl, 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, hsakmt-roct, hsakmt-roct-dev, libdrm-amdgpu-amdgpu1, opencl-driver, openmp-extras-runtime, rocdecode, rocdecode-dev, rocm-clang-ocl, 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: 131
Popularity: 1.01
First Submitted: 2016-12-01 03:45 (UTC)
Last Updated: 2024-04-19 20:50 (UTC)

Required by (114)

Sources (39)

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.

luciddream commented on 2021-12-26 15:14 (UTC) (edited on 2024-04-18 21:02 (UTC) by luciddream)

Current release is for ROCm 6.1.0 opencl-amd package includes only OpenCL / HIP runtime. You also need to use opencl-amd-dev package for ROCm LLVM compiler, OpenCL and HIP SDK. Please relog / reboot after installing so your PATH gets updated

There are now official packages available: rocm-opencl-sdk for OpenCL and rocm-hip-sdk for HIP - You might have better luck with these packages depending on your GPU.

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 77 Next › Last »

luciddream commented on 2023-02-17 16:09 (UTC)

@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.

keilmillerjr commented on 2023-02-16 13:18 (UTC)

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.

luciddream commented on 2023-02-16 10:04 (UTC) (edited on 2023-02-16 10:16 (UTC) by luciddream)

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)

RAMChYLD commented on 2023-02-16 08:26 (UTC)

@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.

apaz commented on 2023-02-16 07:55 (UTC) (edited on 2023-02-16 07:58 (UTC) by apaz)

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.

luciddream commented on 2023-02-13 20:46 (UTC) (edited on 2023-02-13 20:47 (UTC) by luciddream)

@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

RAMChYLD commented on 2023-02-13 20:19 (UTC)

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.

Astrobald commented on 2023-02-12 19:29 (UTC)

The "conflicts=" variable is duplicated in PKGBUILD

luciddream commented on 2023-02-12 18:07 (UTC)

@blueman I'm not sure, I've never used it, and I don't plan to use it at the moment. I will still keep updating opencl-amd for whomever needs to use it. But it's good to have more options.

@merlock yeah, as I commented on the sticky comment legacy support is broken for this release (as usual). Stick to 5.4.1 for now.