I see occasional errors ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110) in journalctl. This occurs at the same time my external monitor randomly disconnects and reconnects. As best I can tell, this is something related to the usb-c connection to the monitor. I am directly connected, connected to power (stock framework brick). This does not occur on another laptop running F39 using the same monitor via USB-C via the back-right usb-c expansion card. I have the 3.03 BIOS update and still see this. The monitor is an Arzopa A1C.
To be fair, the monitor is just using USB-C for power and display. I’m kind of leaning towards the display as I approached troubleshooting, however, I have a similarly spec’d machine that doesn’t have this problem.
Just caught this. So you are using the USB-C connection to push video and for powering the display, this is likely where things are experiencing challenges. Does the display have the option of separate power to connect to? Would be worth testing against this if this is available.
I’ll test it again with an external power source. The only reason it wasn’t a concern was the fact that I connect the display to antother laptop directly via USB-C only with no problems. It aslo runs a 60W PD charger.
This happens when I connect a yubikey 5C Nano with power plugged and unplugged.
The Yubikey is working as I’m able to use it to while logging on to different systems but the key is not detected by the yubikey-manager but I’m not 100% sure if this is the reason why.
My system is a Framework 13 AMD 7840U with Fedora 39
What makes this more confusing is it doesn’t address the problem with the display resetting on me. Those errors don’t correlate with the actual screen resetting…It started happening the second I opened 1password’s site and persisted until I turned the brightness on the display down below 100%.
I just don’t know what to make of it. I’m really not sure I want to pursue it for now. I’ve worked around the issue by setting the display to 85% brightness and all is stable. So most-likely bad display.
As for USB disconnect errors, I don’t see any adverse affects otherwise, everything else behaves, works as expected and is responsive despite the errors showing up occasionally.
As far as I am concerned, it’s been noted and I am satisfied with how everything behaves that I don’t consider it a “Framework support” issue anymore. I’ll leave it up to you and whoever else on the thread wants to drive this, as for me, I am not going to pursue this any further for now.