Contribute
Register

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

The edited DSDT.aml loaded from Clover/ACPI/Patched still gets patched by whatever patches you have in config.plist.

I double-checked just now. The only patch in my config.plist is the SAT0 to SATA patch. An extract of my DSDT via MacIASL shows the patch having been applied.

Anyway, I did it this way because I think my board has a slightly different code for the GPE.TINI statements than the Designare, and the config.plist patch that you used didn't work for me. I'm not smart (or patient) enough to figure out what the patch needed to be for my board!

So, I guess "six of one, half dozen of another". haha.

As for your commas, I'm the king of the run-on sentence. My 7-th grade English teacher rolls over in her grave every time I write an overly-long sentence.

Thanks.

Right! Hey, it works for you. The patch was a good learning experience for what its worth.
 
@faithie999 @NorthAmTransAm

Is the boot delay really bothersome enough to justify killing \_GPE.TINI()?
No, but it's one of those "I do it because I can" things. I'll take the edited DSDT out of my Clover ACPI folder because you're right, there may be unintended consequences.

Thanks for the caution.
 
Feel free to post the following files:
  • Compressed CLOVER folder with serial numbers removed from config.plist.
  • Screenshot of /Library/Extensions
  • The output of this command in Terminal: ls -lR /etc/rc*
Here are the files requested:
Just added a geekbench, do you think that it's values corresponding to my setup? Thanks again.
 

Attachments

  • CLOVER copy.zip
    2.9 MB · Views: 84
  • Capture d’écran 2020-03-25 à 10.40.38.png
    Capture d’écran 2020-03-25 à 10.40.38.png
    136.3 KB · Views: 87
  • Capture d’écran 2020-03-25 à 10.39.48.png
    Capture d’écran 2020-03-25 à 10.39.48.png
    148 KB · Views: 87
  • Capture d’écran 2020-03-25 à 10.50.29.png
    Capture d’écran 2020-03-25 à 10.50.29.png
    64.8 KB · Views: 88
Hello @MACacOsX,

Welcome to the forum -- you may have been here silently, but now you are visible! If you also have an Antelope audio interface, let's hope it can be made to work.

