Framework 16 Ports Randomly Not Working

Framework Laptop 16 Linux
1

I’m using Fedora KDE 43 6.17.12-300.fc43.x86_64 with the BIOS 03.04. I’m using the AMD AI 350 CPU with no GPU. I have three USB c expansion cards, an HDMI, an audio, and a USB c.

I got this laptop a few weeks ago, and everything was running fine until the top two ports stopped working, they wouldn’t charge at all. I disconnected then reconnected the battery and that worked for a day, and now it’s back to it, but only the top right port for some reason. Running /sys/class/typec/portX shows port stuck in source role with no partner detected, and Kernel logs show PD negotiation failures (UCSI_GET_PDOS failed). I’ve also done a Hard EC reset, but that hasn’t proved successful either. I’ve looked at other forum posts and I can’t find someone whos has this issue that wasn’t fixed by that, so I’m not sure what else to do at this point. I submitted a support ticket because I think it might be a hardware issue, but I’m not entirely sure.

image
image1262×698 212 KB

3 Likes
2

I believe there’s something in this. I received my new board w/ AI 370 just few days ago, but only now had chance to connect it to my desktop setup. I’m experiencing massive problems with my monitor with USB-C/Thunderbolt port - depending on cable it’s constantly flapping, negotiating too low current or most works, but starts flapping upon screen suspend (after few minutes of inactivity).

May not be directly related, but def. USB port related.

It’s worth to mention that it worked perfectly fine on my old Framework mobo, I had zero problems. After recent firmware update even Thunderbolt speeds negotiation got fixed.

I’ll be following on that in different post, after I gather more data.

3

ive also had issues with the ports. looking at the expansion card guide, ports 1, 4, and 5 (either with usb-a or usb-c) have stability issues where anything thats connected to those ports seem to stop transferring both power and data. ive noticed this using wired, and wireless mice as well as my usb flashdrives. its definitely a port issue because it happens both on my windows 11 installation and kali linux, with linux specifically mentioning that there is some sort of usb controller issue. it said something along the lines of “usb error 256” during the boot up process

1 Like
4

i managed to get the error code when kali boots up. it shows twice:
”ucsi_acpi USBC000:00: unknown error 256”

5

So, for me this is super internmittant, as in - I dont have a valid “reproducer”.

That being said, I did some digging found that disabling link power management may help prevent this from happening.

(this will lower battery life)

You can try to disable LPM with the following:

sudo grubby --update-kernel=ALL --args=“usbcore.quirks=32ac:0012:k” EDIT - this is to the keyboard module, not the expansion cards/usb c ports - Im still digging for those. Dont do this yet :slight_smile:

I have no idea if this will work, or how bad it will affect battery life, or if its safe.

Do this at your own risk :slight_smile:

So, I was able to get a reproducer. And, as much as I hate it, I got some help from AI (claude with a local MCP server that can read logs faster than I have time to)

Ill add the diagnostics it gave here, and for fun, I am going to test it out..

I found that I had one USB device not working (specifically port 5 - right middle). The AI was confused at first and not able to tell which port, which makes sense, its not like they are numbered the same internally as externally… So, after finding it, I asked it to get me the ID so I could try and disable LPM:

Prompt:

i just did a disconnect and reconnect of the hub with issues and its working - what is the id of this one?

Response:

Let me check
Looking at the dmesg output, I can see the issue - you had a USB disconnect at timestamp 1557 seconds, and then the UCSI error 256 appeared at 1710 seconds.
The problematic hub that required reseating is likely one of these:
• Bus 001 Device 011: ID 05e3:0610
• Bus 001 Device 012: ID 05e3:0610
• Bus 001 Device 015: ID 05e3:0610
Since it required a physical reseat to work and you just got the UCSI error 256 in dmesg after reconnecting, this is a USB-C port initialization issue, not specifically the hub.
The USB-A expansion card with issues uses:
ID 05e3:0610 - Genesys Logic Hub (USB 2.0)
To prevent this from happening again, add the quirk:
sudo grubby --update-kernel=ALL --args=“usbcore.quirks=05e3:0610:k”
sudo reboot
This will keep the hub from entering low-power states that might trigger the UCSI error. However, the root cause is still the UCSI firmware issue - update your BIOS to properly fix it.

