Contribute
Register

Mojave Port Limit Patch for 10.14.1 Working/Not Working

Status
Not open for further replies.

kgp

Retired
Joined
May 30, 2014
Messages
6,743
Motherboard
ASUS WS X299 Sage 10G
CPU
i9-7980XE
Graphics
Vega 64
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
Already? :eek: Umm.. there might be major USB issues as the port limit kext patch approach stopped working during the 10.14.1 betas :rolleyes:..
 
Last edited:

You won’t be ok if you want to use all usb ports, not even with usbinjectall.kext + additional SSDT workaround ;). BTW, I have my own XHC USB kext approach, where the port limitation can be performed directly within the kext without any additional SSDT. It therefore certainly will not be my problem but a problem for all those not knowing how to properly reduce the amount of implemented USB ports in form of a kext or SSDT.

My previous post was just meant as a helpful comment and reminder.
 
Last edited:
You won’t be ok if you want to use all usb ports, not even with usbinjectall.kext + additional SSDT workaround ;). BTW, I have my own XHC USB kext approach, where the port limitation can be performed directly within the kext without any additional SSDT. It therefore certainly will not be my problem but a problem for all those not knowing how to properly reduce the amount of implemented USB ports in form of a kext or SSDT.

My previous post was just meant as a helpful comment and reminder.

Is there some documentation about your approach?
 
Is there some documentation about your approach?

I don't know if I am allowed to provide here a cross-reference to my respective guide and thread. However, I hope it is allowed to provide you at least with a hint, in case you are really interested: just type "XHC USB Kext Creation Guideline" in the search field above and you will find the respective guide and thread listed in this forum. It is very similar to the SSDT approach, but all USB ports are directly defined within the kext. If you want to skip certain ports, simply don't implement them within the kext. For the intrinsic USB port implementation you just need the kext, nothing else. However, I also use a simple USBX-SSDT in addition, which just assigns the proper USB power properties during system boot. This SSDT however is not motherboard specific and always applies to any USB configuration without further adaptation.

The XHC USB Kext approach is just an alternative to the USBInjextAll.kext + SSDT approach. If you continue using the latter you will be totally fine too.

The major problem of 10.14.1 is that the entire AppleUSBXHCI kext-patch approach stopped working. We can still derive the correct port limit patch but it is simply ignored by macOS. There will be no solution to this until a new approach to extend the USB port limit will be found by somebody else in the future. Dropping the implementation of some of the USB onboard connectors now has become absolutely mandatory and currently is also the only solution for motherboards with more USB connectors than allowed by Apple's USB port limitation.

I guess it is not necessary to mention that all this just affects the USB2.0 and USB3.0 ports. USB3.1 ports are usually on different controllers and are not affected by the USB port limitation.
 
Last edited:
I have my own XHC USB kext approach, where the port limitation can be performed directly within the kext without any additional SSDT.
I would like to try your approach. Have you documented it anywhere?
 
Update went fine, but as noted by others USB port limit patch does not work. I was using MacPro 6,1 because without it I get no preview with jpeg files on my RX 580. I switched to iMac 17,1 to see if this fixed the USB issue, but it did not and the jpeg preview issue is back. I may revert to 10.14.0 for now until I can explore other fixes.
 
Update went fine, but as noted by others USB port limit patch does not work. I was using MacPro 6,1 because without it I get no preview with jpeg files on my RX 580. I switched to iMac 17,1 to see if this fixed the USB issue, but it did not and the jpeg preview issue is back. I may revert to 10.14.0 for now until I can explore other fixes.
There lilu plugin for that, google search it, can't remember
 
Status
Not open for further replies.
Back
Top