If anyone has an ssdt for a i5 3570 that they know works ,would you post it please.
Why don’t you generate your own SSDT ?, is it causing trouble for you ?
Have you tried to generate with the -w command ?
Read the power management guide linked into my hp elite guide.
Does USBInjectAll kext still need to be there in the final state of the build - after the details for the ports have been discovered?
Yes it is needed.
@trs96 https://github.com/RehabMan/OS-X-USB-Inject-All
It works perfectly and that should be enough esp as I dont understand it but the link above seemed to be saying you need it to work out the ports which are then injected somehow -
"This kext attempts to inject all ports for each controller, and for hubs as well. You can use this kext (temporarily) to enable all ports so you can determine which ports really need to be in the final injector. " What am I missing?
USBInjectAll.kext does indeed attempt to enable all ports in corellation with USB port limit patch, but that is only for discovering the ports that your Desktop/Laptop use.
As soon as you captured the ports on ioreg.
You go and find SSDT-UIAC-ALL.dsl on Rehabman repo which is the master injector template for all available hardware (contains all their possible ports).
From that SSDT you customize yours and build the injector from it.
I personally rename mine as SSDT-USB for better documentation.
You can compare that master SSDT of Rehabman with the SSDT-USB.dsl from my HP Elite 8300 repo/hotpatch folder.
I have everything documented there (even USB ports real physical locations).
Removing USBinjectAll.kext will make the injector useless as it works only if kext is present.
So the short answer is yes, USBInjectAll.kext is a must.
Whatever kext or other thing that i add, is always needed and has a specific necessary purpose.
Sorry for late answer, im not receiving every notification with email or on website.