"usb usb2-port2: Cannot enable. Maybe the USB cable is bad?" error every 3 seconds

I receive the error message “usb usb2-port2: Cannot enable. Maybe the USB cable is bad?” every 3 seconds no matter the expansion card I plug into my DIY Framework laptop in the lower right expansion card slot.

I’m using Arch Linux. When I plug in the USB expansion card, it works intermittently. When I plug in the 1 TB expansion card, it does not see the drive.

% sudo lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 002: ID 32ac:0002 Framework HDMI Expansion Card
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I am not sure how to proceed from here. Anyone have recommendations?

1 Like

@Craig_Jennings - try the steps here, hopefully they resolve your issue:


Thanks for the prompt reply and link. I followed the steps, and it looked like the EMI sticker was pressed against the connector like in the diagram, so I lifted the sticker away from the connector to give it space and and pressed it to the diode per the instructions. After reassembling and rebooting, the error messages still appear.

I have noticed that I can still use the USB-C expansion slot to charge the laptop, but that’s the only way I can make use of that slot.

Any additional thoughts?

@Craig_Jennings - sorry to hear that the sticker adjustment did not resolve the issue for you. This is a longshot, but if you boot a live image for a different distro (I believe that both Debian SID and Fedora 35 support everything on the laptop as-is, I personally am running Pop!_OS) from a USB do you see the same errors? My guess is yes but it should be relatively easy to test. I am hoping for your sake that it’s not an issue with the motherboard, but in the unfortunate case that it is, I am confident that Framework support will take care of you. They have been fantastic with the two issues that I encountered, one of which was my bad UFS card. Good luck, looking forward to hearing positive results.

FWIW, I was able to clear this up by unplugging my miniSD module, and plugging it back in again. I’ve no idea if this will work for anyone else, but it might be worth a try.

It’s too soon to say that this “fixed” the problem, but so-far the message hasn’t appeared again, since I did that, and it’s been about fifteen minutes.

I found this post when the problem manifested right after I rebooted my laptop. The only change I made right before that was to uninstall the xen packages.

Update: I just read Craig’s post more carefully, and I see that my problem was with the same expansion slot. So I’ll be on the lookout for the return of the problem. I’ll also try the posted solution if it happens again.