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

[svandive]

I’ve updated that section of the build guide. Hopefully it’s more detailed/complete now.

Up and running, with a nice added bonus that it shows me the details for the smart fan controller as well. These three fans are the High Static Pressure NZXT fans that come with the NZXT Kraken x72. I have them configured on the back of the Radiator in a push (RGB fans) Pull setup!!

 

[mbapple]

The standard version of USBInjectAll.kext is incompatible with iMac19,2, but will work with iMac19,1. However, there is a modified version that supports iMac19,2. You therefore have 2 options:

1. Switch to iMac19,1 in SMBIOS.
2. Replace USBInjectAll.kext in both CLOVER/kexts/Other and /Library/Extensions with the following version: https://github.com/Snikii/OS-X-USB-Inject-All/releases
   • After replacing the file in /Library/Extensions, please run Kext Utility to rebuild the kernel cache.

Alas we have tried everything humanly (and legally) possible for the Apple Thunderbolt Display. This includes long detailed technical sessions with engineers at Gigabyte and Intel. The final conclusion: Nope. It will not work.

There are plenty of very good, modern alternatives on the market today...

Hey @CaseySJ

Thanks, I didn't know this but noticed USB didn't seem to fully work, I think I will opt for the modified USBInjectAll.kext.

Also to get Final Cut working do I need to change the even if I'm not running headless?

Aw well that stinks, thanks for letting me know.

Thanks.

 

[Fabrizzioa04]

Thanks for this guide @CaseySJ. I finally achieve installing Windows 10 and Mojave on my machine. The only thing I cannot do its booting with Vt-d enabled and dart=0 removed to using my vrs8 interface. I get panic error every time I boot, already unlocked the CFG. I don't know what I'm missing. I attached some images of my configuration.

 

[FriFlo]

I am stuck ... after installing the 128GB of RAM and the PCIe card (I had to use the BCM94360CS2 on a PCIe Adapter - the first choice is not available anywhere I looked) Clover did not start from the installation from before. So, I made the USB installer stick from scratch to be sure. However, I get this protocol when trying to boot from the stick:

Start ProcessOptions
End ProcessOptions
RegisterRestartDataProtocol: called 0x3261dd98
RestartData protocol installed sucessfully.
(... lots of Starts and Ends ...)
StartInitBootStruct

root device uuid is 'FCC0913B-(...)'
End InitBootStruct
Start LoadRamDisk
End LoadRamDisk
Start FinalizeBootStruct
End FinalizeBootStruct
Start RandomSeed
End RandomSeed
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Could someone help me out? I think, the first logical thing to do would be to rule out, wether the new RAM or the PCIe card is the problem. I am going to do that and report back. Or is there any modification I have to make when using the second choice WIFI solution or RAM with a different speed (2666MHz)?

 

[CaseySJ]

I am stuck ... after installing the 128GB of RAM and the PCIe card (I had to use the BCM94360CS2 on a PCIe Adapter - the first choice is not available anywhere I looked) Clover did not start from the installation from before. So, I made the USB installer stick from scratch to be sure. However, I get this protocol when trying to boot from the stick:

Start ProcessOptions
End ProcessOptions
RegisterRestartDataProtocol: called 0x3261dd98
RestartData protocol installed sucessfully.
(... lots of Starts and Ends ...)
StartInitBootStruct

root device uuid is 'FCC0913B-(...)'
End InitBootStruct
Start LoadRamDisk
End LoadRamDisk
Start FinalizeBootStruct
End FinalizeBootStruct
Start RandomSeed
End RandomSeed
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Could someone help me out? I think, the first logical thing to do would be to rule out, wether the new RAM or the PCIe card is the problem. I am going to do that and report back. Or is there any modification I have to make when using the second choice WIFI solution or RAM with a different speed (2666MHz)?

You have the right idea:

• We should rule out memory by installing half the capacity (64GB).
• Then rule out the WiFi/BT card by removing it.
• Also check the CLOVER/drivers64UEFI folder to make sure you have:
  • OsxAptioFix2Drv-free2000.efi
  • All other OsxAptio drivers and AptioMemoryFix should be deleted
• You can also try reseting CMOS by shorting 2 pins on the motherboard with a flathead screwdriver. The procedure is easy and it will allow the firmware to fully re-scan the system for devices and rebuild all internal data structures and device trees. It's a way of "detoxifying" the system and restoring good health.
• Also ensure you are running firmware (BIOS) version F6 or F7.

 

[CaseySJ]

Thanks for this guide @CaseySJ. I finally achieve installing Windows 10 and Mojave on my machine. The only thing I cannot do its booting with Vt-d enabled and dart=0 removed to using my vrs8 interface. I get panic error every time I boot, already unlocked the CFG. I don't know what I'm missing. I attached some images of my configuration.
View attachment 417336
View attachment 417338
View attachment 417339
View attachment 417340

Hello @Fabrizzioa04,

Some suggestions...

• We cannot use AptioMemoryFix. Please delete and replace that with OsxAptioFix2Drv.free2000.efi, which is available from Post-Install Files.zip in post #1.
• Also check that slide=0 is set in the Boot section of your config.plist.
• Have you tried using FakeSMC instead of VirtualSMC to see whether that makes any difference regarding Vt-d and dart=0?

 

[CaseySJ]

Hey @CaseySJ

Thanks, I didn't know this but noticed USB didn't seem to fully work, I think I will opt for the modified USBInjectAll.kext.

Also to get Final Cut working do I need to change the even if I'm not running headless?

Aw well that stinks, thanks for letting me know.

