Hi, I’m having some problems with my Ethernet expansion card under Linux. I’ve seen others having issues and have read through as many related threads as I can find, but I haven’t been able to find any identical to this one.
My laptop is an 11th Gen Intel i5 unit from batch 8
I’m encountering this issue on Linux Mint 21.1 (Kernel version 5.19.0-41), Ubuntu 22.04, Ubuntu 23.04 and PopOS! 22.04; The issue occurs whether the OS is installed or booted from a live-USB.
When the Ethernet card is inserted into one of the Expansion slots it will occasionally work but usually it will fail to connect and nothing will happen, the OS does not detect it and the lights do not illuminate (even if it is connected to another device).
The Syslog endlessly prints
usb usb2-port4: Cannot enable. Maybe the USB cable is bad?
usb usb3-port4: attempt power cycle
usb usb2-port4: Cannot enable. Maybe the USB cable is bad?
usb usb3-port4: unable to enumerate USB device
usb usb3-port4: Cannot enable. Maybe the USB cable is bad?
usb usb3-port4: attempt power cycle
usb usb3-port4: Cannot enable. Maybe the USB cable is bad?
usb usb2-port4: config error
usb usb3-port4: Cannot enable. Maybe the USB cable is bad?
lshw -C network does not list it and neither can lsusb, the card then has to be moved to another slot where the process repeats- sometimes it will work normally but most of the time it won’t.
Once the Ethernet card has failed to connect to an Expansion slot that slot becomes unusable until the Laptop is restarted; display adapters may or may not work in it, usb connectivity is very unreliable (intermittent and limited to usb 2.0 speeds or slower) and the log continues to print usb errors (the same ones as before, just more slowly). The Syslog prints
[ 3060.053508] usb 3-4: Device not responding to setup address.
for devices connected to a port after the Ethernet card, which is the only peripheral I have that causes this behavior.
I haven’t been able to test the card under Windows on the Framework but it seems to be fine on other Windows devices.
Any advice or troubleshooting ideas would be very appreciated, thanks!
1 Like
Ah, I did, but didn’t notice yours was gone until I had submitted it
1 Like
Hi @Photo_Max
can you share more detailed or longer dmesg / syslog?
maybe we can see some clues there as to what is happening with your ethernet expansion card.
thanks.
1 Like
This is what the Syslog prints on the occasions the card is able to work:
May 5 11:52:00 Max-FrameWork kernel: [ 28.324125] usb 2-4: new SuperSpeed USB device number 2 using xhci_hcd
May 5 11:52:00 Max-FrameWork kernel: [ 28.344756] usb 2-4: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=31.04
May 5 11:52:00 Max-FrameWork kernel: [ 28.344765] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
May 5 11:52:00 Max-FrameWork kernel: [ 28.344769] usb 2-4: Product: USB 10/100/1G/2.5G LAN
May 5 11:52:00 Max-FrameWork kernel: [ 28.344772] usb 2-4: Manufacturer: Realtek
May 5 11:52:00 Max-FrameWork kernel: [ 28.344774] usb 2-4: SerialNumber: 4013000001
May 5 11:52:00 Max-FrameWork mtp-probe: checking bus 2, device 2: “/sys/devices/pci0000:00/0000:00:0d.0/usb2/2-4”
May 5 11:52:00 Max-FrameWork mtp-probe: bus: 2, device: 2 was not an MTP device
May 5 11:52:00 Max-FrameWork fprintd[2564]: libusb: error [udev_hotplug_event] ignoring udev action change
May 5 11:52:00 Max-FrameWork kernel: [ 28.384779] usbcore: registered new interface driver cdc_ether
May 5 11:52:00 Max-FrameWork NetworkManager[914]: [1683283920.4612] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
May 5 11:52:00 Max-FrameWork kernel: [ 28.408790] cdc_ncm 2-4:2.0: MAC-Address: 9c:bf:0d:00:11:4b
May 5 11:52:00 Max-FrameWork kernel: [ 28.408795] cdc_ncm 2-4:2.0: setting rx_max = 16384
May 5 11:52:00 Max-FrameWork kernel: [ 28.408829] cdc_ncm 2-4:2.0: setting tx_max = 16384
May 5 11:52:00 Max-FrameWork kernel: [ 28.409085] cdc_ncm 2-4:2.0 eth0: register ‘cdc_ncm’ at usb-0000:00:0d.0-4, CDC NCM, 9c:bf:0d:00:11:4b
May 5 11:52:00 Max-FrameWork kernel: [ 28.409400] usbcore: registered new interface driver cdc_ncm
May 5 11:52:00 Max-FrameWork kernel: [ 28.413942] usbcore: registered new interface driver cdc_wdm
May 5 11:52:00 Max-FrameWork kernel: [ 28.417157] usbcore: registered new interface driver cdc_mbim
May 5 11:52:00 Max-FrameWork mtp-probe: checking bus 2, device 2: “/sys/devices/pci0000:00/0000:00:0d.0/usb2/2-4”
May 5 11:52:00 Max-FrameWork mtp-probe: bus: 2, device: 2 was not an MTP device
May 5 11:52:00 Max-FrameWork systemd-udevd[4195]: Using default interface naming scheme ‘v249’.
May 5 11:52:00 Max-FrameWork kernel: [ 28.425625] cdc_ncm 2-4:2.0 enx9cbf0d00114b: renamed from eth0
May 5 11:52:00 Max-FrameWork NetworkManager[914]: [1683283920.5150] device (eth0): interface index 3 renamed iface from ‘eth0’ to ‘enx9cbf0d00114b’
May 5 11:52:00 Max-FrameWork NetworkManager[914]: [1683283920.5280] device (enx9cbf0d00114b): state change: unmanaged → unavailable (reason ‘managed’, sys-iface-state: ‘external’)
May 5 11:52:00 Max-FrameWork NetworkManager[914]: [1683283920.5311] settings: (enx9cbf0d00114b): created default wired connection ‘Wired connection 1’
May 5 11:52:00 Max-FrameWork systemd-udevd[4209]: Using default interface naming scheme ‘v249’.
This is what it prints when a USB 3.0 drive is connected to an Expansion slot the card has failed to connect to:
May 5 12:17:15 Max-FrameWork kernel: [ 1197.657620] usb 3-6: new high-speed USB device number 35 using xhci_hcd
May 5 12:17:15 Max-FrameWork kernel: [ 1197.785885] usb 3-6: Device not responding to setup address.
May 5 12:17:15 Max-FrameWork kernel: [ 1197.993780] usb 3-6: Device not responding to setup address.
May 5 12:17:15 Max-FrameWork kernel: [ 1198.201623] usb 3-6: device not accepting address 35, error -71
A more complete log output from my Linux Mint install is very long, so I’ve uploaded it here - Syslog Out - Pastebin.com
hi @Photo_Max , btw have you tried reseating the expansion card and reboot?
1 Like
I have; getting the Ethernet card to work in any way often requires re-seating the card upwards of 5 to 20 times in different slots and may require consecutive reboots. Disconnecting and reconnecting a device can sometimes restore functionality to an expansion slot after the Ethernet card has borked it, but sometimes does nothing at all. The most effective action appears to be fully powering the laptop down and waiting a few minutes before trying again.
@Photo_Max Let’s make sure this isn’t Mint specific (yes, based on 22.04 Ubuntu, there are small differences worth checking).
- Create and boot to a Live Ubuntu 22.04 USB. See if you’re seeing the same log errors or similar.
- If you do, we may need to investigate the card itself. At that stage, we’d ask you to open a support ticket and ask for it to be sent directly to Linux support linking to this thread.
- Before creating the ticket, please test the Live Ubuntu 22.04 USB first.
1 Like
I’ve tested a Live USB image of Ubuntu 22.04, (and a few Distros based on it), as well as Fedora 38; they all produce the same results whether booted as a Live USB or installed to the Disk. It also seems to be more difficult to get the card to connect to either of the left Expansion slots (it seems slightly more reliable in the right ones), though I’m unsure how relevant that is.
Here is a full dmesg from a live Ubuntu 22.04 USB - UbuntuLiveSyslogOut - Pastebin.com
I’ve done more testing and it now seems that this issue is not exclusive to the Ethernet Expansion Card or Linux, so I’ve removed the Linux tag from the thread. I have been able to produce identical behavior with a whole bunch of devices and peripherals such as WiFi/Blutooth adapters, USB hubs, smartphones, cameras and storage devices.
I also installed Windows 10 and experienced exactly the same problem there. Under Windows bugged devices aren’t in device manager and display “The last USB device you connected to this computer has malfunctioned and windows doesn’t recognize it”.
I installed the latest Driver bundle and made sure my Laptop is running the latest firmware.
I also tried performing a Mainboard reset but that didn’t have any effect so I’ll open a support ticket and see if they can understand the problem.
I’ve been having this issue for a long time on the 11th gen board but it only started happening after the warranty had expired. I can really only use one of ports to charge (either) and the bottom right one to connect a monitor via DP. Attempting to connect any USB-C hub results in only one of the connected devices being detected, getting “Cannot enable. Maybe the USB cable is bad?” for all others. Plugging in a USB (either -C or -A) ethernet adapter in any of the ports results in the same error messages.
I attempted to fix things by lifting the sticker off of the USB-C ports but it didn’t help. I also discovered that the plastic cover on top of the top left port had melted 
I’m a huge fan of Framework and I’m willing to consider this experience just growing pains so I’ve pre-ordered an AMD board 
I’m really hoping for a better experience this time around 
Folks, please make sure your BIOS are current. This may help resolve any issues you’re experiencing.
11th Gen 3.19 is about to come out of beta and is looking really good.
I had a similar issue with my original Mainboard, support eventually decided that it was defective and sent a replacement which has been working perfectly well; I’ll put the 3.19 BISO on it once it’s fully released.
1 Like
Ah, I appreciate the insight. Thanks for this.