@qthegaijin: Is the Antelope still problematic even with a flashed Alpine Ridge card?
Thank you @CaseySJ .
Worthy of admiring your dedication supporting everyone on your thread :):clap:
Some information for the investigation:
* CH341a Programmer: Worked well for me withouth 3.3v mod. (Reading -Windows or MacOS- and Writing -MacOS flashrom-). Flashed TitanRidge with DSM2 Firmware first and now with the @Elias64Fr Mod. :cool:
* GC-TITAN RIDGE
- Working as expected with Lacie Rugged Thunderbolt USB3 external HD. (Cold Boot / Hot Plug -i don't configure sleep here-)
- Achieved Local Node / Thunderbolt Bus with mod Firmware and pins Bridged to get GPIOPower. No TB_Header connection.
- Showing correct data with SSDT and TDROM. (Port 7 active)
- Working well with PCIe devices, thanks to SSDT adapted to X299 -> PCIe16_2 or PCIe4_2 (BR1A / RP17 on my MB)
*ANTELOPE
-Same tree in IOReg that @qthegaijin for Antelope Orion32+ (Here this Device has the pci-1d4b,a090 identifier)
-Below driver: lines of IOAudio Strems, but missing IOAudioEngineUserClient and incomplete information properties due to incomplete driver loading:
- I can see at startup that the system tries to read the address of the device and fails. Therefore, the Antelope driver doesn't do its job well. Sometimes I think if it could be solved by injecting properties of the device itself, but I don't have a real mac on hand to compare..
-If I think about the network configuration, Antelope works with a local server running on port 2020 from the address obtained by DHCP (or 2021 / 2022 and so on if we restart the server) . The Antelope driver starts that server and is configured to recognize remote connections (or at least the local one), but maybe the reading is not working since it has not been able to read the device at startup (or we do not have the appropriate functions to capture the read events of the device in HotPlug).
Although LocalNode / TBus is enabled, there is no self-assigned address on Net / Thunderbolt Bridge (marked in red instead of yellow). (Althought Port7 is activated)
 
This might be due to a mismatch between your SMBIOS (iMacPro 1,1) and the DROM (but that doesn't seem likely). The DROM is coded for iMac 19,1 in bytes 13-21 (see Thunderbolt DROM Decoded):
I have tried with iMac19,1 now, too (new serial and board serial/MLB generated, of course), but still the same problem. I wanted to switch to iMac19,1 anyway, because my new iPad arrives tomorrow and for Sidecar I need iMac19,1.
 
I have tried with iMac19,1 now, too (new serial and board serial/MLB generated, of course), but still the same problem. I wanted to switch to iMac19,1 anyway, because my new iPad arrives tomorrow and for Sidecar I need iMac19,1.
The Thunderbolt log (with iMacPro1,1) no longer contains any entries from IOThunderboltFamily even though I intentionally gave you a DROM file with a bad CRC32_C checksum that was designed to illicit a response in the log.

Can you please post a screenshot of IORegistryExplorer --> NHI0@0 with ThunderboltDROM showing? The first 9 bytes should be obscured like this:
Screen Shot 2020-03-24 at 3.35.08 PM.png
This will tell us if the right DROM is being injected.

Do you have two different macOS SSDs in the system (such as a primary and a backup)? If so, are you sure that the system is booting from the primary SSD? We can press F12 at BIOS splash screen to choose.

Going back to your original post in which you stated that during one attempt, flashrom reported that the chip was in an Unknown State. However, a subsequent attempt to flash the chip worked?

It might be a good idea to read the chip contents into a new file, compute its checksum shasum filename, and compare that to the checksum of Elias' firmware file. Do the checksums match?
 
Last edited:
Hello @JimSalabim,
Also check the system boot log as follows:
  • log show --last boot | grep Thunderbolt <<-- Do you see any Thunderbolt errors?
  • log show --last boot | grep ACPI <<-- Do you see any ACPI errors such as 'table not loaded' or other errors?
  • Note also that the original Gigabyte firmware can be flashed back as a last resort.
  • The red line through IOThunderboltFamilyUserClient is normal. Every time we close and reopen System Information and then go to the Thunderbolt page, one of these will be created and deleted.

I actually get quite a few interesting FUD errors in mine.
Last login: Tue Mar 24 16:36:31 on console


iMac:~ user$ log show --last boot | grep Thunderbolt


2020-03-24 16:29:46.833041-0500 0x7e Default 0x0 0 0 kernel: (AppleThunderboltNHI) Thunderbolt runtime power conservation disabled.


2020-03-24 16:29:46.833042-0500 0x7e Default 0x0 0 0 kernel: (AppleThunderboltNHI) Thunderbolt runtime power conservation disabled.


2020-03-24 16:29:46.833405-0500 0x7e Default 0x0 0 0 kernel: (AppleThunderboltNHI) Thunderbolt 255 PCI - LS=0x7043 LC=0x0040 SS=0x0040 SC=0x0008 PMCSR=0x0000 RT=0xffffffff NLRT=0xffffffff LWRT=0xffffffff PRRT=0xffffffff TRT=0x0000 TNLRT=0x0000 TLWRT=0x0000 TPRRT=0x0000 TLUP=0x0001


2020-03-24 16:29:46.833411-0500 0x7e Default 0x0 0 0 kernel: (AppleThunderboltNHI) Thunderbolt 255 PCI - LS=0x7043 LC=0x0040 SS=0x0040 SC=0x0008 PMCSR=0x0000 RT=0xffffffff NLRT=0xffffffff LWRT=0xffffffff PRRT=0xffffffff TRT=0x0000 TNLRT=0x0000 TLWRT=0x0000 TPRRT=0x0000 TLUP=0x0001


2020-03-24 16:30:01.440855-0500 0x766 Default 0x0 62 0 fud: (MobileAccessoryUpdater) Stream event happened for filter: com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch


2020-03-24 16:30:01.440960-0500 0x766 Default 0x0 62 0 fud: (MobileAccessoryUpdater) Stream event happened for filter: com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch


2020-03-24 16:30:01.441021-0500 0x826 Default 0x0 62 0 fud: (MobileAccessoryUpdater) -[FudStateMachine isActive]: state=6 nextState=-1 filter=com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch


2020-03-24 16:30:01.441073-0500 0x826 Default 0x0 62 0 fud: (MobileAccessoryUpdater) -[FudIpcDispatch dispatchStateMachineEvent:] - filter name: com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch - exclusion group - com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch


2020-03-24 16:30:01.441103-0500 0x826 Default 0x0 62 0 fud: (MobileAccessoryUpdater) ExclusionGroupFilter: com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch (com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch)


2020-03-24 16:30:01.441175-0500 0x826 Default 0x0 62 0 fud: (MobileAccessoryUpdater) Creating new state machine for event: FudEvent - Client:(null) Type:114 Filter:com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch Data:<dictionary: 0x7f8967905c20> { count = 4, transaction: 1, voucher = 0x7f8967905ce0, contents =


"PluginIdentifier" => <string: 0x7f8965c0db10> { length = 45, contents = "com.apple.ThunderboltAccessoryFirmwareUpdater" }


"XPCEventName" => <string: 0x7f8965c073d0> { length = 62, contents = "com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch" }


2020-03-24 16:30:01.441228-0500 0x826 Default 0x0 62 0 fud: (MobileAccessoryUpdater) -[FudStateMachine isActive]: state=3 nextState=-1 filter=com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch


2020-03-24 16:30:01.441248-0500 0x826 Default 0x0 62 0 fud: (MobileAccessoryUpdater) -[FudIpcDispatch dispatchStateMachineEvent:] - filter name: com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch - exclusion group - com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch


2020-03-24 16:30:01.441271-0500 0x826 Default 0x0 62 0 fud: (MobileAccessoryUpdater) ExclusionGroupFilter: com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch (com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch)


2020-03-24 16:30:01.441320-0500 0x826 Default 0x0 62 0 fud: (MobileAccessoryUpdater) Creating new state machine for event: FudEvent - Client:(null) Type:114 Filter:com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch Data:<dictionary: 0x7f8967900590> { count = 4, transaction: 1, voucher = 0x7f8967905ce0, contents =


"XPCEventName" => <string: 0x7f8965c07b80> { length = 55, contents = "com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch" }


2020-03-24 16:30:01.441467-0500 0x826 Default 0x0 62 0 fud: (MobileAccessoryUpdater) StateMachine Dealloc pluginName=com.apple.USBCAccessoryFirmwareUpdater filterName=com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch


2020-03-24 16:30:01.441492-0500 0x826 Default 0x0 62 0 fud: (MobileAccessoryUpdater) StateMachine Dealloc pluginName=com.apple.ThunderboltAccessoryFirmwareUpdater filterName=com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch


2020-03-24 16:30:01.441527-0500 0x827 Default 0x0 62 0 fud: (MobileAccessoryUpdater) Disabiling stream events for device class: com.apple.ThunderboltAccessoryFirmwareUpdater


2020-03-24 16:30:01.556649-0500 0x827 Default 0x0 62 0 fud: (ThunderboltAccessoryFirmwareUpdater) -[ThunderboltAccessoryFirmwareUpdater buildFirmwareUpdaterObject] - depth = 0


2020-03-24 16:30:01.556823-0500 0x827 Default 0x0 62 0 fud: (ThunderboltAccessoryFirmwareUpdater) -[ThunderboltAccessoryFirmwareUpdater buildFirmwareUpdaterObject] - appleDevice = 1


2020-03-24 16:30:01.558354-0500 0x766 Default 0x0 62 0 fud: (MobileAccessoryUpdater) <com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch[3075] 0x0>: Device of type com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch detected


2020-03-24 16:30:01.558620-0500 0x827 Default 0x0 62 0 fud: (MobileAccessoryUpdater) FudIPCDispatch: stepComplete(): plugin:com.apple.ThunderboltAccessoryFirmwareUpdater status:1 info={


2020-03-24 16:30:01.559305-0500 0x827 Default 0x0 62 0 fud: (MobileAccessoryUpdater) Enabling stream events for suspended device class: com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch


2020-03-24 16:30:01.559429-0500 0x820 Default 0x0 62 0 fud: (MobileAccessoryUpdater) ExclusionGroupFilter: com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch (com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch)


2020-03-24 16:30:01.559568-0500 0x820 Default 0x0 62 0 fud: (MobileAccessoryUpdater) Modal Default Client - Got device attach event for com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch updateInProgress=0 queue[0]=(


2020-03-24 16:30:01.562478-0500 0x820 Default 0x0 62 0 fud: (ThunderboltAccessoryFirmwareUpdater) -[ThunderboltAccessoryFirmwareUpdater getFWAssetInfo] - isAppleNum = 1. isApple = 1


2020-03-24 16:30:01.562673-0500 0x820 Default 0x0 62 0 fud: (ThunderboltAccessoryFirmwareUpdater) -[ThunderboltAccessoryFirmwareUpdater getFWAssetInfo] - *NO* updater .Bundle... asset path = /tmp/ThunderboltAccessoryFirmwareUpdater.bundle/Contents/Resources


2020-03-24 16:30:01.562795-0500 0x820 Default 0x0 62 0 fud: (MobileAccessoryUpdater) -[FudStateMachine didFind:info:updateAvailable:needsDownload:error:]: find was not successful: Error Domain=com.apple.MobileAccessoryUpdater.StateMachine Code=7 "-[FudStateMachine didFind:info:updateAvailable:needsDownload:error:]: Unspecified error from plugin" UserInfo={PluginName=com.apple.ThunderboltAccessoryFirmwareUpdater, NSLocalizedDescription=-[FudStateMachine didFind:info:updateAvailable:needsDownload:error:]: Unspecified error from plugin, DeviceClassName=com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch}


2020-03-24 16:30:01.562953-0500 0x820 Default 0x0 62 0 fud: (MobileAccessoryUpdater) FudIPCDispatch: stepComplete(): plugin:com.apple.ThunderboltAccessoryFirmwareUpdater status:0 info={


2020-03-24 16:30:01.717014-0500 0x826 Default 0x0 62 0 fud: (MobileAccessoryUpdater) Modal Default Client - completed step:Find device:com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch successful:NO next-step:Find silentUpdate=0 error:Error Domain=com.apple.MobileAccessoryUpdater.StateMachine Code=7 "-[FudStateMachine didFind:info:updateAvailable:needsDownload:error:]: Unspecified error from plugin" UserInfo={PluginName=com.apple.ThunderboltAccessoryFirmwareUpdater, NSLocalizedDescription=-[FudStateMachine didFind:info:updateAvailable:needsDownload:error:]: Unspecified error from plugin, DeviceClassName=com.apple.mau.plugin.thunderboltupdater.ThunderboltType3Switch}


2020-03-24 16:36:49.954398-0500 0x766 Default 0x0 62 0 fud: (MobileAccessoryUpdater) <com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch[3075] 0x0>: Device of type com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch did not meet requirements for update


2020-03-24 16:36:49.955133-0500 0x766 Default 0x0 62 0 fud: (MobileAccessoryUpdater) Enabling stream events for suspended device class: com.apple.mau.plugin.usbcupdater.ThunderboltType1Switch


iMac:~ user$

Attempting to disable it with
Code:
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.MobileAccessoryUpdater.plist

And confirm kill!
Last login: Tue Mar 24 19:34:20 on console


iMac:~ user$ log show --last boot | grep Thunderbolt


2020-03-24 16:51:29.836548-0500 0x114 Default 0x0 0 0 kernel: (AppleThunderboltNHI) Thunderbolt runtime power conservation disabled.


2020-03-24 16:51:29.836549-0500 0x114 Default 0x0 0 0 kernel: (AppleThunderboltNHI) Thunderbolt runtime power conservation disabled.


2020-03-24 16:51:29.836767-0500 0x114 Default 0x0 0 0 kernel: (AppleThunderboltNHI) Thunderbolt 255 PCI - LS=0x7043 LC=0x0040 SS=0x0040 SC=0x0008 PMCSR=0x0000 RT=0xffffffff NLRT=0xffffffff LWRT=0xffffffff PRRT=0xffffffff TRT=0x0000 TNLRT=0x0000 TLWRT=0x0000 TPRRT=0x0000 TLUP=0x0001


2020-03-24 16:51:29.836772-0500 0x114 Default 0x0 0 0 kernel: (AppleThunderboltNHI) Thunderbolt 255 PCI - LS=0x7043 LC=0x0040 SS=0x0040 SC=0x0008 PMCSR=0x0000 RT=0xffffffff NLRT=0xffffffff LWRT=0xffffffff PRRT=0xffffffff TRT=0x0000 TNLRT=0x0000 TLWRT=0x0000 TPRRT=0x0000 TLUP=0x0001


iMac:~ m

@CaseySJ, it's also worth noting that screen sharing from my MBP to the Hack has been an absolute disaster until removing the GPE.TINI section mentioned earlier. I thought it was network related but could speed things up by trying to connect to a known wifi network that was out of reach. It would give me around 15 seconds good screen sharing. I wonder the connection?
 
Last edited:
Here are the files requested:
Just added a geekbench, do you think that it's values corresponding to my setup? Thanks again.
Your setup looks perfectly fine. A few questions below. Apologies if I asked them before, it's been a while...
  • Are you using a Firewire PCIe card?
  • Are any devices connected to F_USB header on the motherboard (internal USB 2.0)?
  • When you configured BIOS parameters, did you start with Load Optimized Defaults?
  • What PCIe cards are in the system?
  • Are any external USB devices connected?
  • Are any Thunderbolt devices connected?
 
Back
Top