Q: What kernels do we support?
A: The supported kernels are documented at https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
These documented kernels are tested and validated.
Note: There may be other kernels that work with ROCm; however, we do not support them officially as they are not tested and validated for ROCm.
Q: Ubuntu supports the latest kernels like v5.12. However, ROCm does not support the latest kernels. Why?
A: We try to implement detailed and thorough testing of the latest kernels before they are made available in a release. This approach ensures that the kernels are added to the supported list only after they are validated completely.
Please refer to ROCm documentation for each release for the latest supported distros and kernels.
https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
Q: Does ROCm support non-LTS OS versions?
A: ROCm does not support non-LTS versions officially. While ROCm might work on non-LTS versions, it is not tested and validated.
Q: Can we install both amdgpu-pro and ROCm on the same machine?
A: We do not recommend keeping both amdgpu-pro and ROCm on the same machine. ROCm installs amdgpu as the base driver. A separate and additional installation of amdgpu-pro will break ROCm as it cannot handle both packages.
For more information, refer to
https://rocmdocs.amd.com/en/latest/Current_Release_Notes/Current-Release-Notes.html#driver-compabili...
Q: Can we install single version ROCm along with multi-ROCm packages?
A: We do not recommend installing single ROCm and multi-ROCm packages on the same machine as the conflicting package versions will result in a faulty installation.
Q: Can we build ROCm from the source?
A: Yes, you can build ROCm from the source. For more information, refer to https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html#getting-the-rocm-sourc...
Q: Are there plans to support ROCm on Macintosh?
A: There are no plans to support ROCm on Macintosh currently. Please refer to the ROCm documentation website for the latest information on supported environments.
https://rocmdocs.amd.com
Q: Does ROCm support gfx8 devices?
A: ROCm does not support gf8 devices officially. ROCm works on some gfx8 devices; however, it is not officially tested and validated.
Q: Does ROCm work with upstream kernels?
A: Yes, most versions of ROCm work with upstream kernels. However, ROCm v4.1 does not work with upstream kernels for 7 nm (Vega20) and displays the following error:
"HSA Error: Incompatible kernel and userspace, Vega 20 [Radeon VII] disabled. Upgrade amdgpu."
The error is due to the SRAM ECC issue. For more information, refer to the documentation at:
https://rocmdocs.amd.com/en/latest/Current_Release_Notes/Current-Release-Notes.html#driver-compabili...
Q: Does ROCm support upgrade?
A: Currently, ROCm does not support the upgrade functionality.
Q: When are we planning to support the Navi series of cards?
A: Navi cards are not supported at this time.
Please check our documentation website at https://rocmdocs.amd.com for the latest updates.
Q: Which versions of Navi does ROCm support?
A: None of the Navi versions are supported currently. Please check our documentation website at https://rocmdocs.amd.com for the latest updates.
Q: Are GUI applications supported with ROCm?
A: Yes, ROCm supports GUI-based applications.
Q: Is ROCm supported on distros other than Ubuntu, CentOS/RHEL, and SLES?
A: Currently, Ubuntu, CentOS/RHEL, and SLES are supported. For more details, see the ROCm Installation Guide at https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
Q: Is there any utility I can use on CentOS v7.9 to stress test MI100 accelerators?
A: The AMD ROCm team recommends using the ROCm Validation Suite (rvs) for rvs stress tests. The steps are as follows:
- Install ROCm using
sudo apt install rocm-dkms
- Install ROCm Validation Suite
sudo apt install rvs
cd /opt/rocm/rvs && sudo cp -rf /opt/rocm/rvs/testscripts/* /opt/rocm/rvs/
- Run the script. For example, use the stress module,
sudo ./rvs-stress-long.sh
