Framework 13 Pro seems incompatible with Anker Prime DL7400 dock due to some kind of USB-PD issue

Framework Laptop 13
, ,
1

I have an Anker Prime DL7400 Docking Station that I want to use when my Framework laptop is at home.

I am getting an issue where it seems to constantly reset. I have 2 other docks of the same type, none of them work on my Framework. I am planning to run Arch/CachyOS on the Framework, but I have also booted into Windows 11 and confirmed it isn’t an OS specific issue, as it happens in Windows as well. I have tried the original Framework power adapter cable, the original dock cable, and various other USB-C cables none of which seem to help. I also tried removing the USB-C dongle card and plugging the dock directly in the motherboard.

The Dock works fully in Arch Linux on my desktop as long as I install the right packages for displaylink.

If I look at the journal logs after connecting it to my Framework, I get the following, as well as several KDE Desktop notififications about the VIA Hub disconnecting/connecting/resetting. The logs seem to point to some kind of incompatibility with Framework’s USB-PD.

Is there any way to work around this issue, and if not does anyone have a similar dock recommendation that works on Framework that won’t have Linux incompatibilities like so many do?

sudo journalctl -kf output:

Aug 29 17:27:56 Laptop kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
Aug 29 17:27:56 Laptop kernel: ucsi_acpi USBC000:00: unknown error 256
Aug 29 17:27:56 Laptop kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Aug 29 17:27:56 Laptop kernel: ucsi_acpi USBC000:00: unknown error 256
Aug 29 17:27:56 Laptop kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Aug 29 17:27:57 Laptop kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
Aug 29 17:27:57 Laptop kernel: ucsi_acpi USBC000:00: unknown error 256
Aug 29 17:27:57 Laptop kernel: ucsi_acpi USBC000:00: con4: failed to register partner alt modes (-5)
Aug 29 17:27:57 Laptop kernel: usb 3-5: new high-speed USB device number 103 using xhci_hcd
Aug 29 17:27:57 Laptop kernel: usb 3-5: device descriptor read/all, error -71
Aug 29 17:27:58 Laptop kernel: ucsi_acpi USBC000:00: unknown error 256
Aug 29 17:27:58 Laptop kernel: ucsi_acpi USBC000:00: con4: failed to register partner alt modes (-5)
Aug 29 17:27:59 Laptop kernel: usb 3-5: new high-speed USB device number 105 using xhci_hcd
Aug 29 17:27:59 Laptop kernel: usb 3-5: Device not responding to setup address.
Aug 29 17:27:59 Laptop kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
Aug 29 17:27:59 Laptop kernel: usb 3-5: Device not responding to setup address.
Aug 29 17:27:59 Laptop kernel: usb 3-5: device not accepting address 105, error -71
Aug 29 17:28:00 Laptop kernel: ucsi_acpi USBC000:00: unknown error 256
Aug 29 17:28:00 Laptop kernel: ucsi_acpi USBC000:00: con4: failed to register partner alt modes (-5)
Aug 29 17:28:01 Laptop kernel: ucsi_acpi USBC000:00: unknown error 256
Aug 29 17:28:01 Laptop kernel: ucsi_acpi USBC000:00: con4: failed to register partner alt modes (-5)
Aug 29 17:28:02 Laptop kernel: usb 3-5: new high-speed USB device number 107 using xhci_hcd
Aug 29 17:28:02 Laptop kernel: usb 3-5: Device not responding to setup address.
Aug 29 17:28:02 Laptop kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
Aug 29 17:28:02 Laptop kernel: usb 3-5: Device not responding to setup address.
Aug 29 17:28:02 Laptop kernel: usb 3-5: device not accepting address 107, error -71
Aug 29 17:28:02 Laptop kernel: ucsi_acpi USBC000:00: unknown error 256
Aug 29 17:28:02 Laptop kernel: ucsi_acpi USBC000:00: con4: failed to register partner alt modes (-5)
Aug 29 17:28:03 Laptop kernel: usb 3-5: new high-speed USB device number 108 using xhci_hcd
Aug 29 17:28:03 Laptop kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
Aug 29 17:28:04 Laptop kernel: ucsi_acpi USBC000:00: unknown error 256
Aug 29 17:28:04 Laptop kernel: ucsi_acpi USBC000:00: con4: failed to register partner alt modes (-5)
Aug 29 17:28:04 Laptop kernel: usb 3-5: new high-speed USB device number 109 using xhci_hcd
Aug 29 17:28:05 Laptop kernel: usb 3-5: New USB device found, idVendor=2109, idProduct=2822, bcdDevice= 2.c4
Aug 29 17:28:05 Laptop kernel: usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 29 17:28:05 Laptop kernel: usb 3-5: Product: USB2.0 Hub
Aug 29 17:28:05 Laptop kernel: usb 3-5: Manufacturer: VIA Labs, Inc.
Aug 29 17:28:05 Laptop kernel: hub 3-5:1.0: USB hub found
Aug 29 17:28:05 Laptop kernel: hub 3-5:1.0: 5 ports detected
Aug 29 17:28:05 Laptop kernel: usb 3-5: USB disconnect, device number 109
Aug 29 17:28:06 Laptop kernel: ucsi_acpi USBC000:00: unknown error 256
Aug 29 17:28:06 Laptop kernel: ucsi_acpi USBC000:00: con4: failed to register partner alt modes (-5)
Aug 29 17:28:06 Laptop kernel: usb 3-5: new high-speed USB device number 110 using xhci_hcd
Aug 29 17:28:06 Laptop kernel: usb 3-5: New USB device found, idVendor=2109, idProduct=2822, bcdDevice= 2.c4
Aug 29 17:28:06 Laptop kernel: usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 29 17:28:06 Laptop kernel: usb 3-5: Product: USB2.0 Hub
Aug 29 17:28:06 Laptop kernel: usb 3-5: Manufacturer: VIA Labs, Inc.
Aug 29 17:28:06 Laptop kernel: hub 3-5:1.0: USB hub found
Aug 29 17:28:06 Laptop kernel: hub 3-5:1.0: 5 ports detected
Aug 29 17:28:06 Laptop kernel: usb 3-5: USB disconnect, device number 110
Aug 29 17:28:07 Laptop kernel: ucsi_acpi USBC000:00: unknown error 256
Aug 29 17:28:07 Laptop kernel: ucsi_acpi USBC000:00: con4: failed to register partner alt modes (-5)
Aug 29 17:28:08 Laptop kernel: usb 3-5: new high-speed USB device number 111 using xhci_hcd
1 Like
2

