- Feb 13, 2012
- Gigabyte Z370M D3H
- RX 560
- Classic Mac
- Mobile Phone
Hey, that EFI looks pretty darn good. Nothing unnecessary or pointless.Thanks for your support, UtterDisbelief. Since I have no idea how to go forward from here, I have attached a zipped copy of my CLOVER folder, less the contents of "doc," misc," "themes," and "tools." (Hopefully that just reduced the size of the file, but not any of its necessary functions.) Would you please look at it and let me know if you see anything, like unchecked or checked boxes in config.plist, or any of the other contents that could block the port limit removal procedure from going through? I would definitely appreciate it!
(P.S.) All the stuff in the right-hand panel with triangles open look to be consistent as far as for numbers and port "count."
Not related to your USB issues, but I would select the tick-boxes I've highlighted here:
Then Save and Reboot etc. These two changes will improve CPU power-management and fix bounce awake (in some cases) from shutdown.
Back to USB ...
There are no SSDT's or USBPorts.kext in the EFI folder but you do have USBInjectAll.kext and the PLRP in place. This set up should be expected to give you HS01 to HS14 and SS01 to SS08 + USR1 and USR2 (probably)
HOWEVER ... Let's get complicated for a second or two:
USBInjectAll.kext is set up for the 8086:a12f device ID of the H170/Z170 Skylake chipsets. BUT the H170 implements two less USB3 ports than the Z170. USBInjectAll only has one entry per device ID, as you'd expect, so this explains why your earlier IORegistryExplorer output showed HS01-HS13 and SS01-SS10 + the USRs. The device ID seems to be the same for both, which to me is a bit odd and illogical.
Whether this causes knock-on problems I simply don't know. But this might explain why you get either SS01 or USR1 on occasion, because they come directly after the HS** ports in the address scheme.
As to why no USB3 (SS**) ports are appearing with that setup, I don't know. The PLR-Patch you are using is correct for Catalina.
There has to be a reason we are not seeing, but ... as yet I haven't spotted it, despite all the digging we've been doing. Just double-check no kexts have slipped into the Library/Extensions folder.