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

[Elias64Fr]

When connecting my MBP with this system via a TB2->TB3 cable adapter in thunderbolt networking mode, the following is activated:
View attachment 455255

@augustopaulo

Good post for explain steps modifications

For this post, as we have to verifying if it really required to have a patched port 7 for thunderbolt networking > Do you have correct operating of Thunderbolt networking with an unpatched TDROM ?

 

[augustopaulo]

@augustopaulo

Good post for explain steps modifications

For this post, as we have to verifying if it really required to have a patched port 7 for thunderbolt networking > Do you have correct operating of Thunderbolt networking with an unpatched TDROM ?

You're right!
Without this TDROM injected data, no TB networking is created!

Below is without the custom TB3 SSDT:


And then with the custom TB3 SSDT:

 

[Elias64Fr]

Here we have different errors messages from IOThunderboltFamily related to DROM:

IOThunderboltEEPROM
IOThunderboltEEPROM:arseDROMData - Failed CRC8 Verification: 0x%x != 0x%x
IOThunderboltEEPROM:arseDROMData - Failed CRC32 Verification: 0x%x != 0x%x
IOThunderboltEEPROM:arseDROMData - overstepped buffer size!
IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Registry (0x%x)
IOThunderboltEEPROM::readDROMFromBuffer - Error getting DROM from I/O Registry (0x%x)
ThunderboltDROMEEPROMMacBookPro8,1MacBookPro8,2MacBookPro8,3MacMiniDROM Patched
IOThunderboltConfigWriteQuadletCommand
IOThunderboltConfigErrorCommand
IOThunderboltCallbackEventSource
IOThunderboltConfigPrepareToSleepCommand
IOThunderboltSwitchType4
IOThunderboltSwitchType4(0x%llx)::readEEPROMInternal - No DROM found. Using default Type 2.1 DROM. >> This is our future
statusIOPMDeepIdleSupported
IOThunderboltProtocolListener
IOThunderboltUserProtocolListener
IOThunderboltSwitchType3
IOThunderboltSwitchType3(0x%llx)::readEEPROMInternal - No DROM found. Using default Type 2.1 DROM.
Mac Pro I/O CardmodelFirmware Mode
NVM Loaded%s - UnsupportedTBTFlags
IONVRAM/optionstbt-options
IOThunderboltSwitchType2
IOThunderboltSwitchType2(0x%llx)::readEEPROMInternal - No DROM found. Using default Type 2 DROM.

 

[Elias64Fr]

About this damn error 0xE00002EB, I have found these log lines, I don't know if its related to our error :

2020-03-18 09:00:47.747138+0100 localhost kernel[0]: (AppleUserHIDDrivers) [IOUserUSBHostHIDDevice.cpp:752][0x1000003c4] CompleteInReport:0xe00002eb
2020-03-18 09:00:47.747142+0100 localhost kernel[0]: (AppleUserHIDDrivers) [IOUserUSBHostHIDDevice.cpp:670][0x1000003c4] Schedule retry reason:0xe00002eb count:9 deadline:8ms
2020-03-18 09:00:47.747401+0100 localhost kernel[0]: (AppleUserHIDDrivers) [IOUserUSBHostHIDDevice.cpp:752][0x1000003c3] CompleteInReport:0xe00002eb
2020-03-18 09:00:47.747404+0100 localhost kernel[0]: (AppleUserHIDDrivers) [IOUserUSBHostHIDDevice.cpp:670][0x1000003c3] Schedule retry reason:0xe00002eb count:9 deadline:8ms

 

[jb007]

Here we have different errors messages from IOThunderboltFamily related to DROM:

View attachment 455256​

IOThunderboltEEPROM
IOThunderboltEEPROM:arseDROMData - Failed CRC8 Verification: 0x%x != 0x%x
IOThunderboltEEPROM:arseDROMData - Failed CRC32 Verification: 0x%x != 0x%x
IOThunderboltEEPROM:arseDROMData - overstepped buffer size!
IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Registry (0x%x)
IOThunderboltEEPROM::readDROMFromBuffer - Error getting DROM from I/O Registry (0x%x)
ThunderboltDROMEEPROMMacBookPro8,1MacBookPro8,2MacBookPro8,3MacMiniDROM Patched
IOThunderboltConfigWriteQuadletCommand
IOThunderboltConfigErrorCommand
IOThunderboltCallbackEventSource
IOThunderboltConfigPrepareToSleepCommand
IOThunderboltSwitchType4
IOThunderboltSwitchType4(0x%llx)::readEEPROMInternal - No DROM found. Using default Type 2.1 DROM. >> This is our future
statusIOPMDeepIdleSupported
IOThunderboltProtocolListene
IOThunderboltUserProtocolListener
IOThunderboltSwitchType3
IOThunderboltSwitchType3(0x%llx)::readEEPROMInternal - No DROM found. Using default Type 2.1 DROM.
Mac Pro I/O CardmodelFirmware Mode
NVM Loaded%s - UnsupportedTBTFlags
IONVRAM/optionstbt-options
IOThunderboltSwitchType2
IOThunderboltSwitchType2(0x%llx)::readEEPROMInternal - No DROM found. Using default Type 2 DROM.

Hi @Elias64Fr and @CaseySJ.
So going by your comment “IOThunderboltSwitchType4(0x%llx)::readEEPROMInternal - No DROM found. Using default Type 2.1 DROM. >> This is our future ” can I read that if we can block the reading of the firmware then it should default to using a Apple generic software firmware, or is the plan to inject a modified firmware via a SSDT that will use this default Type 2 DROM.

If it cant find the hardware firmware then my Designare board that is now missing its chip should work! Of course I planed this all along!