It looks like a negotiation protocol is failing. I agree that the cable is worth considering. If this is not compliant with the right version of the USB spec, that might be the issue. A USB2 cable with USB-C connectors won’t cut it.

(For what it is worth, my FW Pro 13 worked first time with my Dell dock).

Another thing to check, what BIOS are you running?

1 Like
3

I’ve used the Framework 13 Pro power cable itself, the cable that comes with the dock itself, and an “Anker 515 USB-C to USB-C Cable (Thunderbolt 4 Compatible)” cable, which is the cable type I use for 2 other computers with the same dock model.

BIOS version is LFP30.30.02, which seems to be the latest and only BIOS version for the 13 Pro going off Framework Laptop 13 Pro Intel® Core™ Ultra Series 3 — BIOS & Drivers | Resources

For good measure I had also checked if the dock itself had a firmware update, but it is on the latest version when running Anker Dock Manager.

2 Likes
4

Hmm, that cable-checking does seem pretty solid to me.

I take it that sudo fwupdmgr get-updates does not offer you any new upgrades?

5

Only for the fingerprint sensor and Microsoft secure boot dbx

1 Like
6

There are definitely some USB-C PD issues on the FW13 Pro. I’ve got a couple of Anker’s desk chargers that can deliver 140 watts, but they will not charge my FW13 Pro on that port, only on the 100 watt ports. It just bounces around all over the place on voltage, occasionally delivering power, but usually doing nothing.

1 Like
7

I’ve seen several posts of various Anker chargers and docks not working. I did find this post saying the Anker 575 dock works good with Linux and that it worked on a new Framework, so I ordered one and it does work for me in all 4 ports whereas the Anker DL7400 is ususable.

2 Likes
8

I did also notice some PD Differences between the 13 Pro and the FW12 using the same chargers. Specifically on low wattage bricks. On 20W bricks that can only deliver 5V or 9V the 13 Pro will only negotiate 5V 3A instead of the 9V 2.2A that the FW12 will negotiate. It does still charge off it but its not using the highest power mode available from the charger.

1 Like
9

You mean that you used these two cables between the dock & the 13 pro?

If so, note that the Framework charger cable is meant just for charging, it’s USB 2.0. Iirc they said this was to keep the cable thinner, and more flexible, in addition to reducing cost. Of course since you also used a known good Thunderbolt cable this doesn’t really matter for your dock test results, I just mention in case anyone else is trying to use that cable with a dock. I’m guessing Framework didn’t label their cable as charge only or USB 2.0? Disappointing, unlabeled cables are horrible. Come on Framework!

10

The labeling is a big part of why I bought several of the Anker 515 cables. Says it is good for 40Gbps and 240w right on the cable connector so I know it will charge at max speed for any device I own and not be USB 2.0 if I use it for data transfers.

1 Like