I do appreciate it points to this being a firmeware issue - and will probably ask it to dig a bit more - but, I plan to test this out for a few days.

4 Likes
6

Coming back to this, adding the quark didnt help.

What I have done is moved my 250gb expansion card to that port (5). Since doing so, it hasned had any connection issues.

The reproducer I have had is plugging something into that port triggers an overcurrent event, it briefly disconnects my keyboard, touchpad, and numpad…then that port is dead till its reseated.

Probably need to bug this, ill try and get some data for the git when I have time.

1 Like
7

I have same issues. Ports were not working randomly at the beginning, then failed completely. All of them, apart from one on 5070. I’ve got motherboard replaced - and now … ports are not working randomly! FW 16, Ryzen AI 9 HX 370, Bios 03.04. I’ve filled the form to send the machine back, but damn, I don’t want to send it back! But if the ports keep dying - what else can I do.

In my dmesg I see things like:

[ 18.242991] ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed

or

[  147.721374] ucsi_acpi USBC000:00: unknown error 256
[  148.074718]  source-capabilities: Unknown APDO type. PDO 0xe404b1f4
8

Vugshnutte

FW16 2nd Gen, Ai9 HX 370, no added GPU. Received a few weeks ago.

Yours is a hardware issue, simply as I also run Fedora 43 KDE Plasma, obvious now with a newer Kernel, but it worked from the start either on Linux or Win11 Pro (dual boot). I have USB C on Ports 1+4 tested with the 240W PSU…no issues. SD Card Reader on Port 5 tested no issues, USB A on Port 6 tested no issues. I haven’t tested the other ports as Port 2 is HDMI and I can’t remember Port 3…(Laptop is in another room at the moment).

9

I am having a similar issue. I was on the original BIOS shipped with my 7840HS FW16, and updated my BIOS to 4.03 recently following the procedure here to also update the firmware and drivers: Framework Laptop 16 BIOS and Driver Releases (AMD Ryzen™ 7040 Series)

Soon after I started noticing an issue with port 4 (top right side). I have seen a few posts now talking about similar issues with ports, and most are from the last 2 months with new devices or after updating the BIOS, but one person said they rolled back their BIOS and still had the issue too. Here’s what I’ve been able to nail down so far in terms of behaviour:

  • Everything I’m describing below happens pretty similarly on BOTH Mint OS and Windows (dual boot system).
  • I used to have my type C expansion card in port 4 and is usually where I charged. I first started noticing the issue because if it was plugged in and working, but then went to sleep/hibernate/closed lid, when it woke back up, this port would not work to charge anymore. If I restarted the computer into either OS, it started working/charging again.
  • If it is working (e.g., after a restart), it will stay working indefinitely, but if the computer goes to sleep/hibernate/closed lid, OR if I unplug and replug the charging cable, it stops working. If I restart the computer unplugged, and then plug it in, it work.
  • I then started testing in other positions with other cards. My charging cable, and this same type C expansion card works as expected in every single other port, so it’s not hardware with my expansion card or cable.
  • If using port 4 with other expansion cards like my USB-A, AUX jack, or HDMI, it will similarly work if plugged in when I restarted. If I restart my computer with a USB-A expansion card and my mouse plugged into port 4, it works! Unlike my type-C charging cable, if unplug and replug the mouse, it still works. But if I unplug the type-A expansion card itself and replug it, it will not work again until I restart the computer just like my charging cable. It’s now sounding like a type-c issue since this is the interface for the expansion cards.
  • I have not tested the plugging/replugging after restart with the HDMI or AUX, but once the port goes into a “dead” state, neither the AUX or HDMI expansion card works in this port.
  • Under Windows Device Manager it lists an error under USB Connector Managers, for UCM-UCSI ACPI Device, and under properties for this says “Windows has stopped this device because it has reported problems. (Code 43)”, even after I have just now updated my driver bundle from Framework.

Things I have tried so far:

  • I’ve just been living with this restarting each time I need to charge, then not unplugging my charging cable from port 4.
  • I tried reinstalling the driver bundle from the link above, but the issue remains the same.
  • I am now using port 5 to charge from, and port 6 for my mouse wireless dongle (as opposed to 4 & 5 respectively for this).

I plan to contact support shortly for this.

1 Like