Contribute
Register

New USB Raise Port Limit Patch for High Sierra

Thanks.
8086:a36d is xHCI device-id. Same port layout as 200-series, 100-series.

Added support for 8086:a36d xHCI in USBInjectAll project (0.6.5).
Covered also in configuration guide:
https://www.tonymacx86.com/threads/guide-creating-a-custom-ssdt-for-usbinjectall-kext.211311/

Hi. On my Z370 motherboard the Device ID is a2af which is what's found in the 200-series injector. I think that the naming of the injectors may cause some confusion.
Screen Shot 2018-04-21 at 7.34.44 AM.png
 
Hi. On my Z370 motherboard the Device ID is a2af which is what's found in the 200-series injector. I think that the naming of the injectors may cause some confusion.
View attachment 326980

You can use whatever kext matches your device-id.
The README clearly mentions the device-id of each.
 
But was a big problem because no one USB works at the mac os installation stage ; no mouse&keyboard.

That is a new USB device with Intel B360 chipset ( I think that on H370, H310 too).
Intel Cannon Lake PCH USB 3.1 xHCI - device ID 8086_a36d
I replaced 8086_ a2af (200 series PCH USB 3.0 xHCI ) on 8086_a36d in both kexts
All USB ports are working now.
I create SSDT/USB on El Capitan MAC OS only . When Sierra/High Sierra arrive no need for me.
USB works very well on highspeed. Old rule ; new mac os new installation from beginning )

Note: Still no need to modify USBInjectAll.kext. You can provide whatever port data you want via SSDT.

Please attach ioreg and I'll add device id 0xa36d support to USBInjectAll.kext (and SSDT-UIAC-ALL) and add a XHCI-300-series-injector.kext.


Didn't he provide the ioreg file as needed? Im in a similar predicament. except my mobo is a h370.
 
The patch is used during port discovery only.
After you have a correct SSDT for USBInjectAll, and the number of ports injected are within the 15-port limit, no need for the patch.

I'm finally going to make the SSDT for the ITX Motherboard. I need clarification. On the GA-Z170N-WIFI, We have 4 usb 3.0 ports on the back, 1 usb-C 3.1 port. 2 usb 3.0 ports on the front from motherboard header, 1 m.2 wifi port (2.0) and 2 usb 2.0 ports from a motherboard header. With 2 ports defined per USB3.x, I count 14 ports for the USB3 and 3 ports for USB2. If I enable all the which is my desire, I'll have 17 ports defined in the SSDT. Will it work with the port limit patch implemented or do I have to start picking and choosing?
 
I'm finally going to make the SSDT for the ITX Motherboard. I need clarification. On the GA-Z170N-WIFI, We have 4 usb 3.0 ports on the back, 1 usb-C 3.1 port. 2 usb 3.0 ports on the front from motherboard header, 1 m.2 wifi port (2.0) and 2 usb 2.0 ports from a motherboard header. With 2 ports defined per USB3.x, I count 14 ports for the USB3 and 3 ports for USB2. If I enable all the which is my desire, I'll have 17 ports defined in the SSDT. Will it work with the port limit patch implemented or do I have to start picking and choosing?

4xUSB3 back = 8 ports (HSxx + SSxx pair)
1xUSB-C (if it is on the xHCI not TB3): can be up to 3 ports (without switch: 2x SSxx, 1x HSxx), or 2 ports (with switch: SSxx+HSxx)
2xUSB3 front = 4 ports (HSxx + SSxx pair)
m.2 BT = 1
2x USB2 header = 2

Worst case:
8+3+4+1+2 = 18 (but may be only 17 depending on the type of USB-C)

It means you will need to sacrifice 2-3 to stay within the 15-port limit.
 
4xUSB3 back = 8 ports (HSxx + SSxx pair)
1xUSB-C (if it is on the xHCI not TB3): can be up to 3 ports (without switch: 2x SSxx, 1x HSxx), or 2 ports (with switch: SSxx+HSxx)
2xUSB3 front = 4 ports (HSxx + SSxx pair)
m.2 BT = 1
2x USB2 header = 2

Worst case:
8+3+4+1+2 = 18 (but may be only 17 depending on the type of USB-C)

It means you will need to sacrifice 2-3 to stay within the 15-port limit.

Thanks. That answers my next question. I have 15 ports to work with, not fewer than 15. The USB-C unfortunately isn't TB. I'll see what is in the IOReg output when I put a USB-C hub on it. I'll define at least 2 USB3 ports as SSxx only to hit 15. Maybe 3 if I need an extra for the USB-C. I want to leave the USB-C with full functionality.
 
The USB-C unfortunately isn't TB. I'll see what is in the IOReg output when I put a USB-C hub on it.

Must test both orientations.

I'll define at least 2 USB3 ports as SSxx only to hit 15.

Omitting the HSxx will prevent USB2 devices from working in those ports; perhaps other problems.
 
Back
Top