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

[CaseySJ]

Haha. I did that, but I saw your message before you edit it about the backup, LOL. I went for hot changes.
Unfortunately it didn't help. Here's the resulting folders again:

The screenshots are correct. Some questions:

• Are you using an HDMI-to-HDMI cable (no adapters)?
• What is the make/model of your monitor? Is it a TV?
• What version of Clover is running? Simply press "A" for "About" at the Clover Boot Menu.

An alternative solution is to use a USB-C to DisplayPort cable such as this one. Or USB-C to HDMI cable such as this one. However, on-board HDMI should work with those updated/debug versions of Lilu/WhateverGreen.

 

[kromuh]

This is usually a simple thing to fix. Please do this:

• Mount EFI partition of the Mojave SSD
• Expand the CLOVER folder and subfolders so we can see (a) drivers64UEFI or drivers/UEFI, (b) kexts/Other
• Post a screenshot

Most likely there's an incorrect memory EFI driver or multiple memory EFI drivers.

@CaseySJ Thanks for the quick reply
Here are the screenshots of my drivers64UEFI, kext/Other. I've also included About this Mac and System Report for hardware context. You're the man!

 

[maleorderbride]

So I don't know if I missed this in the guide, but the "cheaper" (black) SOIC8 clamp mentioned has 1mm pitch pins... the plastic housings of the regular jumpers you get for 0.1" headers like Raspberry Pi's are too thick to fit on the pins next to one another. I ordered some 1mm breakouts (connector -> header pin) from Amazon. I thought about soldering to the SOIC clamp, or maybe cutting the pins to different heights, but figured it was better to wait than to mess it all up. The good news is that the cheap clamp fits onto the Macronix parts quite well, at least mechanically.

On the X299 Prime Deluxe II one of the two chips is fully visible in the case cutout. So I'll dump that one first and send it along in the hopes that it's the right one of the two.If not I'll take the motherboard out and dump the other one.

@CaseySJ Are you two looking for the stock ASUS X299 Deluxe II TB3 firmware? If so I've attached it.

 

[CaseySJ]

Thanks for the quick reply
Here are the screenshots of my drivers64UEFI, kext/Other. I've also included About this Mac and System Report for hardware context. You're the man!View attachment 482208

In the drivers64UEFI folder, see these two files?

• OsxAptioFix2Drv-free2000.efi
• OsxAptioFix3Drv-64.efi

Both of them are memory EFI drivers. We can only use one at a time, and the one that works is OsxAptioFix2Drv-free2000.efi. So please delete the other one and reboot.

Eventually you should replace OsxAptioFix2Drv-free2000.efi with yet another one (but you can do this later).

 

[CaseySJ]

@CaseySJ Are you two looking for the stock ASUS X299 Deluxe II TB3 firmware? If so I've attached it.

Thanks for the firmware file! I've been working with @joeblough via private mail on his extracted copy of the firmware. We've hit the following issue:

• Thunderbolt controller will not power up unless a USB-C device is connected on cold boot.
• Hot plug does not work.

Do you see similar issues on your board (assuming it's firmware has been flashed)?

 

[maleorderbride]

@CaseySJ
After flashing my current state is:
-Thunderbolt controller will power up regardless of devices connected
-TB3 hotplug works on both ports (hmm, although DSB4 is temperamental at time. I thought I just addressed it, but still happening sometimes)

-USB-C controller will not power up unless USB-C device is connected on cold or warm boot
-USB-C no hotplug

Perhaps with our powers combined we can get both TB3 hotplug and USB-C hotplug working. Feel free to loop me in on the email chain and I can share my SSDT and flashed firmware.

 

[CaseySJ]

After flashing my current state is:
-Thunderbolt controller will power up regardless of devices connected
-TB3 hotplug works on both ports

-USB-C controller will not power up unless USB-C device is connected on cold or warm boot
-USB-C no hotplug

Perhaps with our powers combined we can get both TB3 hotplug and USB-C hotplug working. Feel free to loop me in on the email chain and I can share my SSDT and flashed firmware.

Awesome, you'll be looped in momentarily.

To All:
Once we have made some progress, I will make everything public here. Right now it's better not to make experimental versions of the firmware public.

 

[kromuh]

In the drivers64UEFI folder, see these two files?

• OsxAptioFix2Drv-free2000.efi
• OsxAptioFix3Drv-64.efi

Both of them are memory EFI drivers. We can only use one at a time, and the one that works is OsxAptioFix2Drv-free2000.efi. So please delete the other one and reboot.

Eventually you should replace OsxAptioFix2Drv-free2000.efi with yet another one (but you can do this later).

@CaseySJ
Much appreciated! At what point should I replace it? and will deleting or replacing these files affect the data on my current OS SSD?
Cheers

 

[3Dman]

I have found two more advantages of disabling XMP beside not receiving the disk not ejected properly notifications after sleep.
- My most annoying issue was with bluetooth trackpad and keyboard after waking from sleep has been fixed, now it doesn't take 3 seconds delay before they work.
- Wake from sleep is now instant, in my case it's very close to the time my monitor starts, before it took like 2 seconds.

I didn't notice any real world performance drop after disabling XMP. Maybe macOS is not optimized to use it because real mac don't use it or there's an issue with USB when waking with it enabled thus disconnecting bluetooth and external drives.

 

[3Dman]

Thanks! Do you know if it’s possible to launch the app only in the background? I don’t want to see the app icon in the top bar.

I have modified its source code to remove the menu bar code, but I can't change its preferences now. So you can just download the code, run it and adjust your preferences, edit the code and create a build, add it to your applications folder, and finally to your login items. It's working excellent since then without spamming my menu bar.

I have attached the changes required to disable the icon, just comment these three lines.