Same. Laptop 13 (intel core ultra). Running either Rocky (with 6.11.6-1.el9.elrepo.x86_64) or Fedora. The issue is that it prevents me from using a device connected to it through USB-C directly. Bios is updated to 3.04 beta.
If I use a USB-C to USB-A dongle and a USB-A to USB-C to my device instead of USB-C to USB-C, it is working.
[Laptop FW-13 USB-C] ↔ [Device (USB-C)] ==> not working
[Laptop FW-13 USB-C] ↔ [USB-C → USB-A] ↔ [Device (USB-C)] ==> working
Any updates on this issue, I get this problem also and it makes using external monitors via USBC to HDMI work irregularly. (Essentially when I see this the error the monitors are black but the os shows them as though they are there).
Linux fwbook 6.10.1-zen1 #1-NixOS ZEN SMP PREEMPT_DYNAMIC Tue Jan 1 00:00:00 UTC 1980 x86_64 GNU/Linux
BIOS Information
Vendor: INSYDE Corp.
Version: 03.05
Release Date: 03/29/2024
System Information
Version: A5
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
Wake-Up-Type: PowerSwitch
SKU Number: FRANMDCP05
Family: Laptop
Framework 13 (AMD Ryzen 7 7840U), with expansion cards attached.
System:
Kernel: 6.12.10-x64v3-xanmod1
arch: x86_64 bits: 64
Desktop: Cinnamon v: 6.4.6
Distro: Linux Mint 22.1 Xia
Trying XanMod kernel in a hope to get better support of FW hardware (on default 5.8 Mint kernel I saw amdgpu warnings in dmesg on boot, unfortunately, on this brand new 6.12 amdgpu warnings still there, but text of them slighly differs).
The GET_CABLE_PROPERTY_FAILED and UCSI_GET_PDOS errors appear if both Ports 3 and 4 are occupied by an expansion module. If only one is occupied (it doesn’t matter which), only the GET_CABLE_PROPERTY_FAILED error appears.
Once KDE Plasma is running (or I can see the lock screen, if resuming from hibernate) I find that Expansion Port 4 (the one on the right, furthest from the screen, as you’re looking at the open laptop) will not function unless I pull the expansion card out and plug it back in.
I am wondering if a few of you are experiencing the same problem.
I was also able to reproduce this problem on Fedora Workstation 41.
I went through a long back and forth with Support, who are replacing my mainboard. I’m wondering, though, from reading these posts, if this is actually a kernel issue.
I’m still having this problems along these lines running Debian Trixie, and kernel 6.12.12, which is damn new, the latest stable on kernel.org is only 6.13.5.
One aspect of all these USB C problems is very real and practical: I can’t use my computer with a nice external monitor I have, it keeps disconnecting and then a little later reconnecting. My previous old Dell XPS 13 never had USB-C problems, yet the Framework laptops are crawling with them.
These GET_CABLE_PROPERTY errors are long standing.
I notice the desktop and Framework 13 laptop being teased, and they look very cool. I hope the developers and management aren’t so fixated on moving fast that they can’t ever fix things that are broken. (And have been broken for a long time.)
I’ve seen these errors since day 1 but it’s unclear if they’re real or just the kernel being a bit too verbose.
I can’t use my computer with a nice external monitor I have, it keeps disconnecting and then a little later reconnecting.
That doesn’t sound related to this error. You’ll see it spammed in your logs if you keep connecting and disconnecting regardless of why it disconnects.
I’d consider trying a new DP-capable USB-C cable to see if the problem persists. My other thought would be power delivery. Does this only happen when the laptop is mostly/fully charged?
I also have these problems. They mainly occur when I change my workplace and therefore docks. I usually have to restart my Framework 13 or plug the USB-C power supply in and out several times. After plugging and unplugging the USB-C cable of the dock many times, it sometimes works without restarting.
Is there anything I can do to help solve the problem? It’s really annoying.
I am using Fedora 41 with Kernel 6.13.5, Bios 03.07
This started happening to me today. A few days ago my USB-C cable and dock worked fine. Today they don’t. I’ve updated and rebooted, power-cycled the USB hub. But dmesg just shows ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Running the latest Pop_OS. Any clues as to how to fix it?
Update:
I plugged the cable into the right-hand side USB-C ports and it started working. Something weird is going on!
