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

[svandive]

I finally plan to test OpenCore because I'm intrigued by the inclusion of the DevicePath protocol. However, I wonder if that is different from DevicePathProperties. One of the obstacles for activating Thunderbolt Local Node and Thunderbolt Bus is the following:

• Apple's EFI firmware (BIOS) includes a large number of DXE Drivers. The drivers that we believe are instrumental in setting up Thunderbolt properly include, but may not be limited to, the following:
  • EfiDevicePathPropertyDatabase.efi
  • ThunderboltNhi.efi
  • ThunderboltXDomainDevice.efi
  • PciThunderbolt.efi
  • DevicePathDriver.efi
• The EFI firmware plays a crucial role in setting up or initializing various internal components such as the Thunderbolt controller.
• The EFI firmware sets up key parameters such as:
  • ThunderboltDROM
  • pathcr
  • pathcrumbsv2
  • TBTDPLowToHigh
  • ThunderboltConfig
  • etc.
• These parameters are then passed to Apple's boot.efi, which starts macOS.
• So the Thunderbolt Kexts inside macOS do not set this up. They rely on these EfiDevicePathProperties to be passed in by the EFI Firmware.
• I am not sure whether the Clover Boot Loader includes the EFI protocol necessary for this type of handshake between Firmware and macOS.
• But the OpenCore source code includes the DevicePath protocol, which has me intrigued... Will this allow EfiDevicePathProperties created by the Firmware to be passed to the macOS kernel?

I plan to use your OpenCore EFI on a USB flash disk. If you have a newer or updated version that you think might be a better version to test, please let me know.

Edit (12 July 2019): After reading relevant parts of the UEFI Specification, I need to make some corrections:

• EFI Device Path protocol is standard; it's a fundamental part of the UEFI spec.
• Apple implements a custom AAPL,PathProperties protocol that is implemented in EfiDevicePathProperties.efi.
• Apple's ThunderboltNhi and ThunderboltXDomainDevice are EFI Boot Service drivers (SUBSYSTEM Type = 0x0B) instead of EFI Runtime Drivers. This means they are terminated sometime during the boot process. The macOS kexts no longer rely on them. But these EFI Boot Service drivers pass important Thunderbolt operating properties to the boot loader (via the custom AAPL,PathProperties protocol), which in turn passes them on to AppleACPIPlatform.kext for use by macOS.
• The EFI Boot Service drivers can initialize and configure the Thunderbolt controller, but the UEFI Spec requires the OS-level drivers to not make any assumptions, and to initialize and configure the controller by themselves.

I am extremely interested to see where this line of study and investigation leads. Anything that brings a closer integration of the Thunderbolt sub-system in to the Hackintosh area is GODs work.... I rely on my thunderbolt interfaces on my MacBook Pro daily and getting a closer more real world experience with my Hack is a dream...

Thank You for digging on this CaseySJ

 

[Stewie23]

Hey everyone! Can anyone confirm if Powernap works on the build? Also, any way to prevent sleep? I tried using Caffeine. But, leaving the computer over lunch, it was in sleep when I came back.

 

[AlexComputerWiz]

@CaseySJ I know this a random, unrelated question, but would an i9-9980XE work with MacOS? I know it wouldn't work for this build, but I always have to have another project in the pipeline

 

[CaseySJ]

@CaseySJ Wow! Asus X99 Deluxe II and 6850K CPU guide.
My current Asus X99 Deluxe ll i7-6900K built would love a rebuild based on your guide.

Alas, this is just an experiment for educational purposes rather than a formal build.

 

[CaseySJ]

I'd like to check and see if folks have any workarounds or ideas for these two issues:

1: Watching iTunes DRM movies being streamed from iTunes.
I can download a movie from iTunes and watch it, but if I try and stream it to watch it, it just freezes

2: Watching Netflix in Safari.
Watching low quality in Firefox seems to work, but it errors when using Safari

Both of these seem to be DRM issues, they could be related to HDCP 2.2 support in Mojave, but not sure.

Thoughts,

Have you tried "shikigva=60" in Boot Arguments?

 

[CaseySJ]

nifranza, I'd like to get a look at your Clover setup (config.plist, and what kext your loading). I noticed on a post of yours that your Radeon Vega 64 is showing up in the PCI listings (see attached). I have a similar setup (i9, Ddesignare, Vega 64) but my Vega 64 doesn't show upon in the PCI listing. (It used to and seeing yours reminded me to go figure this out.).... Thanks

Yours,
View attachment 416191

Mine,
View attachment 416192

The Vega64 entries in PCI page are most likely due to the Vega SSDT available in Post #1. This SSDT is no longer recommended with Mojave 10.14.5 and newer because the SSDT incorporates a custom power play table that is superseded by the updated drivers in 10.14.5.

 

[CaseySJ]

Hey everyone! Can anyone confirm if Powernap works on the build? Also, any way to prevent sleep? I tried using Caffeine. But, leaving the computer over lunch, it was in sleep when I came back.

There are reports earlier in this thread of PowerNap working properly.

But if you simply want to prevent Sleep, set System Preferences --> Energy Saver --> Display Sleep to Never. If the display does not sleep, the computer itself will not sleep because the former will raise an InternalPreventSleep assertion.

 

[CaseySJ]

@CaseySJ I know this a random, unrelated question, but would an i9-9980XE work with MacOS? I know it wouldn't work for this build, but I always have to have another project in the pipeline

Yes it should work, but you may need to use iMacPro1,1 and spoof the CPU ID. Would be better to google for a more definitive answer...

 

[PicLock]

Alas, this is just an experiment for educational purposes rather than a formal build.

Thanks CaseySJ. My Asus X99 built was based on KGP guide, my very first Hackintosh really.. Still on 10.12.6 as I found myself having difficulty to follow KGP's subsequent 10.13.6 guide, largely due to my own inexperience. I was hoping to find an easier guide to follow.

 

[donquijote]

Is there really no way to make the onboard WiFi/Bluetooth of the Z390 Designare working? Very sad to leave it unused and having to buy another card...