Contribute
Register

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

Can confirm the Apollo Twin MKII Quad is fully working using the Apple's TB3 to TB2 adapter + Thunderbolt Cable, thanks to everyone involved in this solution!


There's another problem that has been bugging me tho. I've faced a black screen (nothing will respond, not even the audio interface) during normal use, one time was when the screen turned off due inactivity, one time when i was using youtube, and one time when i was working on Ableton Live, the computer will show a white screen and then turned into black, any idea why is this happening?
These kinds of problems are the most difficult to diagnose. We generally start with a broad analysis and then attempt to home in on the cause should we get lucky and stumble upon some effective clues.

Broad analysis:
  • Compare your CLOVER folder against everything in the spoiler marked Final Steps in Post-Installation. Look at every file, every checkbox, every copy-and-paste step, every ACPI patch, every item in Devices —> Properties, etc.
  • Recheck all BIOS parameters. Make sure you’re still on F6.
  • If you’re running 10.14.5, remove all Vega fan and power control solutions. All of them. Let macOS manage the GPU entire by itself. Also remove “device-id” from Devices —> Properties. And set AAPL,ig-platform-id to 0x3E980003 in reverse byte order (you would enter: 0300983E).
  • Update your CLOVER/kexts/Other and /Library/Extensions folder with latest versions of:
    • AppleALC
    • WhateverGreen
    • Lilu
  • After copying new files into /Library/Extensions, run Kext Utility to rebuild the kernel cache. This is mandatory.
  • Use iStat Menus or Intel Power Gadget to monitor system temperature. Make sure fans are physically spinning and system is not overheating.
  • Run Memtest to check that all memory DIMMs are okay. Google “Memtest for MacOS”.
  • What is the wattage of your power supply? If you have smaller than 750W supply, connect a power meter such as the low cost “Kill-A-Watt” to monitor power draw. If it’s approaching the rated wattage of your power supply under load, it’s time to upgrade to a beefier power supply.
Narrow-Down Analysis:
  • Disconnect all USB and Thunderbolt devices except Keyboard and Mouse.
  • Is the system stable when playing YouTube video?
  • Is the system stable when using Ableton Live?
  • Is there an Nvidia GPU in the system? Is Windows installed on the system?
 
