USB C Error on boot

Same. Laptop 13 (AMD Ryzen 7040Series) arrived recently. Running Tumbleweed. Wonder if it is causing my other (minor) issue:

“Battery at 99%, plugged in but still discharging” message pops up intermittently, but then says “Fully charged”.

> cat /etc/os-release

NAME="openSUSE Tumbleweed"
# VERSION="20240924"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20240924"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
# CPE 2.3 format, boo#1217921
CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240924:*:*:*:*:*:*:*"
#CPE 2.2 format
#CPE_NAME="cpe:/o:opensuse:tumbleweed:20240924"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"

> sudo bin/framework_tool --info

Summary
  Is Framework: true
  Platform:     Framework13Amd
BIOS Information
  Vendor:       INSYDE Corp.
  Version:      03.05
  Release Date: 03/29/2024
System Information
  Version:      Some(MassProduction) (A7)
  Manufacturer: Framework
  Product Name: Laptop 13 (AMD Ryzen 7040Series)
  Wake-Up-Type: PowerSwitch
  SKU Number:   FRANDRCP07
  Family:       Laptop
BaseBoard Information
  Version:      Some(MassProduction) (A7)
  Manufacturer: Framework
  Product:      FRANMDCP07

> sudo journalctl -g 'ucsi_acpi USB' -S 'Sep 26 10:00:00' | grep 'kernel'

Sep 26 10:13:06 localhost.localdomain kernel: ucsi_acpi USBC000:00: unknown error 256
Sep 26 10:13:06 localhost.localdomain kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Sep 26 10:23:09 localhost kernel: ucsi_acpi USBC000:00: unknown error 0
Sep 26 10:23:09 localhost kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Sep 26 10:23:10 localhost kernel: ucsi_acpi USBC000:00: unknown error 256
Sep 26 10:23:10 localhost kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Sep 26 10:23:10 localhost kernel: ucsi_acpi USBC000:00: unknown error 256
Sep 26 10:23:10 localhost kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)

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

[ 2.188564] ucsi_acpi USBC000:00: unknown error 256
[ 2.188572] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)

Is there any way to disable this behavior from the bios (I do not really need the PD directly, I would rather have a stable connexion).

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

I also get this error every time something is plugged in, including expansion cards (the non USB-C ones).

Operating System: Kubuntu 24.10
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
Kernel Version: 6.11.0-9-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7640U w/ Radeon 760M Graphics
Memory: 30,7 GiB of RAM
Graphics Processor: AMD Radeon 760M
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A5

When plugging in the charger:

 kernel: ucsi_acpi USBC000:00: unknown error 256
 kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)

When plugging in the HDMI or USB-A expansion card

 kernel: ucsi_acpi USBC000:00: unknown error 0
 kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)

This error also shows sometimes right after plugging something in, not sure it it’s related:

 kernel: workqueue: power_supply_changed_work hogged CPU for >10000us 35 times, consider switching to WQ_UNBOUND
3 Likes

Also having this issue. Is there any updates on this?

Same on boot in dmesg:

ucsi_acpi USBC000:00: unknown error 256
ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)

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).

OpenSUSE Tumbleweed, 6.13.4-1 on a FW13 AMD Ryzen 5. At boot get the following errors:

ucsi_acpi USBC000:00: unknown error 0
ucsi_acpi USBC000:00: GET_CABLE_PROPERTY_FAILED (-5)
ucsi_acpi USBC000:00: unknown error 0
ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)

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.

Also getting this show up in dmesg using kernel 6.14.0-rc4

Still getting this error on

dmesg

[17653.159244] usb 1-4: reset full-speed USB device number 2 using xhci_hcd
[17653.426135] usb 1-4: reset full-speed USB device number 2 using xhci_hcd
[17653.654601] ucsi_acpi USBC000:00: unknown error 0
[17653.654617] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17656.135675] ucsi_acpi USBC000:00: unknown error 0
[17656.135690] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17657.090545] ucsi_acpi USBC000:00: unknown error 0
[17657.090558] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17663.814868] ucsi_acpi USBC000:00: unknown error 0
[17663.814883] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17664.781919] ucsi_acpi USBC000:00: unknown error 0
[17664.781935] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17667.974758] ucsi_acpi USBC000:00: unknown error 0
[17667.974773] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17670.354507] [drm] DM_MST: starting TM on aconnector: 00000000a978853c [id: 117]
[17670.361204] [drm] DM_MST: DP12, 4-lane link detected
[17671.301337] [drm] DM_MST: stopping TM on aconnector: 00000000a978853c [id: 117]
[17672.780136] ucsi_acpi USBC000:00: unknown error 0
[17672.780151] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17675.784209] ucsi_acpi USBC000:00: unknown error 0
[17675.784226] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17678.924160] ucsi_acpi USBC000:00: unknown error 0
[17678.924168] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17689.677736] ucsi_acpi USBC000:00: unknown error 0
[17689.677752] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17690.705768] ucsi_acpi USBC000:00: unknown error 0
[17690.705784] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17693.191507] [drm] DM_MST: starting TM on aconnector: 0000000062ed216b [id: 107]
[17693.198857] [drm] DM_MST: DP12, 4-lane link detected
[17694.190177] [drm] DM_MST: stopping TM on aconnector: 0000000062ed216b [id: 107]
[17695.620756] ucsi_acpi USBC000:00: unknown error 0
[17695.620770] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17698.764903] ucsi_acpi USBC000:00: unknown error 0
[17698.764919] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[17865.567746] sd 0:0:0:0: [sda] Synchronizing SCSI cache

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.

