[Hardware] TB port USB compatibility on FW13 7840U

Community Support
,
1

I’ve had my FW 13 AMD 7840U system for almost a year, and I just noticed something odd:
The 2 thunderbolt ports in the back don’t work for regular USB 3.0 devices.

I have both a USB ethernet adapter (2.5Gb) and a Lenovo ThinkPad USB-C Dock (Model DK1633), and neither of these work (or work fully) in the two thunderbolt ports.

The USB ethernet adapter (don’t have link, as it was replaced with a newer TB compatible one) only works in the front two USB ports on the FW.
For the dock: the onboard ethernet and USB 3.0/C ports don’t work, but video/DP, USB 2.0 and charging work on the TB ports. On the right front port (looking at it like you’re using it), everything works: display, ethernet, USB, charging.

I was already aware that the front right port was the only front port with DP compatibility, which is fine. I wasn’t aware of the TB port issue.

Why? Why don’t USB 3.0 devices work on the TB port? Even FW’s USB-A modules don’t work in the TB ports.
I was expecting TB to add to the feature list, not take away. I’m a tech person, but I haven’t kept on what thunderbolt is (FW is the only device I have with it).

Both of those devices work perfectly fine on my Steam Deck (which doesn’t have TB).

In case it’s relevant, I’m running Windows 10.
When connecting a USB 3.0 device to the port, there’s no indication it was recognized (no chime).

2

Refer to this:

Only the front left port (port 2) should be no good for display port or HDMI.
I haven’t connected very many things to my FW13 7840U, and I don’t have a dock, but so far everything has worked. Both back ports seem to work fine with my USB-C to HDMI lead.

3

None of the ports on an AMD FW16 are Thunderbolt as that is an Intel specification.

The two back ports on the FW13 are USB4. I believe these are connected to the same USB4 controller chip on the FW13.

It seems like this controller chip may not be working properly.

The driver bundle for FW AMD laptops is intended for Windows 11 only. Other users have successfully extracted the drivers for use on Windows 10.

I recommend (re-)installing the extracted USB/chipset drivers from the driver bundle first. If those are successfully installed and the problem persists, you should contact Framework support as this would likely be a defective controller on the mainboard.

1 Like