USB-to-Ethernet Hub cannot be detected when I upgrade EFI to v3.1.0

[wswn]

USB-to-Ethernet Hub cannot be detected when I upgrade EFI to v3.1.0

I have a USB-to-Ethernet hub connected to the right port (type-c) (not Power Source port) by matedock-2. The LAN (labeled as "USB 10/100/1000 LAN" in normal) cannot be detected when I upgrade EFI to v3.1.0. However, the USB ports on the HUB can be recognized, but only usb2.0. Previous EFI Version: I do not remember which version is used now ... HUB model: Lenovo USB-C to RJ45 Adapter C506.

The "USB 10/100/1000 LAN" is recognized as different USB versions.

It is noted that this difference does not affect my daily use, but it does exist. When the USB-to-Ethernet Hub is connected to the left type-c port (close to the 3.5mm earphone jack), "USB 10/100/1000 LAN" works as usb3.0.

When the USB-to-Ethernet Hub is connected to the right type-c port, "USB 10/100/1000 LAN" works as usb2.0.

[profzei]

@wswn Could you provide your previous working EFI, please?

[wswn]

@profzei Sure. The original EFI folder has been compressed and uploaded as the attached file "EFI-Origin". Please check it EFI-Origin.zip .

[unverbraucht]

Did you also update to Monterey recently? Monterey has introduced USB problems that sound quite the symptoms you're seeing: https://screenrant.com/macos-monterey-breaking-usb-hubs-user-reports/

[profzei]

@wswn From a technical point of view there is no difference in USB stuff and support between actual EFI and what you reported: all is unchanged from almost one year!

@unverbraucht Thank you for your report!

Today OpenCore v. 0.7.5 has been released: I'll make very soon a new release for supporting some Bluetooth fixes, but atm nothing else since I'm very busy in real life...

[wswn]

@unverbraucht Thanks for your advice. It doesn't seem like a problem introduced by the macOS version changing because I keep using Big Sur 11.5.

@profzei Thank you, profzei! I re-upgrade EFI to v3.1.0 now and find the hub mentioned above works fine when connected to the left type-c port. But it's still weird that the hub can no longer work as usual (a usb2.0 device as before) when connected to the right port.

I noticed that the USB 3.1 bus disappeared in v3.1.0. Is that related to this problem?

Here are some screenshots: When the hub is plugged into the left port.

When the hub is plugged into the right port.

[profzei]

@wswn Thank you for your reply and attached screens from Hackintool...

Let me clarify the following:

• both USB type-C ports are on the left side of our MBXP
• on the right side there is only a single USB type-A port

Then the USB type-C port next to jack port (what I guess you called left port) is a real USB type-C port controlled and managed by an Intel 9D2F controller: in Hackintool you could see HS01 & SS01 personalities for the same port since it could use both protocols for speed (USB2.0 & USB3.0).

What is the other USB type-C port on the left side of our MBXP? It is a USB type-C port BUT controlled and managed by Alpine Ridge Thunderbolt Controller and it is mapped as HS03 only since you need to enable all Thunderbolt stuff for its USB3.0 interface...

All USB mapping is available in homepage...

For this reason, since in your attached file EFI-Origin.zip there is no trace for having manually and consciously enabled Thunderbolt controller, I doubt legitimately that your hub had previously worked as an USB3 device... since I always disabled Thunderbolt controller in all my EFIs...

However you could find all infos in homepage about enabling it, but I advice you may incur in other issues since Thunderbolt support is very limited in Hackintosh community (it could work only with certain constraints and could break sleep, power management support and even dual-booting with Windows...) and ours is considered the worst since it doesn't double related personalities...

As I reported on homepage,

Due to lack of Thunderbolt devices my interest in this feature is very marginal

In my knowledge, I can only add that very few motherboards have full Thunderbolt support gained flashing Thunderbolt chip with external (serial)programmer board... A lot of people claimed for working Thunderbolt but then they could have issues with sleep support depending on macOS releases basis...

[wswn]

@profzei Very thanks for your reply and clarification! I think I get the idea...

The right type-c port (actually type-A port) supports usb3.0 only if Thunderbolt is enabled.

I naively think both type-c ports can provide USB3.0 even if Thunderbolt is disabled... But, I'm still confused: Why the USB-Ethernet Hub can no longer work as a USB 2.0 device when plugged into the type-A port? it works fine though it works on USB2.0 protocol in previous EFI.