root@theseion:/var/log# grep GET_CABLE_PROPERTY syslog | wc
     72     576    7416
root@theseion:/var/log#

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.)

-kb

3 Likes

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?

1 Like

Hi guys,

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

I can confirm I am also experiencing this issue.
Arch Linux, kernel 6.13.7-arch1-1, Framework laptop 16 (AMD)

[    5.305202] ucsi_acpi USBC000:00: unknown error 0
[    5.305213] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[    5.380450] mt7921e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20241106163310
[    5.443273] ucsi_acpi USBC000:00: unknown error 0
[    5.443283] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
1 Like

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!

1 Like

Must be a very old issue still not fixed till today:
Linux phoenix 6.12.20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.20-1 (2025-03-23) x86_64 GNU/Linux
shows:

Mär 30 14:39:13 phoenix kernel: ucsi_acpi USBC000:00: unknown error 0
Mär 30 14:39:13 phoenix kernel: ucsi_acpi USBC000:00: unknown error 0
Mär 30 14:39:13 phoenix kernel: ucsi_acpi USBC000:00: unknown error 256
Mär 30 14:39:13 phoenix kernel: ucsi_acpi USBC000:00: unknown error 256

Inserting the charger triggers:

Mär 30 15:01:09 phoenix kernel: ucsi_acpi USBC000:00: unknown error 256

Someone’s asked about this on SE:

This also reproduces for me:

Example

[    2.092715] ucsi_acpi USBC000:00: unknown error 0
[    2.092726] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)

Hardware

Slot Connector
Top-Left Type-C USB
Middle-Left Type-C USB
Bottom-Left Type-C USB
Top-Right Type-C USB
Middle-Right RJ-45 Ethernet
Bottom-Right Type-C USB

I’d like to more declaratively provide this list, but you’ll have to wait for:

Though, note that this revealed that my installation also suffers from the undermentioned USB-related problems:

They appear relevant.

Firmware

sudo dmidecode -t bios -q returns:

BIOS Information
	Vendor: INSYDE Corp.
	Version: 03.03
	Release Date: 03/27/2024
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 32 MB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		8042 keyboard services are supported (int 9h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 3.3

Kernel, OS, and DE

kinfo returns:

Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.4
Kernel Version: 6.13.9-200.fc41.x86_64 (64-bit)

I checked again on a Framework Laptop 13 AMD with 4 modules and latest BIOS:

	Vendor: INSYDE Corp.
	Version: 03.07
	Release Date: 02/19/2025
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 32 MB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		8042 keyboard services are supported (int 9h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 3.7

BIOS Language Information
	Language Description Format: Long
	Installable Languages: 4
		en|US|iso8859-1,0
		fr|FR|iso8859-1,0
		zh|TW|unicode,0
		ja|JP|unicode,0
	Currently Installed Language: en|US|iso8859-1,0

and reinserting the charger left top logs

Apr 10 00:12:35 phoenix kernel: ucsi_acpi USBC000:00: unknown error 256
Apr 10 00:12:35 phoenix kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)

@ajb, does the problem not occur unless you insert a charger? I ask because the logs that I’ve aforestated appear on every boot, regardless.

It is there when I boot, but you can trigger this message by reinserting the USB-C power plug.
I wouldn’t call it “problem”, in my eyes it is just a warning (?) message, but it floods a little bit the log. I have not watched any serious problem; maybe there is one but I am not aware of it. I guess the developers should look at this point.

2 Likes

Can confirm this is an issue for me as well, FW 16 running NixOS 25.05.20250503.7a2622e (x86-64). Unfortunately I’m not savvy enough to try contribute towards a fix, but I’ll follow along for the journey!