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
The AMD GPU Driver (amdgpu) 30.30.0 is compatible with ROCm 7.2.x, 7.1.x, 7.0.x, 6.4.x, and 6.3.x. For more information, see `AMD GPU Driver (amdgpu) support matrix
9
+
The AMD GPU Driver (amdgpu) 30.30.1 is compatible with ROCm 7.2.x, 7.1.x, 7.0.x, 6.4.x, and 6.3.x. For more information, see `AMD GPU Driver (amdgpu) support matrix
The release notes provide release highlights and resolved issues since the previous AMD GPU Driver release (30.20.1).
3
+
The release notes provide release highlights and resolved issues since the previous AMD GPU Driver release (30.30.0).
4
4
5
5
## Release highlights
6
6
7
-
The following are notable new features and improvements in AMD GPU Driver 30.30.0.
7
+
The following are notable new features and improvements in AMD GPU Driver 30.30.1.
8
8
9
9
### Operating system and hardware support changes
10
10
11
-
This release doesn't introduce operating system or hardware support changes.
11
+
The AMD GPU Driver 30.30.1 introduces support for Ubuntu 24.04.4 HWE (Hardware Enablement).
12
12
13
13
For compatibility between AMD GPU Driver, ROCm, GPUs, and operating systems, see the [Compatibility matrix](../compatibility/compatibility-matrix.rst).
14
14
15
15
## Resolved issues
16
16
17
-
The following previously known issues have been resolved in this release:
18
-
19
-
- Resolved an issue where several GDB unit tests were timing out because the test application sent a `kill` command to the kernel while it was still shutting down VM entities, and the VM release work queue was active.
20
-
21
-
- Resolved an issue where `MEM_USAGE` showed values in exabytes during KFD tests.
22
-
23
-
- Resolved errors that occurred during the execution of the `mem_leak_hip_samples` test.
17
+
Resolved an issue on Navi3x platforms where the Kernel Fusion Driver (KFD) could stop functioning if a GPU device was removed at runtime. The driver now supports hot‑unplug scenarios and reports device unavailability when all GPUs are removed. This fix has been validated on MI200-Series GPUs and MI300-Series GPUs.
0 commit comments