UtterDisbelief
Moderator
- Joined
- Feb 13, 2012
- Messages
- 9,587
- Motherboard
- Gigabyte B760 Gaming X AX
- CPU
- i5-14600K
- Graphics
- RX 560
- Mac
- Classic Mac
- Mobile Phone
I'm on 10.13.6
I'm following the x299 @kgp guide, and just going down the list, in order. USB port discovery is in E.4, and XHC XHCI PCI implementation is way down the list, at E.9. I'm not sure if/how these two things are related??
I've noticed that when I have XHCI -> XHC patches enabled, i'll get multiple copies of the ports showing up in Hackintools (see attached image), one as an XHC device, and another as an XHCI.
I've tried generating USB port mapping by selecting just the ports listed as XHC, as well as just the ones as XHCI (these display the correct port "########" (number address), as seen in IOReg). I've also tried creating the custom kext from both together, and the issue is still the same.
Another thing I've noticed is that the USB3 ports show up under a single SSxx/HSxx addres, like they're part of an USB hub, as opposed to each port having their own SSxx/HSxx port assignment (see attached image). Is this normal?
UPDATE:
in attempting to isolate the cause of the plug/unplugbehavior, ive removed any and all USB kexts/patches,etc, and the behavior persists.... going to try to see if this happens on the windows side, as well.
Hi there.
The trouble with this build is that it is so complicated, but being X299 that's to be expected. I'll explain -
The guide by @kgp was ground-breaking in that it covered so much. What we don't see easily is if the USB configuration was patched into that DSDT.aml you have in place?
Otherwise the X299 is a standard XHCI controller model. It does not have any EHCI controllers so no need to rename anything in your config.plist. With luck you don't even need XHC1 or XHCI renames either, but YMMV.
Next, this problem sounds just like power delivery. The port not delivering enough power to supply the hub. You do have a patch in place for this - SSDT-X299-USBX.aml.
The duplication of ports is an odd one. It might be caused by code in the DSDT.aml. It might be something easily remedied by clearing Hackintool's cache and reloading - broom icon/circular arrows icon. It might be caused by a rogue kext in Drive: Library/Extensions.
While I was exploring your EFI I noticed you have 3x Memory Fix drivers in place - AptioMemoryFix-64.efi, OsxAptioFix3Drv-64.efi and OsxAptioFixDrv-64.efi - which is a big no-no. Only use 1x.
So far I can see nothing else. Maybe an IORegistryExplorer v2.1 export *.ioreg might help.