USB does not work with Big Sur

[zack4485]

I see lots of people reporting success with OpenCore on z420/z620/z820 and specifically indicating that USB works, but I can't get it working correctly.

I currently have both the front and back Texas Instruments USB3 controllers working in USB2.0 mode by using USBinjectall but only user input devices actually work; things like headsets and USB thumb drives don't work and the Intel USB2 controllers aren't even detected by MacOS...

Do you have the built-in Intel USB2 controllers working correctly? If so how did you do this? I have used the out-of-box EFI folder posted here on Github and when I boot I get no working USB at all...I suspect somehow my problem is with a BIOS setting I have forgotten to change. Can you post BIOS screenshots from your machine?

[joepool]

The USB3 behaviour you mention is normal, as I said in the readme, the USB3 controller isn't supported and the only method to get proper USB3 is a PCIe expansion card.
The USB2 however is working normally for me on multiple Z420's.
My BIOS settings are default with the changes I mentioned in the readme:

Version 3.96 (Latest)
SATA Mode - AHCI
Enable Legacy ACPI CPU Tables

This may be an issue with the kext you are using. You could try manually building your own usb map following this guide
Also, if you are using a Z620 or Z820 it may also differ, and I have no experience with either of those machines.
Let me know if you get it fixed, and I will add some more info to the readme.

[zack4485]

I'm on a z420 (with motherboard revision 2 that supports Ivy Bridge Xeons). To my knowledge the motherboard revision shouldn't matter for USB support since I believe the only difference between them is the bootblock code which HP refused to make available to purchasers of revision 1--I think hardware-wise they're identical.

What's interesting is that I'm literally using your complete unmodified EFI folder and USB doesn't work (on Big Sur for what it's worth). I did have to load a custom SSDT for my 1680v2 CPU because I was getting kernel panics on boot, but with that exception my config is identical to yours...

Do you think it's possible my custom SSDT is the problem? I honestly can't recall when I created the SSDT--it was years ago--so I was probably running an older BIOS when I extracted the raw SSDT and Lord knows what my BIOS settings were at the time I generated it. Does it make sense that if I possibly had different BIOS settings and an older BIOS revision at the time I created the custom SSDT then the resulting SSDT would be dorking up USB today?

Any other brilliant ideas?

[joepool]

Hmm strange, a SSDT issue is possible. Which one specifically did you need to use? It may be worth trying to create a new one, as I did have issues with older bios versions/settings. And yes that is plausible, changes in bios are reflected in SSDT's.
The only main difference between my machine and yours is the CPU (I have a 1650v2) but I see no reason why that would affect USB. No other ideas I'm afraid, other than creating a new USB map or trying USBInjectAll kext if you haven't already.

[zack4485]

I'm currently using USBInjectAll and that's how I've arrived at buggy functionality on the Texas Instruments 3.0 controllers...the fact that it doesn't inject the 2.0 Intel controllers is the thing that has me blaming my SSDT.

My current custom SSDT is self-generated because it was easy enough to do and avoided any problems I'd have trying to use an SSDT built on random motherboard with different hardware :-) With the 1680v2 I ran into the "x86_validate_topology" kernel panic and I resolved it by manually editing SSDT similar to description here: https://www.tonymacx86.com/threads/xeon-1680-v2-custom-mac-compatibility.281233/page-2

It seems there are OpenCore patches I can apply that do this same thing, though, so perhaps I should try those in order to ditch my custom SSDT altogether. It may not be the root cause of my USB problems but ruling it out as a variable can't hurt.

[joepool]

I see, that makes sense. I think as you say, your best bet it to rule out all variables that could affect it as I can't for the life of me think of any other explanation for USB to not work. good luck!