[Guide] Creating a Custom SSDT for USBInjectAll.kext

[RehabMan]

Thanks for your time - OK - that was an error - please recheck...

This setup looks ok as far as USB port injection (assuming you have only the internal/BT HS08, plus 6x USB3 ports).

But...
Your kextcache output proves kexts are not installed correctly.
All kexts you need must be installed to the system volume.
Read post #2 of the Clover guide for details:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

Also, CPU PM not implemented.
See guide:
https://www.tonymacx86.com/threads/guide-native-power-management-for-laptops.175801/

 

[amiles5]

This setup looks ok as far as USB port injection (assuming you have only the internal/BT HS08, plus 6x USB3 ports).

But...
Your kextcache output proves kexts are not installed correctly.
All kexts you need must be installed to the system volume.
Read post #2 of the Clover guide for details:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

Also, CPU PM not implemented.
See guide:
https://www.tonymacx86.com/threads/guide-native-power-management-for-laptops.175801/

Thanks for your help and confirming USB config - Bluetooth kexts are loading now.

Debug attached for info. Onwards to CPU PM ;-

 

[RehabMan]

Thanks for your help and confirming USB config - Bluetooth kexts are loading now.

Debug attached for info. Onwards to CPU PM ;-

Your kextcache output still proves that kexts are installed correctly.
Kexts should be installed to /L/E, not /S/L/E.
And *all kexts you need* should be installed to the system volume.
I don't know why you believe that FakeSMC.kext is not part of the set "kexts you need".

Note also that config.plist/SystemParameters/InjectKexts=true is wrong. Should be set to "Detect".

You should read post #2 of my guide carefully:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

 

[amiles5]

Your kextcache output still proves that kexts are installed correctly.
Kexts should be installed to /L/E, not /S/L/E.
And *all kexts you need* should be installed to the system volume.
I don't know why you believe that FakeSMC.kext is not part of the set "kexts you need".

Note also that config.plist/SystemParameters/InjectKexts=true is wrong. Should be set to "Detect".

You should read post #2 of my guide carefully:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

"*all kexts you need*" should be in "system volume" -- does this mean in /L/E or /S/L/E or something else?

There seems to be difference of opinion about this and the "Vanilla" approach.

Changed "true" to "Detect" and moved Bluetooth kexts to /L/E.

 

[RehabMan]

"*all kexts you need*" should be in "system volume" -- does this mean in /L/E or /S/L/E or something else?

System volume is the partition to which you installed macOS.
As per FAQ, the folder used on 10.11 or later is /L/E.
Please read carefully:
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

There seems to be difference of opinion about this and the "Vanilla" approach.

You're asking for my help, therefore you receive my opinion.

Changed "true" to "Detect" and moved Bluetooth kexts to /L/E.

Must install *ALL* "kexts you need" to /L/E on your system volume.

 

[amiles5]

System volume is the partition to which you installed macOS.
As per FAQ, the folder used on 10.11 or later is /L/E.
Please read carefully:
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/



You're asking for my help, therefore you receive my opinion.



Must install *ALL* "kexts you need" to /L/E on your system volume.

Understood - Thank You!

 

[Warhammer73]

Yes,... now you can do port discovery and create custom SSDT.

It isn't working I think. I can see still all USB ports in IOReg.

 

[RehabMan]

It isn't working I think. I can see still all USB ports in IOReg.

Your SSDT is not coded correctly.
You have "8086_8xxx", but your XHC device is "8086_a2af".
Must use correct identifier/template.

 

[Warhammer73]

Why it is a2af?

Something went wrong. Just have the HS devices...

 

[RehabMan]

Why it is a2af?

As per guide, the device-id is shown in ioreg:

Something went wrong. Just have the HS devices...

It is because of what you coded for the port-count property:

                "port-count",
                Buffer (0x04)
                {
                     0x10, 0x00, 0x00, 0x00                        
                },

Because you set it to 0x10, any ports with "port" addresses larger than 0x10 will be ignored.

As per guide, you should NOT change port-count. The port-count is already correct in SSDT-UIAC-ALL.dsl.