Quick not note for those not familiar with the CentOS 7 peculiarity and especially the repository peculiarity.
Receiving the follwoing error:
Installing dkms on CENTOS 6. Just find the package you need download and install. 1.-Download and install redhat 7 binaries ISO 2.-Register.
- Today we will see how to install Veeam Agent on CentOS 7 server which will enable us to take backup and configure backup on that server. All the backup configuration like which things to be backed up and at what schedule the backup should run are configured at agent side so we will see that part in detail in steps below.
- EPEL aarch64 Official dkms-2.7.1-1.el7.noarch.rpm: Dynamic Kernel Module Support Framework: EPEL armhfp Official dkms-2.8.3-2.el7.noarch.rpm: Dynamic Kernel Module Support Framework.
- The objective is to install VirtualBox Guest Additions on CentOS 7 Linux Operating System and Software Versions. Operating System: - CentOS Linux release 7.5.1804 (Core). $ sudo yum install perl gcc dkms kernel-devel kernel-headers make bzip2 Confirm that kernel-headers installed.
- The virtual machine is installed on Windows Vista. So it is CentOS running virtual inside of Windows Vista, and I am trying to install DKMS onto the CentOS BEFORE I install the client additions onto CentOS. DKMS is recommended because parts of the Oracle VM VirtualBox software are kernel modules.
It means you need a package (or meta-package, which might pull multiple packages and dependencies offering a big framework, for example), which could not be found in the existing repositories. In this very case, we need the DKMS (Dynamic Kernel Module Support) – https://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support
The DKMS is offered in epel repository and it could not be found in the CentOS 7 official repositories. Just add the epel repository.
And rerun your first install yum line. Now you won’t receive the DKMS error.
Deploying ROCm¶
AMD hosts both Debian and RPM repositories for the ROCm v3.x packages.
The following directions show how to install ROCm on supported Debian-based systems such as Ubuntu 18.04.x
Note: These directions may not work as written on unsupported Debian-based distributions. For example, newer versions of Ubuntu may not be compatible with the rock-dkms kernel driver. In this case, you can exclude the rocm-dkms and rock-dkms packages.
Note: You must use either ROCm or the amdgpu-pro driver. Using both drivers will result in an installation error.
Important - Mellanox ConnectX NIC Users: If you are using Mellanox ConnetX NIC, you must install Mellanox OFED before installing ROCm.
For more information about installing Mellanox OFED, refer to:
Prerequisites¶
In this release, AMD ROCm extends support to SLES 15 SP2
The AMD ROCm platform is designed to support the following operating systems:
Ubuntu 20.04.1 (5.4 and 5.6-oem) and 18.04.5 (Kernel 5.4)
Need a driver for sony digital handycam dcr trv250 for mac. Note: Ubuntu versions lower than 18 are no longer supported.
Note: AMD ROCm only supports Long Term Support (LTS) versions of Ubuntu. Versions other than LTS may work with ROCm, however, they are not officially supported.
CentOS 7.8 & RHEL 7.8 (Kernel 3.10.0-1127) (Using devtoolset-7 runtime support)
CentOS 8.2 & RHEL 8.2 (Kernel 4.18.0 ) (devtoolset is not required)
SLES 15 SP2
FRESH INSTALLATION OF AMD ROCm V3.10 RECOMMENDED
A fresh and clean installation of AMD ROCm v3.10 is recommended. An upgrade from previous releases to AMD ROCm v3.10 is not supported.
Note: AMD ROCm release v3.3 or prior releases are not fully compatible with AMD ROCm v3.5 and higher versions. You must perform a fresh ROCm installation if you want to upgrade from AMD ROCm v3.3 or older to 3.5 or higher versions and vice-versa.
For ROCm v3.5 and releases thereafter, the clinfo path is changed to - /opt/rocm/opencl/bin/clinfo.
For ROCm v3.3 and older releases, the clinfo path remains unchanged - /opt/rocm/opencl/bin/x86_64/clinfo.
Note: After an operating system upgrade, AMD ROCm may upgrade automatically and result in an error. This is because AMD ROCm does not support upgrades currently. You must uninstall and reinstall AMD ROCm after an operating system upgrade.
MULTI-VERSION INSTALLATION UPDATES
With the AMD ROCm v3.10 release, the following ROCm multi-version installation changes apply:
The meta packages rocm-dkms<version> are now deprecated for multi-version ROCm installs. For example, rocm-dkms3.7.0, rocm-dkms3.8.0.
Multi-version installation of ROCm should be performed by installing rocm-dev<version> using each of the desired ROCm versions.For example, rocm-dev3.7.0, rocm-dev3.8.0, rocm-dev3.9.0.
‘version’ files should be created for each multi-version rocm <= 3.10.0
command: echo <version> | sudo tee /opt/rocm-<version>/.info/version
example: echo 3.10.0 | sudo tee /opt/rocm-3.10.0/.info/version
The rock-dkms loadable kernel modules should be installed using a single rock-dkms package.
ROCm v3.9 and above will not set any ldconfig entries for ROCm libraries for multi-version installation. Users must set LD_LIBRARY_PATH to load the ROCm library version of choice.
NOTE: The single version installation of the ROCm stack remains the same. The rocm-dkms package can be used for single version installs and is not deprecated at this time.
Supported Operating Systems¶
Ubuntu¶
Note: AMD ROCm only supports Long Term Support (LTS) versions of Ubuntu. Versions other than LTS may work with ROCm, however, they are not officially supported.
Installing a ROCm Package from a Debian Repository¶
To install from a Debian Repository:
Run the following code to ensure that your system is up to date:
Add the ROCm apt repository.
For Debian-based systems like Ubuntu, configure the Debian ROCm repository as follows:
Note: The public key has changed to reflect the new location. You must update to the new location as the old key will be removed in a future release.
Old Key: https://repo.radeon.com/rocm/apt/debian/rocm.gpg.key
New Key: https://repo.radeon.com/rocm/rocm.gpg.key
The gpg key may change; ensure it is updated when installing a new release. If the key signature verification fails while updating, re-add the key from the ROCm apt repository.
The current rocm.gpg.key is not available in a standard key ring distribution, but has the following sha1sum hash:
Install the ROCm meta-package. Update the appropriate repository list and install the rocm-dkms meta-package:
Set permissions. To access the GPU, you must be a user in the video and render groups. Ensure your user account is a member of the video and render groups prior to using ROCm. To identify the groups you are a member of, use the following command:
To add your user to the video and render groups, use the following command with the sudo password:
Note: render group is required only for Ubuntu v20.04. For all other ROCm supported operating systems, continue to use video group.
Installing Dkms On Centos 7 Vm
By default, you must add any future users to the video and render groups. To add future users to the video and render groups, run the following command:
Restart the system.
After restarting the system, run the following commands to verify that the ROCm installation is successful. If you see your GPUs listed by both commands, the installation is considered successful.
Note: To run the ROCm programs, add the ROCm binaries in your PATH.
Uninstalling ROCm Packages from Ubuntu¶
To uninstall the ROCm packages from Ubuntu 20.04 or Ubuntu 18.04.5, run the following command:
Installing Development Packages for Cross Compilation¶
It is recommended that you develop and test development packages on different systems. For example, some development or build systems may not have an AMD GPU installed. In this scenario, you must avoid installing the ROCk kernel driver on the development system.
Instead, install the following development subset of packages:
Note: To execute ROCm enabled applications, you must install the full ROCm driver stack on your system.
Using Debian-based ROCm with Upstream Kernel Drivers¶
You can install the ROCm user-level software without installing the AMD’s custom ROCk kernel driver. To use the upstream kernels, run the following commands instead of installing rocm-dkms:
CentOS RHEL¶
This section describes how to install ROCm on supported RPM-based systems such as CentOS/RHEL v7.8 and CentOS/RHEL v8.2.
Install Virtualbox On Centos 7 Minimal
Preparing RHEL for Installation¶
RHEL is a subscription-based operating system. You must enable the external repositories to install on the devtoolset-7 environment and the dkms support files.
Note: The following steps do not apply to the CentOS installation.
The subscription for RHEL must be enabled and attached to a pool ID. See the Obtaining an RHEL image and license page for instructions on registering your system with the RHEL subscription server and attaching to a pool id.
Enable the following repositories for RHEL v7.x:
Enable additional repositories by downloading and installing the epel-release-latest-7/epel-release-latest-8 repository RPM:
For more details,
see https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm for RHEL v7.x
see https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm for RHEL v8.x
Install and set up Devtoolset-7.
Note: Devtoolset is not required for CentOS/RHEL v8.x
To setup the Devtoolset-7 environment, follow the instructions on this page: https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
Note: devtoolset-7 is a software collections package and is not supported by AMD.
Installing CentOS v7.8/v8.2 for DKMS¶
Use the dkms tool to install the kernel drivers on CentOS/RHEL:
Installing ROCm¶
To install ROCm on your system, follow the instructions below:
Delete the previous versions of ROCm before installing the latest version.
Create a /etc/yum.repos.d/rocm.repo file with the following contents:
CentOS/RHEL 7.x : https://repo.radeon.com/rocm/yum/rpm
CentOS/RHEL 8.x : https://repo.radeon.com/rocm/centos8/rpm
Note: The URL of the repository must point to the location of the repositories’ repodata database.
Install ROCm components using the following command:
Restart the system. The rock-dkms component is installed and the /dev/kfd device is now available.
Set permissions. To access the GPU, you must be a user in the video group. Ensure your user account is a member of the video group prior to using ROCm. To identify the groups you are a member of, use the following command:
To add your user to the video group, use the following command with the sudo password:
By default, add any future users to the video group. Run the following command to add users to the video group:
Note: Before updating to the latest version of the operating system, delete the ROCm packages to avoid DKMS-related issues.
Restart the system.
Test the ROCm installation.
Testing the ROCm Installation¶
After restarting the system, run the following commands to verify that the ROCm installation is successful. If you see your GPUs listed, you are good to go!
Note: Add the ROCm binaries in your PATH for easy implementation of the ROCm programs.
Compiling Applications Using HCC, HIP, and Other ROCm Software¶
To compile applications or samples, run the following command to use gcc-7.2 provided by the devtoolset-7 environment:
Uninstalling ROCm from CentOS/RHEL¶
To uninstall the ROCm packages, run the following command:
Installing Development Packages for Cross Compilation¶
You can develop and test ROCm packages on different systems. For example, some development or build systems may not have an AMD GPU installed. In this scenario, you can avoid installing the ROCm kernel driver on your development system. Instead, install the following development subset of packages:
Note: To execute ROCm-enabled applications, you will require a system installed with the full ROCm driver stack.
Using ROCm with Upstream Kernel Drivers¶
You can install ROCm user-level software without installing AMD’s custom ROCk kernel driver. To use the upstream kernel drivers, run the following commands
Note: You can use this command instead of installing rocm-dkms.
Note: Ensure you restart the system after ROCm installation.
SLES 15 Service Pack 2¶
The following section tells you how to perform an install and uninstall ROCm on SLES 15 SP 2.
Installation
Install the “dkms” package.
Add the ROCm repo.
Run the following command once
Verify the ROCm installation.
Run /opt/rocm/bin/rocminfo and /opt/rocm/opencl/bin/clinfo commands to list the GPUs and verify that the ROCm installation is successful.
Set permissions.
To access the GPU, you must be a user in the video group. Ensure your user account is a member of the video group prior to using ROCm. To identify the groups you are a member of, use the following command:
To add your user to the video group, use the following command with the sudo password:
By default, add any future users to the video group. Run the following command to add users to the video group:
Restart the system.
Test the basic ROCm installation.
After restarting the system, run the following commands to verify that the ROCm installation is successful. If you see your GPUs listed by both commands, the installation is considered successful.
Note: To run the ROCm programs more efficiently, add the ROCm binaries in your PATH.
echo ‘export PATH=$PATH:/opt/rocm/bin:/opt/rocm/profiler/bin:/opt/rocm/opencl/bin’|sudo tee -a /etc/profile.d/rocm.sh
Using ROCm with Upstream Kernel Drivers
Uninstallation
To uninstall, use the following command:
Note: Ensure all other installed packages/components are removed.Note: Ensure all the content in the /opt/rocm directory is completely removed. If the command does not remove all the ROCm components/packages, ensure you remove them individually.
Performing an OpenCL-only Installation of ROCm¶
Some users may want to install a subset of the full ROCm installation. If you are trying to install on a system with a limited amount of storage space, or which will only run a small collection of known applications, you may want to install only the packages that are required to run OpenCL applications. To do that, you can run the following installation command instead of the command to install rocm-dkms.
ROCm Installation Known Issues and Workarounds¶
The ROCm platform relies on some closed source components to provide functionalities like HSA image support. These components are only available through the ROCm repositories, and they may be deprecated or become open source components in the future. These components are made available in the following packages:
hsa-ext-rocr-dev
Getting the ROCm Source Code¶
AMD ROCm is built from open source software. It is, therefore, possible to modify the various components of ROCm by downloading the source code and rebuilding the components. The source code for ROCm components can be cloned from each of the GitHub repositories using git. For easy access to download the correct versions of each of these tools, the ROCm repository contains a repo manifest file called default.xml. You can use this manifest file to download the source code for ROCm software.
The repo tool from Google® allows you to manage multiple git repositories simultaneously. Run the following commands to install the repo:
Note: You can choose a different folder to install the repo into if you desire. ~/bin/ is used as an example.
Downloading the ROCm Source Code¶
The following example shows how to use the repo binary to download the ROCm source code. If you choose a directory other than ~/bin/ to install the repo, you must use that chosen directory in the code as shown below:
Note: Using this sample code will cause the repo to download the open source code associated with this ROCm release. Ensure that you have ssh-keys configured on your machine for your GitHub ID prior to the download.