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

[donquijote]

Ups, accidentally rebooted after MultiBeast was finished without completing the last steps. Now it shows a stop sign when trying to boot into Mojave. How can I get back in again and complete the rest of your guide CaseySJ?

 

[CaseySJ]

Ups, accidentally rebooted after MultiBeast was finished without completing the last steps. Now it shows a stop sign when trying to boot into Mojave. How can I get back in again and complete the rest of your guide CaseySJ?

No problem...

• Insert the USB Install Disk.
• Boot the computer.
• Press F12 at BIOS Splash Screen and select the USB Install Disk.
• When Clover Boot Menu appears, choose "Boot macOS from Mojave".
• Login and complete the post-install procedure.
• Remove USB Install Disk.

 

[PicLock]

Ensure that your USB SSDT is installed and your USB port limit patches in config.plist are Disabled.

• The Mojave 10.14.4 USB port limit patch is not compatible with 10.14.5.

@CaseySJ USB port limit patches in config.plist are Disabled.
This?

 

[donquijote]

No problem...

• Insert the USB Install Disk.
• Boot the computer.
• Press F12 at BIOS Splash Screen and select the USB Install Disk.
• When Clover Boot Menu appears, choose "Boot macOS from Mojave".
• Login and complete the post-install procedure.
• Remove USB Install Disk.

Great CaseySJ thanks!

In the next step you wrote

Now we expand the EFI/CLOVER folder to check things out. Here we can see that ApfsDriverLoader-64.efi and AptioMemoryFix-64.efi are missing. (Update: this problem has been fixed in MultiBeast 11.2.1.) However, your drivers64UEFI folder content may be different. Don't worry; we'll soon replace everything in this folder.

Where is this EFI/CLOVER folder? The EFI partition does not show up anymore for me.

 

[CaseySJ]

@CaseySJ USB port limit patches in config.plist are Disabled.
This?

Yes, you're good to go... (backup, backup, backup first).

 

[CaseySJ]

Great CaseySJ thanks!

In the next step you wrote

Where is this EFI/CLOVER folder? The EFI partition does not show up anymore for me.

Yes that's right. The EFI partition was automatically mounted by MultiBeast. But no worries, you can mount it very easily using Clover Configurator:

 

[CaseySJ]

Hi CaseySJ,

Thank you for your reply.

Yes, I even used AptioMemoryFix.efi with Clover. I did not use AptioFixDrvFree2000, because one of the developers of AptioMemoryFix told me about it being "last resort", as it wasn't a good solution. I don't recall what the exact reason was for it. However, I remember the explanation to be quite technical. At that time AptioMemoryFix wasn't created. AptioMemoryFix is of course also focused on to fix the NVRAM issues people have had with the 100, 200 and 300 series boards. And if AptioMemoryFix.efi doesn't work alone, slide values can help with that. However, I'm not using any Slide argument.

Anyhow. To answer your question about Wifi+BT. I'm using an Apple WiFi card with BlueTooth. I disabled the motherboards onboard BT with uia_exclude=HS14 boot argument, as it was becoming a plague for pairing BT dependant HIDs.

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.

 

[nifranza]

Hi @CaseySJ, quick question:

I'm using headless mode on my UHD 630. If so, should I remove ig-platform-id from the Graphics section of CC?

P.D: Is the iGPU properly implemented in your opinion?
P.D.2: Should I leave ResetHDA set to Enabled or untick it?

Thanks in advance. As always, I can't thank you enough for the excellent quality of this guide!

 

[CaseySJ]

Hi @CaseySJ, quick question:

I'm using headless mode on my UHD 630. If so, should I remove ig-platform-id from the Graphics section of CC?

P.D: Is the iGPU properly implemented in your opinion?
P.D.2: Should I leave ResetHDA set to Enabled or untick it?

Thanks in advance. As always, I can't thank you enough for the excellent quality of this guide!

Hello @nifranza,

You're almost there. Couple of fixes needed:

• Remove "0x3E980003" from Clover Configurator --> Graphics.
• In Clover Configurator --> Devices --> Properties, AAPL,ig-platform-id currently has a value of 3E980003. But this must be specified in reverse byte order as: 0300983E.
• In the same section, one more property needs to be added:
  • Properties Key: framebuffer-patch-enable
  • Properties Value: 01000000
  • Value Type: DATA
• Then save the file, reboot, and run IORegistryExplorer once again to check settings of IGPU.

You may leave "Reset HDA" checked on.

 

[nifranza]

Hello @nifranza,

You're almost there. Couple of fixes needed:

• Remove "0x3E980003" from Clover Configurator --> Graphics.
• In Clover Configurator --> Devices --> Properties, AAPL,ig-platform-id currently has a value of 3E980003. But this must be specified in reverse byte order as: 0300983E.
• In the same section, one more property needs to be added:
  • Properties Key: framebuffer-patch-enable
  • Properties Value: 01000000
  • Value Type: DATA
• Then save the file, reboot, and run IORegistryExplorer once again to check settings of IGPU.

You may leave "Reset HDA" checked on.

Done, is it better?