Thanks.

Final Cut, iMovie, and some other A/V/P (audio/video/photo) apps will immediately crash if you enable video display from the iGPU. It is absolutely necessary to switch the iGPU into headless mode with Platform ID 0x3E980003 in order to run these apps. This will switch off the HDMI and DisplayPort video output from the iGPU, but it will not affect your Vega 56.

 

[FriFlo]

You have the right idea:

• We should rule out memory by installing half the capacity (64GB).
• Then rule out the WiFi/BT card by removing it.
• Also check the CLOVER/drivers64UEFIfolder to make sure you have:
  • OsxAptioFix2Drv-free2000.efi
  • All other OsxAptio drivers and AptioMemoryFix should be deleted
• You can also try reseting CMOS by shorting 2 pins on the motherboard with a flathead screwdriver. The procedure is easy and it will allow the firmware to fully re-scan the system for devices and rebuild all internal data structures and device trees. It's a way of "detoxifying" the system and restoring good health.
• Also ensure you are running firmware (BIOS) version F6 or F7.

Thanks! it seems to be the RAM. I removed everything unnecessary, but only with the RAM exchanged with the 64GB kit, I can boot from the Mac OS installation and also from the installer?
- I can verify the WIFI-card working with the 64Gb-kit installed
- I don't know how to access the EFI partition on the USB stick, now, but I am sure I have deleted and replaced the files
- Bios F6 is installed

What can I try to make the 128GB work?
I did try the RAM in a Windows 10 installation, which does work. It is these Samsung sticks:
4x 32GB (32768MB) Samsung M378A4G43MB1-CTD DDR4-2666 DIMM CL19 Single

 

[Rag]

Interesting article on the new Vegas, this explains the withdrawal of Radeon VII.

AMD Vega 20 GPU Specs

4096 Cores, 256 TMUs, 64 ROPs

www.techpowerup.com

 

[CaseySJ]

My Fenvi T9191 arrived yesterday and I now have a fully working machine!

Running 10.14.5. In built graphics driving two monitors - HDMI and Thunderbolt to DP. Firewire card working. Bluetooth, Wireless, An extra 4 USB 2 ports on the rear and two on the front. On board and HDMI audio.

Thank you so much Casey for all your work here.

The last thing to get working is my Antelope Orion 32+. I've looked into it but it's all beyond me. Does anyone know the likelihood of the thunderbolt bus ever working fully? I've spotted a few errors on boot with the orion as seen in this image posted here. Can anyone shed some light on the situation with this information?

I totally sympathize. It's frustrating to come this close and hit a seemingly insurmountable obstacle. I am quietly working on understanding why Thunderbolt Bus and Local Node are not working. What I've found so far (and the process is far from over):

• Apple's firmware (BIOS) contains at least 4 EFI drivers that play an important role:
  • PciThunderbolt.efi
  • ThunderboltNhi.efi
  • ThunderboltXDomainDevice.efi
  • EfiDevicePathPropertiesDatabase.efi
• On the Gigabyte we might only need the last 3.
• I have extracted these EFI files from Apple's firmware image files and copied them into the CLOVER/drivers64UEFI folder.
• Clover loads them during boot, but these drivers (according to UEFI Specification) will not actually initialize or configure the physical device until a third-party "connects" the driver to the device and asks it to perform certain operations.
• On real Macs, we believe it's the firmware code itself that connects these drivers to their devices and invokes function calls on the drivers (i.e. invokes the protocols supported by the drivers).
• However, some other EFI component can also do this; even Apple's "boot.efi" could in theory perform this role.
• At the Clover Boot Menu, we can launch an EFI Shell (like a Terminal or command line prompt). This shell lets us look into the inner workings of the running EFI system.
  • An EFI system is like a full, but mini operating system. If you ever wondered what software displays the BIOS splash screen or runs the Setup GUI or displays the mouse cursor or accepts keyboard input or can fetch new BIOS updates from the network, the answer is: The Firmware. The firmware is a large collection of drivers and applications that support USB devices, SATA devices, network devices, keyboard/mouse, graphics, etc. The firmware is therefore a mini operating system.
  • When we finally boot into MacOS or Windows or Linux, nearly all of the EFI drivers and applications are terminated and removed from memory, and the real OS takes over and provides its own set of drivers.
  • But some EFI drivers remain in memory and provide runtime services to the OS. They belong to the class of "Runtime Drivers". I do not think that any part of Thunderbolt is governed by a runtime driver.
• The EFI Shell, therefore, lets us peek into the EFI System that is currently loaded.
• It shows that ThunderboltNhi.efi and ThunderboltXDomainDevice.efi and EfiDevicePathPropertiesDatabase.efi are all loaded by the Clover Boot Loader, but they are all in a "disconnected" state.
• The EFI Shell allows us to list all current Devices and Drivers in the system using the "devices" and "dh" commands. These commands return the device handles and driver handles.
• The EFI Shell also allows us to connect device handles to driver handles in order to activate a driver. But any attempt to manually connect these Apple drivers to Thunderbolt device handles results in a failure.
• Why would we need to do this if the OS provides its own complete set of Thunderbolt drivers?
• Because certain properties of Thunderbolt are only extracted by the EFI driver and then passed on to the host operating system through a custom protocol (i.e. interface or API) that the host's "boot.efi" uses to grab these properties. Boot.efi then passes the properties to Apple's IO PCI Platform drivers and then they appear in IOReg.
• So the first thing we are trying to do is to see whether we can get this little piece of the puzzle to work.
• Hence the investigation continues...