You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[ROCm support in upstream Linux kernels](#rocm-support-in-upstream-linux-kernels)
@@ -47,6 +47,9 @@ The following list of GPUs are enabled in the ROCm software, though full support
47
47
As described in the next section, GFX8 GPUs require PCI Express 3.0 (PCIe 3.0) with support for PCIe atomics. This requires both CPU and motherboard support. GFX9 GPUs, by default, also require PCIe 3.0 with support for PCIe atomics, but they can operate in most cases without this capability.
48
48
49
49
At this time, the integrated GPUs in AMD APUs are not officially supported targets for ROCm.
50
+
As descried [below](#limited-support), "Carrizo", "Bristol Ridge", and "Raven Ridge" APUs are enabled in our upstream drivers and OpenCL runtime.
51
+
However, they are not enabled in our HCC or HIP runtimes, and may not work due to motherboard or OEM hardware limitations.
52
+
As such, they are not yet officially supported targets for ROCm.
50
53
51
54
For a more detailed list of hardware support, please see [the following documentation](https://rocm.github.io/hardware.html).
52
55
@@ -86,23 +89,25 @@ Experimental support for our Hawaii (GFX7) GPUs (Radeon R9 290, R9 390, FirePro
86
89
does not require or take advantage of PCIe Atomics. However, we still recommend that you use a CPU
87
90
from the list provided above for compatibility purposes.
88
91
89
-
#### Not supported or very limited support under ROCm
90
-
######Limited support
92
+
#### Not supported or limited support under ROCm
93
+
##### Limited support
91
94
92
95
* ROCm 2.0.x should support PCIe 2.0 enabled CPUs such as the AMD Opteron, Phenom, Phenom II, Athlon, Athlon X2, Athlon II and older Intel Xeon and Intel Core Architecture and Pentium CPUs. However, we have done very limited testing on these configurations, since our test farm has been catering to CPUs listed above. This is where we need community support. _If you find problems on such setups, please report these issues_.
93
96
* Thunderbolt 1, 2, and 3 enabled breakout boxes should now be able to work with ROCm. Thunderbolt 1 and 2 are PCIe 2.0 based, and thus are only supported with GPUs that do not require PCIe 3.0 atomics (e.g. Vega 10). However, we have done no testing on this configuration and would need community support due to limited access to this type of equipment.
94
-
* AMD "Carrizo" and "Bristol Ridge" APUs are enabled to run OpenCL, but do not yet support HCC, HIP, or our libraries built on top of these compilers and runtimes
97
+
* AMD "Carrizo" and "Bristol Ridge" APUs are enabled to run OpenCL, but do not yet support HCC, HIP, or our libraries built on top of these compilers and runtimes.
98
+
* As of ROCm 2.0, "Carrizo" and "Bristol Ridge" require the use of upstream kernel drivers.
95
99
* In addition, various "Carrizo" and "Bristol Ridge" platforms may not work due to OEM and ODM choices when it comes to key configurations parameters such as inclusion of the required CRAT tables and IOMMU configuration parameters in the system BIOS.
96
100
* Before purchasing such a system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2 and that the system BIOS properly exposes the correct CRAT table. Inquire with your vendor about the latter.
97
-
* AMD "Raven Ridge" APUs are enabled to run OpenCL, but do not yet support HCC, HIP, or our libraries built on top of these compilers and runtimes
101
+
* AMD "Raven Ridge" APUs are enabled to run OpenCL, but do not yet support HCC, HIP, or our libraries built on top of these compilers and runtimes.
102
+
* As of ROCm 2.0, "Raven Ridge" requires the use of upstream kernel drivers.
98
103
* In addition, various "Raven Ridge" platforms may not work due to OEM and ODM choices when it comes to key configurations parameters such as inclusion of the required CRAT tables and IOMMU configuration parameters in the system BIOS.
99
104
* Before purchasing such a system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2 and that the system BIOS properly exposes the correct CRAT table. Inquire with your vendor about the latter.
100
105
101
-
######Not supported
106
+
##### Not supported
102
107
103
108
* "Tonga", "Iceland", "Vega M", and "Vega 12" GPUs are not supported in ROCm 2.0.x
104
109
* We do not support GFX8-class GPUs (Fiji, Polaris, etc.) on CPUs that do not have PCIe 3.0 with PCIe atomics.
105
-
* As such, do not support AMD Carrizo and Kaveri APUs as hosts for such GPUs.
110
+
* As such, we do not support AMD Carrizo and Kaveri APUs as hosts for such GPUs.
106
111
* Thunderbolt 1 and 2 enabled GPUs are not supported by GFX8 GPUs on ROCm. Thunderbolt 1 & 2 are based on PCIe 2.0.
107
112
108
113
### The latest ROCm platform - ROCm 2.0
@@ -155,6 +160,7 @@ The latest supported version of the drivers, tools, libraries and source code fo
155
160
#### Supported Operating Systems - New operating systems available
156
161
157
162
The ROCm 2.0.x platform supports the following operating systems:
163
+
158
164
* Ubuntu 16.04.x and 18.04.x (Version 16.04.3 and newer or kernels 4.13 and newer)
159
165
* CentOS 7.4, 7.5, and 7.6 (Using devtoolset-7 runtime support)
160
166
* RHEL 7.4, 7.5, and 7.6 (Using devtoolset-7 runtime support)
@@ -165,6 +171,7 @@ As of ROCm 1.9.0, the ROCm user-level software is compatible with the AMD driver
165
171
As such, users have the option of either using the ROCK kernel driver that are part of AMD's ROCm repositories or using the upstream driver and only installing ROCm user-level utilities from AMD's ROCm repositories.
166
172
167
173
These releases of the upstream Linux kernel support the following GPUs in ROCm:
174
+
168
175
* 4.17: Fiji, Polaris 10, Polaris 11
169
176
* 4.18: Fiji, Polaris 10, Polaris 11, Vega10
170
177
@@ -198,6 +205,7 @@ This allows users to install only the packages they need, if they do not wish to
198
205
These packages will install most of the ROCm software into `/opt/rocm/` by default.
199
206
200
207
The packages for each of the major ROCm components are:
0 commit comments