Building a Legacy Hackintosh: Component Selection Guide for macOS 10.6–10.13

Choosing components for a legacy Hackintosh is not like assembling a modern PC where the latest GPU and CPU guarantee support. Every version of macOS from 10.6 Snow Leopard through 10.13 High Sierra has a specific set of hardware requirements that change with each minor kernel revision. Without a road map, you waste money on a motherboard whose Ethernet controller was dropped in 10.11, or a GPU that works on Mavericks but panics on El Capitan. The only sane approach is to target a single macOS version from the start. The following steps outline how to choose components for that one version.

Start with the Target macOS Version

Before looking at CPUs or motherboards, decide which macOS version you need. The answer depends on software compatibility: audio production suites, legacy Adobe CS6, or pro video codecs that were broken after 10.12. Write down the exact build number (e.g., 10.10.5 build 14F27) and the supported hardware generation. Apple’s own Mac models for that era are your compatibility baseline. If a MacBookPro11,3 shipped with an Intel Broadwell CPU and an NVIDIA GeForce GT 750M, then a Broadwell CPU with Kepler or Maxwell GPU is a safe target. Anything newer — Skylake or Pascal — will require spoofing and patches that add instability.

Kernel Compatibility Constraints

Each macOS kernel (XNU) has a fixed set of CPU instructions it expects. Snow Leopard (32-bit kernel by default) supports Core 2 Duo and early Core i-series but not Ivy Bridge without a patched kernel. Mountain Lion dropped 32-bit kernel support entirely. High Sierra still boots on Sandy Bridge, but the kernel requires SSE4.2 — which means Core 2 Quad (Yorkfield) needs a kernel extension patch to avoid a panic at boot. Document these constraints before buying a single part.

Motherboard Selection and Chipset Road Map

The chipset determines which CPU generation, which SATA controller, and which onboard audio codec you can use. For a legacy build targeting macOS 10.10–10.13, the most documented chipsets are Intel Series 6 (H61, P67, Z68), Series 7 (B75, H77, Z77), and Series 8 (H81, B85, H87, Z87). Avoid X79 unless you have experience with DSDT patching for the C600 series controller — TRIM and sleep require extra work.

For the audio codec, ALC887, ALC892, and ALC1150 have stable AppleALC injection kexts for every macOS version from 10.8 onward. ALC269 and ALC282 are trickier on 10.9 and earlier. Check the codec ID against the AppleALC supported list before buying. If the board uses a Realtek ALC662, expect to use VoodooHDA instead — which introduces glitches on sleep/wake cycles.

Ethernet is the most common roadblock. Realtek RTL8111 variants are supported by the RealtekRTL8111 kext up to 10.13, but the RTL8169 and older RTL8139 need separate kexts that break on 10.12+. Intel I217-V and I210 work natively in 10.10–10.13 if you inject the correct device ID. Broadcom BCM57781 appears in many Gigabyte boards and requires no kext at all — it is the safest choice for a trouble-free network stack.

GPU Selection: The Narrowest Path

Graphics compatibility is the most version-dependent variable. A GPU that works flawlessly on Mavericks may show a black screen on Yosemite after the IOConsoleUsers change, or require an injected EDID on El Capitan. For a legacy road map, divide GPUs into three tiers:

• Tier 1 (native, no injection): NVIDIA Kepler (GT 640, GTX 650, GTX 660, GTX 680, GTX 770, GTX 780) — works on 10.8 through 10.13 without any web driver. AMD GCN 1.0 (HD 7750–7970, R9 270–280) works on 10.9 through 10.12 with some framebuffer patching.
• Tier 2 (web driver required): NVIDIA Maxwell (GTX 750, GTX 960, GTX 970, GTX 980) — requires NVIDIA Web Driver on 10.10–10.13. No support on 10.9 or earlier. Pascal (GTX 1050–1080) needs Web Driver and a boot flag nvda_drv=1; broken on 10.13.4+.
• Tier 3 (patched or unsupported): AMD Polaris (RX 460–580) works on 10.12.6 and 10.13 with WhateverGreen, but requires a board-id spoof and can fail on 10.11. Intel HD Graphics 4000 works on 10.8–10.13 but needs a framebuffer patch for HDMI audio and sleep.

