Linux users struggle to get older AMD GPUs working with new drivers

Many Linux users are having trouble using older AMD graphics cards. They need to change computer settings to make them work, which is harder than before.
By Newsroom | Technology, Software |

Persistent Hurdles Plague AMD GPU Users in Linux Environments

Users continue to report difficulties and seek workarounds for enabling and optimizing AMD graphics processing units (GPUs) within various Linux distributions, particularly Fedora.

The ongoing discourse reveals a fractured landscape for AMD GPU support. While newer 'RDNA' architectures largely function with minimal intervention, older hardware, specifically those based on the 'GCN 1-3' architectures, present persistent compatibility issues with the amdgpu driver. The radeon driver, an older alternative, often proves more stable for these older cards, especially for 2D acceleration and specific functionalities like VSync control, though it notably lacks support for modern graphics APIs like Vulkan.

This driver dichotomy, radeon versus amdgpu, is a central point of contention, forcing users to choose between legacy stability and modern feature support. The reliance on specific kernel parameters to force the system to use one driver over the other is a common, albeit cumbersome, solution.

Forcing Driver Compatibility and Kernel Parameters

Several users have detailed methods to manually enable the amdgpu driver or revert to the radeon driver. This often involves modifying kernel boot arguments, a process that requires careful attention to syntax and system configuration. Common parameters cited include radeon.si_support=0, amdgpu.si_support=1, radeon.cik_support=0, and amdgpu.cik_support=1. These parameters are typically added to GRUB configurations, with subsequent updates to the bootloader required for changes to take effect.

Read More: Acer Laptops: Nvidia GPU Not Detected on Nitro and Predator Models Since January 2024

  • radeon.si_support=0 and amdgpu.si_support=1: Primarily for 'Sea Islands' (GCN 1.0) GPUs.

  • radeon.cik_support=0 and amdgpu.cik_support=1: For 'Southern Islands' (GCN 1.1) and 'Volcanic Islands' (GCN 1.2) GPUs.

The necessity of these manual interventions suggests that automatic detection and driver assignment are not universally reliable, especially across a range of hardware generations.

On old AMD GPU support. Radeon vs AMDgpu - Fedora Discussion - 1

Performance and API Limitations

Beyond basic functionality, users report performance disparities and limitations. For instance, one user noted that the Xorg hardware-specific DDX (Direct Rendering Driver) performed better than modesetting on an Intel UHD 630. While amdgpu aims to provide a unified driver for modern AMD GPUs, its compatibility with older hardware remains a significant concern, limiting access to features like Vulkan, which is essential for modern gaming and high-performance computing via layers like DXVK.

Read More: New NVK Driver Replaces Nouveau for NVIDIA GPUs on Linux in 2025

  • Vulkan Support: Crucial for modern applications, but not supported by the radeon driver.

  • 2D Acceleration: The radeon driver is sometimes preferred for its direct handling of 2D acceleration, a benefit for older games. amdgpu, by contrast, may route 2D through 3D rendering pipelines, potentially impacting performance in legacy applications.

Firmware and Hardware Specifics

The functioning of the amdgpu driver is also intricately linked to the availability of correct firmware blobs. Users have encountered issues where missing or incorrect firmware files lead to driver initialization failures, preventing the GPU from being properly recognized or utilized. The list of required firmware files varies significantly based on the specific GPU architecture, such as Polaris, Vega, or Navi series.

  • Firmware Location: Firmware files are typically found in /lib/firmware/amdgpu/.

  • Naming Conventions: Firmware files often follow naming patterns like [gpu_codename]_[component].bin (e.g., polaris10_ce.bin, green_sardine_sdma.bin).

Troubleshooting often involves verifying that the correct firmware for the user's specific GPU model is present in the system's firmware directory.

Broader System Stability and Driver Crashes

Reports of system instability, including grey screens, input lag, and spontaneous reboots, are also linked to amdgpu driver issues. In some cases, these problems manifest without clear logging, making diagnosis difficult. Error messages related to page faults, such as amdgpu: [gfxhub] page fault, indicate deeper issues within the graphics driver's interaction with the system's memory management or kernel.

Read More: RTX 5060 Ti 16GB Price Drops Below $400 in November 2024 Sales

  • Error Patterns: page fault errors, ring timeout, and coredump files point towards potential driver bugs or hardware interaction problems.

Background: A Shifting Driver Landscape

Historically, AMD GPUs on Linux relied on the proprietary fglrx driver or the open-source radeon driver. As AMD transitioned to newer architectures and adopted a more open development model, the amdgpu driver emerged as the primary open-source solution. This driver is intended to support a broad range of AMD GPUs, from older GCN-based cards to the latest RDNA series. However, the transition has not been seamless. Older hardware often retains better stability with the legacy radeon driver, creating a persistent fork in support. This situation requires users to navigate complex configuration steps, often specific to their distribution and hardware, to achieve optimal graphics performance and stability. The ongoing discussions highlight a community effort to document and disseminate these workarounds, underscoring the often-unpredictable nature of hardware and software compatibility.

Frequently Asked Questions

Q: Why are Linux users having problems with AMD graphics cards?
Users with older AMD graphics cards, especially those from GCN 1-3, find they don't work well with the new 'amdgpu' driver. The older 'radeon' driver is sometimes more stable but lacks modern features.
Q: What are the main issues with AMD GPU drivers on Linux?
The main problem is choosing between the old 'radeon' driver for stability on older cards or the new 'amdgpu' driver for modern features like Vulkan. Users often need to manually change computer settings to pick the right driver.
Q: How do Linux users fix AMD GPU driver problems on older cards?
Users often add special commands to their computer's startup settings (like GRUB). These commands tell the system to use the 'amdgpu' driver or to stick with the 'radeon' driver for specific older cards.
Q: What are the performance and feature limits for older AMD GPUs on Linux?
Older cards might not work with new features like Vulkan, which is needed for modern games. The 'radeon' driver might be better for older games, but the 'amdgpu' driver is needed for newer technology.
Q: Can missing firmware files cause AMD GPU problems on Linux?
Yes, if the correct firmware files for the specific AMD GPU are missing from the system, the driver might not start correctly. Users need to make sure the right firmware is in the '/lib/firmware/amdgpu/' folder.
Q: What kind of system problems can AMD GPU driver issues cause on Linux?
Driver problems can lead to the screen going grey, slow responses, or the computer restarting by itself. Error messages about 'page fault' can show there are deeper issues with how the driver works.