Mountain Lion on Vintage Hardware: Storage, Bootloaders, and Kext Survival

When Mountain Lion refuses to see a hard disk on older hardware, the culprit is almost never the drive itself. It is the storage controller. LGA 775 and early LGA 1156 boards shipped with ICH7, ICH8, ICH9, and ICH10 chipsets, and OS X 10.8 expects those to present themselves in a specific AHCI or at least IDE configuration that matches what Apple's own firmware would expose. Leave the BIOS in legacy IDE mode and the installer either fails to locate any disk or hangs on the familiar "Still waiting for root device" line. The fix that works on the majority of boards is straightforward: switch SATA operation to AHCI before booting the installer. On the minority of boards where AHCI is missing entirely or the implementation is broken, a patched AppleAHCIPort.kext with the correct device IDs injected can sometimes get the drive recognized. Disk performance usually takes a hit, and hot-plug becomes a coin toss, but the machine boots. More Mountain Lion install attempts die at this single BIOS setting than at any missing DSDT.

Choosing a Bootloader: Chameleon vs. Clover on 10.8

For a pure Mountain Lion installation, Chameleon—and specifically its Enoch branch—is still the path of least resistance. Clover was maturing during the 10.8 era, and while modern Clover revisions can boot older systems, the configuration surface balloons quickly. Chameleon keeps things flat: /Extra/org.chameleon.Boot.plist handles GraphicsEnabler, EthernetBuiltIn, and GenerateCStates/PStates with a handful of keys that are easy to read and adjust. The AppleIntelCPUPowerManagement panic on unsupported CPUs disappears with a single NullCPUPowerManagement.kext dropped into /Extra/Extensions.

If Clover is the choice—perhaps to unify a multi-boot setup across several OS versions—stick to a legacy Clover installation paired with an older boot file that does not depend on UEFI runtime services. The safest configuration essentially tells Clover to emulate a Chameleon-style environment: disable KernelPm and set a FakeCPUID only when the actual CPU lacks SSE4.2, which certain XNU builds of Mountain Lion's kernel demand. Throwing unnecessary patches at a working CPU just adds instability.

Graphics Acceleration and the NVIDIA 8xxx–9xxx Series

Mountain Lion was the last release to ship with 32-bit kernel support, but its graphics drivers were already mid-transition toward 64-bit-only acceleration for newer GPU families. Cards like the GeForce 8800 GT, 9600 GT, and 9800 GTX+ can reach full QE/CI with minimal injection—provided the right NVDANV50Hal.kext and NVDAResman.kext actually load. The detail that trips people up is the IOPCIMatch string. If the GPU's device ID is absent from the stock kexts, GraphicsEnabler=Yes does nothing. The ID has to be added manually inside the kext's Info.plist, followed by a permissions repair and a kernel cache rebuild with kextcache -system-prelinked-kernel.

Older Fermi-based cards—the GeForce 4xx and 5xx series—sit in an awkward middle ground. They are partially supported but prone to OpenCL hangs that are hard to reproduce and harder to fix. The safer recommendation is to stay with the GeForce 9xxx series or jump to a Radeon HD 5770 or 5870. Those use the native AMD5000Controller and need only a framebuffer personality injection through Chameleon's AtiConfig key.

For users who have already worked through similar GPU diagnostics on other legacy builds, the principles described in Decoding the 2014-12-07 Hackintosh Screenshot: GPU Diagnostics in Yosemite apply here as well—the IORegistry and kextstat output reveal exactly which driver personalities are attaching to the card.

Audio: The VoodooHDA and AppleHDA Fork

Mountain Lion sits right on a fault line for audio support. Realtek ALC8xx codecs that worked with a patched AppleHDA under Lion frequently break in 10.8 because Apple restructured the layout and pathmap definitions. VoodooHDA 2.8.4 works as a fallback and gets sound out of the speakers, but the default gain levels can produce noticeable distortion, and the preference pane has a habit of forgetting output device selections between reboots.

A more precise fix involves pulling the codec verbs from a Linux dump and building a minimal Platforms.xml and layoutXX.xml pair for a stripped-down AppleHDA. It is tedious work, but the result is cleaner sound and native volume control that integrates with the system properly. The Legacy Hackintosh Ethernet and Audio: A Practical Guide for macOS 10.6–10.13 article walks through this verb extraction process in detail for the ALC889 and ALC892 codecs—two of the most common chips on X58 and P55 boards from that period.

ACPI and Sleep: Deep Idle Pitfalls

