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

[tpep]

Yes, my backup plan was to try to attempt to use Clover injection, then my backup-backup option was to attempt to flash the BIOS from a Sapphire card over. I have read that this *may or may not* work though. Evidently, it working or not depends upon the some of the components used in the card. I think that was more of a Vega64 issue, than a Radeon VII issue though (again, they're all supposed to be reference cards). Neither of which I was real enthused about, but def wanted to research my options.

I honestly think you'll be fine either way you go. Both of these cards seem well supported at this point, but there is no denying that XFX can sometimes be problematic on Hackintosh setups. I can honestly say, I've experienced no issues with mine though. If this wasn't a reference based card design, I definitely would not have even attempted an XFX card though. I rolled the dice.

@jleahy2 Ok thanks. I've ordered a new XFX Radeon VII from Amazon. We'll see how it goes.

 

[Elias64Fr]

Hi @Elias64Fr, I tried the file modified firmware but was unsuccessful with the Thunderbolt Bus Activation. Is there something else I can try ?

@mango1122
Before patched firmware testing, you have to see if GPIO3FrPwr is OK then not using any SSDT thunderbolt related (first step of SSDT only without patching modify registers content .. that is why we don't use it).It doesn't matter if we have PXSX instead of UPSB, and no other sub-devices naming.
Flash firmware, shutdown, switch off power supply for 1 minute, switch on, boot to macOS and then verify under IOReg if you have full thunderbolt tree and XHC2 (not named like that) part populated.

 

[CaseySJ]

@scottkendall Why do you use the Designare Firmware on the AIC Card?
Does the NVM23 version by @Elias64Fr for the PCIe card doesn't work correctly on your Build ?

@Elias64Fr : Could you maybe take a look at this firmwares and edit the magical 7 Bytes on it also ?
Would be awesome and thanks for all the hard work you guys did on this and still do

The Asus UX550 firmware is NVM 33, but it may be Alpine Ridge instead of Titan Ridge. Anyway, attached ZIP contains two slightly different modifications of the Asus TB3 firmware. If you can comfortably read/write to the Asus chip, then please try each one and be prepared to flash the original back in case of problem.

No guarantee that either of the mods will work...

 

[S1lla]

Will show results after work! @CaseySJ @Elias64Fr

Thanks guys

 

[faithie999]

I know all (at least most of) the excitement here is about the Designare TR onboard chip, but...

UPS man is on the way today with my GC-Alpine Ridge and flashing clip, in hopes that Alpine will recognize my TB1 hard disk dock.

my plan is:
In windows, install the drivers that come with the card, then install the card in windows and see what I get.
then I will warm boot into Catalina and see what I get.

assuming not everything (maybe nothing) is working, I will add the SSDT(s) for alpine. would someone be kind enough to recommend the SSDT(s) I should try? (I have the Z390 Aorus Pro, which has the THB_C header).

then assuming less than full functionality, I will flash the card using the mini-guide. which ROM should I flash onto the TB chip?

thanks in advance!!

 

[CaseySJ]

...
- I put it as 0X01 since my mobo has the built in alpine ridge+just wanted to see what would happen.
- Whatever is in the attached SSDT.
- Z170X-Designare with 10.15.3.

/* 0000 */ 0xE1, 0x01, 0x02, 0x10, 0x03, 0x23, 0x33, 0x00, // .....#3.
/* 0008 */ 0x00, 0xBF, 0x6B, 0xDA, 0x44, 0x01, 0x58, 0x00, // ..k.D.X.
/* 0010 */ 0x01, 0x00, 0x0D, 0x00, 0x01, 0x08, 0x08, 0x81, // ........
/* 0018 */ 0x80, 0x02, 0x80, 0x00, 0x00, 0x00, 0x08, 0x82, // ........
/* 0020 */ 0x90, 0x01, 0x80, 0x00, 0x00, 0x00, 0x08, 0x83, // ........
/* 0028 */ 0x80, 0x04, 0x80, 0x01, 0x00, 0x00, 0x08, 0x84, // ........
/* 0030 */ 0x90, 0x03, 0x80, 0x01, 0x00, 0x00, 0x05, 0x85, // ........
/* 0038 */ 0x50, 0x00, 0x00, 0x05, 0x86, 0x50, 0x00, 0x00, // P....P..
/* 0040 */ 0x02, 0x87, 0x0B, 0x88, 0x20, 0x01, 0x00, 0x64, // .... ..d
/* 0048 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x03, 0x89, 0x80, // ........
/* 0050 */ 0x05, 0x8A, 0x50, 0x40, 0x00, 0x05, 0x8B, 0x50, // [email protected]
/* 0058 */ 0x40, 0x00, 0x0B, 0x01, 0x47, 0x49, 0x47, 0x41, // @...GIGA
/* 0060 */ 0x42, 0x59, 0x54, 0x45, 0x00, 0x11, 0x02, 0x47, // BYTE...G
/* 0068 */ 0x43, 0x2D, 0x54, 0x49, 0x54, 0x41, 0x4E, 0x20, // C-TITAN
/* 0070 */ 0x52, 0x49, 0x44, 0x47, 0x45, 0x00 // RIDGE.
},

"ThunderboltConfig",
Buffer (0x20)
{
/* 0000 */ 0x00, 0x02, 0x1C, 0x00, 0x02, 0x00, 0x05, 0x03, // ........
/* 0008 */ 0x01, 0x00, 0x04, 0x00, 0x05, 0x03, 0x02, 0x00, // ........
/* 0010 */ 0x03, 0x00, 0x05, 0x03, 0x01, 0x00, 0x00, 0x00, // ........
/* 0018 */ 0x03, 0x03, 0x02, 0x00, 0x01, 0x00, 0x02, 0x00 // ........
},

In this Quick Comparative Analysis we did a few days ago, we found that the first byte of ThunderboltConfig is the Bus ID. So if you change the Bus ID in ThunderboltDROM to 0x01 (byte #2 in red), please change byte #1 in ThunderboltConfig (green byte) to 0x01 as well, and see if you still see 4 ports.

 

[Lesabendio]

It works!!

Just installed Windows 10 Build 1903 (May 2019 Feature Update):

• Windows NVMe installed in the top M2M slot
• Mojave NVMe installed in the bottom M2P slot

With this configuration, the Windows installer does not interfere with Clover or EFI partition on the Mojave SSD.

Hi, thanks for this amazing workaround, it works fine !

Nevertheless, I'm still a newbie and I am looking for instructions to install Windows 10 without interfering with MacOS. I didn'i get the thing with M2M or M2P

Do you know where I could find a tutorial ? (Important : I choose to enable native NVRAM)

 

[CaseySJ]

Hi, thanks for this amazing workaround, it works fine !

Nevertheless, I'm still a newbie and I am looking for instructions to install Windows 10 without interfering with MacOS. I didn'i get the thing with M2M or M2P

Do you know where I could find a tutorial ? (Important : I choose to enable native NVRAM)

Please see Tips for Installing Windows 10 in the spoiler on Post #1:

 

[Lesabendio]

Please see Tips for Installing Windows 10 in the spoiler on Post #1:

View attachment 455514

Thanks for your answer, I read this spoiler actually, but I didn't understand how I should procede for the installation.

I only have one SSD (Samsung SSD 970 EVO 1TB), what is the M2M slot ? If I just create a FAT32 partition in order to install W10, is it ok ? Or should I use Bootcamp ?

 

[CaseySJ]

@Elias64Fr,

I would like to create a Thunderbolt DROM Micro-Guide for GC-Alpine Ridge. The DROM inside the firmware is as follows:

AD100000 00000086 8020A1E3 C9006600
ED001980 01010881 80028000 00000882
90018000 00000883 80048001 00000884
90038001 000002C5 0B866001 00640000
00000003 87800588 00000002 C9058A50
000002CB 02CC0B01 47494741 42595445
00120247 432D414C 50494E45 20524944
474500

This is my attempt to decode it:

• AD — CRC-8
• 10000000 00008680 — UID (Bus ID 0x10?)
• 20A1E3C9 — CRC32_C
• 006600ED 00198001 01 — Make/Model Identifier
• 08818002 80000000 — TBPort 1 / DualLink Port 2 / HPMAddr 0
• 08829001 80000000 — TBPort 2 / DualLink Port 1 / HPMAddr 0
• 08838004 80010000 — TBPort 3 / DualLink Port 4 / HPMAddr 1
• 08849003 80010000 — TBPort 4 / DualLink Port 3 / HPMAddr 1
• 02C5 — TBSwitch 5
• 0B866001 00640000 000000 — TBPort 6 / PCI Down Adapter DSB1
• 038780 — TBPort 7 / PCI Down Adapter DSB4
• 05880000 00 — TBPort 8 / DisplayPort or HDMI?
• 02C9 — TBSwitch 9 ?
• 058A5000 00 — TBPort A / DisplayPort or HDMI?
• 02CB — TBSwitch B ?
• 02CC — TBSwitch C ?
• 0B014749 47414259 544500 — “GIGABYTE”
• 12024743 2D414C50 494E4520 52494447 4500 — “GC-ALPINE RIDGE”

Some things look strange...

• It seems there is TBSwitch 5, TBSwitch 9, TBSwitch B, and TBSwitch C.
• On Titan Ridge, we only enable TB Switch 7, so the question for GC-Alpine Ridge is:
  • Should we only change 02C5 to 0285?
  • Or change them all like this?
    • 02C5 --> 0285
    • 02C9 --> 0289
    • 02CB --> 028B
    • 02CC --> 028C
• This card contains an HDMI port, so that might explain the need for an additional switch or two.
• HDMI port is shared with Thunderbolt Port #1.
  • When DP-IN #1 is connected, then user can choose either Thunderbolt Port #1 or HDMI (not both).
  • DP-IN #2 will only drive Thunderbolt Port #2.