Installing Mac OS X 10.6–10.9 on a Custom PC: Hackintosh Guide for Sandy Bridge and Ivy Bridge

Installing Mac OS X 10.8 Mountain Lion on a Sandy Bridge system often hits a kernel panic during boot due to unsupported CPU power management. Apple's kernel expects specific ACPI tables and CPU P-states that most desktop motherboards lack. Before you see the installer, you need to align your bootloader and kernel patches with your hardware. This guide covers the essential steps for installing Mac OS X 10.6 through 10.9 on a custom PC, focusing on installer creation, bootloader selection, and post-installation validation to prevent data loss.

Prerequisites and Hardware Compatibility

Before writing any files, check that your components are supported by the target macOS version. For Mac OS X 10.6 (Snow Leopard) you need a 64‑bit Intel Core 2 Duo or newer. For 10.7–10.9, any Intel Core i3/i5/i7 of the Nehalem, Sandy Bridge, or Ivy Bridge generation works with the correct kernel patches. Avoid AMD processors unless you are prepared to use a modified kernel, which introduces instability and security risks. Graphics cards must be natively supported or have a known working kext; for example, Intel HD Graphics 3000 and 4000 require framebuffer injection and a compatible SMBIOS. For detailed graphics configuration, refer to the Intel HD Graphics Hackintosh Guide: Fixing Black Screen, Framebuffer Injection for Sandy Bridge to Haswell.

Back up all data on the target drive. The installation process will erase the partition you select. Even if you plan a dual‑boot, use a separate physical drive to avoid corrupting existing Windows or Linux installations.

Creating a Bootable Installer USB

You need a genuine Mac OS X installer – either from a purchased copy or a recovery partition. Obtain the InstallESD.dmg from the App Store (if you have a valid Apple ID with a previous purchase) or from a physical disc. The process differs slightly per version:

• Snow Leopard (10.6): Use Disk Utility to restore the DVD image to a 8 GB USB drive. Then apply the legacy kernel and a bootloader like Chameleon or Chimera.
• Lion / Mountain Lion (10.7–10.8): The InstallESD.dmg contains a BaseSystem.dmg and a Packages folder. Use the “createinstallmedia” command in Terminal (if available) or manually restore the BaseSystem and replace the Packages folder.
• Mavericks (10.9): The official method via createinstallmedia works, but you must add a bootloader manually after the command finishes.

After the base system is on the USB, install your chosen bootloader (Chameleon r2248 or later, or Chimera 2.0+ for 10.8). Copy the bootloader’s boot files to the root of the USB. For most legacy systems, installing Chameleon with the “Install to USB” option is sufficient.

Bootloader and Configuration

The bootloader must be able to inject the correct SMBIOS, enable kernel patches (e.g., cpus=1 for troubleshooting, or kext-dev-mode=1 for 10.9), and load the necessary kexts from /Extra/Extensions. Create a folder /Extra on the USB with an org.chameleon.Boot.plist (or boot.plist for Chimera). At minimum, specify:

<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>-v npci=0x2000</string>
<key>EthernetBuiltIn</key>
<string>Yes</string>
<key>Graphics Mode</key>
<string>1920x1080x32</string>

Adjust npci=0x2000 or npci=0x3000 based on your motherboard’s PCI configuration. Add cpus=1 if you encounter a kernel panic early in the boot process. For Ivy Bridge systems, you may need to add ssdt=1 or a custom SSDT to handle CPU power management. The process of creating a custom SSDT is covered in detail in the article Creating a Custom SSDT for Legacy Hackintosh LPC, SMBus, and GPIO Controllers.

Place any required kexts (e.g., FakeSMC.kext, NullCPUPowerManagement.kext for Sandy Bridge, or a patched AppleRTC.kext) in /Extra/Extensions and make sure the bootloader’s configuration includes <key>Kexts</key><array><string>Yes</string></array>.

Installation Process

Boot from the USB with the -v flag to watch for errors. The installer will load after a few minutes. Use Disk Utility from the menu bar to format the target partition as Mac OS Extended (Journaled) with GUID Partition Map. Proceed with the installation. The process may take 20–40 minutes depending on drive speed. When the installer finishes, the system will reboot. Do not attempt to boot from the target drive yet – boot again from the USB, and at the bootloader, select the newly installed volume.

Once the OS loads to the setup assistant, you have successfully completed the core installation. Do not configure iCloud or iMessage at this stage; that requires a valid SMBIOS and network configuration that you will finish later.

Post‑Installation Validation

After the setup assistant completes, install the bootloader to the target drive (e.g., run Chameleon’s installer again and select the system drive). Then copy the /Extra folder from the USB to the target drive’s root. Reboot without the USB to verify the system boots independently. Check the following:

• Audio: If your audio codec is not working, inject AppleHDA via a patched kext or use VoodooHDA (see our guide on VoodooHDA tuning).
• Ethernet: Verify that the built‑in network interface is recognized. If not, make sure the EthernetBuiltIn flag is set in boot.plist and that the correct kext is loaded.
• Graphics: Confirm that QE/CI is enabled. For Intel HD Graphics, refer to the framebuffer injection guide linked earlier. For NVIDIA GeForce 6/7 series, consult the GeForce 6 and 7 Series Hackintosh Guide: What Works and What Breaks.
• Sleep: Test sleep and wake. If the system sleeps but does not wake, you may need a custom SSDT or a USB fix.

Common Pitfalls and Risks

Installing Mac OS X on non‑Apple hardware is not officially supported. Every system update (even a minor point release) can break your installation. Always keep a backup of your /Extra folder and the bootloader. A failing kernel extension can cause a kernel panic that renders the system unbootable – have a bootable USB ready to recover. Do not attempt to install on a drive that contains important data without a verified backup.

If you encounter a cyclic reboot or a “Still waiting for root device” error, check your SATA configuration (set to AHCI in BIOS) and verify that the USB installer is plugged into a USB 2.0 port. For older boards, using a USB 3.0 port may cause the installer to freeze.

Finally, after everything is stable, create a disk image of the working system using Disk Utility. This allows you to restore the entire installation in minutes if something goes wrong during a future tweak. A single image file saved on an external drive is the most reliable safety net for a legacy Hackintosh.