Contribute
Register

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

i tried to update one of my 2 machines from 10.14 to 10.4.4 ..... downloaded the update from appstore and then run the upgrade... but soething crashed ... better to do a complete new installation to 10.14.4 ?
i have the same 5 fans like Casey - how can i make them silent ? by now the are running on 100 % all ;-) and make a lot noise
Problem 1: crash during update.
Can you post a photo of the crash? Please enable verbose boot mode if it’s not already enabled. Depending on the nature of the crash we can decide whether it’s better to fix the problem or install 10.14.4 from afresh.

Problem 2: loud fans.
On my system the fans subside to a low hum that is still audible. I’ll see if I can apply a different fan curve in BIOS.
 
@itepfoto,

Good post, good advice!

Is your last bullet a thinly veiled cry for help? ;)
HA! I am going to use it for a few days before I start my post-post-post; make a list of anomalies (I see the Time Machine USB just improperly ejected by itself) and then plead for help ;)
 
... But I had to step away for a bit so I just quickly saved config.plist to desktop. When I came back, the computer had fallen asleep and on wake a circle with a line through it appeared.
Public service announcement: Something even worse happens when we use our smartphones while driving.

I rebooted, F12, selected the usb drive, then boot from Mojave. The system came back up, and that's where I am now. The EFI partition on my usb drive is gone. Is that expected behavior? Should I recreate the drive with Unibeast? Where do I need to save config.plist to?
Thanks in advance!
Let's see if we can get to the bottom of this:
  • Because you could boot from USB install disk by pressing F12, it proves that EFI partition on USB install disk is perfectly okay.
  • The EFI partition on your Mojave SSD should also be okay.
  • If you ran MultiBeast during Post-Installation, it installed Clover into the EFI partition of the Mojave SSD.
  • But the EFI partition is not automatically mounted by MacOS because this is supposed to be fully managed by MacOS on real Macs.
  • So we have to mount the EFI partition manually. There are several ways to do this, but probably the easiest is to use Clover Configurator because you should already have that downloaded and available. See image below for instructions:
    Screen Shot 2019-04-23 at 12.48.47 PM.png
  • Once you mount the EFI partition, you'll see an "EFI" disk icon on your desktop. If you don't see it, go to Finder --> Preferences and check this on:
    Screen Shot 2019-04-23 at 12.50.29 PM.png
  • Now you can open the EFI disk icon, and inside you'll find an EFI folder, and inside that you'll find the CLOVER folder.
  • During Post-Installation, you have to save your config.plist into this CLOVER folder.
  • If the CLOVER folder is already present, you don't have to run MultiBeast again. Instead, just repeat the steps in the spoiler Final Steps in Post-Installation.
 
UAD Apollo Thunderbolt 1 interfaces with FireWire connectors are confirmed to work over FireWire with the Designare with the two Apple adapters 'FireWire to Thunderbolt' and 'Thunderbolt 1/2 to Thunderbolt 3'.
So I guess that most FireWire devices that have their own power supply will work.

Of course buying a FireWire card is cheaper than buying the two adapters :-D But if you already have one of them (or both), it’s a good solution.
 
Now you can open the EFI disk icon, and inside you'll find an EFI folder, and inside that you'll find the CLOVER folder.
  • During Post-Installation, you have to save your config.plist into this CLOVER folder.
  • If the CLOVER folder is already present, you don't have to run MultiBeast again. Instead, just repeat the steps in the spoiler Final Steps in Post-Installation.

Thanks. That seems to have done it. Will post further if anything else comes up.
 
Followed the guide, and prior to the guide, I had removed the on-board WiFi module and installed Fenvi T919, it works great in Windows I tested it with an external SSD on Windows and was working in Mojave before I did the final steps of the guide. I get "The WiFi network BlahBlah requires a WPA2 password" This is after rebooting following the guide. Which kext should I check? Not sure where to troubleshoot what exactly is interfering from your guide with my Fenvi WiFi WPA2 password authentication. The driver is working and I can see WiFi networks i just can't join them anymore with a password. Hmm... How would WPA2 authentication get affected? strange. Console shows: IO80211AssociationJoinSnapshot::captureRequestCallback Problem reported from corecapture

UPDATE: its working. I have no idea, maybe just the flakey-ness of the WiFi ??? I was able to connect to my 5G wifi and authenticate, and then after a few reboots the regular 2.4G wifi in my house. Who knows. OK its not related to the install process. Even though I physically removed the motherboard's WiFi I do have the SSDT-DESIGNARE-Z390-NO-CNVW.aml copied to the CLOVER/ACPI/patched folder on the EFI partition of the Mojave SSD.

Maybe i rebooted so many times it messed with the Fenvi's chipset, next time i should unplug. False alarm.
 
Last edited:
Hello all!

First of all, thank you for this guide. I'm a first time Hackintosh builder and contemplating whether to jump into this ship.

I have one question about the WiFi/BT and the PCI-E module used here. I couldn't find the exact parts linked in the guide from amazon.de, but would these two work - at least in theory?

Adapter:

https://www.amazon.de/dp/B07GXHLK3N/?tag=tonymacx8603-21

WiFi/BT card:

https://www.amazon.de/dp/B07QJVNMJ8/?tag=tonymacx8603-21

Do all cards that have the label "BCM94360CS2" generally work? I've seen a lot of different companies selling cards that look exactly the same and I'm not sure if there's any differences. Some of them however have "Broadcom Corporation Ltd." printed on the card though, so in lack of any other measure of quality, I've chosen one of those.
 
Hey guy! For some reason my iMessage stopped working. It asks me login and after typing in my password it gives me "Could not sign in to iMessage. An error occurred during activation. Try again." Im still on 10.14.3. Any help would be appreciated!
 
Hey guy! For some reason my iMessage stopped working. It asks me login and after typing in my password it gives me "Could not sign in to iMessage. An error occurred during activation. Try again." Im still on 10.14.3. Any help would be appreciated!

Do you have EmuVariableUEFI-64.efi installed? If not, try putting it back into drivers64UEFI and restarting. I’ve had this happen to me a couple times and each time putting EmuVariableUEFI-64.efi back fixed it. I eventually ended up just leaving the file in drivers64UEFI.
 
Thank you for your amazing post @CaseySJ !! Because of this post, I went out and spent $2,700 on my second hack. Deets in my info. Everything was working great until 10.14.4.

PROBLEM 1: I cannot wake from sleep.
SYMPTOMS: one monitor (display port) remains dark, the second monitor mini HDMI to DVI usually comes back. Both plugged in to my Vega Frontier. Sometimes both remain dark. Every once in a while, both come up. However, if I put it back to sleep the second time, it never wakes.

NOTE: if I log in with only one monitor awake (by clicking randomly until I blindly click the log in icon then typing my password), the computer will freeze if I try and shut down or restart. If both monitors come back online after a sleep, then everything is good - unless I have it go to sleep a second time.

I'm in headless mode with onboard graphics disabled in BIOS. So far I have deleted everything in devices and injected Intel. That gave me the best performance so far in Davinci Resolve and woke up the most times before failing.

Also, the latest version of Adobe Premiere freezes on rendering but only when using Adobe Encoder. Rendering in the app works (but not for OpenCL - that freezes). However, Davinci does not freeze in Metal or OpenCL. I'm almost wondering if it is an Adobe thing...

PROBLEM 2: One USB 2.0 port on the front does not work. I have the Fractal R6 case and used the SSDT. Config attached.
 

Attachments

  • config.plist
    8.1 KB · Views: 126
Last edited:
Back
Top