[SOLVED] Slackware64 current (15.0) OpenCL added to stock Mesa amdgpu - call for testing
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just for giggles I fired up PhoenixMiner and it seems it found the correct RX5700XT OpenCL platform (Slackware64-current mulilib kernel 5.10.17, default settings, with just -amd -acm) Although, at 50 MH/s I won't be expecting much "profit" ;-)
So I'd say there might be something screwy on your end.
What happens when you move '/etc/OpenCL/vendors/mesa.icd' somewhere else?
When I did that, nsgminer started working and the pool accepted a share. PhoenixMiner is taking longer to start, but it might be that the pool I'm on tests your GPU for a while first. Could I just rename it mesa.icd.bak or would it still be detected?
I'm wondering if by Slackware 15 we won't have to make this minor tweak anymore. I'd never have figured it out without expert help...
... Could I just rename it mesa.icd.bak or would it still be detected?
I'm wondering if by Slackware 15 we won't have to make this minor tweak anymore. I'd never have figured it out without expert help...
Renaming "might" work...not sure. Don't forget too that mesa.icd will be replaced on each Mesa upgrade. There should be a setting in these miners to pick the OpenCL platform.
heh "expert". much appreciated, though befuddled. I'm just a hobbyist that like to tinker!
Hi, it looks like AMD ROCm starting from version 3.7 has open-source OpenCL image module included. I have used rocm few years ago and this post help me with install https://www.linuxquestions.org/quest...re-4175638428/ but that was 3 years ago. A lot has change since then and I remember it was pain to get romc opencl running. There was bug in rocm image support back then so I switched to binary opencl package created by kingbeowulf.
Did anyone tried latest ROCm ? I think it would be helpful to have slackbuild script to build ROCm from source, but this is beyond my skills.
What do you think ? I would like to hear your opinions.
I'm looking into it, as an option to replace the repackaging of the OpenCL bits from amdgpu-pro. Supposedly ROCm finally added Navi support (?) which was holding me back. There are some other limitations and requirements as well that make ROCm unsuitable for a GUI desktop. I just wish they would just release a simple OpenCL library and runtime without all the ROCm API and SDK complexity.
Renaming/moving that configuration file didn't work to get PhoneixMiner nor ethminer working for ethereum--they started but just never continued. I still was able to mine with ryominer (for ryo), nsgminer (for feathercoin), but can't also test lolMiner (for bitcoin gold) yet. I am unable to try ROCm but it'd be preferable, except I use desktops. AMD's drivers had several more versions since this thread continued, up to at least version 21.30. Will we see builds for these?
I think it's important to keep all versions of the builds around. Some older drivers work better, but if you have too new a kernel, and were using some OS it installs DKMS, you will no longer have a display (had this problem on KDE Neon GNU/Linux family PCs). A lot of the newer drivers are shoddier and all the miners just exit (may be a too low-Watt power supply unit (PSU) issue) but if you have a new enough kernel, some of them end up being okay, but if you do something as simple as upgrade a card, miners may start exiting again. It just takes trial & error to determine which will work at this point. Any particular driver won't necessarily work for everyone's situations.
Using amdgpu-pro-20.40-1147286-ubuntu-20.04.tar.xz, I was able to get an updated OpenCL slackbuild working on Slackware64-current (15.0, Sun Nov 15 00:02:28 UTC 2020).
I've just built and installed the resulting package. Works like a charm using AMD OpenCL 20.40-1147286 in Slackware64-current Sun Dec 19 18:57:11 UTC 2021.
Release 21.40.1 is the first Radeon™ Software for Linux that uses unified ROCm™ and graphics drivers. This release has not been fully validated for Machine Learning use cases. Users are recommended to use https://rocmdocs.amd.com/en/latest/C...ase-Notes.html for ROCm™ use cases.
This release introduces a new driver distribution model that is based on public package repository instead of tarball. The installer is posted on amd.com.
The amdgpu-install and amdgpu-uninstall scripts have been modified to support the above unified stack and new distribution model. Additional information on amdgpu-install and amdgpu-uninstall can be found in the installation documentation at https://amdgpu-install.readthedocs.io/en/21.40/ .
The installer streamlines the installation process by:
Abstracting the distribution-specific package installation logic,
Performing the repository set-up,
Allowing users to specify the use case and automating the installation of all the required packages,
Downloading only packages that are needed for the chosen use case and reducing download size, and
Performing post-install checks to verify whether the installation was performed successfully.
EULA acceptance for proprietary components has been moved from amd.com to the installer.
So I ask to @kingbeowulf: do you plan to upgrade your amdgpu-opencl.SlackBuild to use the new structure?
I've tried to do it by following AUR opencl-amd model but failed miserably.
EDIT: here's OpenCL working on my box with the now outdated 20.40-1147286...
I'm waiting for Slackware-current to settle down a bit more, as well as work, home etc has been a bit hectic. Rumor has it that "real soon now" might actually be "real soon"! LOL.
ROCm still does not yet "officially" support NAVI and NAVI2 GPUs, yet now ROCm is slipped into AMDGPU-PRO. Bunch of weirdos. I'm going to take a stab at a buildscript for ROCm to get the runtime (ROCr) bits working. The AMDGPU-PRO installation as in my amdgpu-opencl-20.40 script will be problematic from a maintenance standpoint, and the their installer uses those weird package managers (apt, yum etc). I'll try packaging 21.40.1 as well.
@denydias thanks for the feedback. Since you have Ryzen integrated GPU (Vega 8 I think), you may be better off with 20.40 than trying ROCm/ROCr until AMD clarifies support.
@dchmelik with amdgpu-opencl-20.40, on my RX5700XT and RX590, PhoenixMiner (eth, etc) work with about 51 and 27 MH/s respectively, as do various BOINC projects, over various 5.14.x and 5.15.x kernels. The RX590 does crash on occasion, but I think that is my card. Both boxes have 850 W power supplies. Not sure why you can't run PhoenixMiner.
I'll keep versions on my vanity website. Once Slackbuilds.org opens up, people can use their cgit to access older versions as well.
I'm waiting for Slackware-current to settle down a bit more, as well as work, home etc has been a bit hectic. Rumor has it that "real soon now" might actually be "real soon"! LOL.
Dunno... if it doesn't come in two days, then I don't now when it will come. :P
Quote:
Originally Posted by kingbeowulf
@denydias thanks for the feedback. Since you have Ryzen integrated GPU (Vega 8 I think), you may be better off with 20.40 than trying ROCm/ROCr until AMD clarifies support.
My pleasure. 20.40 is rock solid here. The only issue is imagemagick compiled with `--disable-opencl`, but gimp, libreoffice's calc and others are working like a charm.
Whenever you release a new ROCm/ROCr SBo, just ping us here.
@dchmelik with amdgpu-opencl-20.40, on my RX5700XT and RX590, PhoenixMiner (eth, etc) work with about 51 and 27 MH/s respectively, as do various BOINC projects, over various 5.14.x and 5.15.x kernels. The RX590 does crash on occasion, but I think that is my card. Both boxes have 850 W power supplies. Not sure why you can't run PhoenixMiner.
I was able to run some non-ethereum (ETH) miners, but as for ETH, I switched to TeamRedMiner, which is specifically for AMD GPUs.
I'm looking forward to your next SlackBuild--the one I'm using now might be a bit old...
I'm getting there "real soon now." Instead of a binary repack, I thought I'd wade through the ROCm runtime stuff. Either I'm an old man stuck in the '80s, or AMD is making a basic, simple OPENCL runtime build as difficult as possible. Extremely convoluted. I'll sift through the new AMDGPU-PRO soon. I promise!
I'm getting there "real soon now." Instead of a binary repack, I thought I'd wade through the ROCm runtime stuff. Either I'm an old man stuck in the '80s, or AMD is making a basic, simple OPENCL runtime build as difficult as possible. Extremely convoluted. I'll sift through the new AMDGPU-PRO soon. I promise!
ROCm is really complex... much more than it seems it should be. If it's not tackled before I get my system finally upgraded to 15.0, I may try and get a SlackBuild going. However, I also have an impending move to a new area of the country, so depending on when I find time to upgrade, it could be after the move. So others will probably have the opportunity to do it before I get a chance.
@kingbeowulf
Then I'm and old man stuck in '80s like you too. I told you that I tried to build the new ROCm thing from arc templates before using your script. That attempt took me some precious hours and failed miserably. Unfortunately I'm still too busy with the project I'm working on to give proper attention to this right now, so I'm just sticking with whatever you come up with... as a proof of my appreciation, I'm willing to help you and others on reviewing and testing anything you guys need.
I have a new amdgpu-opencl based on AMDGPU-PRO-22.10.1 for the proprietary (legacy, non-ROCm) OpenCL stack. This "should" work for Vega and older cards. No-go so far for newer Navi since the llvm and libclc included with Slackware is missing, for example, /usr/share/clc/gfx1010-amdgcn-mesa-mesa3d.bc for my Radeon RX 5700 XT (NAVI 1O). I have an old RX 590 (Polaris 30) somewhere - I'll try it as soon as I find it - but it may be too "new" as well. The buildscript is based on Redhat's rpms this time. The Ubuntu debs were a mess.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.