This will eliminate this errors on framework hardware:
kernel: ucsi_acpi USBC000:00: unknown error 0
kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
kernel: ucsi_acpi USBC000:00: unknown error 256
kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
committed 09:01AM - 24 Jan 26 UTC
The PD controller returns UCSI_ERROR_UNDEFINED when querying alternate
modes for… passive cables, which lack the electronics to respond to
SOP'/SOP'' messages. This is expected behavior, not an error.
Previously this caused confusing "unknown error 256" messages in dmesg,
leading users to believe USB-C functionality was broken.
Pass the original command to ucsi_read_error() so it can identify
cable alt mode queries (GET_ALTERNATE_MODES with recipient SOP_P or
SOP_PP) and log a debug message instead of an error.
Signed-off-by: Daniel Schaefer <dhs@frame.work>
Solution: Blacklist UCSI Modules
Create /etc/modprobe.d/blacklist-ucsi.conf:
blacklist ucsi_acpi
blacklist typec_ucsi
FWIW that commit only demotes the dev_err to dev_dbg for one specific case: GET_ALTERNATE_MODES returning UCSI_ERROR_UNDEFINED against a passive cable (recipient SOP’/SOP’'). It doesn’t touch GET_CABLE_PROPERTY and doesn’t change any behavior, so even if it were upstream it wouldn’t help with the functional issues some of us are hitting here.
system
Closed
4 June 2026 17:00
3
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.