[RESPONDED] Framework 13th AMD with Raspberry Pi board, fails to connect/initiate device Ethernet-CDC, USB device disconnects intempestively

Framework Laptop 13 Linux
,
1

Which Linux distro are you using?
NixOS

Which release version?
24.05
(if rolling release without a release version, skip this question)

(If rolling release, last date updated?)
Rolling release possible using unstable branch

Which kernel are you using?
6.10.3

Which BIOS version are you using?
3.05

Which Framework Laptop 13 model are you using? (AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™)
AMD Ryzen 7040 Series, 7 7480U, 64GB, Expansion card USB-A

Logs :

[550675.670174] usb 1-2: New USB device found, idVendor=0525, idProduct=a4a2, bcdDevice= 6.01
[550675.670181] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[550675.670184] usb 1-2: Product: RNDIS/Ethernet Gadget
[550675.670187] usb 1-2: Manufacturer: Linux 6.1.21+ with 20980000.usb
[550675.732461] cdc_ether 1-2:1.0 usb0: register 'cdc_ether' at usb-0000:c1:00.3-2, CDC Ethernet Device, 0e:5c:ef:c1:c8:f2
[550675.746189] cdc_ether 1-2:1.0 enp193s0f3u2: renamed from usb0
[550675.775867] usb 1-2: USB disconnect, device number 26
[550675.776078] cdc_ether 1-2:1.0 enp193s0f3u2: unregister 'cdc_ether' usb-0000:c1:00.3-2, CDC Ethernet Device
[550676.016386] usb 1-2: new high-speed USB device number 27 using xhci_hcd
[550676.147301] usb 1-2: New USB device found, idVendor=0525, idProduct=a4a2, bcdDevice= 6.01
[550676.147310] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[550676.147314] usb 1-2: Product: RNDIS/Ethernet Gadget
[550676.147317] usb 1-2: Manufacturer: Linux 6.1.21+ with 20980000.usb
[550676.212469] cdc_ether 1-2:1.0 usb0: register 'cdc_ether' at usb-0000:c1:00.3-2, CDC Ethernet Device, 0e:5c:ef:c1:c8:f2
[550676.224132] cdc_ether 1-2:1.0 enp193s0f3u2: renamed from usb0
[550679.300017] usb 1-2: USB disconnect, device number 27
[550679.300171] cdc_ether 1-2:1.0 enp193s0f3u2: unregister 'cdc_ether' usb-0000:c1:00.3-2, CDC Ethernet Device
[550680.348339] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[550680.463308] usb 1-2: new high-speed USB device number 29 using xhci_hcd
[550680.800106] usb 1-2: New USB device found, idVendor=0525, idProduct=a4a2, bcdDevice= 6.01
[550680.800113] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[550680.800117] usb 1-2: Product: RNDIS/Ethernet Gadget
[550680.800119] usb 1-2: Manufacturer: Linux 6.1.21+ with 20980000.usb
[550680.852569] cdc_ether 1-2:1.0 usb0: register 'cdc_ether' at usb-0000:c1:00.3-2, CDC Ethernet Device, 0e:5c:ef:c1:c8:f2
[550680.869431] cdc_ether 1-2:1.0 enp193s0f3u2: renamed from usb0

Anyone else having the same issues with Raspberry Pi, I have tested an RPI Zero v1.3 and an RPI v1 as well as an RPI v3.

All those devices could not establish a connection to my Framework device via USB.

I’m not sure if it’s due to me being on KDE specifically or not hence why I would like feedback from other users ? There might be something wrong with my configuration.

2

Hi @AkechiShiro, Have you tried different USB Cables to the RPI?

3

Hello I did try multiples cables yes, I will try to again set those up, it may be my networking setup on my Linux that may be wrong, I think this issue can be closed right now, I’ll reopen it or a new one when I do try again a clean/proper setup.

4

You’ve setup your pi usb port as an ethernet adapter/gadget I think. The pi usb interface can be customized quite a bit and possibly wrongly. I suggest you try a different microsd with some default firmware? Or mount the microsd and remove the gadget script or config.

Are you using the same microsd across the different pi models?

5

I’ve burned this image on the microSD (tried on multiples MicroSD Cards) https://www.raspberrypi.com/software/operating-systems/

Always led to this, maybe due to this new interface popping trying to be managed by NetworkManager, NetworkManager is interfering with the Pi interface setup process.

6

What are you using to image the microsd? Some imaging software allows you to config the pi. Could be its applying that when you are imaging?

7

Just plain old dd also tried etcher there weren’t any differences.

8

Did you verify it works on another laptop/computer? Maybe rule out kernel issue with live iso?

9

I tried another laptop running under a similar OS or under Windows but I didn’t have much progress trying that, as I said I still need to try if I set the new interface that shows up as unmanaged by NetworkManager this would maybe fix the issue.

I’ll report back once I try that.

10

You mean the pi also didn’t show up on a Windows machine? Have you tried checking that the image you are using matches the md5 they give?

11

You might need to respecify exactly what your issue is. Are you trying to share network connection to the pi over usb?

12

I was just trying to connect to the Pi over USB