Contribute
Register

Thunderbolt 4, modified firmware, Full Thunderbolt Bus tree

THX @Elias64Fr for the instructions!
THX @CaseySJ but I have patched the FW on my own and surprise it works :) But man... that was hard work.

Now Both Cards can Hotplug!
 

Attachments

  • Bildschirmfoto 2024-04-11 um 20.30.16.png
    Bildschirmfoto 2024-04-11 um 20.30.16.png
    794.2 KB · Views: 32
Message for all experimenters, is someone could post his Thunderbolt DEBUG Logs explain here with his ASUS Z690/Z790 without any Firmware patches ?

I want to understand why macOS Thunderbolt drivers can deal with a disabled Thunderbolt Host Interface on port@7 :)

If you can also make 2 screenshots of IORegistryExplorer by pointing on IOThunderboltPort@7 & IOThunderboltSwitch(OS, Type6 or USB4), it would be appreciated.
Dear @Elias64Fr here are the requested files and snapshots for a Z790 ProArt Creator based platform (no kernel patches applied; OC 099; BIOS 2102, Sonoma 14.4.1)
Hope this helps and many thanks for all the great stuff you provide to this community.

Bonne soirée
 

Attachments

  • Capture d’écran 2024-04-11 à 20.28.27.png
    Capture d’écran 2024-04-11 à 20.28.27.png
    1.8 MB · Views: 14
  • Capture d’écran 2024-04-11 à 20.28.33.png
    Capture d’écran 2024-04-11 à 20.28.33.png
    1.4 MB · Views: 15
  • LOG_Thunderbolt01.txt
    403.4 KB · Views: 7
Hi @sihl32a from Switzerland, neighbour country :)

We still have same error 0xe0002d6 like saw on @Inmike09 results. On disassembled code, redundant logs with this error code are related to "command time-out", I can't say more. Experimentation with unflashed firmware is new for Thunderbolt part of component.

For USB part (XHCx), I have experienced on my system an unplug/replug for USB devices on wake from sleep with USB Error banner. This is not the case for thunderbolt devices.

Thanks for sharing your informations !
@Elias64Fr, not sure if this would help but I noticed that after boot or reboot, I never get the 0xe0002d6 error on the link status. However I do see this after waking the hack from sleep (sleep works super well on my platform). Below are 2 snapshots to highlight this.
 

Attachments

  • Pre-sleep.png
    Pre-sleep.png
    1 MB · Views: 20
  • Post-sleep.png
    Post-sleep.png
    1 MB · Views: 20
Last edited:
@Elias64Fr,

If it helps, here are screenshots from:
  • Asus Z690 ProArt Creator
  • macOS Big Sur 11.7.10
  • Un-flashed firmware
  • Latest Maple Ridge SSDT with TBTFlags = 08 00 00 00
  • Sleep/wake works normally
In screenshot #2 below, notice that IOThunderboltPort@7 is very different -- I wonder if this is what we would like to see.

Screen Shot 2024-04-11 at 12.47.22 PM.png
Screen Shot 2024-04-11 at 12.47.28 PM.png
Screen Shot 2024-04-11 at 12.47.33 PM.png
 
@Elias64Fr,

If it helps, here are screenshots from:
  • Asus Z690 ProArt Creator
  • macOS Big Sur 11.7.10
  • Un-flashed firmware
  • Latest Maple Ridge SSDT with TBTFlags = 08 00 00 00
  • Sleep/wake works normally
In screenshot #2 below, notice that IOThunderboltPort@7 is very different -- I wonder if this is what we would like to see.

View attachment 581334View attachment 581335View attachment 581336
Thanks ! If you have some time, can you attach thunderbolt debug log for Big Sur ?
 
Thanks ! If you have some time, can you attach thunderbolt debug log for Big Sur ?

Sure, the Big Sur Thunderbolt debug log is attached.
 

Attachments

  • tblog-big-sur-asus-z690.txt
    44.4 KB · Views: 4
@joevt
from Thunderbolt DEBUG Log of CaseySJ's ASUS ProArt Z690, I have found this :
(AppleThunderboltDPOutAdapter) 1427806us AppleThunderboltDPOutAdapter<<private>>::start - fDPMaxHBRBandwidth = 80

and found this from DisplayPort Wiki :
Capture d’écran 2024-04-11 à 23.00.01.png


This may help for HBR3 compatibility :) ?
 
Update on sleep issue on Asus Z690 ProArt Creator:
  • With Sonoma 14.5 public beta, this system does not enter sleep even with Thunderbolt disabled in BIOS
  • With Sonoma 14.3, sleep works normally even with Thunderbolt Local Node enabled via new SSDT
  • I do not have Sonoma 14.4 pre-installed so haven't checked, but I recall Apple making fixes to USB hubs in monitors; this may have broken sleep on Z690 ProArt
  • I'll do a clean install of 14.5 to see what happens...
 
@joevt
from Thunderbolt DEBUG Log of CaseySJ's ASUS ProArt Z690, I have found this :
(AppleThunderboltDPOutAdapter) 1427806us AppleThunderboltDPOutAdapter<<private>>::start - fDPMaxHBRBandwidth = 80

and found this from DisplayPort Wiki :
View attachment 581338

This may help for HBR3 compatibility :) ?
What's wrong with HBR3 compatibility?

I don't know what fDPMaxHBRBandwidth means.

If 80 is 80 Gbps, then that means UHBR 20 but that would require Thunderbolt 5 or USB4 v2?

Your logs also have fDPMaxHBRBandwidth = 80. Are there any logs that don't have fDPMaxHBRBandwidth = 80?

My Macmini8,1 with TitanRidge also says fDPMaxHBRBandwidth = 80.

Maybe 80 is a DP rate multiplier? HBR2 is 20 = 17.28 Gbps. HBR3 is 30 = 25.92 Gbps. 80 would be 86.4 Gbps (21.6 Gbps per DisplayPort lane). Seems unlikely.

Maybe it's a DP rate multiplier for 4 lanes? Then 80 is HBR2 * 4 lanes. Titan Ridge should support HBR3 but Mac mini GPU is limited to HBR2.

The units might be something else. Like bandwidth credits. PCI Thunderbolt Adapters have bandwidth numbers like 100 or 200.


My Macmini8,1 log has DP Out Adapter with current_bandwidth = 160 (lane_count = 4, link_rate = 2 : which is HBR2).
 
Back
Top