- Dec 26, 2015
- Asus ROG Strix Z370-F
- HD 630 + GT 710
- Classic Mac
Core i5-8400 + Asus ROG Strix Z370-F + iGPU
Core i5-8400 + Asus ROG Strix Z370-F + iGPU
Intel Core i5-8400 2.8GHz 6-Core Processor
Thermal Grizzly Kryonaut 1g 1g Thermal Paste
ASUS ROG STRIX Z370-F GAMING ATX Motherboard
Corsair Vengeance RGB 16GB (2 x 8GB) DDR4-3000 Memory
Samsung 950 PRO 256GB M.2-2280 Solid State Drive
NZXT S340 Elite (Black/Blue) ATX Mid Tower Case
EVGA SuperNOVA G3 550W 80+ Gold Certified Fully-Modular ATX Power Supply
NZXT Aer RGB120 (3-pack) 61.4 CFM 120mm Case Fans
I created this build as a direct replacement for my still-kicking Hackintosh NUC5i5RYK, focusing on the increase in compute power and aesthetics. There still isn't a lot of information out there about the best ways to implement RGB lighting when running a Hackintosh (or Linux for that matter) so hopefully this will answer some of those questions for those of you who have been wondering. Overall this was a successful build with the exception of Asus ROG 1220A audio, which I have not been able to get to work in 10.13.5. More on that later.
I used this excellent build log by Lepus48 as my starting place since I used the same motherboard in my build; I note a few specific instances where my process deviated below.
ASUS Memory Slot Placement: I ran into the same issue as as many others have with ASUS Z370 motherboards where the macOS installer halts at ‘End RandomSeed ++++...” just before memory allocation due to not being to identify the system RAM when it is placed in Slots 1 and 3 -- the ASUS-recommended placement (motherboard diagram A2, B2) when using two sticks of memory. You can resolve this issue by moving the memory to Slots 0 and 2 (A1, B1), or by editing config.plist and manually specifying the slot location, capacity, and mhz speed of your memory. The latter is required if you are using more than two memory sticks for macOS to see all 4 of them. Note that you will need to edit the SMBIOS section of your config.plist in the Clover EFI of your UniBeast USB installation media in order for your memory to be recognized by the installer, and then make the same edit to the config.plist of your Clover EFI on your internal macOS disk after MultiBeast setup in order to properly boot off of your OS disk. I attached the relevant section of my config.plist that allowed me to install successfully with my memory in slots A2, B2.
BIOS / UEFI Settings
- Advanced/Intel Virtualization Technology - Enabled
- Advanced/System Agent (SA) Configuration/VT-d - Disabled
- Advanced/System Agent (SA) Configuration/Graphics Configuration/Primary Display - CPU
- Advanced/USB Configuration/Legacy USB Support - Enabled
- Boot/CSM (Compatibility Support Module)/ Launch CSM - Disabled
- Boot/Secure Boot/ OS Type - Other OS
- AI Tweaker - Enabled XMP to get full RAM speed timings, and adjusted BCLK back down to 100.0 since Corsair set it to 103.0 in their XMP profile. Not necessary to install macOS.
- Follow the Tonymacx86 Installation guide to get the OS installed via the usual UniBeast-created USB installer thumb drive. No special steps required. Note: UniBeast installation media creation will fail if you have BitDefender installed with AutoPilot enabled; disabling AutoPilot resolves issue.
- Installer 2nd Stage note: On the second stage of the installation, after the first reboot when you boot from the internal drive to complete the installation process, the installer crashed for me within about 60 seconds, but I was able to complete the installation process by retrying the second stage (after the crash, again booting from the internal drive to restart the second stage of the installation). I've seen it reported elsewhere that others have encountered the same issue; and I tried installing with different BIOS settings several different times to avoid the crash without success. However, completing installation this way does not seem to have any negative effect on the resulting final OS install.
- Run MultiBeast post install, with
- Quick Start > UEFI Boot Mode
- Drivers > Audio > Realtek ALCxxx > 100 / 200 / 300 Series Audio Support*^
- Drivers > Audio > Realtek ALCxxx > 200 / Z370 Series / X299 Audio Device ID Patch*^
- Drivers > Misc > FakeSMC Plugins (only necessary for reading sensor data from motherboard within OS utilities)
- Drivers > Misc > FakeSMC HWMonitor Application (OS utility for reading motherboard sensor data)
- Drivers > Network > Intel > IntelMausiEthernet v2.4.0
- Customize > Graphics > Intel HD 6xx
- Customize > Graphics > Intel Graphics Fixup
- Bootloaders > Clover UEFI Boot Mode
- Customization > System Definitions > iMac > iMac 14,2
- Build - Confirm the above and Install
- Run MultiBeast again, with
- Drivers > Audio > Realtek ALCxxx > ALC1220A (ASUS ROG STRIX Only)*^ (see note below)
^Update: Audio now working by using the following steps:
200/Z370 Intel Motherboard Series
- Restart, boot off of internal disk EFI
- MultiBeast > Drivers > Audio > RealtekALCxxx:
- √ 100 / 200 / 300 Series Audio Support
- √ 200 / 300 Series / X299 Audio Device ID Patch
- MultiBeast > Drivers > Audio > RealtekALCxxx
- √ ALCxxx (Valid: ALC887/887B, ALC892, ALC1150, ALC1220, ALC1220A)
Tweaks / Other Notes
Multi-Monitor: Booting with multiple monitors on the iGPU (one on HDMI, one on DisplayPort) caused display garbling / GUI artifacts for me on 10.13.5. If you boot with just the HDMI or DisplayPort plugged in by itself, and then plug the other monitor in after you've logged in, multi-monitor seems to work without issue. This is inconvenient but works -- this is a machine that I basically keep on all the time so it's less of a hassle for me, but if anyone has any experience with this issue please let me know.
Sleep: Sleep works perfectly out of the box on this system with a single monitor, but results in blank screen and failure to wake up with multi monitor on the igpu. Still working on way to resolve this.
USB: All USB ports on my motherboard, including USB 3.0 and USB-C 3.1, seem to work out of the box in 10.13.5.
RGB Lighting Compatibility
Most RGB parts on the market today require the use of Windows-only utility software to set the color and lighting mode effects, and a significant proportion of them immediately revert to default colors or rainbow patterns as soon as you logout of Windows or reboot. However, some kits will ‘remember’ color profiles set in Windows in local storage on the device and retain those settings after you reboot. So, although it requires having a separate partition or hard drive with Windows installed to initially set color profiles or change them later, it is possible to use custom RGB color profiles within macOS. The specific kits I used for this build are:
1. NZXT Hue+ Lighting Controller: Colors/modes applied via NZXT’s CAM utility to connected AER RGB fans and Hue RGB Strips are stored in the lighting controller and persist after reboot into macOS.
2. Corsair Vengeance RGB Memory: Single fixed color applied via Corsair Link utility persist after reboot. (The other popular RGB memory kit right now, G.Skill Trident RGB, does not remember its color settings outside of Windows.)
3. Asus ROG Strix Z370-F Motherboard: Single fixed color applied to the onboard lighting using the Asus Aura utility persist after reboot.
Once you set the colors in Windows, they will persist in macOS through reboot and shutdown. If the computer is unplugged from the wall or the power supply is switched off, the colors will revert to default until your next trip to Windows.
- Custom RGB Lighting Settings (persist from Windows settings)
- HWSensors (some motherboard fan locations not registering)
- USB (all ports, including USB type C)
- Multi-Monitor issues (requires plugging in after bootup, causes issue with Sleep)
Geenbench 4: 5465 Single / 20333 Multicore
Verified during benchmark that Core i5-8400 hit its top turbo level (4.0 Ghz).
- config.plist RAM fix example for slots A2, B2
- Geekbench 4 Results