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

[Inqnuam]

Hello @Inqnuam

Thunderbolt Bus IDs should begin with 0 and probably stop at 10. I wouldn't expect anyone to have more than 10 Thunderbolt controllers in their system!

should I assign automatically a random TB ID between 0 and 10 or give to users an option to enter a number by their self

 

[CaseySJ]

@CaseySJ / @iRamon - Quick update. In the pursuit of perfection, I just couldn't let it go and decided to leave Find My Mac turned on for more testing.

It now appears that the machine wakes every couple of hours for a few minutes, however the reason code is no longer due to /Network, but rather, due to /User Activity

The WakeDetails Driver Reason is now given as PXSX. Now, from my rudimentary research, PXSX is either USB or Ethernet/Wifi. Does that mean there's potentially a USB issue with my Mac, or is PXSX just another name for network (even though the wake reason is no longer /Network but rather /User Activity?)

Thanks.

PXSX is an upstream PCI bridge. If you look at IORegistryExplorer and search for PXSX you may find a handful of them. Devices that connect to the PCI bus attach themselves to one of these bridges.

Think of the PCI bus as the river Thames, which we know from circling the London Eye, is lined with numerous bridges. On one side of the river is the PC itself; on the other side are peripheral devices wanting to connect to the PC. Just as bridges along the Thames connect the left and right sides, so do the PCI bridges.

On every bridge there is an entry/exit point on the left side and an entry/exit point on the right side. We can call these points the "ports" of entry and exit. On the PCI bus, the port on the left side (i.e. the computer side) is called the Root Port and there is of course one Root Port for each bridge. These are labeled RP01..RPxx (RP = root port). Then on the other side of the bridge is another port, but this port is controlled by the peripheral or add-in-card. PXSX is the generic name of this port.

 

[CaseySJ]

should I assign automatically a random TB ID between 0 and 10 or give to users an option to enter a number by their self

Default should always be 0. Because most systems have only 1 Thunderbolt controller, there is no need to randomly change the number. If someone has more than 1 controller, they should have the option to manually select an ID for that controller (from 0 to 10).

 

[hyevans]

I have that same card and a brand new unopened Magic Mouse 2. I'll test it out tomorrow.

I connected the mouse with the computer with the lightning-to-USB cable and it works now!!!!

Thanks all!

 

[Inqnuam]

Default should always be 0. Because most systems have only 1 Thunderbolt controller, there is no need to randomly change the number. If someone has more than 1 controller, they should have the option to manually select an ID for that controller (from 0 to 10).

I think I'll put the limit to 9, because after 9, so 10 and more we need 2 bytes.

 

[Inqnuam]

I connected the mouse with the computer with the lightning-to-USB cable and it works now!!!!

Thanks all!

I can confirm too, its working perfectly since day one.

 

[Synt4xTerror]

Just wanted to report that my system has been working PERFECTLY with the inatek card all week.

I installed my Inatek card yesterday.

Previously on HS11/HS12 through an internal hub I had:

1. NZXT Pump Controller
2. Corsair Lightning Node Pro
3. Coolermaster ARGB LED Controller
4. Fenvi T919 Bluetooth USB header

Now I have only the Fenvi T919 on HS11/HS12 and everything else running through the internal USB3 port on the back of the Inatek card, via a USB 3 to USB 2 internal cable, and using the same internal hub I was using previously on HS11/HS12.

So far, so good... but time will tell.

This has also seemingly fixed the bluetooth lag I was getting with Handoff enabled (only while I was streaming BT audio), so congestion on that hub seems to have been the reason for this!

Pretty pleased, no bluetooth lag, and no USB drop-outs so far!

Edit: Sleep still working too, and all other USB devices - Logitech webcam etc running from the Inatek

 

[joevt]

I think I'll put the limit to 9, because after 9, so 10 and more we need 2 bytes.

One byte can represent bus numbers 0 to 255. (0x00 - 0xFF)

 

[Inqnuam]

One byte can represent bus numbers 0 to 255. (0x00 - 0xFF)

Oh yes sorry, thank you Sir!

 

[hamzab]

PXSX is an upstream PCI bridge. If you look at IORegistryExplorer and search for PXSX you may find a handful of them. Devices that connect to the PCI bus attach themselves to one of these bridges.



Think of the PCI bus as the river Thames, which we know from circling the London Eye, is lined with numerous bridges. On one side of the river is the PC itself; on the other side are peripheral devices wanting to connect to the PC. Just as bridges along the Thames connect the left and right sides, so do the PCI bridges.

On every bridge there is an entry/exit point on the left side and an entry/exit point on the right side. We can call these points the "ports" of entry and exit. On the PCI bus, the port on the left side (i.e. the computer side) is called the Root Port and there is of course one Root Port for each bridge. These are labeled RP01..RPxx (RP = root port). Then on the other side of the bridge is another port, but this port is controlled by the peripheral or add-in-card. PXSX is the generic name of this port.

Thanks Casey, your explanation resonated even more as I’m a Londoner! Looking into the DriverReason more deeply however, it appears that even when the wake reason is given as due to /Network and due to /UserActivity Assertion the line below which depicts the DriverReason both have PXSX as the reason, so still points to it being a Network issue imo even if the WakeReason is now UserActivity

I think it’s time for me to pack up and just leave Find My Mac off for this Hackintosh. My previous Hack never left it’s location for 8 years, and thanks to your guide, more important things like iCloud/iMessage, Handoff, sync etc all work perfectly (which blows my mind!) so I’m now going to get some sanity back and reformat as new to 10.15.4 and then update.

My last question is around the change log. In May you made some adjustments to the .Zip file for the USB installer, namely:

The May 2020 Update - Catalina 10.15.4 Fresh Install.zip also contains these features:

• NVMeFix.kext for improved power management of NVMe SSDs.
• USBWakeFixup.kext and associated SSDT-USBW.aml for proper one-key wake from sleep (do not use darkwakeboot argument).
• Boot argument igfxfw=2 to allow macOS to load its GuC (Graphics MicroCode) to the iGPU for improved clock speeds.
• Uses OcQuirks-22 as the EFI memory driver.
• Sets shikigva=80 instead of 16.

My USB installer works perfectly but as it was created in April 2020, doesn't have the above changes. Are these above changes necessary (as my Machine, even with multiple reinstalls, is woken perfectly by my Apple Magic Keyboard or Apple Magic Mouse). If however there is even a small bit of value from including the above, is there a way I can 'edit' my USB install flash drive without having to go through the whole process again?

Thanks!