For a single-target build, pick a Tier 1 card. The extra cost is offset by zero graphics debugging at boot.

Wireless and Bluetooth: Native vs. Patched

Wi-Fi and Bluetooth are often the last piece to stabilize. Broadcom BCM94360CS2 and BCM943602CS adapters connect natively with AirDrop, Handoff, and iMessage — they appear as genuine Apple hardware. The installation procedure for these cards on a desktop is covered in the BCM94360CS2 Hackintosh Guide: Native WiFi with Wireless 3 Cards. For older builds targeting Snow Leopard or Lion, a BCM943224HMS card with a patched IO80211Family.kext is the only reliable option.

Bluetooth wake from sleep is a recurring issue on legacy builds. The BCM2046 chip found in many Broadcom combo cards requires an ACPI wake method patch. Specific steps and SSDT modifications are documented in Wake a Legacy Hackintosh with Bluetooth: BCM2046 Patches and ACPI Fixes. Without these patches, the system may sleep but never wake via Bluetooth keyboard or mouse.

Storage and TRIM on Legacy Systems

SSD TRIM is not enabled by default on third-party drives in macOS. On 10.10 and earlier, the trimforce command does not exist — you must patch the IOAHCIBlockStorage.kext manually. On 10.11 and later, trimforce enable works but can cause kernel panics on certain Samsung 840 EVO drives with old firmware. For a detailed walkthrough of patching and verifying TRIM on older systems, see Fixing Storage Sleep and TRIM on Legacy Hackintosh Builds.

AHCI mode is mandatory. IDE emulation in the BIOS will prevent the installer from seeing the drive. Some legacy boards (G41, G31) have a buggy AHCI implementation that drops the drive after suspend — a known issue on Gigabyte GA-EP45-UD3P with macOS 10.6.8. If you use such a board, disable sleep or add a custom DSDT _WAK method.

ACPI and Bootloader: The Final Layer

Every legacy build needs a bootloader that can patch ACPI tables. Clover (r5122 or older for 10.13) is the standard choice because its config.plist allows per-version DSDT fixes. For a single-target build, you can minimize patches: only add FixShutdown, FixHPET, and FixRTC for most Intel chipsets. Avoid enabling all fixes in the ACPI section — unnecessary patches cause wake failures on 10.9 and 10.10.

If you target 10.6 or 10.7, Chameleon with a custom DSDT.aml is simpler and more stable than Clover. The DSDT must be extracted from the board’s BIOS using Ubuntu Live CD, patched with the MaciASL application, and placed in /Extra/. This approach is fragile — any BIOS update overwrites the DSDT — but it produces the most reliable sleep and CPU power management for those OS versions.

Validation Checklist Before First Boot

Before you install macOS, confirm each component against the target version:

• CPU: matches the kernel’s required instruction set (SSE4.1 for 10.9+, SSE4.2 for 10.11+)
• GPU: appears in the native driver database or has a working web driver for the exact OS build
• Ethernet: kext exists for the chipset AND the OS version (check the kext’s Info.plist for OSBundleRequired)
• Audio: codec is supported by AppleALC or VoodooHDA with a confirmed layout-id for that motherboard
• Storage: AHCI enabled, TRIM patched if needed, backup of existing data on a separate drive
• ACPI: DSDT extracted and patched for RTC and HPET, or Clover fixes selected

Boot the installer from a USB drive created with createinstallmedia on a real Mac or a working Hackintosh. If the installer panics on a missing kext, do not force the installation — diagnose the exact panic string. Common panics include AppleIntelCPUPowerManagement (add NullCPUPowerManagement.kext temporarily), AppleAHCIPort (check SATA mode), and IOConsoleUsers (inject -x flag for safe mode). Write down the working configuration after a successful boot and keep a copy of the EFI folder on a FAT32 partition for recovery.

After you've built and tested the system, create a backup of the EFI folder on a separate USB drive. Label it with the exact macOS build number and motherboard revision. That way, if a BIOS update or drive failure forces a rebuild, you can restore the exact configuration without re-diagnosing every kext.