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

[Elias64Fr]

Hi @Elias64Fr,

Let's use this as reference:

• 71 -- CRC (cyclic redundancy check)
• 00 11 22 33 44 55 ED 00 -- UID SwitchType3: ED000000000000
• E0 -- CRC
• 40 34 98 01 69 00 ED 00 -- To be defined
• 08 C0 01 01 -- To be defined

Based on your screenshot and my previous post, is it correct to revise this as follows?

• 71 -- CRC8 (cyclic redundancy check)
• 00 11 22 33 44 55 ED 00 -- UID SwitchType3: ED000000000000
• E0 40 34 98 -- CRC32
• 01 69 00 ED 00 -- To be defined
• 08 C0 01 01 -- To be defined

Where:

• 71 -- CRC8
• 00 -- Thunderbolt Bus ID
• 11 22 33 44 55 -- 5-byte UID (7-byte UIDs are also possible)
• ED -- Unknown
• 00 -- Unknown, but could be a null-termination character
• E0 40 34 98 -- CRC32
• 01 69 00 ED 00 -- To be defined
• 08 C0 01 01 -- To be defined

With some little correction if you allow me:

Based on your screenshot and my previous post, is it correct to revise this as follows?

• 71 -- CRC8 (cyclic redundancy check)
• 00 11 22 33 44 55 ED 00 -- UID SwitchType3: ED000000000000
• E0 40 34 98 -- CRC32
• 01 69 00 ED 00 08 C0 01 01 -- To be defined

Where:

• 71 -- CRC8
• 00 -- Thunderbolt Bus ID (part of UID)
• 11 22 33 44 55 -- 5-bytes UID (part of UID)
• ED 00 -- Part of UID (header?)
• E0 40 34 98 -- CRC32
• 01 69 00 ED 00 08 C0 01 01 -- To be defined (seem to be a fixed value by PciThunderbolt.efi driver)

 

[Elias64Fr]

I have updated my previous post

 

[CaseySJ]

With some little correction if you allow me:

Interesting! Now we just need to confirm the assumption about the 9-byte "fixed value". Do you have these values for Mac Pro 7,1?

• 71 -- CRC8 (cyclic redundancy check)
• 00 -- Thunderbolt Bus ID (part of UID)
• 11 22 33 44 55 -- 5-Byte UID (part of overall UID)
• ED 00 -- Part of UID (header?)
• E0 40 34 98 -- CRC32
• 01 69 00 ED 00 08 C0 01 01 -- Possibly fixed values assigned by PciThunderbolt.efi driver

Some real examples of those last 9 bytes:

• 01 58 00 01 00 10 00 01 00 Mac Pro 7,1
• 01 58 00 01 00 0d 00 01 00 iMac 19,1
• 01 58 00 01 00 0d 00 01 00 MacBook Pro 15,2

The binary representations of 10 and 0d are:

• 0001 0000
• 0000 1101

This might be a bit field (just an assumption).

 

[mango1122]

• It's okay not to use SSDT for now.
• With original firmware, does Thunderbolt appear on RP21?
• Is "Force Power" still enabled in BIOS?
• Just to be clear, we're talking about on-board Alpine Ridge controller (not add-in-card)?

Hi Casey -

• Ok
• Yes TB appears under RP21 in the original firmware
• GPIO3 Force Pwr is enabled - please see attached screenshot,
• Yes - this is the on board Alpine Ridge Controller

 

[CaseySJ]

Hi Casey -

• Ok
• Yes TB appears under RP21 in the original firmware
• GPIO3 Force Pwr is enabled - please see attached screenshot,
• Yes - this is the on board Alpine Ridge Controller

So unfortunately the modified firmware is not working. Back to the drawing board.

 

[Elias64Fr]

Interesting! Now we just need to confirm the assumption about the 9-byte "fixed value". Do you have these values for Mac Pro 7,1?

• 71 -- CRC8 (cyclic redundancy check)
• 00 -- Thunderbolt Bus ID (part of UID)
• 11 22 33 44 55 -- 5-Byte UID (part of overall UID)
• ED 00 -- Part of UID (header?)
• E0 40 34 98 -- CRC32
• 01 69 00 ED 00 08 C0 01 01 -- Possibly fixed values assigned by PciThunderbolt.efi driver

@CaseySJ

Unfortunaly, I can't extract EFI Firmware of MacPro7,1 because of T2 Chip as we know to confirm this on this Mac. But I can see on previous model like iMac18,3 that don't not include TDROM on thunderbolt EFI driver but on FreeForm file with 5E7BE016-33CF-2D42-8758-C69FA5CDBB2F GUID

As we can see here :

 

[phrfpeixoto]

Please note that Forum Rules prohibit the use of self-identifying photos in your profile.

---

View attachment 455087

I really don't get why, since we upload the photos ourselves, in the sense that we chose to identify. But OK, I'm not here to make the rules. Sorry about that.

 

[CaseySJ]

@CaseySJ

Unfortunaly, I can't extract EFI Firmware of MacPro7,1 because of T2 Chip as we know to confirm this on this Mac. But I can see on previous model like iMac18,3 that don't not include TDROM on thunderbolt EFI driver but on FreeForm file with 5E7BE016-33CF-2D42-8758-C69FA5CDBB2F GUID

As we can see here :
View attachment 455102

I updated my previous post with real examples of those 9 bytes. You should look at that!

 

[Elias64Fr]

Interesting! Now we just need to confirm the assumption about the 9-byte "fixed value". Do you have these values for Mac Pro 7,1?

• 71 -- CRC8 (cyclic redundancy check)
• 00 -- Thunderbolt Bus ID (part of UID)
• 11 22 33 44 55 -- 5-Byte UID (part of overall UID)
• ED 00 -- Part of UID (header?)
• E0 40 34 98 -- CRC32
• 01 69 00 ED 00 08 C0 01 01 -- Possibly fixed values assigned by PciThunderbolt.efi driver

Some real examples of those last 9 bytes:

• 01 58 00 01 00 10 00 01 00 Mac Pro 7,1
• 01 58 00 01 00 0d 00 01 00 iMac 19,1
• 01 58 00 01 00 0d 00 01 00 MacBook Pro 15,2

The binary representations of 10 and 0d are:

• 0001 0000
• 0000 1100

This might be a bit field (just an assumption).

@CaseySJ

And YES it is confirmed

 

[CaseySJ]

@CaseySJ have you had similar reports? How to solve this?

I really don't get why, since we upload the photos ourselves, in the sense that we chose to identify. But OK, I'm not here to make the rules. Sorry about that.

Thanks for making the change. Now let's get back to your question...

I have not seen any reports of problems with the new VirtualSMC, Lilu, WhateverGreen, and AppleALC kexts. These are all produced by "acidanthera" and are in extensive use by hundreds or thousands of Hackintosh and Classic Mac Pro users. If these kexts were giving problems, there would be a lot of problem reports.

My recommendation is to double-check your Clover configuration and /Library/Extensions folder. If the problem cannot be easily identified, one should perform a fresh installation of macOS on a spare SSD. This takes only a few minutes, whereas trying to chase down a difficult problem can take days.

If the new fresh installation performs well, then we know the fault lies in the old installation. So next we can install our applications one by one into the new fresh installation, check for system stability, then install the next app, and so on until the new installation is ready to be used as the primary installation. After using this "new primary" disk for at least 1-2 weeks, if everything is normal, we can clone it to the original macOS SSD (but make a backup of the original SSD first).