How do I check AMD ROCm and CPU architecture support on a dedicated server?
Validate the full combination of GPU model, CPU architecture, operating system, kernel, ROCm release and application framework. AMD GPU presence alone does not establish ROCm support. An ARM64 or x86-64 application image also needs compatible native libraries and accelerator support.
Before you start
- The intended ROCm/framework version and the server’s exact GPU and CPU specification.
Instructions
1. Identify the host and installed tooling
Read the host architecture and, when AMD SMI is already installed, its device list. A missing command is a tooling issue to investigate; do not install a driver simply to discover the server’s identity.
uname -m
amd-smi listReports the Linux architecture and visible AMD GPU identities using an existing AMD SMI installation.
2. Match the official compatibility tables
Use the matrix for the release you intend to run, including the particular accelerator or Radeon model, OS and supported framework. Verify CPU architecture support in the relevant installation and framework documentation; do not infer ARM support from a GPU’s appearance in a general device list.
3. Validate the actual application environment
Check container image architecture, compiled extensions and driver access. Run a representative application test in a controlled environment before migration. Use AMD’s supported tools for AMD devices; NVIDIA-specific commands and CUDA-version output cannot verify a ROCm deployment.
Check the result
- Every required platform component is explicitly supported for the selected release.
- The application detects the intended AMD device and completes a representative operation.
Troubleshooting
- The GPU is listed but a framework reports no compatible device
- Compare the exact framework build, ROCm version, OS/kernel support and device permissions. Hardware enumeration alone does not establish compute-runtime readiness.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.