X79 Hackintosh DMG Files: What’s Inside and Why You Should Inspect First

Enthusiast forums are full of files named X79_10.13.6_17G220.dmg or downloads x79 dmg 2. The number after the underscore usually points to a specific macOS build — most often High Sierra 10.13.6 (build 17G220) or, less frequently, Mojave 10.14.6. These aren't official Apple recovery media; they're pre-assembled disk images created by community members, meant to be restored onto a USB drive or directly to an SSD using dd or BalenaEtcher. The idea of a one-boot solution is tempting, but the contents of such an archive vary wildly depending on the author, the date of creation, and the exact hardware assumptions baked into the configuration.

What Is Typically Inside an X79 DMG

A well-maintained X79 DMG usually contains a standard macOS installation partition alongside a separate EFI System Partition (ESP) that holds the bootloader and kexts. The bootloader is almost always Clover, rarely OpenCore for these older builds. The EFI folder will include:

ACPI patches — SSDTs for CPU power management (ssdtPRGen-generated or hand-tuned for a specific Xeon E5 or Core i7-39xx/49xx) and a DSDT that may contain fixes for USB, RTC, and HPET. Many of these patches were originally written for Gigabyte GA-X79-UD3/UD5 or ASUS P9X79 boards.
Kexts — FakeSMC (or VirtualSMC in newer images), Lilu, WhateverGreen (for GPU compatibility), AppleALC (for onboard audio — often ALC898 or ALC892 on X79), and RealtekRTL8111.kext for the most common Ethernet controller on these boards.
Boot arguments — debug=0x100, keepsyms=1, npci=0x2000 (to avoid PCI configuration hangs), slide=0 or darkwake=0 depending on the sleep behavior the author observed.

Some images also ship with a patched AppleHDA.kext or a layout ID set in the config.plist — usually layout 1, 2, 3, or 7 for ALC898. If you are lucky, the DMG includes a PDF or a README.txt listing the exact hardware used during testing. If that file is missing, you are essentially flying blind.

What Is Almost Never Inside

The biggest gap in any pre-built X79 DMG is the lack of validation for your specific motherboard revision. An X79 board from ASRock, Gigabyte, ASUS, or EVGA all use different GPIO pinouts, different USB controllers (often a mix of Intel and ASMedia), and different BIOS ACPI tables. A DSDT patch that works flawlessly on a Gigabyte GA-X79-UP4 may cause a kernel panic on an ASUS P9X79 Deluxe because of conflicting SSDT-PM references. The same applies to Ethernet: while Realtek RTL8111 is the dominant controller, later revisions (e.g., RTL8111G vs. RTL8111E) require different pci-aspm-default settings or a different kext version. I covered the specifics of chip revision handling in detail in the article on Fixing Realtek RTL8111 Ethernet on Hackintosh High Sierra: Chip Revisions, Kexts, and ACPI Patches — the same principles apply here, but the DMG author may have only tested one revision.

Another missing piece is a working sleep/wake profile. X79 boards are notoriously picky about S3 sleep. The DMG may boot and run stably for days, but the first time the system enters sleep, it may never wake — or wake only after a hard reset. The SSDTs for _WAK and _PTS are highly board-specific. Most DMG creators do not document which ACPI patches they applied to fix sleep, or whether they tested it at all.

Risks of Using a Pre-Built DMG Without Verification

Restoring an unknown DMG to your main drive can overwrite your existing EFI partition, including any working Windows or Linux bootloaders. The image may contain a kextcache that was built with a different kernel version — restoring it to a system with a different build number can cause immediate boot failure. Worse, some archives are distributed with a modified boot.efi or a Clover version that is several years old and no longer receives security updates. If the DMG was created in 2018 and uses Clover r4640, you are inheriting all the bugs and vulnerabilities of that version.

There is also the question of integrity. DMG files are large (often 6–8 GB compressed). A corrupted download may not be detected until the restore fails mid-write. Always verify the SHA-256 checksum if the author provides one. If no checksum is posted, consider the image suspect.

How to Safely Inspect an X79 DMG Before Restoring

You can mount a DMG in macOS or Linux without restoring it to a disk. In macOS, double-clicking mounts it; in Linux, use dmg2img or 7z to extract the 2.hfs partition. Once mounted, examine the EFI folder:

Open the EFI partition (usually mounted at /Volumes/EFI).
Read config.plist in a plist editor. Check the SMBIOS — is it MacPro6,1 or iMac14,2? An X79 system should use MacPro6,1 for dual-GPU setups or iMac14,2 for single-GPU with good power management. Avoid MacBook SMBIOS — it will break CPU frequency scaling.
Look at the kexts/Other folder. Are there kexts for your specific GPU? For example, if you have an NVIDIA Kepler card, you need AGPMEnabler or NvidiaGraphicsFixup.kext (pre-WhateverGreen). If the DMG only has WhateverGreen but no Lilu, it will not load.
Check the ACPI/patched folder. If there is only one SSDT and it is named SSDT-1.aml, that is likely a generic CPU PM SSDT. For X79, you typically need at least two: SSDT-PM.aml and SSDT-USB.aml (or SSDT-X79.aml). A missing USB SSDT often causes Waiting for DSMOS hangs.

If the DMG passes these checks, you can restore it to a spare USB drive (not your main system drive) and attempt a test boot. This approach gives you a chance to capture boot logs via -v without risking your existing installation.

Building Your Own EFI Is Still the Safer Path

Even after inspecting a DMG, the safest long-term solution is to use the image only as a starting point — extract the EFI folder, discard the macOS installation partition, and build your own config.plist from scratch using the extracted kexts as a reference. The ACPI patches from the DMG may serve as a template, but you should regenerate SSDTs for your exact CPU using ssdtPRGen and create a custom USB SSDT with Hackintool or USBMap. For users encountering ACPI panics on X79, the dedicated guide on Fixing ACPI Panics on X79/X99 Hackintosh for macOS High Sierra walks through the most common AppleACPIPlatform errors and how to patch them at the DSDT level.

Before you even think about restoring that DMG, mount it and inspect the EFI folder. If the SMBIOS is set to MacBook or the ACPI folder is empty, stop right there. That image is not worth the risk. Use it as a reference for kexts and patches, but build your own EFI from scratch. The few hours you spend doing that will save you from a kernel panic that wipes out your weekend.