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

[SilentFlute]

@CaseySJ,

Hopefully a simple question from an LED noob. Using the same components you suggested, where should the LED headers from the various fans be going? Is it correct to connect the Orcus header to the LED_C header?

 

[CaseySJ]

@CaseySJ,

Hopefully a simple question from an LED noob. Using the same components you suggested, where should the LED headers from the various fans be going? Is it correct to connect the Orcus header to the LED_C header?

There are 2 kinds of LED headers: RGB and ARGB (addressable RGB). The first kind used 12V while the second uses 5V. The Orcus is an ARGB device that cannot be plugged into the RGB headers on Designare because alas the Designare does not support ARGB. (Plugging a 5V device into a 12V header will destroy it.) The Orcus comes with a fan and lighting hub, so that’s where those wires will go.

 

[SuDoDmz]

The motherboard has two on-board gigabit Ethernet ports, ideal for 802.3ad LACP link aggregation. One of the ports is natively supported, but the other (Intel i211) requires a modified Smalltree kext, which is also included and applied in post-installation. Note that the Smalltree driver for the i211 Ethernet port does not support 802.3ad link aggregation at this time, but any macOS-compatible add-in or external Gigabit Ethernet port will work in combination with the Intel i219 port. For example, the Gigabit Ethernet port built into the OWC Thunderbolt 3 dock works perfectly in combination with the Intel i219.

Just wanted to note: for the I219-V you still need IntelMausiEthernet.kext, or am I mistaken? (Or did you just write natively supported, because you were going to install the kext anyway?).

