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

[snakePanda]

I think what Caseysj was recommending was to try the Fenvi in the bottom LONG slot, not the bottom x1 slot.

Yes I know, I said that I also tried the bottom long slot that it is a PCI X4 and same result.

Thanks!

Is the original WiFi module plugged in, or still removed? If it’s plugged in, then Windows is probably using it instead of the Fenvi.

Have you tried rebooting the router and also checking to see whether it might be blocking or restricting any MAC addresses?

I've tried both, with original WiFi module plugged in and without it. Windows is using Fenvi card. Router rebooted and no blocking any MAC. I assume that it is a incompatibility within my router and the Fenvi card with macOS, but dont know why it works on Windows.

EDIT: Using OpenCore it works! Can I use it as a dialy bootloader? Thunderbolt will also work with OpenCore?

Thanks!

 

[Lensjocky]

Casey,

I'm Enabling Native NVRAM on my system.

When I "Remove Clover RC scripts (if installed) by typing these commands in Terminal: (be very careful)"
the terminal comes back at me with "File not found" on all of the RC Scripts. Must I change directory in the terminal before executing those commands? If so to what volume and directory? I'm certain the RC Scripts are installed on my system. There's not a clear explanation of removing these RC SCRIPTS that I could find anywhere.

Also if I have been successful will the "nvram.plist" file reappear in my EFI Partition after I've deleted it?

Thanks for your guidance.

Alright I looked into the hidden /etc directory and I can confirm the "RC Scripts" files in question are not there. So strange as I could have sworn I installed them.

 

[MrNobody112233]

it seems USB ports only turn on when a USB device is connected to them during boot. On the other hand, Thunderbolt devices only connect when hot-plugged.

Did you expect something different?
First of all there is the point that the Thunderbolt chip is not on the card of the MacPro but on the logicboard and therefore the injection process is very different from a hackintosh.

We have to help with SSDT to make something happen.

In terms of function the slot is not irrelevant, in my case the USB controller is only continuously loaded if the card is in a matching slot and the correct ThunderboltConfig is set in the SSDT.

If not : the Thunderbolt ports don't load the full tree or something will not work correctly.

 

[CaseySJ]

Casey,

I'm Enabling Native NVRAM on my system.

When I "Remove Clover RC scripts (if installed) by typing these commands in Terminal: (be very careful)"
the terminal comes back at me with "File not found" on all of the RC Scripts. Must I change directory in the terminal before executing those commands? If so to what volume and directory? I'm certain the RC Scripts are installed on my system. There's not a clear explanation of removing these RC SCRIPTS that I could find anywhere.

Also if I have been successful will the "nvram.plist" file reappear in my EFI Partition after I've deleted it?

Thanks for your guidance.

@Lensjocky,

The commands are already using full pathnames so no need to change directory. If the result is File not Found then you're okay. It means RC scripts were not installed.

When native NVRAM is installed, then "nvram.plist" will no longer be created or updated.

P.S. Please do not quote the entire mini-guide as stated in boldface in the 2nd line.

 

[CaseySJ]

Yes I know, I said that I also tried the bottom long slot that it is a PCI X4 and same result.

Thanks!



I've tried both, with original WiFi module plugged in and without it. Windows is using Fenvi card. Router rebooted and no blocking any MAC. I assume that it is a incompatibility within my router and the Fenvi card with macOS, but dont know why it works on Windows.

EDIT: Using OpenCore it works! Can I use it as a dialy bootloader? Thunderbolt will also work with OpenCore?

Thanks!

Strange, but good to know. By the way, what version of Clover were you using?

OpenCore can be used as the daily boot loader. Thunderbolt will work as long as Thunderbolt SSDT is specified in OpenCore config.plist.

 

[CaseySJ]

Did you expect something different?
First of all there is the point that the Thunderbolt chip is not on the card of the MacPro but on the logicboard and therefore the injection process is very different from a hackintosh.

