Contribute
Register

[Guide] Creating a Custom SSDT for USBInjectAll.kext

RehabMan said:
"Problem Reporting" files are incomplete.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Click to expand...
Hi RehabMan,
Please refer to the attachment for the files.
Could you please review my usb configurations?
I am having usb problem after sleep.
I am using usb dongle bluetooth mouse.
When pc is sleeping, I can shake the mouse and pc will wake up.
However, when the pc is awake, sometimes I cannot move my cursor. (this happened like 3 out of 10)
Replugging the mouse usb dongle to the same port again will work.
With or without FakePCIID_XHCIMux.kext installed does not help my situation.
So I only have USBInjectAll.kext installed at the moment.
The .ioreg file and SSDT-UIAC-ALL.aml shows my usb port without FakePCIID_XHCIMux.kext.
Please note this is a desktop.
Hope you can assist me, thank you.
 

Attachments

  • mastermindsos.zip
    2.6 MB · Views: 66
mastermindsos said:
Hi RehabMan,
Please refer to the attachment for the files.
Could you please review my usb configurations?
I am having usb problem after sleep.
I am using usb dongle bluetooth mouse.
When pc is sleeping, I can shake the mouse and pc will wake up.
However, when the pc is awake, sometimes I cannot move my cursor. (this happened like 3 out of 10)
Replugging the mouse usb dongle to the same port again will work.
With or without FakePCIID_XHCIMux.kext installed does not help my situation.
So I only have USBInjectAll.kext installed at the moment.
The .ioreg file and SSDT-UIAC-ALL.aml shows my usb port without FakePCIID_XHCIMux.kext.
Please note this is a desktop.
Hope you can assist me, thank you.
Click to expand...

You should follow the guide in post #1 to create a custom SSDT for your ports.
And you should read the laptop FAQ regarding Google Chrome:
http://www.tonymacx86.com/el-capita...faq-read-first-laptop-frequent-questions.html
 
RehabMan said:
You should follow the guide in post #1 to create a custom SSDT for your ports.
And you should read the laptop FAQ regarding Google Chrome:
http://www.tonymacx86.com/el-capita...faq-read-first-laptop-frequent-questions.html
Click to expand...
I will follow up with the google chrome fix.
Can you give me a hint where did I miss?
- EHC1->EH01 and EHC2->EH02 rename (in config.plist), if applicable (your chipset may not have EHCI, or it may be disabled) checked
- XHCI controller must be named XHC (for most PCs it is default) checked
- install USBInjectAll.kext (install to the system volume) checked
- if you plan to use it, install FakePCIID.kext + FakePCIID_XHCIMux.kext not planning to use currently
- XHCI injector kext, if required (200-series need XHCI-200-series-injector.kext) not required
- run IORegistryExplorer, keep it running throughout the test checked
- test each port with both USB2 and USB3 devices checked
- remove configuration sections that don't apply to the target hardware checked
- remove ports from the various sections that are not needed checked
 
Last edited:
mastermindsos said:
I will follow up with the google chrome fix.
Can you give me a hint where did I miss?
- EHC1->EH01 and EHC2->EH02 rename (in config.plist), if applicable (your chipset may not have EHCI, or it may be disabled) checked
- XHCI controller must be named XHC (for most PCs it is default) checked
- install USBInjectAll.kext (install to the system volume) checked
- if you plan to use it, install FakePCIID.kext + FakePCIID_XHCIMux.kext not planning to use currently
- if you have an existing SSDT for USBInjectAll, use -uia_ignore_rmcf define existing SSDT, is SSDT-UIAC-ALL.aml consider as existing?
- XHCI injector kext, if required (200-series need XHCI-200-series-injector.kext) not required
- run IORegistryExplorer, keep it running throughout the test checked
- test each port with both USB2 and USB3 devices checked
- remove configuration sections that don't apply to the target hardware checked
- remove ports from the various sections that are not needed checked
Click to expand...

Your ioreg seems to imply that -uia_ignore_rmcf is set.
-uia_ignore_rmcf causes USBInjectAll.kext to ignore your SSDT-UIAC-ALL.aml.

Note: Typically, SSDT-UIAC-ALL is renamed to something more appropriate... such as SSDT-UIAC.aml (because it does not contain 'all' after you customize it).
 
RehabMan said:
Your ioreg seems to imply that -uia_ignore_rmcf is set.
-uia_ignore_rmcf causes USBInjectAll.kext to ignore your SSDT-UIAC-ALL.aml.

