Contribute
Register

[solved] Mojave 10.14.1 update lost USB 3.0

Status
Not open for further replies.
When i do the IOreg none of my ports say ss01 they all say HS when i create the port plist how do i change that so ss is seen Screen Shot 2018-11-09 at 10.38.46 AM.png
 
Build 1
ROG STRIX Z370-E GAMING |  i7 8700K |  Vega 56 8GB
chiefbeats said:
Got it. Even though this guide is for a laptop, it should be fine, right? Just confirming.
Click to expand...

Yes.
Many solutions cross the laptop/desktop boundary.
Not surprising really as the chipsets are essentially the same.
 
gunnatalk said:
When i do the IOreg none of my ports say ss01 they all say HS when i create the port plist how do i change that so ss is seenView attachment 364367
Click to expand...

Based on RehabMan's guide, and my understanding of it, you have two options:

Option 1: use the port limit patch in Clover (didn't work for me)

Option 2: use the -uia_include/-uia_exclude bootflags in your config.plist to get specific ports to show up. For example, you currently see all HS ports in your IOregistry. This is because 15 ports is the limit. So, to get your SS ports to show up, you have to exclude some HS ports using the proper -uia_exclude bootflag, as described in RehabMan's guide. As he explained, be careful not to exclude the ports that carry your mouse and keyboard as applicable. I had a hard time with it, but I got it to work. Just read it 100 times, and you'll get it. :lol:
 
Build 1
ROG STRIX Z370-E GAMING |  i7 8700K |  Vega 56 8GB
chiefbeats said:
Based on RehabMan's guide, and my understanding of it, you have two options:

Option 1: use the port limit patch in Clover (didn't work for me)
Click to expand...

My guide DOES NOT use the port limit patch.

Option 2: use the -uia_include/-uia_exclude bootflags in your config.plist to get specific ports to show up. For example, you currently see all HS ports in your IOregistry. This is because 15 ports is the limit. So, to get your SS ports to show up, you have to exclude some HS ports using the proper -uia_exclude bootflag, as described in RehabMan's guide. As he explained, be careful not to exclude the ports that carry your mouse and keyboard as applicable. I had a hard time with it, but I got it to work. Just read it 100 times, and you'll get it. :lol:
Click to expand...

No such thing as "-uia_include". No such thing as "-uia_exclude".

There is "uia_include" (used in the guide). And "uia_exclude" (used in the guide to exclude USR1/USR2).
Also "-uia_exclude_ss", and "-uia_exclude_hs" (both used in the guide).
 
Last edited:
holly crap i did it!!!! thanks Rehabman. only thing i did wrong was mad all the ports except 2 ssxx ports now my usb 2.0 devices only work in 2 ports lol
 
Last edited:
RehabMan said:
My guide DOES NOT use the port limit patch.
Click to expand...

The fact: Using the port limit patch is not a long term solution. For reliable USB (assuming your ACPI implementation of _PLD and _UPC is broken... and you don't want to fix it), you must implement a custom SSDT for USBInjectAll.kext that configures your ports on XHC such that the port limit patch is not needed, and each UsbConnnector value is correct for each port.

I didn't say it did. I was referring to using the port limit patch to show all ports while you're performing port addressing, assuming it actually works with your system.

Your guide DOES explain the port limit as an implied option, however, just not a permanent one. The sentence bolded and underlined above implies it, especially if you already have a working port limit patch in place; I know because I did it. If the port limit patch works for someone, and they wish to implement your method, they should already be able to identify all their port addresses without using the -uia/uia bootflags. That's actually what I did to identify all my ports prior to upgrading to 10.14.1. Good thing I did, because 10.14.1 broke the patch, but it is still applicable for a lot of people. If their port limit patch works currently, and they wish to implement your method, there is no need to go through the bootflag process to get to the same end result, which is SSDT + USBInjectAll.kext (no port limit patch).

Again, I know because I identified all my ports when my port limit patch was actually active in 10.14, and I didn't need to use the -uia/uia bootflags. It may not be YOUR way, but it is a way. If the port limit patch isn't permanent (will be removed), it doesn't matter whether you use it, or not, to identify all your ports, as you will eliminate it once you have installed the kext and SSDT in accordance with YOUR GUIDE. As much as you claim the port limit patch is a problem, I've never had any issues with it or my USB ports, until it simply stopped working. So, I don't think people using it for a few additional minutes to identify their ports would cause any problems, like you claim. It's definitely worth explaining better, or adding as another option, in your guide.

RehabMan said:
No such thing as "-uia_include". No such thing as "-uia_exclude".

There is "uia_include" (used in the guide). And "uia_exclude" (used in the guide to exclude USR1/USR2).
Also "-uia_exclude_ss", and "-uia_exclude_hs" (both used in the guide).
Click to expand...

I was typing the bootflags off the top of my head assuming he would read the guide for everything exactly, which is why I referred him to YOUR GUIDE. I stand corrected.

RehabMan said:
Great.
Click to expand...

I didn't get a "Great!" :lol:
 
Build 1
ROG STRIX Z370-E GAMING |  i7 8700K |  Vega 56 8GB
chiefbeats said:
I didn't say it did.
Click to expand...

You implied with this:
Based on RehabMan's guide, and my understanding of it, you have two options:

Option 1: use the port limit patch in Clover (didn't work for me)
Click to expand...

The fact: Using the port limit patch is not a long term solution.
...
Click to expand...
Your guide DOES explain the port limit as an implied option,
Click to expand...

I have rewritten that sentence in the guide. Hope you like it.

I didn't get a "Great!" :lol:
Click to expand...

LOL.
 
Last edited:
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top