We have to help with SSDT to make something happen.

In terms of function the slot is not irrelevant, in my case the USB controller is only continuously loaded if the card is in a matching slot and the correct ThunderboltConfig is set in the SSDT.

If not : the Thunderbolt ports don't load the full tree or something will not work correctly.

Are you DSM2 by any chance?

These are the test conditions:

• Gigabyte Designare Z390 board (Hackintosh with SMBIOS iMac19,1)
• This board has Titan Ridge controller built-in, on RP05. A different SSDT is being used for RP05.
• GC-Titan Ridge in bottom long slot. It's not immediately clear whether that would be Slot 3 or Slot 5 or something else.
• For the GC-Titan Ridge, a customized SSDT is being used (RP21) to avoid conflict with built-in controller.
• In the SSDT we specify ThunderboltDROM and ThunderboltConfig as device properties injected via NHI0._DSM().
• When you say "...the correct ThunderboltConfig is set..." are you referring to the ThunderboltConfig device property in NHI0.DSM() or to the overall SSDT?

 

[CaseySJ]

Hey @CaseySJ , thanks for you advice. I have a problem at the step 3 of the Catalina back-up, I put the terminal notes in attached files. Could you help me ? I don't see the step with the log messages...

Please try @byteminer's latest script from the link below. This is a much improved version and works just fine under Catalina. I plan to delete EFIClone-v4.sh from the two Bootable Back mini-guides and instead provide links to @byteminer's GitHub repository.

GitHub - kobaltcore/EFIClone: macOS Shell Script to automatically clone the EFI partition from either Carbon Copy Cloner or SuperDuper! when run on a Hackintosh.

macOS Shell Script to automatically clone the EFI partition from either Carbon Copy Cloner or SuperDuper! when run on a Hackintosh. - kobaltcore/EFIClone

github.com

 

[scottkendall]

After further tests with the GC-Titan Ridge running DSM2.Hackintosh firmware on Z390 Designare, it seems USB ports only turn on when a USB device is connected to them during boot. On the other hand, Thunderbolt devices only connect when hot-plugged.

Try the SSDT I sent you yesterday to look at: I have Hot/Cold Plug on all my TB2/TB3 devices "nothing needs to be plugged at boot", sleep as long as nothing is plugged into the Titian Ridge, No USB at all. I do not have the USB connected from the header to the Ridge. Maybe you can use a little bit of what ever is in that one to help you with the needing to be pugged to get hot plug.


Not really sure about the slot issue it never seems to affect the behavior on my system.

 

[qthegaijin]

Are you DSM2 by any chance?

These are the test conditions:

• Gigabyte Designare Z390 board (Hackintosh with SMBIOS iMac19,1)
• This board as Titan Ridge controller built-in, on RP05. A different SSDT is being used for RP05.
• GC-Titan Ridge in bottom long slot. It's not immediately clear whether that would be Slot 3 or Slot 5 or something else.
• For the GC-Titan Ridge, a customized SSDT is being used (RP21) to avoid conflict with built-in controller.
• In the SSDT we specify ThunderboltDROM and ThunderboltConfig as device properties injected via NHI0._DSM().
• When you say "...the correct ThunderboltConfig is set..." are you referring to the ThunderboltConfig device property in NHI0.DSM() or to the overall SSDT?

Awesome work!

- For your customized SSDT to avoid conflict, was it just adjusting the RP values or was there more that was needed to change?
- Here are some errors I pulled from Log regarding the Antelope Audio drivers loading on the Modified TR card, both on a real Mac Pro 5,1 and my Z170X Hackintosh. Curious what your thoughts are and if SSDT edits will be the trick to fixing these errors:

WORKING:

