Recent content by discosoc

Thanks for the help guys. Once I got the correct 200-series patch in place, the remaining issues ended up being hardware-related and easily fixed. Turns out that the Netgear a7000 USB wifi cradle has an unusually large magnet that was interfering with the system's front panel USB3 ports - to...

That was it -- at least for the first part. USB3 devices still aren't working, but now I can at least get back to following along with the guides and Readme's. Very much appreciated.

The only difference I could find the replace value is different from 10.12.x to 10.13.x which I updated. IOReg now looks to be showing the USB3 ports as injected, however there is still no device data associated with any of them. I also have the XHCI-200-series-injector file in my "Other"...

I've read through that, but I can't actually use it because -- as I mentioned above -- my ports in IORegistryExplorer don't actually show anything being connected to. Here's another few screenshots to maybe illustrate what I'm talking about: Here's a USB section from the system report showing...

The problem is that the ports don't ever update in the IORegistry. That first screenshot, for example, was taken while a mouse, keyboard, a wifi adapter, and two USB drivers were plugged in and working. My understanding is that something should be showing up there, as per the RehabMan guide...

I don't see where it says those patches aren't required, but I apologize if I missed something. The closest I see is "There is no EHCI controller in 100-series, so several of the solutions (and problems) for 7/8/9-series don't apply to 100-series." And then it completely fails to mention which...

I'm having trouble getting USB3 to work on a new install. All ports function as USB2. Most USB3 devices aren't recognized (except for my Netgear a7000, which seems to work fine as USB2 -- "Up to 480 Mb/sec" according to system report). I read through the USBInjectAll.kext readme, as well as...

It might be nice to clarify your installation guide a bit, on this point. It's written as if the process will work as presented, when the entire Multibeast section doesn't actually work.