Thanks @CaseySJ , I have converted my W10 SSD from MBR to GPT about a month back or so. Before that I upgraded that SSD from W7 to 10 on the older box and then moved to already running HAC on Disignare, settled it (W10) on MBR for about 2 months and after seeing no issues (with the only application that I'm using under Windows) converted it to GPT. It was stable on MBR and ran without issues as a secondary OS to my High Sierra. The idea to get back to MBR came after reading about one of the W updates went wild and made some BIOS changes. I'm not sure if MBR would help here but it does seem to me that MBR is kind of more contained environment. I may be wrong though.
I expect to swap my NVMe drives around this afternoon. Currently macOS is in M2M and Windows in M2P. After moving Windows to M2M, I’ll see if the next feature release goes through smoothly without impairing the macOS EFI partition. If so, that would really be the way to go.
 
@CaseySJ I need some help. I purchased the same motherboard as yours and followed the instruction to create the USB and BIOS setting. But it kept rebooting at the 15-30 mins installation window. I tried it on both SSD and HDD, same issue. Here are few screenshots and the EFI.
Hello @dkshaq, at which step in the overall process are you encountering this problem? Please see list of steps here:
The Guide mentions up to 2 sudden restarts and 1 graceful restart at the end of the Mojave installer.
 
Thank you.
I'll give the USB SSDT guide a try and see how I go.
I'd also need to review the other SSDTs I downloaded from your guide and see if I need to modify them as 1) I have RX 570 and in slot 2 and 2) I have PCIEx Thunderbolt card and not built in one.
If you can attach Thunderbolt and USB-C devices normally, then the Thunderbolt SSDT is okay. But feel free to run IORegistryExplorer and select File —> Save As... and upload that file. It will allow me to confirm your Thunderbolt configuration.

Regarding RX570 in Slot 2, I am beginning to think that we should not use the SSDT at all with 10.14.5. And we can use “Devices —> Arbitrary” to inject information device properties so they appear in System Information —> PCI. This Guide shows the way.
 
Fantastic Guide. Up and running, still waiting on Wifi/Bluetooth from Amazon. (Really Amazon? Did it fall of the truck or something?) There was one point early on in the install where I couldn't boot from the USB. Cycling power got it through that. Install was flawless, 1 reboot, everything automatically completed. Still booting verbose for a week. I had 1 panic on a cold boot.

Video Codec stuff didn't work, but I'll sort it out later.
Good job. Regarding the video codec, we found that VDA Decoder (H.264) only works under the following conditions:
  • If headless platform ID is used, it will only work with sysdef iMac19,1
  • If non-headless platform ID is used, Final Cut and iMovie will crash, but VDA Decoder will work with any sysdef.
If you’re facing a different video codec problem, let us know...
 
This is not as ominous as it sounds. It primarily affects professional audio interfaces and their plug-ins.

Well. That's what I do with my Hack. Pro audio work. I've an UAD card, several pro audio interfaces, and tons of plug ins.
I also do some photo editing, but that doesn't worry me.
 
Well. That's what I do with my Hack. Pro audio work. I've an UAD card, several pro audio interfaces, and tons of plug ins.
I also do some photo editing, but that doesn't worry me.
Ah, that changes the calculation. However:
  • For the purposes of making a bootable backup, this should not be a problem because the same hardware will be used when booting from that backup.
  • For the purposes of changing sys-def or using Migration Assistant to move to an entirely new machine, perhaps past experience can be a guide. For example, when these plug-ins and their host applications were installed on this machine, were brand new licenses used or previous licenses were transferred? If transferred, what was that process like?
 
Ah, that changes the calculation. However:
  • For the purposes of making a bootable backup, this should not be a problem because the same hardware will be used when booting from that backup.
  • For the purposes of changing sys-def or using Migration Assistant to move to an entirely new machine, perhaps past experience can be a guide. For example, when these plug-ins and their host applications were installed on this machine, were brand new licenses used or previous licenses were transferred? If transferred, what was that process like?
I upgraded from a Z68 to a Z170 3 years ago. I don't think I used the Migration Assistant, just adapted my EFI partition for my new Hack, I think.
It worked, but I had quite a bit of trouble before everything ran smoothly. Had to do with bugs in early BIOS versions and Clover, too much SSDT's, weird selections in config, and what not.

I also had to spend quite some time updating licenses, 90% worked or was easy to fix, but 10% gave me trouble and I had to get into contact with the companies who made them. Lots of mails and telephone calls. No fun.

I do migrations with real Macs on a regular basis using the Migration Assistant, and that definitely gives less trouble. Sounds a bit convoluted, though. Sad to think that people using cr*cked software will have no trouble with this.
 
Thanks @CaseySJ , I have converted my W10 SSD from MBR to GPT about a month back or so. Before that I upgraded that SSD from W7 to 10 on the older box and then moved to already running HAC on Disignare, settled it (W10) on MBR for about 2 months and after seeing no issues (with the only application that I'm using under Windows) converted it to GPT. It was stable on MBR and ran without issues as a secondary OS to my High Sierra. The idea to get back to MBR came after reading about one of the W updates went wild and made some BIOS changes. I'm not sure if MBR would help here but it does seem to me that MBR is kind of more contained environment. I may be wrong though.
I expect to swap my NVMe drives around this afternoon. Currently macOS is in M2M and Windows in M2P. After moving Windows to M2M, I’ll see if the next feature release goes through smoothly without impairing the macOS EFI partition. If so, that would really be the way to go.
Drives have been swapped. Currently on Windows 10 build 1809 and waiting for 1903. That will be the test of our theory that moving Windows to the M2M slot will prevent it from interfering with EFI partitions on other disks.
 
Back
Top