Very frustrated with this process, I was with Ubuntu which was a challenge to get working and I received an update and it crashed everything. Tried Fedora, and Centos8 with no luck and now back to Ubuntu.
I downloaded the drivers which changed on me between reinstalls of OS (to be sure I matched your drivers). I finally believe I have the right version of Ubuntu and I performed the install.
Radeon™ Software for Linux® installer version 21.50 for Ubuntu 20.04.4
Revision Number 21.50 File Size 14 KB Release Date 2/16/2022
amdgpu-install --opencl=legacy
Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 https://repo.radeon.com/amdgpu/21.50/ubuntu focal InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:5 https://repo.radeon.com/rocm/apt/5.0 ubuntu InRelease
Hit:6 http://security.ubuntu.com/ubuntu jammy-security InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package clinfo-amdgpu-pro
E: Unable to locate package opencl-legacy-amdgpu-pro-icd
CLInfo says:
Number of platforms 0
How do get the full info from CLInfo?
the OS does acknowledge I have the correct card looking on the system info screen, about.
Just cant get the advanced features?
Same for me !
I'm using FEDORA LINUX 35.
And I can't install amdgpu using radeon repositories.
I'm actually using amdgpu 21.30 because all others are NOT working.
Amdgpu 21.30: Working on Fedora 35.
Amdgpu 21.40: NOT working on Fedora 35.
Amdgpu 21.40.1: NOT working on Fedora 35.
Amdgpu 21.40.2: NOT working on Fedora 35.
Amdgpu 21.50: NOT working on Fedora 35.
Amdgpu 21.50.1: NOT working on Fedora 35.
Sadly, I need to modify many things to before be able to install amdgpu for rhel/centos on FEDORA !
WHY ? WHY NOT A FEDORA STANDALONE INSTALLATION
This must be where cry's for help go to die!
I just moved to CentOS Stream 9, so don't feel bad. I gave up using the amdgpu-install command. the installer RPM does not install the proper GPG keys because there is no CentOS 9 Stream repo yet, and the code in AMD's repo is woefully out of date. Plus, since CentOS 8 ceased operation, the centos base packages are all out of date as well, and that means no support there. You can't even update in order to move to stream because the archives are not updated either. I hosed my gaming PC/MythTV box trying, and I can't even troubleshoot the infinitv driver properly due to the fact that I am trying to deal with multiple hardware upgrades (should not be that severe, as they are a CPU upgrade, on a new motherboard with an ASUS X570 chipset similar to the original that fried, and more memory, the only issue might be with the X570, but as I went from an X-570 Prime-P to an X570-Tuf Gaming, that is no real change). I am running on a Ryzen 9 5950X proocessor with an RTX 6700 RX graphics card. The CPU was upgraded from a Ryzen 3 3200G. Memory went from a paltry 32 GB to 128 GB. My SSDs stayed the same at 1 TB and 2 TB PCIe4.0 NVMe drives from Seagate, and two SATA SSDs raided together for 8TB of space. I hate being resource constrained.
it isn't the rpm's per se. I have libffi version 8 and they want version 6 only. That's okay, though, because lsb does not exist either, so my epson driver cannot install
the latest version of the installer is still broken. I am getting a 'bad key' signature exception from AMD's key. It breaks all updates because the single bad key corrupts the entire RPMDB entry set. Until AMD fixes the issue they are causing, I cannot update my system at all - even for things like grub, which doesn't even use the AMD driver. Of course, they are denying blame because they failed to properly test their RPMs on CentOS 9 Stream, claiming that they only support the baseline CentOS 9 (which everyone with half a brain cell or access to Google knows does not exist). Their solution? "Oh, just blow away your entire system and install a version of the operating system that we support but which is no longer maintained because we are too damned lazy to support our customers when they ask us to undertake the massively complicated effort to update our GPG signature key." I am a software developer. I also maintain systems for companies. We update said keys four times a year, and we maintain a Hell of a lot more than one vendor's key.