Note: Typically, SSDT-UIAC-ALL is renamed to something more appropriate... such as SSDT-UIAC.aml (because it does not contain 'all' after you customize it).
Click to expand...
I have just applied the chrome setting=Disabled.
I have rebooted the pc just to make sure the pc is "fresh".
I have let the pc to sleep and I still come across this usb issue.
Noted about the file naming.
I have searched my config.plist, it does not contain the -uia_ignore_rmcf text.
Where is it set?
 
mastermindsos said:
Hi RehabMan,
Please refer to the attachment for the files.
Could you please review my usb configurations?
I am having usb problem after sleep.
I am using usb dongle bluetooth mouse.
When pc is sleeping, I can shake the mouse and pc will wake up.
However, when the pc is awake, sometimes I cannot move my cursor. (this happened like 3 out of 10)
Replugging the mouse usb dongle to the same port again will work.
With or without FakePCIID_XHCIMux.kext installed does not help my situation.
So I only have USBInjectAll.kext installed at the moment.
The .ioreg file and SSDT-UIAC-ALL.aml shows my usb port without FakePCIID_XHCIMux.kext.
Please note this is a desktop.
Hope you can assist me, thank you.
Click to expand...
mastermindsos said:
I have just applied the chrome setting=Disabled.
I have rebooted the pc just to make sure the pc is "fresh".
I have let the pc to sleep and I still come across this usb issue.
Noted about the file naming.
I have searched my config.plist, it does not contain the -uia_ignore_rmcf text.
Where is it set?
Click to expand...

"Problem Reporting" files are incomplete (missing kextcache output)
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
 

Attachments

  • mastermindsos.zip
    2.6 MB · Views: 71
mastermindsos said:
Indeed it is missing, I have re-attached the new file.
Click to expand...

Your Clover bootlog (extracted from ioreg) shows no SSDT-UIAC-ALL.aml.
Code: 
4:140  0:000  === [ ACPIPatchedAML ] ====================================
4:140  0:000  Unsorted
4:140  0:000  Inserting SSDT-XWAK.aml from EFI\CLOVER\ACPI\patched ... Success
4:157  0:017  Inserting SSDT-XSEL.aml from EFI\CLOVER\ACPI\patched ... Success
4:161  0:004  Inserting SSDT-ESEL.aml from EFI\CLOVER\ACPI\patched ... Success
4:162  0:000  Inserting SSDT-GFX0.aml from EFI\CLOVER\ACPI\patched ... Success
4:175  0:013  Inserting SSDT.AML from EFI\CLOVER\ACPI\patched ... Success

It means you are not booting from the CLOVER that you attached.
 
RehabMan said:
Your Clover bootlog (extracted from ioreg) shows no SSDT-UIAC-ALL.aml.
Code: 
4:140  0:000  === [ ACPIPatchedAML ] ====================================
4:140  0:000  Unsorted
4:140  0:000  Inserting SSDT-XWAK.aml from EFI\CLOVER\ACPI\patched ... Success
4:157  0:017  Inserting SSDT-XSEL.aml from EFI\CLOVER\ACPI\patched ... Success
4:161  0:004  Inserting SSDT-ESEL.aml from EFI\CLOVER\ACPI\patched ... Success
4:162  0:000  Inserting SSDT-GFX0.aml from EFI\CLOVER\ACPI\patched ... Success
4:175  0:013  Inserting SSDT.AML from EFI\CLOVER\ACPI\patched ... Success

It means you are not booting from the CLOVER that you attached.
Click to expand...
I can see from your point of view.
My saved .ioreg in the attachment was to show my usb port discovery.
Hopefully to verify with you if my SSDT-UIAC-ALL.aml is done correctly.
At that time, the SSDT-UIAC-ALL.aml was not compiled and used yet.
I have re-attached my latest .ioreg file.
Sorry for the trouble.
 

Attachments

  • mastermindsos.zip
    2.2 MB · Views: 67
mastermindsos said:
I can see from your point of view.
My saved .ioreg in the attachment was to show my usb port discovery.
Hopefully to verify with you if my SSDT-UIAC-ALL.aml is done correctly.
At that time, the SSDT-UIAC-ALL.aml was not compiled and used yet.
I have re-attached my latest .ioreg file.
Sorry for the trouble.
Click to expand...

Hub port connected to internal devices (such as bluetooth) should be marked portType=2.
You should also remove VirtualBox.
The extra ports on HUB1 are coming from IOUSBHostFamily Info.plist. Eliminating them requires patching the plist.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top