On another note my replacement Designare has arrived, so I plan to install that later tomorrow.
I have at my disposal both the Designare and also a Titan an Alpine ridge and a MacBook Pro 2019 13” so I’m willing to help where possible. What is not clear to me is what if any changes have to be made to the Ridges firmware and what SSDTs to use. I understand this is all happening so fast and things are changing which is why I’m a little unsure where to start.

 

[Bobby22]

This might be easy to fix:

• First follow the procedure in Designare owner's manual to perform a CMOS Reset. You can use a flathead screwdriver to short the two designated pins. Again, please refer to manual.
• This will reset the memory map and also reset all BIOS parameters to factory defaults. So configure BIOS once again, starting with Load Optimized Defaults.
• If you unlocked the MSR 0xE2 register, it will most likely have to be unlocked again. But if you did not do this, then no problem. Continue to next step.
• Now try booting macOS.
• Let me know if "+++++" still appears.

Thank you very much for your help. As a Doctor, I haven't much time to spend on it on these times... Hopefully you are here <3.

1) I Used a Flathead Screwdriver to Reset the Bios and got the message "Bios has been reset". I loaded Optimized Defaults and then Setup the Bios again as advised (Running F8 Firmware).
2) But, The Bios settings were still saved (Got my Profile 1 still saved).
3) I tried to Boot on the USB EFI (MSR EFI) To change the MSR 0xE2 with the guide you gave us : which I did in the past to enable Native Nvram.
This was unsuccessful I can't boot on the UEFI USB (MSR-EFI one) : it just reloads the "Select Boot Device Screen".
(I double checked and everything is at the right position on the USB EFI partition). Can't boot whether I put CSM on or OFF, Whether I Put WinOs/Other Os.

4) I tried removing the Motherboard Battery, then CMOS reset (FlatScrew), then putting back the Battery. When I Put back the Battery the bios settings are still saved (Windows Boot Manager still appear/Clover Boot Manager also (which I added with EasyUEFI on Windows) (how ??? do I have to wait 12h without the Motherboard's Battery ?).
So I tried again to Load Optimized Default, set everything in the bios. Can"t boot on the USB (MSR UEFI one) again. (Tried to Boot on the EFI part, then on the non UEFI part : nothing works)

I Still can boot on windows and cloverBootManager but not on the MSR EFI.

Do i have to Flash the Bios ?
Thank you very much.

 

[Elias64Fr]

Hi @Elias64Fr and @CaseySJ.
So going by your comment “IOThunderboltSwitchType4(0x%llx)::readEEPROMInternal - No DROM found. Using default Type 2.1 DROM. >> This is our future ” can I read that if we can block the reading of the firmware then it should default to using a Apple generic software firmware, or is the plan to inject a modified firmware via a SSDT that will use this default Type 2 DROM.

If it cant find the hardware firmware then my Designare board that is now missing its chip should work! Of course I planed this all along!

On another note my replacement Designare has arrived, so I plan to install that later tomorrow.
I have at my disposal both the Designare and also a Titan an Alpine ridge and a MacBook Pro 2019 13” so I’m willing to help where possible. What is not clear to me is what if any changes have to be made to the Ridges firmware and what SSDTs to use. I understand this is all happening so fast and things are changing which is why I’m a little unsure where to start.

Hi @jb007

ThunderboltSwitchType4 is our future included thunderbolt on CPU (IceLake by Intel).
This kind of Error is, unfortunately about DROM only, not whole firmware We can do anything about this interpretation (Type 2.1 DROM)

You can tell to @augustopaulo @S1lla , he has around 100 blank FlashROM chip

Thanks, all kind of help is evidently welcome !

We are working on a simple way for an SSDT/Firmware patch .. for now you could look at @CaseySJ previous posts

 

[Elias64Fr]

@CaseySJ

As we are talking about an SSDT ready to play, I have prepared (not lunch but )a basic SSDT for enabling Link status to 0x101 (normal state) instead of 0x7 (disconnected) :

This can be used as a base of the final one.
We have to disabling _E17 to XE17 before use it but not tested if it is really required so I have it like that for now.
And also renaming RP05.PXSX to RP05.UPSB on our favourite boot loader

 

[tpep]

I am using the XFX Radeon VII. I was a bit weary, as I've heard some really bad things about compatibility with XFX products on Hackintoshes, but I've had zero issues since swapping over to this card. In my research, *all* the Radeon VII's are reference cards, so they should all function the same. I'm shocked at the price differences between brands, if this is truly the case.

Worst case scenario, I was expecting to try flashing a different manufacturer's BIOS to this card, OR use Clover to inject it if there were any issues. However, the card was working flawlessly for me on Catalina. I have since reinstalled and downgraded to Mojave to get a bit more stable/compatible environment for audio production though and again, no issues using it on 10.14.6.

@jleahy2 My story so far. Got a Sapphire Radeon VII (used) on Ebay. Unfortunately the card was faulty and couldn't even post! Had to return it. At least got my money back. Since then I've tried to find another Sapphire Radeon VII but was unlucky. It is very hard if not impossible to get one now days. So I am contemplating whether a choice of going with an XFX or Gigabyte (or any other of the available brands) is too risky OR is it safer going with something more trustworthy like the Sapphire Vega64?

 

[Elias64Fr]

@CaseySJ and all other interested by this adventure !

I'm happy to announce that if you boot to macOS before Windows, connect your thunderbolt device and then make a simple reboot to Windows, this make Thunderbolt device operating

But If you revert to macOS, there might be some troubles That's what happen when you want to switch to another OS than our favourite macOS

That's all !