USBToolBox / tool

the USBToolBox tool

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Tried on High Sierra 10.13.6 on my Ryzentosh to fix lack of USB 3.0 "personalities" with no luck

Zuffle opened this issue · comments

Describe the bug
I don't know if this is a bug or just a bad hardware setup on my part but I might as well share since this has been driving me crazy for awhile and I guess this tool for some reason didn't map my system completely. I had an issue on my ryzentosh that when I tried to USB map, USB 3.0 devices would not connect to a new port but would rather be identified in a 2.0 port. I have 2 AMD USB controllers each with 3.0 ports and one with two 2.0 ports. The controller with only 3.0 ports would only show 4 ports in IORegistry, and they would only be listed as USB 2.0. The other had some 3.0 ports listed but would never be populated with a device when plugging in 3.0 USB drives to the correct ports. I thought I might try this tool to fix it. I ran the tool and detected my USB ports and on Windows everything looked great (I dual boot) with the correct personalities showing up, although the mixed 2.0 and 3.0 controller seemed to be a bit messy with ports that I don't have physically. After selecting and correcting some of the port types I built the kext and proceeded to move it into my EFI/OC/kexts folder (after adding the USBToolBox.kext and UTBDefault.kext then performing a restart). I rebooted and, while my ports are nice and organized and named AND WORKING (which is awesome, great work with this tool), to my dismay the ports are all listed as HSxx and Hackintool (not sure how reliable this is) lists their speeds at 480 Mbps instead of the 5 Gbps I would have expected from my USB 3.1 ports. The interesting part is that in IORegistry the types on the ports are correct (3 for the dual personality USB 3.0 ports and 9 for the one Type-C port), but they still don't register as 3.0. I might be crazy and off so please let me know but it looks like my USB ports were not mapped correctly with MacOS not recognizing USB 3.0 devices for whatever reason.

The generated kext seems to looks great actually:
Screen Shot 2021-06-19 at 9 38 13 PM
The mixed controller

Screen Shot 2021-06-19 at 9 38 45 PM
USB 3.0 only controller with 4 ports (one is Type-C)

But they still don't appear in IORegistry:
Screen Shot 2021-06-19 at 9 44 27 PM

Some strange results with repeated ports from Hackintool:
Screen Shot 2021-06-19 at 9 42 25 PM

Let me know what you think, sorry if this isn't the right place to ask about this cause it seems like your tool was working very well. Thank you for the tool and for any help, in advance.

To Reproduce
Steps to reproduce the behavior:
Have my exact setup and follow the tool instructions... (Not reproducible I think?)

Debugging information
This is not really a bug as far as the tool working it worked great for the most part. If a debug log is necessary let me know I will get one.

Hardware:

  • Motherboard AsRock Fatal1ty AB350 Gaming-ITX/ac
  • OS: High Sierra 10.13.6
  • CPU: Ryzen 3600

Additional context
I did already install High Sierra and attempted my own USB Mapping and XHCI Unsupported.kext fiddling and RHUB_SSDT.aml but I did remove all of those kexts and amls and rebooted before incorporating USBToolBox.kext but now that I think about I forgot to remove RHUB before adding in USBToolBox.kext and UTBDefault.kext for the first time so maybe I messed something up there.

AMD pls, y u do dis

Do you have XhciPortLimit on? Try with it off, an IOReg (from IORegistryExplorer) and a debug log (sudo dmesg | grep -i USBToolBox > ~/Desktop/UTB_debug_log.txt) would also be appreciated

Alright I turned off XhciPortLimit and rebooted but nothing has changed, but I wasn't sure if I need to do something else like remap or something. But I thought it wouldn't matter since I did the mapping on the Windows side of my dual boot. Let me know if I am incorrect on that.

Here is the ioReg in a zip:
Zuffle's Ryzentosh.ioreg.zip

And I couldn't generate the debug log using the shell commands you gave, the file was empty. I was able to use the debug_dump.exe to generate a debug dump in a .json so here is that:
debug_log.json.zip

I hope this is what you needed and thanks a ton for the help!