Timestamp                       Thread     Type        Activity             PID 
2020-03-06 18:25:12.606386-0800 0x110      Default     0x0                  0      kernel: (AntelopeUnifiedDriver) Antelope Thunderbolt Audio (Version:3.30 Build:901dc5c 2019-07-30/11:27): starting for device 1d4b a140
2020-03-06 18:25:12.914444-0800 0x110      Default     0x0                  0      kernel: (AntelopeUnifiedDriver) AntelopeAudioDevice::setPluginPartition() -- partition 0 32 32 --> 00000000
2020-03-06 18:25:18.337492-0800 0x1d0      Default     0x0                  0      kernel: (AntelopeUnifiedDriver) AntelopeTBAudioDevice/247: warning: user-client failed to start
2020-03-06 18:25:37.767099-0800 0x113      Default     0x0                  0      kernel: (AntelopeUnifiedDriver) AntelopeTBUserClient/331: error: user-client send message 0000000a failed e00002db (once)

NOT WORKING:

Timestamp               Ty Process[PID:TID]
2020-03-06 17:26:02.124 Df kernel[0:197] (AntelopeUnifiedDriver) Antelope Thunderbolt Audio (Version:3.30 Build:901dc5c 2019-07-30/11:27): starting for device 1d4b a140
2020-03-06 17:26:02.327 Df kernel[0:1de] (AntelopeUnifiedDriver) AntelopeTBMessageChannel: max DMA stall 25
2020-03-06 17:26:02.327 Df kernel[0:1de] (AntelopeUnifiedDriver) AntelopeTBMessageChannel/207: error: Timeout waiting for DMA completion
(once)
2020-03-06 17:26:02.327 Df kernel[0:1de] (AntelopeUnifiedDriver) AntelopeTBMessageChannel/440: error: Timeout waiting for DMA message header
(once)
2020-03-06 17:26:05.040 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/882: error: error getting device info
2020-03-06 17:26:05.040 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/785: error: failed to read device info
2020-03-06 17:26:10.041 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/924: error: no reply getting channel info
2020-03-06 17:26:10.041 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/791: error: failed to read channel info
2020-03-06 17:26:10.041 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeAudioDevice::setPluginPartition() -- partition 0 -1 -1 --> 00000000
2020-03-06 17:26:15.041 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/1011: error: device failed to return sample rates
2020-03-06 17:26:15.041 Df kernel[0:197] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/800: error: failed to read sample rate ranges
2020-03-06 17:26:20.175 Df kernel[0:954] (AntelopeUnifiedDriver) AntelopeTBAudioDevice/705: error: error getting sample rate 0x0 0 0
2020-03-06 17:26:20.176 Df kernel[0:954] (AntelopeUnifiedDriver) AntelopeTBEngine/856: error: failed to set format <private> -> e00002c2
2020-03-06 17:26:20.176 Df kernel[0:954] (AntelopeUnifiedDriver) AntelopeTBEngine/856: error: failed to set format <private> -> e00002c2

 

[rj510]

UPDATE:

• DSB2 is correctly identifying itself as Device-ID 0x15EA.
• Device-ID 0x15EC is the XHC controller, which is a sub-device of DSB2.

Sorry for confusion. The observation of DSB4 being expanded was NOT due EC150000 injection, but due to simply a warm re-boot using "Restart...". The injection was only co-incidental and not causal. Experimenting this morning on another build clarified this issue.

DSB1-4 only expand when something is connected with a warm re-boot, not a cold startup, with devices already connected from the initial boot.

Although, on initial boot, SystemInfo/Thunderbolt shows the Thunderbolt Bus with all items connected (but not functional). However, there is no "Thunderbolt Device Tree at the top in its own pane. This Thunderbolt Device Tree, pane at the top, only appears in the window on the warm re-boot, when the TB connected devices finally connect and are usable (see spoiler from the X299 build with a NVM 23 flashed GB Titan Ridge PCIe card; pins 3,5 shorted).

Spoiler: TB Bus After Warm Re-boot

In reading recent comments, we must then not have things in the correct slot (which may be tricky on mobos without a TB header) or an inaccurate ThunderboltDROM?