Hackintosh Compatibility on August 19, 2017: macOS High Sierra 10.13 Beta 6

By August 19, 2017, macOS High Sierra 10.13 beta 6 (build 17A344b) had been out for five days. The Hackintosh community had already learned that APFS conversion was mandatory for SSDs during installation, that Realtek RTL8111 Ethernet kexts broke under the new IONetworkingFamily, and that Pascal GeForce cards ran at 1024×768 with no hardware acceleration. For a typical Kaby Lake build on a Z270 board, these three issues defined the state of compatibility on that exact date. This article reconstructs the precise fixes and workarounds based on forum archives and release notes from the period.

The Core System: Kaby Lake on Z270 with 10.13 Beta 6

By mid-August 2017, the most common enthusiast build was an Intel Core i7-7700K on a Z270 motherboard (typically the Gigabyte GA-Z270X-Ultra Gaming or the ASUS ROG Maximus IX Hero) paired with a Radeon RX 580 or a GeForce GTX 1060. Beta 6 had been seeded on August 14, and it was the first beta where APFS conversion during installation became mandatory for SSDs — a change that caught many users off guard. If you had previously installed Sierra on an HFS+ volume and then upgraded to the High Sierra beta, the installer would convert the target drive to APFS automatically, and there was no supported rollback path without a full erase and restore from a Time Machine backup. Users who had dual-boot configurations with Windows on the same physical drive reported that the APFS container sometimes expanded into unallocated space after the conversion, corrupting the Windows partition's GPT table. The safest practice on that date was to install High Sierra on a dedicated SSD, disconnect all other drives during installation, and verify the partition layout with diskutil list before booting into the new system.

ACPI and Bootloader Stability

The transition from Sierra to High Sierra brought changes to the way macOS handled _PTS (Prepare To Sleep) and _WAK (Wake) ACPI methods. On many Z270 boards, the default DSDT contained a _PTS method that referenced the XHC device (USB 3.0 controller) in a way that caused a kernel panic on wake from sleep. The fix on August 19, 2017, was to apply a Clover ACPI patch that renamed _PTS to XPTS and provided a custom _PTS implementation that skipped the problematic USB controller code. This was documented in several forum threads, but the exact patch varied by motherboard vendor. For the Gigabyte Z270X-Ultra Gaming, the correct patch was:

Comment: Fix _PTS for Z270 Gigabyte
Find: 5F505453 01
Replace: 58505453 01

Without this patch, the machine would reboot or panic every time it attempted to enter S3 sleep. Users who had already applied similar patches for Sierra 10.12.4 often found that the same patch worked in the High Sierra beta, but the _WAK method also required a rename on some boards to prevent a five-second delay on wake. The combination of these two patches was the single most common fix applied during that week.

Ethernet: The Realtek RTL8111 Situation

High Sierra beta 6 shipped with a modified IONetworkingFamily that broke the then-current version of the RealtekRTL8111 kext (v2.2.1). The symptom was simple: the kext would load, the Ethernet interface would appear in System Preferences, but no DHCP lease would be obtained, and manual IP configuration resulted in a self-assigned 169.254.x.x address. The root cause was a change in the way the kernel handled the IOEthernetController::enablePacketFilters method. Mieze, the kext's developer, released a beta version (v2.2.2b1) on August 17 that addressed the issue, but it required manual installation into /Library/Extensions and a kext cache rebuild. Users who had not yet updated the kext were stuck without wired networking, which made downloading the fix itself a chicken-and-egg problem unless they had a secondary Ethernet adapter or Wi-Fi card that worked out of the box. The Broadcom BCM94360CS2 (the native Apple card used in 2013–2015 MacBook Airs) connected via a PCIe adapter was the recommended fallback — it required no kexts and worked with native Airport drivers in all High Sierra betas.

Graphics: The NVIDIA Web Driver Gap

If you were running a Pascal-based GeForce card (GTX 1060, 1070, 1080, or Titan Xp) on August 19, 2017, you were likely running at 1024×768 resolution without hardware acceleration. NVIDIA had not yet released a Web Driver for any High Sierra beta, and the built-in macOS GPU drivers did not support Pascal architecture. The first High Sierra–compatible Web Driver (version 378.10.10.10.10.101) would not appear until September 27, 2017, the day after the public release of 10.13.0. This left Pascal users with a choice: stay on Sierra 10.12.6, switch to an AMD GPU, or accept a non-accelerated display for the remaining six weeks. The Radeon RX 580, by contrast, worked with the native AMD9500Controller.kext in the beta, though some users reported green-screen glitches in the Photos app and during video playback in Safari — both traced to the new HEVC decoder not being fully initialized on Polaris GPUs. The workaround was to disable HEVC hardware decode in the Info.plist of AppleGVA.framework, a hack that broke iMovie export but fixed the green tint.

