What’s Inside an X99 DMG Update? A Practical Guide for Hackintosh Builders

Background

An "X99 DMG Updated" is a purpose-built installer image for the Intel X99 platform — Haswell-E and Broadwell-E processors paired with the C612 chipset. The maintainer has revised it to fix recurring compatibility issues with legacy macOS versions. Unlike generic installer DMGs, these images bundle platform-specific patches, kexts, and bootloader configurations that address the quirks of X99. Apple never officially supported this architecture beyond the Mac Pro (Late 2013), but it became a popular Hackintosh foundation because of its core count and PCIe lane flexibility.

When a maintainer updates such a DMG, they’ve usually incorporated newer kext versions, adjusted ACPI tables for a broader range of X99 motherboard revisions, or worked around an incompatibility introduced by a macOS security update. The goal is a drop-in solution that boots an installer — typically macOS 10.12 Sierra through 10.15 Catalina — on an X99 board with minimal tinkering.

Typical Contents of an X99 DMG Update

An updated DMG is more than a macOS installation image. It’s a complete toolset for the X99 architecture. Inside you’ll commonly find:

• Bootloader — Clover (usually r51xx or later for APFS support) or OpenCore (0.5.x to 0.6.x for older macOS). The EFI folder comes preconfigured with the correct UEFI drivers (ApfsDriverLoader, HfsPlus, VBoxHfs, etc.) and a config.plist tailored for X99.
• Kexts — Lilu.kext and WhateverGreen.kext for graphics patching, AppleALC.kext for onboard audio (ALC1150, ALC1220 layouts common on X99 boards), USBInjectAll.kext or XHCI-unsupported.kext for USB port recognition, SmallTreeIntel82576.kext or IntelMausiEthernet.kext for Ethernet, and NVMeFix.kext if NVMe drives are present.
• ACPI patches — At minimum a SSDT-EC.aml to fake the Embedded Controller (required for macOS 10.13+), a SSDT-PLUG.aml for CPU power management (usually based on the PluginType method in Clover or the plist in OpenCore), and a SSDT-USBX.aml to provide USB power properties. Many updated DMGs also include a custom SSDT-X99.aml that combines fixes for the RTC, XHCI, and HPET devices.
• Boot args and kernel patches — Pre-applied boot arguments (e.g., -v, darkwake=0, npci=0x2000) and kernel patches for X99’s XCPM power management, ACPI errors, and memory map issues.

Key Patches and Configurations Specific to X99

What sets an updated X99 DMG apart from a generic one is how it handles the platform’s known trouble spots.

CPU Power Management (XCPM and SSDT)

Haswell-E and Broadwell-E processors depend on the XNU CPU Power Management (XCPM) subsystem. macOS expects this to be enabled by an ACPI PluginType property on the CPU0 device. Without a correctly generated SSDT-PLUG.aml, the system may reboot during idle or fail to wake from sleep. The common pitfalls in CPU power management SSDT creation — discussed in our earlier breakdown of SSDT screenshots — apply directly here. Many X99 DMG updates correct the ACPI path or method signatures that earlier guides often got wrong.

USB Port Limit and XHCI

X99’s XHCI controller usually maps more ports than the 15-port limit macOS enforces. An updated DMG will include a USBPorts.kext or a config.plist with a port limit patch (e.g., AppleUSBXHCI kext patch for 10.13.x). The June Q&A session on ACPI patches, USB mapping, and sleep fixes covers many of the same quirks that appear on X99 — especially the need to inject USB properties via SSDT-USBX or a custom DSDT edit.

Audio and Ethernet

Audio codecs on X99 boards are often ALC1150 or ALC1220. The DMG update will specify the correct alcid=xxx boot argument and verify that AppleALC.kext is built with the appropriate codec layout. Ethernet controllers on X99 are typically Intel I210, I211, or I217; the chosen kext (IntelMausiEthernet for newer, SmallTreeIntel82576 for older) must match the kernel version in the DMG.

Verifying an Updated X99 DMG Before Use

These DMGs circulate through forums and personal repositories, so treat each new update as a potentially untrusted payload. Before writing the image to a USB drive or transferring it to an existing EFI partition, run through these checks:

1. Checksum validation — Compare the SHA-256 hash of the DMG against the value published by the maintainer. If no hash is provided, ask for one or generate your own and compare over a trusted channel.
2. Inspect the EFI folder — Mount the DMG without booting from it, then examine the EFI/OC or EFI/CLOVER folder. Verify that kexts are from known sources (e.g., Acidanthera) and that the config.plist does not contain unknown boot arguments or unverified kernel patches.
3. Test on a dedicated drive — Never modify your primary macOS installation or EFI partition with an untested DMG. Use a separate USB drive or a spare SSD to confirm that the system boots, that sleep/wake works, and that audio and Ethernet function before copying anything to your main setup.
4. Back up current EFI — Before applying any changes from an updated DMG, create a full backup of your working EFI partition. A simple misconfiguration in the new DMG (e.g., a wrong DeviceProperties injection) can cause a boot loop that may require recovery.

Safe Testing Procedure

To minimise risk when evaluating an X99 DMG update, follow this isolated testing routine:

• Prepare a second USB flash drive (16 GB or larger) that contains the updated DMG written with dd or a tool like Etcher.
• Disconnect all storage devices except the test USB drive and, if needed, a single known-good SATA SSD formatted as macOS Extended (Journaled).
• Boot from the test USB and reach the macOS Recovery or Installer screen. If the system crashes during boot, note the panic string — common X99 panics include AppleIntelCFLGraphics (wrong ig-platform-id), AppleUSBXHCI (port limit), or IOConsoleUsers (GPU initialization).
• If the installer launches, open Terminal from Utilities and run ioreg -l to confirm that all expected ACPI tables (EC, PLUG, USBX) are loaded and that the CPU appears as AppleProcessor rather than ACPI_CPU.
• Perform a quick functional test: play a sound through the audio output, access a network share to verify Ethernet, and put the system to sleep briefly. If all three pass, the DMG update is likely safe to incorporate into your regular setup.

Before adopting an updated X99 DMG into your daily build, cross-reference the bundled kext versions against the official Acidanthera releases to ensure no unapproved modifications were introduced. A single outdated or patched kext can silently destabilise the system weeks after installation.