The 1G adapter is USB, the 2.5G is PCIe. So you can just check what kind of ethernet adapter it is. In Windows by putting DevMgr into devices by connection view.
Sadly, Lenovo does not document when it will switch. There were some reports on reddit from an Apple user that they got a USB4 connection, but only the USB3 1G controller. Unclear if this only happens if PCIe tunneling somehow fails or if there is some proprietary negotiation with the host to decide etc. Similar with the TB-out/USB-c out of the dock.
I wanted to add a Dell Ultrasharp U3223QE Display with USB-C dock and 100W PD capability but it seems like we need a second table. It gave me an error that vthe maximum character count of 32000 is exceeded .
Two BenQ GW2480-T monitors work fine via DisplayPort. I could not get the USB charging passthrough to work though with the framework 16 180 watt charger (includes e-marker cable). This is consistent with what other users of this dock have said about using chargers over 100W and having troubles. Using Power-Z Cable Tester KM003C, it does show passing through charging protocol PD3.0 83W but at 0W. Via HWiNFO64 I could see occasional charge occurring but minor, like 1-3 watts every 10 seconds and the battery was definitely discharging. I tried an alternate charger (model YMS-868) that has a 100W rated charging port with an e-marker cable and I have observed up to 60W charging with light use using HWiNFO64 (after powering the device; a Framework 16 is said to take 60W minimum). Using the Power-Z Cable Tester KM003C the 100W charger was showing passthrough power protocol of PD3.0 @ 93W, PPS and QC5. This confirms that I should be able to see up to a 93W charge eventually. So not a 100W but sufficient. The major downside of this dock is a 6" long fixed dock to laptop cable. The tester showed it is not an e-marker cable. I’d prefer no cable at all so I could change the length of the cable and use an e-marker cable.
Note: This dock does not come with an included power source.
I also didn’t really like the length of the cable because I wanted to hide the dock under the table, so I tested two USB-C extension cables, both of them worked flawlessly (Two 4K60 monitors, 100W charging, several USB2 and 3 devices, using for work 8+ hours a day for a month now):
Before that I used the one that looks like this 0.5m one.
But I’d wager most quality extensions will work, even though they are a forbidden type of cable in a way
Edit: For me, the network card in this adapter was overheatung during Teams calls and doing something weird where it lost connection, but not fully. Really weird - can handle 100 Mbit/s sustained just fine, but 2 Mbit/s teams call it craps out. I ended up plugging in a USB3 Ethernet adapter. And I also ended up pointing a fan at it under the table to make sure it doesn’t overheat.
i have tested a BlitzWolf® BW-TH13 and every thing works on my framework 16 with the frame work 60w charger but it doesn’t work with the 180w that came with the laptop but that was expected because some compatibility problems with PD 3.1 i think they were busy on a fix trough the bios i will test with the frame work charger and update this post as soon as there is a bios fix
The mystery of the WD19TB.
I see conflicting reports on this dock. I think I know why. Depends on what firmware is running when you get the dock.
I have the TBS model. I am running a Ryzen Framework 13.
This all started after I updated to the newest version available for this dock at the time of writing which was delivered by the firmware update tool (DellDockFirmwarePackage_WD19_WD22_Series_HD22_01.00.20)
This firmware made the dock go absolutely nuts. Especially and only when you had a monitor ( in my case through a kvm) going in via a “display over USB C” interface on the back. You could make it work by unplugging the usb C/ display cable and plugging it back in after the dock was powering the laptop. But, Screw that noise.
By rolling back to the firmware to the software delivered by (DellDockFirmwarePackage_WD19_WD22_HD22_Series_01.00.09)
suddenly I got reliable connections in both Fedora 40 and Windows 10.
Here is a tip. If you want to roll back firmware using the Dell updater in windows, you have to do the following:
Open the update software
Look in the upper right hand corner. To the left of the minimize/full-screen/close button set, you will see a cog wheel
click the cog wheel and you will see " command line settings". Here you want to type WITHOUT QUOTES “/f”. This will let you force the update and downgrade the firmware.
wait for finish and close the software.
unplug the dock from the laptop and reboot the laptop. While rebooting, unplug the dock from its power.
re-power the dock and attach to laptop. and Magic!
For bonus points I also tried (DellDockFirmwarePackage_WD19_WD22_Series_HD22_01.00.16). It works but reliability is bad.
Thanks. Still too many issues on current (.36?) but I’ll keep this post in mind if FW doesn’t provide new drivers soon to refresh them since ~April 24. There are some known usb c issues with the beta version and your post might be the best method.
Has anyone tried the HP Thunderbolt Dock 120 watt G4 (preferably on a FW 13 AMD + Linux) yet? On paper, it’s the perfect dock for me with 2.5Gbit ethernet and all the bells & whistles I could possibly want, but I’m hesitant to spend almost €200 only to find out it doesn’t work (reliably) on my FW13 AMD + Linux.
Successfully testes scenarios:
connect 2x DP and open lid
connect dock at boot
dis-/connect dock after OS login
dis-/connect dock with lid closed
dis-/connect various USB devices
wake up from sleep/suspend
connected dock to USB-C port 1 and port 2 on laptop (closest to hinge)
Unsuccessfully tested scenarios:
Boot/wake-up laptop by pressing dock-power-button (only turns dock on/off)
Yes it depends on firmware. But I would expect most people complaining about issues to have tried the newest one. Its not like they come out every week.
But also, the classic problems are that there is a specific monitor, maybe with specific firwmare, maybe with a specific MST hub or adapter (with firmware) and the MST hub and TB controller in the dock on a specific firmware AND a specific GPU driver that causes such issues. Change one element and the problem is often gone. By and large the MST Hub inside the dock has improved and fixed many bugs with its firmware updates. But its so complex that you can probably always find some weird edge case. And GPU drivers play a big role. Because it is often also about the GPU driver understanding the connected topology of devices and then choosing the right settings, including DSC & MST to make all of them work. I had a bunch of issues where monitors would remain dark even though the OS thought they were working fine. All of those issues solved by newer Intel and Nvidia GPU drivers. My monitor has even gotten 3 firmware updates to fix MST+DSC issues. And Linux (I use Fedora when I use it) has just been way behind in fixing those issues for my Intel GPUs. Stuff that works perfectly under Windows still fails under current Fedora (its a complex setup with the MST hub in the WD19TB + MST Hub in one of my monitors again (also with some DSC support). So not a typical dock setup).
I am not sure about the firmware versions, but the MST hub in the HP TB Dock G4 is basically the same as in the Dell WD19/22 family of docks and the same as in multiple Lenovo Docks (USB-C / TB3 Gen 2, half of what is in the TB4 dock). Since the MST Hub is the main part that causes problems with monitors, if they are on same firmware, you can pretty much expect them to behave extremely similar (with respect to the outputs of the MST hub). The TB controllers by comparison had very few updates that I think HP, Lenovo and Dell all would have shipped quickly.
This is what I use. I’m on a 12th-gen Intel FW13 running NixOS 24.05 and didn’t need any drivers or firmware updates. The 2.5Gbit link works great, and I run two monitors by running one off of the thunderbolt passthrough. The lack of a 3.5mm audio port is frustrating, but I get around that with a USB-C adapter. Can highly recommend. The small footprint on the desk is also nice.
I’m currently having an issue with my AMD FW 13 where my Anker 778 will work with one monitor but if I connect both I get no external display at all. I’m also having an issue now where my peripherals aren’t detected at all where they were working just fine before.
for some reason i can’t edit the list so can someone plz add this to the list thanks a lot. |Blitzwolf BW-TH13 | TH13 | Banggood Easy Online Shopping | jochem_steenbrink | Windows 11 (no drivers needed):
M.2 SATA3.0 5Gbps (up to 2TB) x1
USB2.0 480Mbps x2
USB3.0 5Gbps x3
DP/VGA 4K@30Hz x1
HDMI 4K@60Hz x1
HDMI 4K@30Hz x2
RJ45 1000Mbps x1
USB-C PD3.0 100W in 87W out
USB-C 5Gbps x1
3.5mm Audio port in/out x1
USB-C 1(Host 1) for mac or HDMI1 only
USB-C 2(Host 2)
TF Card Reader 104MB/s x1
SD Card Reader 104MB/s x1
curently framework 16 only works with 100W and lower chargers when charging trough PD3.0 hubs I use ESSAGER ES-CD37
Like @Michael_Fox and @UniversalSuperBox I have a Corsair TBT100 DP hub. It is fully working (two 4K monitors at 60Hz) with the 13th-gen Intel motherboard.
I did need to enable Thunderbolt (services.hardware.bolt.enable = true on NixOS) before it’d work at all, and I needed to prod xrandr to use 60hz on both.
It turns out that my issue with using the Corsair TBT100 was related to the Thunderbolt 3 cable that came with it. I bought a new, high quality, TB4 cable and everything has worked fine on Windows 11 ever since. The only issue I have now seems to be unrelated to the dock. Basically, when the laptop goes to sleep, it will not recognize external monitors on awakening. I have to restart it to get external monitors to display again.
Can’t edit the table, but I report here successfull tests on Anker Prime (A83B6) on Framework 13" Intel® Core™ Ultra Series 1 under Ubuntu 24.04 (no specific driver)
2 x HDMI @2560x1440 60Hz
Network Gigabit
Audio
USB
Charging
Beware on the cable, I tested different 100W certified cables before finding a working one (can’t say if it’s the one given with the docking…)