Guide 226: ACPI Fixes for Sandy Bridge and Haswell Hackintosh

A technical retrospective on Guide 226, a community resource for ACPI patching on Sandy Bridge and Haswell Hackintosh systems, with sleep and audio fixes.

Guide 226 first appeared on the InsanelyMac forums in late 2016 as a structured approach to ACPI patching for two distinct CPU generations: Sandy Bridge (2nd) and Haswell (4th). Its revision number, 2.2.6, indicated the guide’s maturity and the two-part structure covering both desktop and HEDT platforms. The “4” in the original filename referred to the four motherboard chipsets officially supported: Z68, Z77, Z87, and Z97. This article examines the guide’s methodology, its relevance to modern legacy installations, and the specific fixes it addressed for sleep, audio, and USB stability.

Background: Why Sandy Bridge and Haswell?

Both generations share a common ACPI challenge: incomplete DSDT tables from motherboard manufacturers that break macOS power management. Sandy Bridge systems often suffer from immediate wake (S3->S0) due to missing _PRW methods, while Haswell boards require patching of _PTS and _WAK to prevent kernel panics on sleep. Guide 226 consolidated these fixes into a single reference, using SSDT overlays rather than modifying the DSDT directly. This approach reduced the risk of bricking the firmware and allowed users to switch between macOS versions without re-patching the entire table.

Hardware Requirements

The guide explicitly listed compatible chipset families and recommended CPU models. According to the original thread, the following boards were verified:

  • Z68: ASUS P8Z68-V PRO, Gigabyte GA-Z68X-UD3H-B3
  • Z77: ASUS P8Z77-V, Gigabyte GA-Z77X-UD5H
  • Z87: ASUS Z87-Pro, Gigabyte GA-Z87X-UD3H
  • Z97: ASUS Z97-A, Gigabyte GA-Z97X-UD5H-BK

For CPUs, the guide advised using i5-2500K or i7-2600K for Sandy Bridge, and i5-4670K or i7-4770K for Haswell. Integrated graphics (HD 3000/4000/4600) were supported only with the correct framebuffer patching, which Guide 226 included as an appendix. Dedicated GPUs like the GeForce GTX 660 (Kepler) required no additional ACPI work, but the guide cautioned that NVIDIA Web Drivers for Sierra were mandatory for Fermi cards.

Key ACPI Patches

The core of Guide 226 consisted of three SSDTs:

  1. SSDT-UIAC.aml – Enables USB port limit breaking for macOS Sierra and High Sierra. Without this, systems with more than 15 USB ports would lose connectivity after sleep. The guide provided a sample config for Z77 and Z87 chipsets.
  2. SSDT-PRW.aml – Renames _PRW methods to prevent false wake signals from USB devices. This patch was critical for Sandy Bridge systems where the DSDT often listed USB 2.0 ports as wake sources.
  3. SSDT-PTS.aml – Corrects the _PTS (Prepare To Sleep) method to avoid hangs on Haswell boards. The guide included a patch that reassigned sleep states and disabled the S4 capability, which often caused kernel panics on Z87 chipsets.

Additionally, the guide provided a detailed Clover config.plist example with the necessary ACPI patches, sorted by generation. Users were instructed to place the SSDTs in /EFI/CLOVER/ACPI/patched/ and enable the corresponding drop tables in the bootloader.

Audio Patching and Realtek

Audio was a secondary focus of the guide. Many Z68 and Z87 boards feature Realtek ALC892 or ALC1150 codecs. Guide 226 recommended using the AppleALC kext with the correct layout-id (1, 2, or 3 for ALC892). However, the community later discovered that on some Z77 boards, the layout-id needed to be injected via the SSDT rather than the bootloader. This nuance was documented in a separate article on Fixing Realtek Audio on Legacy Hackintosh: Sierra and High Sierra Guide, which expanded on the static hiss and sleep-wake audio drop issues.

For users running Sierra 10.12.5 or later, Guide 226 also advised disabling the AudioDxe driver in Clover to avoid boot delays. This was a simple but often overlooked step that improved reliability on Haswell systems.

Risks and Precautions

Despite its thoroughness, Guide 226 had several limitations. First, the SSDTs were not one-size-fits-all; motherboard-specific differences in IRQ assignments could cause boot failures. The guide explicitly warned users to verify the DSDT with a hex editor before applying the patches. Second, the _PTS fix for Haswell sometimes interfered with the system’s ability to enter S3 sleep on certain Gigabyte boards, requiring a custom SSDT-PTS descendant. Third, the guide did not cover systems with Thunderbolt add-in cards, which require additional ACPI routing. For those configurations, the Legacy Hackintosh Guide: Ivy Bridge, Haswell, Broadwell-E, and Thunderbolt 2 Fixes provides a more targeted approach.

Data loss risks were present if the SSDTs caused a kernel panic during an active write operation. The guide recommended testing the patches on a cloned installation first, using a temporary bootable USB. It also advised disabling the “Restart After Sleep” preference in Energy Saver until the patches were confirmed stable.

Network and Ethernet Considerations

Ethernet drivers were not part of Guide 226’s scope, but the guide noted that Realtek RTL8111/8168 chips required the RealtekRTL8111 kext, while Intel I217-V needed the IntelMausiEthernet kext. These kexts had to be injected before the ACPI patches were applied, because a failed network initialization could mask ACPI errors. The guide recommended using a USB-to-Ethernet adapter as a fallback during testing.

Adapting the Guide for Modern Systems

While the original guide targeted macOS Sierra (10.12) and High Sierra (10.13), the SSDT structure remains valid for older versions like El Capitan and older. For macOS Mojave, the _PRW patch sometimes causes a loop on systems with USB 3.0 hubs; the workaround is to replace SSDT-PRW with a rename table that only targets specific devices. Guide 226’s repository was last updated in early 2017, but the patches can still be extracted and reused with OpenCore by converting the SSDTs to the .aml format and adjusting the config.plist ACPI section.

Users who downloaded pre-built DMG images containing Guide 226’s patches should inspect the files thoroughly, as some unofficial distributions included modified SSDTs that introduced instability. The article The Hidden Risks of Haswell DMG Hackintosh Images and How to Inspect Them Safely offers a verification workflow that applies to any third-party patched image.

A Final Implementation Note

Guide 226’s greatest strength was its modularity. By separating patches into individual SSDTs, it allowed users to enable or disable fixes without rebuilding the entire ACPI table. If you are still running a Sandy Bridge or Haswell Hackintosh, start by extracting your native DSDT with Clover’s F4 key, then compare the generated SSDTs against the guide’s sample files. Pay special attention to _PRW methods that list both USB and PCI devices; these are the most common sources of sleep failure. Once the SSDTs are in place, test sleep with a single sleeep/wake cycle before enabling auto-sleep. A successful test after three cycles indicates the patches are stable for daily use.