Believe it or not, I can read, but that doesn't mean I fully understand it. Honesty, you provide so much information on many different places, that it somehow becomes a complex puzzle game to find the right path. I really don't get why you instead do not write a "simple" step-by-step guide with reduced sentences and reduced side notes/infos. Wouldn't that be in your own interest, too, since you answer so many questions all the time...
Step-by-step guide for creating SSDT-UIAC.aml already linked in post #1 and, specially for you, in post #2290.
The guide has images and a clear description of the process.
Also it seems you really want to prevent a novice user to configure a hackintosh, due the style of provided information. So only script kids and hackers are able to do this. I find this quite counterproductive, since we all know that Apple does not provide any serious good hardware anymore for a long time now, but that's another topic.
Hackintosh is not easy... and quite technical. It is not for everyone.
- On the one hand, you say use the port limit patch, on the other hand you write that it is not a long term solution and causes erratic behaviour on usb. Huh? So what, I conclude not to use that patch then? Since it seems all ports are available in the ACPIPlane...
As per guide, you use the port limit patch only for port discovery. After port discovery, you eliminate ports such that you're within the 15-port limit such that you can remove the port limit patch.
- You write "- if you have an existing SSDT for USBInjectAll, use -uia_ignore_rmcf" in your SSDT for USBInjectAll.kext guide. On another place you write "you can always use -uia_ignore_rmcf to disable the override code in SSDT"... So it seems to me the opposite of the first statement...
Not opposite.
The RMCF method in SSDT-UIAC.aml (which is derived from SSDT-UIAC-ALL.dsl) provides configuration data for USBInjectAll.kext. Without the SSDT, USBInjectAll.kext gets the data from its own Info.plist. And if you have the SSDT, but wish to temporarily ignore it (because you made a mistake with it), you can boot with -uia_ignore_rmcf to ignore it without actually removing the file.
The most common case of using -uia_ignore_rmcf would be the following:
- you created an SSDT-UIAC.aml
- installed it
- rebooted and discovered you made a mistake (for example all USB ports not working, or USB2 not working, making it difficult to control the computer)
- reboot with -uia_ignore_rmcf so you can correct your mistake