Package Details: opencl-amd 1:6.3.2-1

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: 132
Popularity: 0.21
First Submitted: 2016-12-01 03:45 (UTC)
Last Updated: 2025-01-29 20:12 (UTC)

Required by (128)

Sources (38)

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 2025-01-29 20:13 (UTC) by luciddream)

Current release is for ROCm 6.3.2 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 .. 44 45 46 47 48 49 50 51 52 53 54 .. 79 Next › Last »

Recompiler commented on 2020-12-10 16:22 (UTC) (edited on 2020-12-10 17:01 (UTC) by Recompiler)

Correct me if I'm wrong but I think I know why I had problems with this aur package. You're combining two different versions of opencl implementations, the proprietary amdgpupro stack and the newer open source rocm stack. I've recently been testing rocm with mesa on Gentoo and it seems to be pretty decent. It's a lot better than amdgpupro.

sperg512 commented on 2020-12-10 16:05 (UTC)

@jiweigert Your CPU is supported just as any other, but ROCm only supports Vega 10 and up. Since some of the issues we had were fixed (clinfo segfaulting), some more things should work for you. Who knows though, this IS a graphics driver, this IS a new one released for new hardware, and this IS Linux, let alone one not even officially supported by the driver.

jiweigert commented on 2020-12-10 15:56 (UTC)

Any update on the state of this package in terms of supporting Picasso CPU / Vega 8 APUs?

sperg512 commented on 2020-12-09 13:51 (UTC)

Actually, I fixed it. In the file ~/.config/libreoffice/*/user/registrymodifications.xcu, you'll find an entry that says "UseOpenCL". I set it to false and it worked.

sperg512 commented on 2020-12-09 13:49 (UTC)

@coxackie Nope, just straight up crashes with an "application error" when I open anything. Even just LibreOffice. Tried updating it, still didn't work. Guess I've got to stick to OpenOffice or something for now...

luciddream commented on 2020-12-09 13:47 (UTC)

Unrelated with the package but I also had issues with Libreoffice (it's crashing on copy paste on wayland), so I removed it and I'm using wps-office flatpak now which is much faster.

coxackie commented on 2020-12-09 13:42 (UTC)

@sperg512 you need OpenCL for an English test? Presumably you mean you need LibreOffice. Can you not open the basic "Libreoffice" frontend and disable OpenCL there? (Alt-F12 for Options, go to OpenCL, disable).

sperg512 commented on 2020-12-09 13:38 (UTC) (edited on 2020-12-09 13:44 (UTC) by sperg512)

Little extra note, for me LibreOffice doesn't launch with OpenCL on. Wish I hadn't tested it now, because I need it for my English exam which I'm working on currently...

ALSO now clinfo doesn't wanna work. Welp...

Recompiler commented on 2020-11-27 22:53 (UTC) (edited on 2020-12-07 21:34 (UTC) by Recompiler)

Just wanted to update everyone on my findings. I switched to gentoo over the past week and tried out proprietary opencl for my vega 10 and well, it crashed blender as soon as i opened the properties menu, and clinfo still seg faulted.

Step 2 was obviously to test opencl in windows to see if it ever worked to begin with. To my surprise it worked, but it was really slow. Switching back to the cpu greatly improved the speed by over 10x. I don't know why it's like that but maybe the gpu just wasn't optimized enough for it, it is a low-end igpu after all.

Interestingly even cpu rendering in blender on windows proved to be 25% faster than cpu rendering was in linux.

My final thoughts: opencl can work if you're willing to jump through a bunch of hoops but expect low-end iGPUs to be outperformed by the CPU. Also for serious rendering/encoding just get a Nvidia GPU, cuda is way better and a whole lot easier to get working. I plan to send my large renders to my server to use my cuda cores to render with. But at least I have a okayish setup on my laptop for light renders by using opencl with my cpu.

I hope anyone else with a Ryzen 7 3700U and a Vega 10 iGPU can find this helpful. If you have questions feel free to contact me at vectorflaredesigns@gmail.com

sperg512 commented on 2020-11-21 17:21 (UTC)

@macgeneral oh, I thought it meant for the entire thing. will remove from depends

« First ‹ Previous 1 .. 44 45 46 47 48 49 50 51 52 53 54 .. 79 Next › Last »