Contribute
Register

[Guide] Creating a Custom SSDT for USBInjectAll.kext

Attachments

  • debug_25357.zip
    1.6 MB · Views: 60
Because I thought maybe you wanted to see how many USB ports are possible on this system.

Done, everything should now be up to date, and the port limit removal stuff is gone. Report attached.

The USB discovery for this particular model was done long ago.
But I wanted to update the comment regarding the bluetooth controller, as it was not known which port it was attached. So, that //REVIEW comment is now resolved.
Thanks.

Note commit here:
https://github.com/RehabMan/HP-ProB...mmit/345ac53a684459b7bbc0adc9294151df01ccf39c
 
Hello all, I have tried to read the original post by @RehabMan and since I am on a Hackintosh for a week or so, I must say that I am totally lost. Although I am quite experienced with Mac OS (I am a Mac OS user since 1988), I am intimated by the hardware I am dealing with. Mac users -usually- never had to deal with this.

I have been given a PDF that shows the mapping of the USB ports for my mobo. Would that save me the original procedure? Would anyone with the same motherboard would be able to provide me with the desired entries for the config.plist? Or is this procedure a must for everyone? I am not lazy or anything, just lost. The terminology is completely unknown to me.

Suggest you walk through the guide in post #1.
 
Suggest you walk through the guide in post #1.
I have gone through the post #1 all the way to the IORegistry Explorer bit where the port investigation begins. I have downloaded the IOreg app and tested it. But I am not sure regarding the requirements. There are too many "if's" which I can't answer since I don't know what they even mean.
- EHC1->EH01 and EHC2->EH02 rename (in config.plist), if applicable (your chipset may not have EHCI, or it may be disabled)
- XHCI controller must be named XHC or XHCI (for most PCs it is default XHC)
- install USBInjectAll.kext (install to the system volume)
- if you plan to use it, install FakePCIID.kext + FakePCIID_XHCIMux.kext. FakePCIID_XHCIMux only applicable if you have enabled EHCI controller(s).
- if you have an existing SSDT for USBInjectAll, use -uia_ignore_rmcf
- XHCI injector kext, if required (XHCI-unsupported.kext)
I am applying these patches to a config.plist file on my desktop. I will give it a go this weekend given the fact that I have an external bootable drive at hand, just in case things go hairy.
 
I have gone through the post #1 all the way to the IORegistry Explorer bit where the port investigation begins. I have downloaded the IOreg app and tested it. But I am not sure regarding the requirements. There are too many "if's" which I can't answer since I don't know what they even mean.

I am applying these patches to a config.plist file on my desktop. I will give it a go this weekend given the fact that I have an external bootable drive at hand, just in case things go hairy.

The hardware in your profile has no Intel EHCI controller (100-series and later are xHCI only).
So you can disregard any discussion of EHCI, FakePCIID_XHCIMux.
 
The hardware in your profile has no Intel EHCI controller (100-series and later are xHCI only).
So you can disregard any discussion of EHCI, FakePCIID_XHCIMux.

Thanks for that... So, from the requirements I focus on the following?

- XHCI controller must be named XHC or XHCI (for most PCs it is default XHC)
- install USBInjectAll.kext (install to the system volume) (already installed)
- if you plan to use it, install FakePCIID.kext <--- ( What is this needed for? Should I use it? )
- if you have an existing SSDT for USBInjectAll, use -uia_ignore_rmcf (Again not sure if I have an existing SSDT or not. I just know that USBInjectAll is installed)
- XHCI injector kext, if required (XHCI-unsupported.kext)
 
Thanks for that... So, from the requirements I focus on the following?

- XHCI controller must be named XHC or XHCI (for most PCs it is default XHC)
- install USBInjectAll.kext (install to the system volume) (already installed)
- if you plan to use it, install FakePCIID.kext <--- ( What is this needed for? Should I use it? )
- if you have an existing SSDT for USBInjectAll, use -uia_ignore_rmcf (Again not sure if I have an existing SSDT or not. I just know that USBInjectAll is installed)
- XHCI injector kext, if required (XHCI-unsupported.kext)

Hope you're not expecting me to answer your questions concretely when you failed to attach problem reporting files...

FakePCIID.kext does nothing by itself (it is obviously needed if you're using FakePCIID_XHCIMux.kext).
You don't likely already have an SSDT for USBInjectAll.kext, otherwise you would not be asking these questions (as you would have had to go through the process of creating one already).
No harm in installing XHCI-unsupported.kext even if you don't need it.
 
@RehabMan - thx mate for your commitment to this community. I've spend few hours on trying to understand your guide and the result is all USB2.0/3.0 ports working like a charm on 10.14.1 (MSI Z97 Gaming 3 mobo).
For all those struggling with configuration. Read carefully and follow step by step, the guide. There's all you need.
Thanks again.
 
Back
Top