Legacy Hackintosh Installation Guide: Snow Leopard to Yosemite (10.6-10.10)

Installing macOS on a custom PC from the Snow Leopard through Yosemite era follows a different set of rules than modern Hackintosh builds. The boot architecture, kext loading mechanisms, and PCI device enumeration changed substantially between 10.6 and 10.10, so one recipe rarely works across the entire range. This guide walks through the common steps that apply to most legacy installations, highlighting version-specific pitfalls and the critical principle of verifying every component before writing anything to disk.

Prerequisites and Hardware Compatibility

Before touching a USB drive, confirm that your motherboard chipset, CPU, and GPU are supported by the target macOS version. For 10.6–10.8, Core 2 Duo and first-generation Core i-series processors with Intel GMA 950, GMA X3100, or NVIDIA GeForce 8/9 series GPUs are the safest choices. For 10.9–10.10, Ivy Bridge and Haswell CPUs with integrated HD Graphics 4000/4600 or NVIDIA GeForce 600/700 series discrete cards work well. A detailed compatibility check for NVIDIA GPUs is available in the NVIDIA GeForce 8 Series Hackintosh Guide.

You will need a legitimate copy of the macOS installer—either from the Mac App Store or a physical retail disc. Piracy introduces risks of corrupted files and modified kernel extensions that can silently damage your installation. Keep a backup of your current system and any important data on a separate drive.

Preparing the Installer USB

On a real Mac or a working Hackintosh, download the installer from the App Store and run the following command to create a bootable USB drive (replace MyVolume with your drive’s name):

sudo /Applications/Install macOS Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume --applicationpath /Applications/Install macOS Mavericks.app

For Snow Leopard (10.6), you must restore the DMG directly using Disk Utility’s “Restore” function because the createinstallmedia tool did not exist yet. Always use a 8 GB or larger USB 2.0 drive—USB 3.0 controllers often cause boot failures on legacy firmware without additional kexts.

BIOS/UEFI Configuration

Enter the BIOS and set the SATA controller to AHCI mode. Disable Secure Boot, Fast Boot, and any legacy USB legacy support options that might interfere with keyboard detection. For systems using a discrete GPU, set the primary display adapter to PEG/PCIe. If your motherboard has a UEFI firmware (most 2012+ boards), disable CSM (Compatibility Support Module) for 10.9+ installs, but enable it for 10.6–10.8 because those versions expect a legacy BIOS boot path.

Booting the Installer

Insert the USB drive and boot from it. At the bootloader prompt, add the following boot flags for your first attempt:

• -v (verbose) – shows kernel messages; essential for diagnosing hangs.
• kext-dev-mode=1 – required for 10.9–10.10 to load unsigned kexts.
• npci=0x2000 – avoids PCI configuration stalls on many LGA 1155/1150 boards.
• GraphicsEnabler=No – disables the bootloader’s automatic GPU injection; use only if you suspect framebuffer issues.

If the installer kernel panics, note the panic string and search for it in the Hackintosh community archives. Common causes include unsupported CPU power management (missing ssdtPRGen data), incompatible SATA controller, or a mismatched SMBIOS setting.

Post-Installation: Bootloader and Kexts

After the installer completes, boot from the same USB drive again but select the newly installed volume. Once inside macOS, install the bootloader to the system drive. For 10.6–10.8, run Chameleon Wizard to install Enoch to the EFI partition (or the root partition if using MBR). For 10.9–10.10, use Clover Configurator to mount the EFI partition and copy the Clover package.

Essential kexts to place in /EFI/CLOVER/kexts/Other (or /Extra/Extensions for Chameleon):

• FakeSMC (mandatory) – without it, the kernel refuses to load.
• NullCPUPowerManagement – disables Apple’s native CPU power management if your board lacks UEFI firmware tables; use only as a diagnostic step.
• RealtekRTL8111 or AppleIntelE1000 – for wired Ethernet.
• VoodooHDA or AppleHDA patched – for audio.

At this stage, the system will likely boot with basic VESA graphics. To enable hardware acceleration, you must inject the correct framebuffer for your GPU. Refer to the Decoding a 2014 Hackintosh Screenshot article for a practical example of diagnosing Intel HD Graphics on Yosemite.

First Boot and Diagnostics

Boot the system without the USB installer. If it hangs, reboot with the -x (safe mode) flag to bypass non-essential kexts. Once you reach the desktop, immediately check the System Information app:

• Verify that the SATA controller shows up under “SATA/SATA Express”.
• Check that Ethernet has a valid MAC address and an IP address via DHCP.
• Open the Console app and filter for “kernel” to spot any recurring IOKit errors.

If sleep does not work, the most common cause on legacy builds is a missing ACPI patch for the SATA controller. The SATA Hot Swapping on Legacy Hackintosh guide explains how to modify the DSDT to enable proper power state transitions.

Troubleshooting Common Issues

Stuck at “PCI Configuration Begin” – Add npci=0x2000 or npci=0x3000 to the boot flags. If that fails, try dart=0 to disable VT-d.

Kernel panic on “AppleIntelCPUPowerManagement” – Place NullCPUPowerManagement.kext in the kexts folder, then generate a custom SSDT using ssdtPRGen to eventually remove the dummy kext.

Graphics glitches or no acceleration – For NVIDIA GPUs, try GraphicsEnabler=Yes with PCIRootUID=1. For Intel HD, replace the injected ig-platform-id in Clover’s config.plist.

USB ports not working – On 10.7–10.10, inject the USBInjectAll.kext and set the XHCI hand-off to enabled in BIOS. For 10.6, USB 2.0 ports are usually fine, but USB 3.0 hubs require a third-party driver that is not recommended for production use.

After you confirm that network, audio, and graphics are functional, run a full disk verification with Disk Utility and create a backup of the EFI partition. This baseline configuration will serve as a recovery point for future upgrades or component swaps. Always keep the USB installer handy; it is the only way to re-enter the system if a kext mismatch prevents the bootloader from completing.