AMD Vega GPU Graphics Patches and Framebuffer Requirements in OCLP

OpenCore Legacy Patcher applies a legacy Radeon X5000 driver stack and version-specific Monterey-derived framebuffers to enable AMD Vega GPU acceleration on Macs lacking AVX2.0 support.

The laobamac/oclp-mod repository maintains specialized patchsets for legacy Mac hardware, including dedicated AMD Vega GPU graphics patches that restore hardware acceleration on unsupported configurations. These patches target systems where the CPU lacks AVX2.0 instructions, requiring a custom driver stack and careful framebuffer selection to ensure compatibility across macOS Monterey through Sonoma.

Legacy Radeon X5000 Driver Stack

OCLP installs a complete legacy graphics stack to replace modern AMD drivers that require AVX2.0. This stack is defined in oclp_mod/sys_patch/patchsets/hardware/graphics/amd_vega.py within the _model_specific_patches function (lines 78-84).

Core Driver Components

The patchset copies the following extensions to /System/Library/Extensions:

• AMDRadeonX5000.kext — The core Radeon X5000 driver containing the built-in GPU framebuffer. This is the only driver required for Vega GPUs; additional bundles provide acceleration binaries.
• AMDRadeonVADriver2.bundle — Video Acceleration driver utilized by macOS 13+ Metal-based acceleration.
• AMDRadeonX5000GLDriver.bundle — OpenGL driver for legacy application support.
• AMDRadeonX5000MTLDriver.bundle — Metal driver with versions varying by target OS.
• AMDRadeonX5000Shared.bundle — Shared resources required by the driver stack.
• AMDShared.bundle — Common AMD resources needed by all Radeon drivers.

Extended Patch for Mixed GPU Configurations

Systems containing both legacy GCN GPUs and modern Vega cards receive an additional extension. The _model_specific_patches_extended function (lines 109-116 in amd_vega.py) installs:

• AMDRadeonX5000HWServices.kext — Enables support for mixed legacy and modern AMD GPU configurations, such as a Mac Pro 6,1 using an external Vega eGPU alongside an internal legacy graphics card.

Framebuffer Version Resolution

The AMDRadeonX5000.kext contains its own framebuffer implementation, which changed significantly after macOS 12 Monterey. OCLP selects the correct version using the _resolve_monterey_framebuffers() helper function defined in oclp_mod/sys_patch/patchsets/hardware/base.py (lines 153-171).

macOS Version to Framebuffer Mapping

The function maps kernel versions (xnu) to specific pre-built framebuffer folders:

• macOS 12 Monterey (xnu < 22) — Uses the 12.5 folder containing the original Monterey framebuffer.
• macOS 13 Ventura (22 ≤ xnu < 23) — Uses the 12.5-25 folder ("Tahoe" build) to match Ventura's new framebuffer layout.
• macOS 14 Sonoma early (xnu < 23.4) — Uses the 12.5-23 folder for Ventura-compatible framebuffers on early Sonoma builds.
• macOS 14.4+ Sonoma (xnu ≥ 23.4) — Uses the 12.5-23.4 folder for the latest Sonoma framebuffer requirements.
• macOS > Sonoma (future xnu) — Falls back to 12.5-23.4 until newer framebuffer folders are added to the patchset.

Patch Activation Requirements

The AMD Vega patchset activates only when specific hardware and software conditions are met:

1. GPU Detection — A Vega GPU must be present in the system.
2. CPU Capability Check — The system CPU must not provide AVX2.0 instructions, necessitating the legacy driver stack.
3. Installation Target — All listed kexts and bundles are copied to /System/Library/Extensions on the system volume.

Summary

• OCLP installs six core AMD Radeon X5000 extensions plus an optional hardware services kext for mixed-GPU setups.
• The correct framebuffer version is selected automatically based on the target macOS kernel version using _resolve_monterey_framebuffers().
• These patches specifically target Macs with AMD Vega GPUs but without AVX2.0 CPU support, restoring acceleration on macOS 13 Ventura and later.

Frequently Asked Questions

What specific kexts does OCLP install for AMD Vega support?

OCLP installs AMDRadeonX5000.kext, AMDRadeonVADriver2.bundle, AMDRadeonX5000GLDriver.bundle, AMDRadeonX5000MTLDriver.bundle, AMDRadeonX5000Shared.bundle, and AMDShared.bundle. If a legacy GCN GPU is also present, it additionally installs AMDRadeonX5000HWServices.kext to handle mixed configurations.

How does the framebuffer version selection work?

The selection logic resides in base.py within the _resolve_monterey_framebuffers() function. It examines the target macOS kernel version (xnu) and returns a specific folder name (such as 12.5-23.4) that corresponds to the correct Monterey-derived framebuffer for that OS version.

Why is the AMDRadeonX5000HWServices.kext patch needed?

This extended patch is required when a Mac contains both a legacy AMD GCN GPU (like those in Mac Pro 6,1) and a modern Vega GPU (such as an eGPU). The kext provides necessary hardware services to support simultaneous operation of both graphics architectures.

Which macOS versions are supported with these Vega patches?

The patchset supports macOS 12 Monterey through macOS 14 Sonoma (including 14.4+), with framebuffer folders specifically tailored for each major version. Future macOS versions fallback to the latest available framebuffer (12.5-23.4) until the patchset is updated.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}