Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

To surmount the "This Version of Mac OS X is not supported on this platform!" issue try booting with -no_compat_check
And sorry to ask but I don't see that as an argument when I right click in the boot arguments field. Should I just paste
-no_compat_check into an empty field?
 
With MSR unlocked, have you tried replacing OsxAptioFix2Drv-Free2000.efi with AptioMemoryFix-64.efi and removing slide=0?
No, but I don't think the problems with Aptio is related to MSR. I will give it a try anyway.
 
With MSR unlocked, have you tried replacing OsxAptioFix2Drv-Free2000.efi with AptioMemoryFix-64.efi and removing slide=0?

I too unlocked the MSR on the Designare mobo and ran the tests you ask about. Since unlocking the MSR, I've un-checked KernelPM (and AppleIntelCPUPM is also un-checked), and booting is fine.

I tried:
  • AptioMemoryFix-64.efi ± slide=0
  • AptioMemoryFix-64.efi + EmuVariableUefi-64.efi ± slide=0
All of the above won't boot (crossed circle).

I returned to OsxAptioFix2Drv-Free2000.efi + EmuVariableUefi-64.efi + slide=0, and all is well again.

ADDED 5/2019
When using OsxAptioFix2Drv-Free2000.efi + EmuVariableUefi-64.efi + slide=0, if BIOS is set to
"Auto" for "Enhanced Multi-Core Performance" (within MIT tab) computer won't boot (crossed circle). This value needs to be "Disabled".

***

BTW, on the ASRock Z390 Phantom Gaming ITX mobo, it appears that v1.6 BIOS is natively unlocked. While the Designare CFG Lock is at 0x5C1, the ASRock is at 0x5C4 and shows 0x00 if booted with Grub. (I did start a new thread but it's waiting on Moderator approval, and posted these results.) The ASRock works well with OsxAptioFix2Drv-Free2000.efi alone, but panic re-starts on AptioMemoryFix-64.efi alone, but is stable if EmuVariableUefi-64.efi is also present.
 
Last edited:
Hi, newbie to this mackintosh stuff and actually had someone help me install it so not totally familiar with the whole process.
Overall, the setup has been working. But, after I did migration assistant to move over some files and applications, I now have sound that will drop out after prolonged sleep; i.e., overnight. I get sound working normally with short periods of sleep--put it to sleep for 5s, 5 min, etc. It comes back normally after I reboot. It doesn't seem to do this in Windows.

Anyone else with similar problem or suggestion? Should try the fix suggested in post 4,319?
Thanks.
 
MacOS 10.14.5 has robust support for Vega 56, Vega 64, and Radeon VII. I'll add this statement to the build guide shortly, but for 10.14.5 we should not need to apply any fix whatsoever for these GPUs.

EDIT: Added the following statement in red to build guide:
View attachment 407091

OK cool I got it
deleted the Vega64 fan and power
however...
Im confused about the platform IDs specified under the 'Going the extra mile' chapter.
if i keep my iMac 19,1 SMBIOS and want iGPU in headless mode
where do i input that configuration under the 'devices' tab of config.plist?
am i missing a PciRoot under 'devices'?

I've attached screenshot

thank you Sir!
 

Attachments

  • Screenshot 2019-05-20 at 08.45.00.png
    Screenshot 2019-05-20 at 08.45.00.png
    196.8 KB · Views: 113
Ps Speed seems higher with 10.14.5
My Geekbench scores are a bit lower than yours (6290/34014) on 10.4.5, but my memory is only 2666Mhz...
What's your memory speed and do you have any BIOS memory/CPU optimisation or overclock ?
 
Is this build still relevant in May 2019? When you would build it today - would you take newer components? i9?
 
Some other suggestions:
  • When running MultiBeast 11.2.1 there is an option to install UEFI Bootloader + EmuVariable. This option installs "rc scripts" to aid in reboot and shutdown.

I can't believe that I got so careless. The whole time I was thinking I forgot something. RC Scripts did the trick, installed using the "normal" Clover installer though.

To disable the CFG Lock, we would need to write the value 0x0 to offset 0x5C1.

I can confirm 0x5C1 for Z390 Aorus Xtreme on BIOS Version F5, too. Nice that you made a tutorial, a little late for me, but I appreciate someone helping the newer generations. We have to apply that trick on every BIOS-Update, I suppose (unless settings are not reset, but I suppose that almost never happens).

I tried:
  • AptioMemoryFix-64.efi ± slide=0
  • AptioMemoryFix-64.efi + EmuVariableUefi-64.efi ± slide=0
All of the above won't boot (crossed circle).

For me both options work fine (and have worked fine even before CFG-Unlock), so I dumped the other memory fix quite early and turned to AptioMemoryFix. But without EmuVariableUefi sleep and shutdown get...let's say funny
 
Last edited:
Back
Top