Sleep and wake on Mountain Lion with older hardware is fragile in ways that are hard to diagnose without a serial debugger. The OS expects a proper _WAK method that restores PCI configuration space, and many DSDTs from the Core 2 era simply omit the necessary register writes. A minimal DSDT patch for the LPC controller—injecting a compatible device ID that AppleLPC.kext recognizes—can enable native power management, but it also exposes deeper C-states that the board may not handle stably. The machine enters sleep correctly and then hangs on resume: black screen, or a USB controller that never comes back.

For a box that needs to stay up 24/7, the most reliable configuration is to disable sleep entirely in System Preferences, rely on display sleep alone, and keep DarkWake disabled in the boot arguments. If true S3 sleep is a requirement, the testing has to be methodical. Start with no USB devices attached at all. If that works, add the keyboard and mouse. Then networking. One peripheral at a time until the wake reason that triggers the hang reveals itself.

Ethernet Compatibility and the Realtek–Intel Divide

Two Ethernet controllers dominate the boards of this era: the Realtek RTL8111/8168 family and the Intel 82579V. The Realtek chips work out of the box with Mieze's updated RealtekRTL8111.kext, which fixes the intermittent link drops that plagued earlier versions under Mountain Lion's IPv6-heavy networking stack. The Intel 82579V is trickier. The stock AppleIntelE1000e.kext in 10.8 sometimes fails to negotiate gigabit speeds and falls back to 100 Mbps without any obvious indication beyond slow transfers. A manual duplex setting in Network preferences, combined with disabling Energy Efficient Ethernet in the kext's Info.plist, usually stabilizes the link.

Boards with Marvell 88E8056 chips have it worse. No native driver exists, and the aging skge.kext from the Snow Leopard era causes kernel panics under heavy UDP traffic. These boards are best paired with a PCIe gigabit adapter based on the RTL8111 chipset and the onboard Marvel controller disabled in BIOS.

Building the Installer Correctly

A common mistake is trying to create the Mountain Lion USB installer from a modern Mac or Hackintosh using the current createinstallmedia tool. The Mountain Lion InstallESD.dmg structure differs from later releases: the actual packages are hidden inside a Packages folder on the disk image, and the BaseSystem.dmg must be restored manually using Disk Utility's Restore function, then the Packages folder copied into the correct location afterward. Skipping this manual step produces a USB stick that boots but cannot complete the installation.

If the installer boots but the installation log shows "Can't verify Mac App Store receipt," the date needs to be set back to a point when Apple's signing certificate was still valid—typically any date in 2013 or 2014—via Terminal in the recovery environment. This is not an activation bypass. It is a simple timestamp validation that Apple's own offline installer performs, and it fails because the certificate has long since expired.

Post-Install: Security and the Modern Web

Browsing the web from Mountain Lion in any kind of production context is a calculated risk. The last security update for 10.8 shipped in 2015, and the built-in Safari cannot render many modern HTTPS sites correctly—expired root certificates and lack of TLS 1.3 support see to that. Firefox ESR 78 was the last major browser to offer partial compatibility, and even that requires manual certificate import for sites that use Let's Encrypt. The most practical use for a revived Mountain Lion machine is offline media work, legacy software testing, or as a dedicated box for audio production tools that were never updated for newer macOS versions. If network access is unavoidable, isolating the machine on a separate VLAN with no access to other trusted devices reduces the exposure to something manageable.

Before applying any post-install tweaks or experimenting with unsupported kexts, cloning the working installation to a spare drive gives an immediate rollback path. The method outlined in Safe Updates for Legacy Hackintosh: Testing on a Separate Drive describes a straightforward cloning workflow that avoids incremental corruption of the only bootable system.

Kext Cache and Permissions in 10.8

Mountain Lion uses a hybrid of the older Extensions.mkext and the newer prelinked kernel model. When adding or modifying kexts in /System/Library/Extensions, the order of operations matters. Run kextcache -system-prelinked-kernel first, then kextcache -system-caches. Reversing that order can trigger a race condition where the kernel loads a stale cache and silently ignores the updated kexts. The permissions repair step—chmod -R 755 and chown -R root:wheel on each modified kext—must happen before the cache rebuild. If it does not, the prelinked kernel skips the kext with a permissions error logged quietly to system.log.

The telltale symptom is a kext that shows up in kextstat but whose functionality is absent. Checking /var/log/system.log immediately after boot for "Kext rejected due to improper filesystem permissions" lines identifies exactly which kexts were dropped. When the system is fully configured, a final boot with -v kept in the Chameleon boot plist for at least three cold starts confirms that no kext load failures or ACPI errors appear intermittently. Only then does the verbose flag come off for daily use.