I’ve got a current gen Framework 13 with an AMD Ryzen™ AI 9 HX 370 CPU running Fedora 42 (fully updated as of posting) and it sometimes refuses to connect to my CalDigit TS3 Thunderbolt dock. Re-connecting the cable, rebooting, and fully powering off never seems to make a difference.
When I connect I see the same error message in dmesg. When connecting to the left-side TB port I see only:
When I connect to the right-side TB port I see only:
ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-70)
Nothing else seems to happen, though I do get power according to the battery indicator in gnome.
That said, I’m posting because I just found a workaround: plugging in a USB flash drive
I was just trying to see if the USB port was even working at all, so I plugged a USB-C flash drive into the left TB-capable port (while my dock was already attached to the one on the right) and suddenly my dmesg starts spewing and my monitors came on. Figured I’d post in case anyone else runs into this.
I ran into something similar with my AMD Ryzen AI 7 350 on the latest (beta) BIOS and my CalDigit Soho dock. Everything was working perfectly—charging, video output, no issues. Then suddenly, it stopped charging the laptop and there was no video output at all.
What I think happened is that I plugged the laptop into the powered Soho while the lid was closed, and Linux booted up in that state.
Like you, I tried everything—reconnecting the cable, rebooting, powering off completely, resetting EC/PD. Nothing worked.
What did fix it was disabling a BIOS setting related to power-saving—something like “switch to PCIe Gen3 when on battery.” After turning that off, the dock worked perfectly again. Even weirder, I re-enabled the setting afterward, and it still works. So… yeah. Go figure.
It just got into that state again, so I can confirm that with the TB dock plugged into the left port while getting the -5 error, plugging a flash drive into the right TB-capable also makes the dock suddenly start working.
I think my issue might be slightly different, though quite possibly related.
I just rebooted with dock connected and lid closed. When it came back up my monitors connected to the dock didn’t turn back on. However, I did have USB via the dock. Re-connecting the TB cable didn’t fix anything. This time, plugging in a USB flash drive to the the other TB port also didn’t do anything. Looking at dmesg while I did that confirmed that a lot more was already happening, it seemed to be fully initializing ThunderBolt and USB when connecting the TB cable. It just wasn’t doing the displays:
[ 134.578564] ucsi_acpi USBC000:00: unknown error 0
[ 134.578578] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
[ 135.112169] thunderbolt 1-2: new device found, vendor=0x3d device=0x11
[ 135.112178] thunderbolt 1-2: CalDigit, Inc. TS3 Plus
[ 135.840560] thunderbolt 1-0:2.1: new retimer found, vendor=0x1da0 device=0x8833
[ 135.956291] pcieport 0000:00:01.2: pciehp: Slot(0-1): Card present
[ 135.956300] pcieport 0000:00:01.2: pciehp: Slot(0-1): Link Up
[... several hundred more lines]
Edit:
Though, interestingly, after switching to the right TB port it’s back to just printing [ 553.269939] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-70) and nothing else. Even switching back to the left port again it just prints [ 641.562855] ucsi_acpi USBC000:00: unknown error 0 [ 641.562869] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5) and nothing else again. Hmm, maybe it is actually exactly the same problem.
I’m also seeing something similar on my Ryzen 9 AI 370, where I can boot up with a thunderbolt (5, or 4, I’ve tried two) dock and the lid closed and everything will work. If it the system goes into sleep, which should be s2idle, it almost never comes back, let alone with thunderbolt connected. If I disconnect the thunderbolt cable, I usually can’t get it to reconnect without rebooting. My dmesg shows