I think I have a related problem to this. I’m using NixOS and when I do a rebuild with anything (including a module) plugged into my Framework AMD 7040, I intermittently can crash the rebuild. NixOS then prints out that USB1-Port1 has a bad cable and it can’t be initialised. I’m then forced to reboot the computer and do a rebuild. I’m hoping that any fix to this helps, cause I also have the kernel errors in my logs.
1 Like
So I’ve been noticing this same issue on my Framework 16. But I’m running Ubuntu 24.04. For a little while now I’ve been having a hard time getting it to boot into the OS. I checked to see if there was a BIOS update I think this past weekend. But after I prompted to reboot after an update, I remembered I could hit esc to see the log as it was booting and saw a few errors in the beginning. Which lead me here.
1 Like
Hi, same behaviour here:
FW13, AMD Ryzen AI 5 340, Fedora42, firmware 03.04, kernel 6.16.3
When unplug then replug the USB-A addon, I get the dmesg entry:
[ 1012.005455] ucsi_acpi USBC000:00: unknown error 256
[ 1054.281388] ucsi_acpi USBC000:00: unknown error 256
Port seems to work (tried with mass media storage), but I don’t enjoy red entries!
1 Like
I see it too on
+++ System Info
System = Framework A7 Laptop 13 (AMD Ryzen 7040Series)
BIOS = 03.16
OS Release = Gentoo Linux
Kernel = 6.16.6-gentoo
But doesn’t seem to do any harm.
Best
Søren
1 Like
I’m experiencing this too on Arch. It isn’t appearing to cause any actual issues for me beyond the unnecessary message in my tty. For now I just set my boot options to “quiet” in /boot/loader/entries/<my boot entry.conf>. Just add quiet after options so it looks like: options quiet root=…. This is on systemd boot. If you are using something else like GRUB you would need to look up how to suppress messages for that specifically.
Obviously this isn’t a fix but I’m using the Ly display manager and the messages were appearing on that which was bugging me, so at least visually I don’t need to worry about it.
Looking forward to any updates on this from Framework as it seems like this is affecting everyone running linux.
I’m seeing this on Ubuntu 24.04. I found it when I went digging around in journalctl to try get to the bottom of my touchpad not being detected on boot about 50% of the time (I think this issue) but that could be unconnected to this problem.
## Hardware Information:
- **Hardware Model:** Framework Laptop 16 _AMD Ryzen 7040 Series_
- **Memory:** 64.0 GiB
- **Processor:** AMD Ryzen™ 9 7940HS w/ Radeon™ 780M Graphics × 16
- **Graphics:** AMD Radeon™ 780M
- **Graphics 1:** AMD Radeon™ RX 7700S
- **Disk Capacity:** 4.0 TB
## Software Information:
- **Firmware Version:** 03.05
- **OS Name:** Ubuntu 24.04 LTS
- **OS Build:** (null)
- **OS Type:** 64-bit
- **GNOME Version:** 46
- **Windowing System:** Wayland
- **Kernel Version:** Linux 6.14.0-29-generic
I’m seeing this on a FW 16 AMD 7040 with Ubuntu 24.04 whenever I connect my pixel phone through USB C.
Android Studio then complains that I should use a better cable to connect to my pixel for a faster connection.
That seems to be the only consequence though. I have no problems booting.
[28414.897521] ucsi_acpi USBC000:00: unknown error 0
[28414.897529] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
1 Like
I encountered the message when plugging in an external display via USB-C, and the display would power up but not be recognized in Linux. After reading your post, I removed the USB-A card. Now the messages still appear when connecting the display via USB-C, but the display is now recognized!
2 Likes
Are we not getting a fix for this? It drives me crazy.
3 Likes
Yes, this is extremely frustrating. I have read (and followed suggestions from) multiple lengthy threads in this forum, but the stubborn fact remains that since June (so about 4 months old Framework 13 AMD 7840), I can no longer charge the laptop while I use two external 4k monitors via a Dell WD19TB dock the way I used to before.
Note the laptop refuses to charge from the TB dock via power delivery (PD) but also from the original Framework charger when plugged on no matter which other USB-C port.
3 Likes
I’ve also had them from day 1. It’s never caused a problem and I’m not convinced it is a problem. Just a chatty kernel.
1 Like
It’s frustrating because it prints random messages making real errors become diluted.
It also spams the TTY causing issues with TTY based DM’s and TTY use.
2 Likes
1 Like
Adding a new data point. Seeing GET_CABLE_PROPERTY error on Framework Desktop too. Same USB devices on Lenovo laptop don’t show anything like that.
(I noticed this while investigating a USB hub cut off problem on Framework Desktop)
2 Likes
I have the messages too. I am on a 7640u on Debian Trixie. I didnt have the message with the included 6.12.x kernel, but it came after I installed 6.18.2. Any updates on the “issue”?
2 Likes
Started seeing this message when I upgraded from Debian bookworm to trixie.
Problem seen with kernel 6.12.57+deb13-amd64 and 6.17.8+deb13-amd64
2 Likes
I am experiencing the same error when plugging my usb-a adapter module into the either side of the laptop (Framework 13 2.8K Display, AMD Ryzen 7 7840U) on ubuntu 25.10 using kernel 6.17.0-8-generic. Depending on which side I use, I get slightly different errors:
2026-01-06T14:02:44.435236+01:00 framework kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
2026-01-06T14:03:00.757186+01:00 framework kernel: ucsi_acpi USBC000:00: unknown error 0
2026-01-06T14:03:00.757209+01:00 framework kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
2026-01-06T14:03:14.255172+01:00 framework kernel: ucsi_acpi USBC000:00: unknown error 256
I did not experience the issue before I updated Ubuntu from 24.10, kernel 6.11. So I’ll try to downgrade to a LTS kernel and will see if that helps.
2 Likes
Hi everyone, could you please let us know if you are having an issue using plugged in devices or if you are only seeing this error message.
In almost all cases this error message does not indicate a problem with functionality. It’s just the kernel trying to get more information from the PD subsystem. It expects things to behave like a Chromebook but you PD subsystem is implemented differently, which is why we see these error messages. They don’t normally indicate a problem, just the kernel trying to get some non-vital information about the Type-C cable or devices.
I agree, seeing this “error message” causes a lot of confusion, we need to figure out how to avoid/fix it.
If you are having a functional issue, we need to debug it differently. We need to know what Framework Computer, what firmware and what peripheral device you are using on which port.
4 Likes
Personally, I did not suffer any USB issue although I see those messages in my system logs.
1 Like
Hi @Daniel_Schaefer would you mind explain more here?
1 Like