[SUCCESS] blouse's "Hack Pro" :: i9-9900K + Z390 Aorus Pro + Vega 64 + TB3 + USB3 :: 100% working

[blouse]

Huzzah, it's working all of a sudden...

After searching around, I found that it was likely memory releated, so I tried OsxAptioFix2Drv-64.efi, OsxAptioFixDrv-64.efi, OsxAptioFix3Drv-64.efi, OsxAptioFix2Drv-free2000.efi (all gave runtime errors) and finally back to the original AptioMemoryFix-64.efi... then it kicked and made it through the rest of the installer.

I guess I should have listened closer to myself: original instructions "don't be alarmed if the computer needs to restart a bunch of times".

 

[derJan]

Hello everyone,

I just built my very first Hackintosh with almost the same configuration. I'm using two Samsung 970 EVO 1TB M.2 to dual-boot Windows 10, 32GB (2x16) of Corsair Vengeance LPX and one Sapphire Vega 64 Nitro+.

The installation was without problems (and yes, it does restart a lot, I almost thought it didn't work) and with the iGPU fix macOS Mojave runs buttery smooth. Audio via USB and Ethernet is also working OOB.

What I can't get to (reliably) work is Sleep / Restart / Shutdown. It does what it's supposed to do about one in four times, but in between it goes into a weird state where the Motherboard and GPU RGB LED's stay on, the fans keep spinning, and nothing happens anymore. If I shut it off via the case switch and back on it is in a weird boot loop state where not even the BIOS screen appears. The monitor detects an HDMI signal, but the screen stays black and then the signal goes away again – at repeat. After cycling the power a few times it boots up again without any problems. Note that this does never happen when booting into and shutting down / restarting / sleeping from Windows 10 – only from macOS.

I tried to follow the iDiots guide to iMessage, but noticed that NVRAM doesn't seem to work. What is the current recommended way to get it enabled?

For the SSDT I enabled "plugin type" and used "plugin type 1" like recommended here but I don't think the 9900k turbos up to 5 GHz correctly. When running Cinebench Single CPU the Intel Power Gadget only shows a clock rate of 4,7 GHz. Is there anything else that needs to be enabled for the CPU to correctly turbo up to 5 GHz?

 

[blouse]

Did you use Emuvariableuefi and RC scripts or not? Means you checked native NVRAM? Did you manipulate config.plist on UniBeast for the initial install? Did you use Aptiomemoryfix? Could you post your config.plist without SMBIOS board identifier...

The only changes I made to config.plist straight out of Unibeast were:
System Parameters → Inject Kexts : Yes
Boot → slide = 0

No changes to the drivers64UEFI folder in the end. In kexts/Other, I added Lilu & Whatevergreen.

Note: These settings do not reflect my normal boot config

 

[blouse]

Do you set in BIOS all cores to 5ghz with voltage adaptions and so on? You need to set the bios correctly, plugintype just works according the turbo states reflected in BIOS...

I have found in my own case that in order to have a Turbo Boost functioning as expected (through HWP enabled support), I had to:

• disable MCE (Multicore Enhancement) in Gigabyte BIOS
• use the MacMini8,1 identifier in SMBIOS
• use Board-ID Mac-7BA5B2DFE22DDD8C

Following this, HWP was enabled and Turbo Boost works as advertised. By disabling MCE alone, my temps dropped by 10 degrees Celsius. By using MacMini8,1, I began taking advantage of HWP support native to the Mac-7BA5B2DFE22DDD8C board identifier (which uses an i7-8700k).

 

[derJan]

Did you use Emuvariableuefi and RC scripts or not? Means you checked native NVRAM? Did you manipulate config.plist on UniBeast for the initial install? Did you use Aptiomemoryfix? Could you post your config.plist without SMBIOS board identifier...

If I understand correctly the 9900K boosts up to 2 cores to 5 GHz without overclocking. It might be the Intel Power Gadget, if I check the CPU frequency in HWMonitor it shows 5 GHz. I assume it's working then

Usually there are test's available if your nvram is writebale or not. Normally Aptiomemoryfix is doing it, but depends you need emuvariableuefi and RC enabled, but worth to check...

For native NVRAM check this thread: https://www.tonymacx86.com/threads/native-nvram-available.192920/

Yes, I checked the NVRAM with the method described in the thread above. The test variable is gone after reboot. Can others with the Z390 Aorus Pro confirm that?

Did you use Emuvariableuefi and RC scripts or not? Means you checked native NVRAM? Did you manipulate config.plist on UniBeast for the initial install? Did you use Aptiomemoryfix? Could you post your config.plist without SMBIOS board identifier...

If I understand correctly I'm currently using AptioMemoryFix-64, but not EmuVariableUefi-64 (sorry, first Hackintosh, still leaning all the different things…). I can install EmuVariableUefi-64 from Install Drivers in Clover Configurator, but don't see an option for the RC scripts. Where can I get them, or do I need to re-install macOS for that?

 

[blouse]

It turns out yesterday I used the newest 10.14.2 image without realizing it. Everything now feels fine, if not better. Not sure what is better now because I have a clean install (minus all of the tweaking/learning I did getting it set up initially) vs what is better via the more recent macOS version.

Fixed the iGPU device-id to 0x3E92 (desktop) per @pastrychef's suggestion. Thanks @pastrychef. I was getting some random slow downs in some of my 3D apps, not anymore that I've noticed...

 

[derJan]

I have found in my own case that in order to have a Turbo Boost functioning as expected (through HWP enabled support), I had to:

• disable MCE (Multicore Enhancement) in Gigabyte BIOS
• use the MacMini8,1 identifier in SMBIOS
  
• use Board-ID Mac-7BA5B2DFE22DDD8C

Following this, HWP was enabled and Turbo Boost works as advertised. By disabling MCE alone, my temps dropped by 10 degrees Celsius. By using MacMini8,1, I began taking advantage of HWP support native to the Mac-7BA5B2DFE22DDD8C board identifier (which uses an i7-8700k).

Interesting, I don't see any changes to the CPU temperatures or Cinebench CPU scores with HWP enabled, MCE disabled and MacMini8,1 identifier.

Also, if I add EmuVariableUefi-64.kext macOS does not boot anymore, I get an "Couldn't allocate runtime area" error. Is there any other way to get NVRAM working?

 

[DenOfLore]

@blouse have been painstakingly getting this board to work. When I get home, I’ll upload and send you the working audio kexts. They’re descriptors AppleALC and has all ports working.

Also, I’d love to see your Geekbench scores comparing Mac Mini vs iMac18,3. The board UUID (serial #) generated has nothing to do with power management and everything to do with iTunes iCloud IMessage.

Also, run activity manager processor history to see how many threads are running. I bet you’re shutting your cores.

SMc helper and APTIOmemoryfix. The guides say different they are dirty liars. 3 days / or some 30 hrs to realize the old ways are the best ways.

 

[DenOfLore]

AppleALC with port layout for the ALC chip on the Aorus Master

if anyone wants to tinker with this here is the layout and Pin Configuration Chart

 

[blouse]

Thank you!! Wow, incredible.

Thank you, @DenOfLore