Nevertheless, after a long while of lurking, I too managed to set up a build with partial use of your instructions and attachments. For anyone having problems installing on an Aorus Xtreme Z390 I attached my EFI Folder. Worked on 10.3.3 (had to install because of the Aquantia LAN, but did something else entirely in the end, as mentioned in the 10Gbe Support thread. At this point I'd like to express my utmost gratitude to @pastrychef for his informative thread, which, I believe, was the trigger bumping me into the direction I went) and currently on 10.4.4. Here I'd also like to thank you for sharing your informations (I believe they were utterly necessary for me, since our boards are "almost" identical).

I used the onboard createinstallmedia of OS X to build an installer and used kexts and patches JUST in the EFI folder.
While still having problems reaching the installer, I had the brilliant idea of plugging my HDD into my "old" x58 rig, installed OS X from there and just bothered with booting into it further on.

As far as I can tell everything seems to work fine (except one of my two Wi-Fi Cards, but that's another story entirely, didn't test TB3 and the 10Gbe LAN though, but they are recognised under System Informations).

My current setup goes like:

SMBIOS: iMac18,3 (19,1 won't boot, so, without even doing research my guess is, that you'd need one of the "special"
OS X builds for that one)
MoBo: Aorus Xtreme Z390
CPU: i9-9900K
MEM: 2 x 8GB G.Skill Trident Z Royal Silver (still slotted A1-B1 , waiting for the 16GB modules to arrive in Germany
for further upgrading to 64GB)
Graphics: Sapphire Radeon RX Vega 56 Nitro+ (dude, why u buy 56? Because I in person can't stand heat or too
much light)
PSU: Seasonic Prime Ultra Titanium 850W
Case: Full House Noctua cooled Corsair Dark Base Pro 900 rev2 (I know what you might be thinking, but actually I
chose the case and THEN found out about the prebuilt custom SSDT, though my USB 3.1 port on the case
seems not working, just getting power. Also still have to figure out what to plug in where to make the light
switch work )
CPU Cooler: EKWB Block, Radiator and Res (Acetal, not plastic) with Mayhems hose and liquid and Bitspower fittings.
Actually funny story, because there was no other cooler I could fit onto a delidded CPU
Wi-Fi: BCM94331 (still a bit jumpy under Windows) in a PCIe x1 adapter (with BCM94360 verbose is stuck at
IO80211Controller start, haven't figured out why, yet, works fine under Windows)

 

[CaseySJ]

Just wanted to note: for the I219-V you still need IntelMausiEthernet.kext, or am I mistaken? (Or did you just write natively supported, because you were going to install the kext anyway?).

Good catch. It's "natively" supported by UniBeast and MultiBeast, but not by macOS. Sentence has been reworded.

Nevertheless, after a long while of lurking, I too managed to set up a build with partial use of your instructions and attachments. For anyone having problems installing on an Aorus Xtreme Z390 I attached my EFI Folder. Worked on 10.3.3 (had to install because of the Aquantia LAN, but did something else entirely in the end, as mentioned in the 10Gbe Support thread.

The Aquantia LAN drivers are included now in UniBeast and MultiBeast so it should be possible to install Mojave directly. If I recall correctly, three other AORUS Xtreme/Waterforce owners (@ummario, @Snoots, @rj510) installed Mojave directly. Their experiences are captured in earlier posts.

If a direct Mojave installation did not work in your case, do you recall what problems or symptoms you encountered?

As far as I can tell everything seems to work fine (except one of my two Wi-Fi Cards, but that's another story entirely, didn't test TB3 and the 10Gbe LAN though, but they are recognised under System Informations).
...
Wi-Fi: BCM94331 (still a bit jumpy under Windows) in a PCIe x1 adapter (with BCM94360 verbose is stuck at
IO80211Controller start, haven't figured out why, yet, works fine under Windows)

While it's common for computers to contain two or more Ethernet ports, it is not usual for them to contain more than one WiFi/BT module. MacOS (and perhaps Windows as well) will be confused by the presence of multiple WiFi/BT modules, which is why we use SSDT-Z390-DESIGNARE-NO-CNVW.aml and the USB SSDT (which disables Bluetooth on HS14) to render the Intel CNVi module invisible to MacOS.

 

[SuDoDmz]

The Aquantia LAN drivers are included now in UniBeast and MultiBeast so it should be possible to install Mojave directly.

Didn't use neither of the tools

If a direct Mojave installation did not work in your case, do you recall what problems or symptoms you encountered?

I never attempted a direct Mojave install, because of the Apple Aquantia FW flash procedure. Updating just went fine, reaching the installer of 10.13.3....that's another story entirely, it always stopped somewhere at the beginning (don't remember the verbose output, but imagine 3mm of the loading bar, where not even my G910 was lit)

While it's common for computers to contain two or more Ethernet ports, it is not usual for them to contain more than one WiFi/BT module. MacOS (and perhaps Windows as well) will be confused by the presence of multiple WiFi/BT modules, which is why we use SSDT-Z390-DESIGNARE-NO-CNVW.aml and the USB SSDT (which disables Bluetooth on HS14) to render the Intel CNVi module invisible to MacOS.

I used that SSDTs from the beginning (and also disabled the integrated card in Windows Device-Manager). My fault for not being specific: I tried one at a time. But oddly both of them work fine on my x58 system

EDIT: I stand to be corrected; I also tried both of the cards in my second x16 slot (it even booted with the BCM94360cd card), but unfortunately no Wi-Fi (both cards, both systems)

EDIT2: Since Mojave update Windows boot is jumpy, gets stuck on the circle sometimes, when booting with Clover, throws a Bluescreen, when booting directly, but immediately continues boot, when pressing enter.

 

[luckyal]

SMBIOS = Macmini8,1 for now. But with 10.14.5 in the future, we will experiment with iMac19,1.

You can have 19,1 now. In Clover Configurator first select iMac18,3 from dropdown, select and copy your Board-ID, go back and select iMac19,1 from drop down and paste your Board-ID into the same field.

Not sure, but for iMessage and stuff you might have to generate your serial before you change that Board-ID so you can run it through everymac/apple for validation.

 

[Robertyu]

Just an update from my build, and just some feedback as to how the attempt to use the XFX RX-580 8GB card for Mojave went...

I did get the XFX RX-580 graphics card to work with not detectable issues for several days now. I removed the card for install and just ran on the Intel 630 graphics, and then installed after install. Once installed and configured, I did the other (FCPX no crash) patch in this thread to use the iGPU in headless mode and FCPX runs great and scrubbing 4K 100MB/s is very fast.

This card has been working so well that I bough another one on sale at Best Buy for $160.

After I got everything working well on this new build, I did a fresh Mojave install on my old Asus Z97 Deluxe. I tried just the normal generic Mojave install from this site, and that system is now up and running better than where I had it on High Sierra. I'm using that other XFX card in this machine now, and it appears to be working well.

I'll reflash both of these cards to another brand's image if I must, but have not run into a reason to do that yet.

 

[michelegelmini]

I'm not sure if this topic is already been discussed: my hackintosh is using only 10-15% of the cpu according to the Intel Power Gadget utility. I'm trying to export a simple video with FCPX and it's taking reaaaaaally long.

My build is almost identical to the one in this guide, I'm a newbie, probably I'm forgetting something really stupid

 

[wickett]

After the second one highlighted in red. Please ensure that each <dict> statement is terminated by a closing </dict> statement further down the file.

Thanks very much

 

[chaosminionx]

for the Z390 - Vega56/64 SSDT, I tried unpacking the aml with iasl, and then used maciasl to edit the device name so that it woudl show Vega 56 over Vega 64 however I am getting an issue with the compile regarding an unexpected return code, theres 2 parts within the SSDT that have a return value it apparently isnt expecting. I tried deleting those values, and then building it however "about this mac" now shows "Vega 56 8GB 8GB..."


am I missing something? I saw it was adapted from work kgb did, and I figured it was edited in the same manner. I used the iasl function of "iasl -da -dl *.aml" to unpack.

Thanks in advance, I tried searching but didnt look like anyone had that specific issue.