- Joined
- Jun 24, 2014
- Messages
- 289
- Motherboard
- ASUS Maximus VII Hero
- CPU
- i7 4790k
- Graphics
- HD 4600 + GTX 970
- Mac
- Mobile Phone
Yes, that's the one. I couldn't get it to work with just using USBPorts.kext so I had to use USBInjectAll.kext.
It's funny because I upgraded to 10.15.1 and my system broke. It doesn't show me filevault2 login screen anymore
Are you using FileVault2?
It sounds like you are using USBInjectA.kext from Rehabman to populate the USB ports on a TB dock. I would very much like to see the IOreg on that when all the USB ports are in use on the TB device.
All that kext does is populate as many USB ports as possible for the system. Which is why it's used to map ports out on desktop rigs, etc. Meant to be used with a custom SSDT to only inject mapped ports. Unsafe and could cause instability of the system in the long run. Now if I could see the IOreg and confirm what is being mapped if that is truly what is happening, I could prossibly implement them into our current USBPorts.kext. That way you don't cause unnecessary system instability issues.
I find it a bit hard to believe that kext makes it work as the our ACPI TB tree has it's own USB tree, I actually had a short discussion before with Rehabman about it and he verified TB ACPI devices may have the same name for USB devices but are apart of a different tree and have no correlation to standard USB ports. As far as I know Rehabman's kext is not intended to expose those ports to macOS but may be you discovered something or something has changed in macOS since then. If you and others can provide the IOReg for this state of the system, I'll be glad to take some time to see what I can do.