Contribute
Register

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

Please try this to rename RP05:_INI to RP05:XINI
  • Find: 5F494E49 00704C54 52314C54 525A7050 4D4C314C 4D534C70 504E4C31 4C4E534C 704F4246 314F4246 5A140F5F 50525700 A4475052 570A690A 0414165F 50525400 A00A5049 434DA441 523038A4 50523038 5B824D39 52503036
  • Replace: 58494E49 00704C54 52314C54 525A7050 4D4C314C 4D534C70 504E4C31 4C4E534C 704F4246 314F4246 5A140F5F 50525700 A4475052 570A690A 0414165F 50525400 A00A5049 434DA441 523038A4 50523038 5B824D39 52503036
  • Comment: RP05:_INI --> RP05:XINI

@CaseySJ you're a genius.

It's hot-swapping when booted plugged in! Next to try hot-plug from cold boot!!

Screen Shot 2020-05-12 at 9.33.19 PM.png


Screen Shot 2020-05-12 at 9.34.34 PM.png
 
Hi Casey

Can you leave the dock plugged in and see what effect does sleep wake have on it or just say after 2 hours of dock plugged in without sleep ?. I have noticed that the System/Thunderbolt shows 'no device device connected' after a random amount of time OR after a random amount of sleep wakes. The dock stays connected - I can use the devices connected to the dock , hot plug but strangely the System/Thunderbolt shows 'no device device connected'. Thank you

Edit: A reboot brings it back. The logs show no errors. I even injected the Thunderbolt DROM in the SSDT - same effect
I can try this later this evening or tomorrow morning. Some observations:
  • If a Thunderbolt device is connected to the Asus ThunderboltEX 3 during boot, the entire card becomes disabled.
  • If computer is booted with no TB devices connected, then all is well and hot-plug gets them connected.
  • This might be specific to this motherboard. Spent some time trying to find a solution, but will try again later.
 
Last edited:
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
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.

Screen Shot 2020-05-12 at 7.36.40 PM.png
 
Copy everything from the old drivers64UEFI folder to the new drivers/UEFI folder.
  • Open the new drivers folder (drivers/UEFI) and check that all the necessary drivers are present there.
    • What are the "necessary drivers"? They're the ones that are currently in the old drivers64UEFI folder.
  • Now we need to delete the old drivers64UEFI folder.
  • Reboot.
I just installed Clover_r5117.pkg and going further through your instructions, I notice that the (drivers/UEFI) directory already has those same drivers without the "-64" designation. Should those files be replaced with the ones in drivers64UEFI folder?
 

Attachments

  • Screenshot 2020-05-12 20.05.44.png
    Screenshot 2020-05-12 20.05.44.png
    92.9 KB · Views: 85
Hm... using FakeSMC stores few key values in NVRAM and I could not delete the "fakesmc-key-$Num-ui8" with these nvram -d and nvram -c commands nor flashing BIO did work. Only clearing the CMOS will delete it. Is there other way to delete some entries that won't delete besides clearing the CMOS?
 
I just installed Clover_r5117.pkg and going further through your instructions, I notice that the (drivers/UEFI) directory already has those same drivers without the "-64" designation. Should those files be replaced with the ones in drivers64UEFI folder?
The files in “drivers/UEFI” are actually the newer ones despite having shorter names so they should be retained. The older ones in “drivers64UEFI” can be deleted. The -64 suffix doesn’t make any difference.
 
For the sake of completeness, you will also need this ACPI rename:
  • Find: 5F453233
  • Replace: 58453233
  • Comment: _E23 --> XE23
I've also reattached the Thunderbolt SSDT.


In the case of Z170x-UD5 TH, I had to revert the MMBA method back to GPCB as I was getting ACPI errors in the boot log.

Code:
Method (MMBA, 1, Serialized)
        {
            Local0 = (\_SB.PCI0.GPCB () + 0x000E4000)
            OperationRegion (MMMM, SystemMemory, Local0, 0x24)
            Field (MMMM, DWordAcc, NoLock, Preserve)
            {
                Offset (0x19),
                SB19,   8,
                Offset (0x20),
                SB20,   32
            }

with this I get no ACPI errors and full TB tree.

Screen Shot 2020-05-12 at 11.32.34 PM.png
 
Hm... using FakeSMC stores few key values in NVRAM and I could not delete the "fakesmc-key-$Num-ui8" with these nvram -d and nvram -c commands nor flashing BIO did work. Only clearing the CMOS will delete it. Is there other way to delete some entries that won't delete besides clearing the CMOS?
Have you tried F11 from Clover Boot Menu?
 
In the case of Z170x-UD5 TH, I had to revert the MMBA method back to GPCB as I was getting ACPI errors in the boot log.

Code:
Method (MMBA, 1, Serialized)
        {
            Local0 = (\_SB.PCI0.GPCB () + 0x000E4000)
            OperationRegion (MMMM, SystemMemory, Local0, 0x24)
            Field (MMMM, DWordAcc, NoLock, Preserve)
            {
                Offset (0x19),
                SB19,   8,
                Offset (0x20),
                SB20,   32
            }

with this I get no ACPI errors and full TB tree.

View attachment 469159
Some questions:
  • If a TB device is connected before boot, does it remain connected after logging in?
  • Do TB devices reconnect after wake-from-sleep?
  • What is your BIOS version?
 
Last edited:
The files in “drivers/UEFI” are actually the newer ones despite having shorter names so they should be retained. The older ones in “drivers64UEFI” can be deleted. The -64 suffix doesn’t make any difference.
Thanks for the clarification. One thing about Hackintoshes is that even minute details mater, so while your guide is informative, these are the type of questions that arise regardless. You may want to add that caveat to your post so as to prevent further questions like mine. :) And THANK YOU!
 
Back
Top