mirror of
https://github.com/ROCm/ROCm.git
synced 2026-02-04 11:25:03 -05:00
* Remove install instructions for unsuported RHEL 8.8 and 9.2
Current ROCm release does not support these versions of RHEL
* Centralize disclaimers and perquisites for installation
- Move the single-version to multi-version diclaimer to the install
overview page where single vs multi installs are discussed.
- Move the installation of kernel-headers and development packages
to the install preparation page. Unify it mainly from the quick start
content.
* s/Name/name/ in repository config files for RHEL
The repository name can be set as `name=><name>` instead of `Name`,
otherwise yum complains about the repo not having a name, e.g:
```output
Repository 'ROCm-5.3.3' is missing name in configuration, using id.
```
This is fixed with this commit.
* Clean up render/video group section on prerequisites
* Installation and Upgrade restructuring & fixes
- Fix the rocm package urls for RHEL in the install & upgrade guides
- RHEL8 and 9 have different URLs, add a tab-set similar to ubuntu
for them.
- Fix the package URL in the upgrade guide for SLES (previously pointed
to the amdgpu url)
- Change the apt-signing key download and conversion to the method used
in the quick start guide, which is the recommended by ubuntu maintainers
- Change the install steps from list items to rubrics with numbered entries
which is more readable and matches the style in the quick start guide
- Do not pass `--append` to `tee` in the upgrade guide, because it is
meant to overwrite.
- Split the one long tab-set to multiple tab-sets in the upgrade guide
to improve readability
72 lines
2.4 KiB
Markdown
72 lines
2.4 KiB
Markdown
# ROCm Installation Options (Linux)
|
|
|
|
Users installing ROCm must choose between various installation options. A new
|
|
user should follow the [Quick Start guide](./quick_start).
|
|
|
|
## Package Manager versus AMDGPU Installer?
|
|
|
|
ROCm supports two methods for installation:
|
|
|
|
- Directly using the Linux distribution's package manager
|
|
- The `amdgpu-install` script
|
|
|
|
There is no difference in the final installation state when choosing either
|
|
option.
|
|
|
|
Using the distribution's package manager lets the user install,
|
|
upgrade and uninstall using familiar commands and workflows. Third party
|
|
ecosystem support is the same as your OS package manager.
|
|
|
|
The `amdgpu-install` script is a wrapper around the package manager. The same
|
|
packages are installed by this script as the package manager system.
|
|
|
|
The installer automates the installation process for the AMDGPU
|
|
and ROCm stack. It handles the complete installation process
|
|
for ROCm, including setting up the repository, cleaning the system, updating,
|
|
and installing the desired drivers and meta-packages. Users who are
|
|
less familiar with the package manager can choose this method for ROCm
|
|
installation.
|
|
|
|
(installation-types)=
|
|
|
|
## Single Version ROCm install versus Multi-Version
|
|
|
|
ROCm packages are versioned with both semantic versioning that is package
|
|
specific and a ROCm release version.
|
|
|
|
### Single-version Installation
|
|
|
|
The single-version ROCm installation refers to the following:
|
|
|
|
- Installation of a single instance of the ROCm release on a system
|
|
- Use of non-versioned ROCm meta-packages
|
|
|
|
### Multi-version Installation
|
|
|
|
The multi-version installation refers to the following:
|
|
|
|
- Installation of multiple instances of the ROCm stack on a system. Extending
|
|
the package name and its dependencies with the release version adds the
|
|
ability to support multiple versions of packages simultaneously.
|
|
- Use of versioned ROCm meta-packages.
|
|
|
|
```{attention}
|
|
ROCm packages that were previously installed from a single-version installation
|
|
must be removed before proceeding with the multi-version installation to avoid
|
|
conflicts.
|
|
```
|
|
|
|
```{note}
|
|
Multiversion install is not available for the kernel driver module, also referred to as AMDGPU.
|
|
```
|
|
|
|
The following image demonstrates the difference between single-version and
|
|
multi-version ROCm installation types:
|
|
|
|
```{figure-md} install-types
|
|
|
|
<img src="/data/deploy/linux/image.001.png" alt="">
|
|
|
|
ROCm Installation Types
|
|
```
|