Contribute
Register

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

Thanks! :)

Unfortunately, they are blinking RED in all my connection attempts...

Also, I've measured 5Vdc on the CH341a pins, so that could also be the problem....

It's almost 01h00 here in the UK, and I do have a RaspberryPi 4B, so I'll try to use that instead for reading this onboard TB3 chip tomorrow morning.;)

Good night all!
Yes, please use the Raspberry Pi... Good night!
 
Because en0 exists, have you tried any of the following:
  • Deleting /Library/Extensions/SystemConfiguration/NetworkInterfaces.plist and rebooting?
  • Ensuring that ROM field in OpenCore config.plist uses MAC address of en0?
  • Clearing NVRAM now that NVRAM is working?


-There is no SystemConfiguration folder in my Library at all. (searched in Root Library, User Library and System Library)
-Yes I found the MAC address from the Bottom Ethernet port, the one closest to audio jacks. Intel I219. It's the only one I use and I found it in Settings>Network>Ethernet>Advanced..>Hardware>MAC address
-Cleared NVRAM both with sudo nvram -c and Reset NVRAM option from Picker.
-Turned Location services ON

Login problem remains on FaceTime and Messages. (Tried two separate fresh accounts made for this Hackintosh)
 
@CaseySJ

Next level is to modify ThunderboltDROM including CRCs to enable Port 7, It will probably required for network through Thunderbolt.

I still don't understand how Apple CRC8 operate despite all CRC calculators found on web !

Here a sample from an iMac 18,3 :
UUID extracted from DROM is 00 c6 7a cc 18 fb 01 00 (0x0001FB18CC7AC600)
and related CRC8 is 9d :|
 
@CaseySJ

Next level is to modify ThunderboltDROM including CRCs to enable Port 7, It will probably required for network through Thunderbolt.

I still don't understand how Apple CRC8 operate despite all CRC calculators found on web !

Here a sample from an iMac 18,3 :
UUID extracted from DROM is 00 c6 7a cc 18 fb 01 00 (0x0001FB18CC7AC600)
and related CRC8 is 9d :|
Yes exactly -- this affects Thunderbolt Bus ID and if we use the ThunderboltDROM from the firmware, we get better Thunderbolt reliability. So this is going to be somewhat important.
 
Last edited:
Please try this SSDT for GC-Titan Ridge. It's using RP05 so just make the necessary change for your PCI path. This one uses correct ThunderboltDROM.

EDIT: Also attached is the modified GC-Titan Ridge firmware for NVM43.

EDIT 2: If your System Information --> Thunderbolt page shows two Thunderbolt buses with the same Bus Number, please use the newly uploaded SSDT instead: SSDT-TBOLT3-RP21-GC-TITAN-RIDGE-APPLE-DROM.aml

I tried both of your SSDT and both of them did not work well in my system. However, using the SSDT that I have been using seems to work well. I really not know what the difference is, but when I use yours the tree is there but devices do not attach. : /

Update: Seems the EGPU does not know how to eject on the Titan ridge & sleep but USB is working, I am not sure if the EGPU worked correctly with the DSM2 Firmware either.
 
Last edited:
I did see that. and Ill try again, but like I said, im not getting 'dim' lights. they are either on or they are off. :/
I had my Raspberry pi set up for flashing the TitanRidge and Alpine Ridge cards. Should be the same pin-out for flashing the winbond on the motherboard right?
Have you tried the "wiggle" suggestion? It takes practice. The LEDs will dim if we gently wiggle the clip away.
 
Last edited:
Yes exactly -- this affects Thunderbolt Bus and if we use the ThunderboltDROM from the firmware, we get better Thunderbolt reliability. So this is going to be somewhat important.
Sure we stay with all Designare TDROM port configuration except for port 7 > 0x02C7 should be moved to 0x02B7 to enable it. It is not required that new TDROM is flashed but only as a property :) .. You can test that by extracting it from a real iMac19,1 (IOReg found on web)
 
@CaseySJ

Next level is to modify ThunderboltDROM including CRCs to enable Port 7, It will probably required for network through Thunderbolt.

I still don't understand how Apple CRC8 operate despite all CRC calculators found on web !

Here a sample from an iMac 18,3 :
UUID extracted from DROM is 00 c6 7a cc 18 fb 01 00 (0x0001FB18CC7AC600)
and related CRC8 is 9d :|
Linux has a couple of CRC functions that seem very difficult to read. They are used by the Thunderbolt driver for sending packages on the transmit ring.

Please see:
  • drivers/thunderbolt/eeprom.c
  • drivers/thunderbolt/ctl.c
 
Last edited:
Have you all tried running your cards with Thunderbolt disabled in bios? It works for me on a different setup.
 
Have you tried the "wiggle" suggestion? It take practice. The LEDs will dim if we gently wiggle the clip away.


Yeah I tried that. I cant get it to work. The pi keeps crashing on me as I wiggle it, and I can never seem to get the leds "dim".. just on or off.

I may have to wait for a different solution. :/
 
Back
Top