Contribute
Register

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

@dgsga @faithie999 @canyondust @losinka @scottkendall *Party Noises*


This is incredible! Good freaking work. I'm going to flash my OEM firmware back onto my card and give it a go, go!

@CaseySJ, as for the Force Power issue I still keep tbforcepower.efi active as a backup. It's comes in handy when experimenting the with fixing sleep as it gets rid of the need for the shutdown/unplug fiasco.

Perhaps thats enough to get it going on the z390? It might take a boot and reboot to get it going. Good luck and thanks for being so thorough. This community is at it's brightest over here.

We should also update the XHC on the SSDT for the single USB port. You can use mine as a reference from the repo.

heyya @NorthAmTransAm where does one fine Tbforcepower.efi? I need a force-power solution for my setup as well, I have to boot with a TB device plugged in for the tree to load.

Cheers!

EDIT: I couldn’t find it because I was spelling it wrong. I found it.
 
Last edited:
@CaseySJ Looks like this didn't work. Followed the process to a T. Any ideas? I did delete the drivers64UEFI folder as instructed. My previous post has the screenshot which includes contents of both folders.
 

Attachments

  • 02CD156E-C3D9-4596-9A36-95C0267BBDF1.jpeg
    02CD156E-C3D9-4596-9A36-95C0267BBDF1.jpeg
    4.3 MB · Views: 57
Please use the SSDT for GC-Alpine Ridge located here. It should work as-is.
I'm so grateful for you support. Thanks for you time!

I used that files with the following results rebooting NUC 10 times:

The first time, on System Information´s Thunderbolt section: "Thunderbolt: No drives are loaded."

I shutdown it and restarted it for the second time: Now the tree appeared so I connected my TB3 Drive. It worked!. I disconnected it and hot plugged my Core X eGpu. It mounted. So I tested it with Geekbench. Everything worked great. Also the eject button for the eGPU appeared for the first time ever! I disconnected it and hotplugged again my drive. It worked. I send the computer to sleep but when it waked up the drive was ejected and nothing worked again. The tree disappeared.

Form boot 3 to 7 again "Thunderbolt: No drives are loaded"

And from boot 8 to 10, the TB3 tree appears but no device can be mounted.

So, just worked (until sleep) for one time in 10 boots, is here any special thing I need to do in clover, config.plist etc?

EDIT: if I clear NVRAM in clover at boot time, everything works, except sleep issues...

EDIT2: I don't know if its related but since I started flashing and playing with my TB3 the last 3 days, my Date and Time constantly are erased, 75% of the occasions at boot time my bios said that CMOS Time and Date is wrong, I don't think is my battery, my Nuc is year and a half old and constantly connected to AC, very weird.

thanks again!
 

Attachments

  • Screen Shot 2020-05-12 at 10.49.27 PM.png
    Screen Shot 2020-05-12 at 10.49.27 PM.png
    102.9 KB · Views: 63
Last edited:
If a TB device is connected before boot, does it remain connected after logging in?

Do TB devices reconnect after wake-from-sleep?

so far: device needs to be plugged in at boot else the tree does not populate at all (I might need a method to force power).
I did a quick sleep test and device reconnected, including a usb-c drive on port two (didn’t get the improper eject warning). I’m in bed now and sleeping the computer so I’ll try more in the morning. Also, the drom I’m using is from an Asus TB3 EX so I’m going to track down the real Z170x-UD5 TH alpine ridge firmware and extract it’s drom. I’ll report my findings :)
 
Hello @Wildside,

This comes up very often, hence it's Note #1 in the Catalina installation guide. What you're seeing is okay. As long as your Apollo Twin is being recognized, you're fine. We should check System Information --> PCI to see if the Apollo is showing up. Remember that Apollo needs latest firmware to be installed and latest macOS drivers.

View attachment 469156
Thanks Casey,
Unfortunately its not coming up in the PCI information.
Screenshot 2020-05-13 at 07.20.48.png
 
Hi All,

Complete noob here. I have tried to read as much of this thread as possible to get thunderbolt working and therefore recognising my Apollo twin. I have a official thunderbolt 3 to 2 adapter. After being pretty certain my bios and efi are what I hope are correct I get as far, "thunderbolt : no driver loaded" in the system report. any help much appreciated.
thanks

I see ''no driver loaded'' too, but UA stuff still works. Basically, UA over TB works straight out of the box, you don't need any convoluted TB chip reprogramming to get an Apollo working.
Haven't tried all their models(there are just too many) and versions, but I don't see why one would work and not the other.
 
Im so grateful for you support, thanks for you time!

I used that files with the following results rebooting NUC 10 times:

The first time, on System Information´s thunderbolt section: "Thunderbolt: No drives are loaded."

I shutdown it and restarted it for the second time: Now the tree appeared so I connected my TB3 Drive and It worked!, disconnected it and hot plugged my Core X eGpu, it mounted so I tested it with Geekbench, everything worked great, also the eject button for the eGPU appeared for the first time ever!, I disconnected it and hotplugged again my drive and it worked, I send the computer to sleep but when it waked up the drive was ejected and nothing worked again and the tree disappeared.

Form boot 3 to 7 again "Thunderbolt: No drives are loaded"

And from boot 8 to 10, the TB3 tree appears but no device can be mounted.

So, just worked (until sleep) for one time in 10 boots, is here any special thing I need to do in clover, config.plist etc?

EDIT: if I clear NVRAM in clover at boot time, everything works, except sleep issues...

EDIT2: I don't know if its related but since I started flashing and playing with my TB3 the last 3 days, my Date and Time constantly are erased, 75% of the occasions at boot time my bios said that CMOS Time and Date is wrong, I don't think is my battery, my Nuc is year and a half old and constantly connected to AC, very weird.

thanks again!
hey vicantu,
same problem here (NUC8i5BEH).
I flashed "NUC8i7HNKpatched.bin", added "ssdt-tbolt3-rp05-port7-gc-alpine-ridge-aml" and "ssdt-dtpg-aml" to my OpenCore EFI, just changed UID and CRC-8, then it works like a charm.
tbt 100% died after wake-from-sleep.
 
I see ''no driver loaded'' too, but UA stuff still works. Basically, UA over TB works straight out of the box, you don't need any convoluted TB chip reprogramming to get an Apollo working.
Haven't tried all their models(there are just too many) and versions, but I don't see why one would work and not the other.
Thanks for you reply zip. You gave me the final push I needed. The fix to my issue was to shutdown unplug, re-plug. down load the uad "reset-uad-access-control.command" from their website. Then re-instal the uad software. On restart it recognised it. wahoo. I'll report back if any issues from here.
thank you
 
heyya @NorthAmTransAm where does one fine Tbforcepower.efi? I need a force-power solution for my setup as well, I have to boot with a TB device plugged in for the tree to load.

Cheers!

EDIT: I couldn’t find it because I was spelling it wrong. I found it.

No worries. Let us know if it solves your issue.

It looks like someone else was working on a Force Power driver in 2017. Linked below.

 
Back
Top