Audio: The AppleALC 1.1.3 Milestone

On the audio front, August 19, 2017, was a relatively good day. AppleALC 1.1.3 had been released on August 10, adding layout IDs for several Realtek ALC1220 and ALC1150 codecs that were common on Z270 and X299 motherboards. The kext worked with Lilu 1.2.0, and users reported that audio output via the rear 3.5mm jack functioned correctly after injecting the correct layout ID via Clover's Devices > Audio > Inject field. For the Gigabyte Z270X-Ultra Gaming (ALC1220), layout ID 1 worked for front and rear outputs, but the optical S/PDIF output remained silent unless layout ID 2 was used. The difference was in the Platforms.xml.zlib file inside AppleALC, which mapped different mixer paths. This was a known limitation that persisted until AppleALC 1.2.0 in November 2017.

USB and Bluetooth: The Port Limit Patch

High Sierra beta 6 introduced a stricter enforcement of the 15-port limit per USB controller. On Z270 chipsets, the Intel Sunrise Point PCH exposes two xHCI controllers (one for USB 3.0, one for USB 2.0), each with up to 16 physical ports. macOS would only recognize 15 ports per controller, so the 16th port (often the internal Bluetooth header or a front-panel USB-C port) would be ignored. The fix was to apply a Clover port-limit patch that disabled the port count check. The patch for High Sierra was different from the Sierra version because the kernel function that enforced the limit had moved. The correct binary patch for 10.13 beta 6 was:

Comment: USB port limit patch HS13 beta6
Name: com.apple.iokit.IOUSBHostFamily
Find: 83 FB 0F 0F 87
Replace: 83 FB 10 0F 87

After applying this patch, all 16 ports on each controller became available. Users who skipped this patch reported that their Bluetooth USB dongle (typically connected to an internal USB 2.0 header) would not be detected after sleep, and that USB 3.0 devices plugged into the 16th port would fall back to USB 2.0 speeds.

What Was Working (and What Was Not)

To give a concrete overview, here is the compatibility matrix as of August 19, 2017, for a typical Kaby Lake / Z270 / RX 580 build running High Sierra beta 6:

For users who were still on Sierra 10.12.6 on that date, the decision to upgrade to the High Sierra beta was a gamble. The APFS conversion alone was a one-way door — once you upgraded, you could not revert the boot drive to HFS+ without erasing it. Many experienced Hackintosh builders maintained a separate test SSD for the beta and kept their Sierra drive untouched. That practice, documented in the earlier guide on building a Hackintosh in May 2017 with Kaby Lake and Z270, remained the recommended approach through the entire beta cycle.

The X99 and X79 Edge Case

On August 19, 2017, users on X99 (Haswell-E / Broadwell-E) and X79 (Sandy Bridge-E / Ivy Bridge-E) platforms faced additional ACPI complexity. The High Sierra beta introduced a new requirement for the _DSM method on the X99 platform's PCIe root complex, without which the system would panic on boot with the error PCI configuration begin. The fix involved patching the SSDT-PCI.aml table to provide the missing _DSM for the RP01 through RP09 devices. This was a known issue that had been documented in the guide on fixing ACPI panics on X79/X99 Hackintosh for macOS High Sierra, and the same patches applied to the beta releases. Users who ignored that guide and attempted to boot the beta with an unpatched DSDT on X99 were greeted with a black screen and a repeating kernel panic — a showstopper that required booting from a USB installer to replace the ACPI tables.

Preserving the Configuration for Future Reference

On August 19, 2017, the smartest thing you could do was save your /EFI folder, DSDT dumps, and kextstat output. When High Sierra 10.13.0 shipped on September 25, those files were the quickest way to restore a working setup after the new GPU driver architecture broke several existing patches. Several forum users were already doing this, anticipating that future macOS updates might break their setup — a prescient habit, given that the final release required yet another round of ACPI and kext tweaks.