I’ve been using Framework AMD 13 for 8 months with a wavlink dock as a charger / dock.
Starting two days ago, the dock can no longer charge the laptop. I did perform a linux update on Saturday (Linux amd13 6.5.0-41-generic #41~22.04.2-Ubuntu) which I suspect is part of the issue.
Did anyone else see similar problem? Did you manage to get it resolved?
Oh. Bios 3.0.5, charging through the framework charger works fine (but do not have access to my attached devices). Using Wavlink WL-UMD05 dock.
Welcome to the community!
Have you tried other ports, other expansion cards, or plugged directly into the mainboard without any expansion card? Just curious. Also, have you tried charging anything else with the dock to rule out a possible issue with the dock itself?
Thanks for replying.
I tried switching cables, expansion cards and their positions.
Switching chargers obviously works.
I am wondering about the dock itself. I don’t think I have another device that requires usb-c power. I’ll see if I can come up with something. The dock USB devices do work when plugged in, just not charging.
Try power cycling the dock?
In addition to power cycling the dock, you can boot into the older kernel to see if it is related to the kernel update.
If the kernel update is what stopped it from working, please report the kernel bug to Ubuntu so they can fix the regression.
I will try that tonight. I need this machine to work.
I have a little bit more information. After a full day of not using the dock, it worked for a few minutes this morning. Then it stopped again.
I’m seeing messages like this:
Jul 09 09:51:35 amd13 kernel: usb 1-2-port4: attempt power cycle
Jul 09 09:51:26 amd13 kernel: usb 2-2-port3: attempt power cycle
It appears that both USB-C devices I have plugged in (only one is providing power, the other is passive hub), are flapping. Connecting and disconnecting, every 3 to 5 seconds.
[ 3605.677349] usb 2-2: USB disconnect, device number 48
[ 3608.094334] usb 2-2: new SuperSpeed USB device number 49 using xhci_hcd
[ 3608.118886] usb 2-2: New USB device found, idVendor=1d5c, idProduct=5001, bcdDevice= 1.00
[ 3608.118992] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3608.119045] usb 2-2: Product: USB3.0 Hub
[ 3608.119090] usb 2-2: Manufacturer: Fresco Logic, Inc.
[ 3608.371246] usb 2-2: USB disconnect, device number 49
[ 3610.781623] usb 2-2: new SuperSpeed USB device number 50 using xhci_hcd
[ 3610.800932] usb 2-2: New USB device found, idVendor=1d5c, idProduct=5001, bcdDevice= 1.00
[ 3610.800941] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3610.800947] usb 2-2: Product: USB3.0 Hub
[ 3610.800951] usb 2-2: Manufacturer: Fresco Logic, Inc.
[ 3611.079837] usb 2-2: USB disconnect, device number 50
[ 3613.492656] usb 2-2: new SuperSpeed USB device number 51 using xhci_hcd
[ 3613.517602] usb 2-2: New USB device found, idVendor=1d5c, idProduct=5001, bcdDevice= 1.00
[ 3613.517610] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3613.517612] usb 2-2: Product: USB3.0 Hub
[ 3613.517614] usb 2-2: Manufacturer: Fresco Logic, Inc.
[ 3614.014594] usb 2-2: USB disconnect, device number 51
[ 3616.428663] usb 2-2: new SuperSpeed USB device number 52 using xhci_hcd
[ 3616.449401] usb 2-2: New USB device found, idVendor=1d5c, idProduct=5001, bcdDevice= 1.00
[ 3616.449408] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
I will definitely try the older kernel after work today and report back.
I’m providing an update. Problem not fixed, but I have more information.
Problem appears to be related to ucsi_acpi module, with the fast USB-c devices power cycling every few seconds. That is what appears to stop the charging (obviously).
I tried several different kernel modules. Some changed which devices connected to usb-c behave (I had a second hub with vga output). That stopped working, one of the older versions brought it back.
I went as far back as linux-image-6.2.0-39-generic, but 6.2 is no longer compatible with some other stuff I have. It is possible that one of the 6.5 kernels I skipped over would kinda work, but probably not worth the effort.
I don’t quite have enough information to put in a problem report. I saw several similar messages both in frame.work and linux forums. Some solutions like moving display to one side did not appear to do anything for me. Same with disabling usbcore.autosuspend - did not resolve the issue.
My workaround right now is to use the framework charger and accept a loss of several USB ports. With the issue being somewhat visible I hope it will be fixed at some point in the near future.