Hello, i just got my new 11th gen laptop today, put ubuntu on it, everything was great and no problems whatsoever. but for some reason now, my ethernet is not working anymore. at the start i just needed to plug in the cable and it was done. now it is gone. i am new to ubuntu so i dont really know how to troubleshoot connection problems. it is just weird that for hours it works flawlessly and now it doesnt anymore. the card sometimes gives a milisecond a orange LED flash, so it gets power. but any idea how i can fix this? i already restarted but nothing. wifi works fine. but i want to use the cable.
under network in the settings, it says cable unplugged and in that setting, āconnect automaticallyā is checked. so any ideas what i could do? thanks
EDIT: it seems to be an ubuntu problem. the card is regonized but many others had this bug on their ubuntu on different versions. i cant find a solution to mine yet. help is still appreciated, if someone else with a fw laptop had this issue on his 22.04 ubuntu desktop.
it really sucks, that i bought the ethernet card to use it and then the software doesnt work with it.
My name is Matt Hartley and I am the brand new Linux Support Lead. With that, I apologize for the lengthy delay. This will not be a problem going forward because I am handling Linux support, personally.
Letās tackle this first at a hardware level. Please open a terminal and type the following please, to see if we can āseeā the adapter at all.
sudo lshw -C network
Then using your mouse, please copy/paste the results back here. Based on the output, we can take the next steps to either get this working or have support see about getting you a working cardā¦output depending as to what is needed.
Okay, thus far this is looking good. Just to get ahead of this, I would power down. Reseat the expansion card, but in a different slot this time.
If itās still not working, please try:
sudo systemctl restart NetworkManager
If itās still not working, please try
sudo apt install --reinstall network-manager`
Also please try another cable. Additionally, itās worth trying a shorter cable near the router itself as this is often used to determine if this is in fact a cable issue. Iāve seen this happen before at another position I held previously.
Give these steps a shot, let me know if this helps at all.
Hi, I tried each of the above steps, but havenāt had any luck. Let me know if there are any additional commands or logs I can grab to help diagnose the issue.
It may also be worth mentioning that when I close/sleep my laptop and then plug in the ethernet cable, I see normal looking activity from the framework ethernet dongle (flashing lights of both colors), but then once I open or wake the computer, the ethernet dongle stops showing any activity.
Oh wow, that is really interesting! I just received my own ethernet expansion card and I have the exact same problem. Linux doesnāt detect any carrier on the card, but when I suspend the laptop, the LEDs go back up as if there was a link then! Pop open the lid again, and boom, as soon as Linux resumes, the LEDs go off. They blink a little from time to time, but itās just a blip, not a solid āyep, we have a link hereā.
Here are the logs when I plug in the device:
Dec 02 18:25:55 angela kernel: usb 4-2: new SuperSpeed USB device number 5 using xhci_hcd
Dec 02 18:25:55 angela kernel: usb 4-2: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=31.04
Dec 02 18:25:55 angela kernel: usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Dec 02 18:25:55 angela kernel: usb 4-2: Product: USB 10/100/1G/2.5G LAN
Dec 02 18:25:55 angela kernel: usb 4-2: Manufacturer: Realtek
Dec 02 18:25:55 angela kernel: usb 4-2: SerialNumber: 4013000001
Dec 02 18:25:55 angela NetworkManager[59731]: <info> [1670023555.2285] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/8)
Dec 02 18:25:55 angela kernel: cdc_ncm 4-2:2.0: MAC-Address: REDACTED
Dec 02 18:25:55 angela kernel: cdc_ncm 4-2:2.0: setting rx_max = 16384
Dec 02 18:25:55 angela kernel: cdc_ncm 4-2:2.0: setting tx_max = 16384
Dec 02 18:25:55 angela kernel: cdc_ncm 4-2:2.0 eth0: register 'cdc_ncm' at usb-0000:00:0d.0-2, CDC NCM (NO ZLP), REDACTED
Dec 02 18:25:55 angela mtp-probe[67996]: checking bus 4, device 5: "/sys/devices/pci0000:00/0000:00:0d.0/usb4/4-2"
Dec 02 18:25:55 angela mtp-probe[67996]: bus: 4, device: 5 was not an MTP device
Dec 02 18:25:55 angela systemd-udevd[67995]: Network interface NamePolicy= disabled on kernel command line.
Dec 02 18:25:55 angela NetworkManager[59731]: <info> [1670023555.8143] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 02 18:25:55 angela mtp-probe[68056]: checking bus 4, device 5: "/sys/devices/pci0000:00/0000:00:0d.0/usb4/4-2"
Dec 02 18:25:55 angela mtp-probe[68056]: bus: 4, device: 5 was not an MTP device
Notice how NetworkManager doesnāt seem to like the interface somehowā¦
Hereās what iproute2 thinks of that interface:
anarcat@angela:~$ ip link show eth0 | head -1
6: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
Interesting! Thanks for creating a support ticket, is there anyway to share that link or is it private?
One last detail that may be helpful is that my ethernet expansion card was working well for a while when I first received it. It only stopped working sometime around early November (I canāt remember exactly when since I wasnāt using it that often at that time)
unfortunately, i couldnāt find a clear link. it seems thereās a message-id to keep track of threads, but that doesnāt give you a web view. Iāll give updates here as soon as i have them.
for me it never worked. which version of the laptop do you have, and on which OS?
Got a reply from support, they asked me to reproduce in one of the distros mentioned here, but I replied that someone here (@Cameron_Abma) had the same problem in Ubuntu 22.04.
They have also asked for a video where we see the behavior, which I also sent. Here is a copy:
If I reboot the laptop, the link LEDs actually come back up during the POST boot, before the kernel loads. Then when the Linux kernel runs, they turn off and then back on, steadily, until ā¦ something runs and then they turn back off.
So something is breaking this during boot, because in the BIOS, it just works! Fascinating!
I bet this is a problem with powertop. When I run powertop, there is an entry like this in the Tunables tab:
Good Autosuspend for USB device USB 10/100/1G/2.5G LAN [Realtek]
Hitting space bar here magically fixes the ethernet card, woohoo!
Or, if you will, this magic command whould turn the card back on:
Hmmā¦ Are either of you using one of those wacky āgreenā ethernet switches? If so, I wonder if there are any tools or means of trying it out with those features disabled.
@Matt_Hartley sorry for the late reply, i fixed it by reinstalling ubuntu. for now, no issues with the adapter or the cable. so sorry, i cant show you any data anymore, what i could remember is that the adapter was recognized by the system, just for some reason, it would not accept the cable. anyway, sorry i didnt get responed earlier.
@SodaStream i dont know what you mean, but i use the ethernet expansion card directly to the modem/router of my provider. no switches there.
No. The first tests were performed against some generic tplink switch, and the latter test against a Turris Omnia router. Not sure what a whacky green switch is eitherā¦
Could this be that you changes some power saving settings in the first install and those were lost in the second? I used powertop here and that seems to be the root cause of the problemā¦
cant remember but i highly doubt it, i was not changing any power saving settings, just installed a bunch of stuff that is recommanded. but will try out and report back. if that would be the case, i would be super mad. it also doesnt make much sense to me, isnt wifi more costly energy wise than ethernet?
Edit: first, i have the newest ubuntu now, so 22.10, i had the issue with 22.04, so it could be already fixed. but i have here now the power saver option and the automatic power saver enabled. and ethernet works fine.
As @anarcat already posted, the device/chipset doesnāt seem to be playing nicely with power saving optimisations. Following @anarcatās manual sysfs workaround indeed stops the immediate issue for me.
I donāt really want to have to execute ad hoc commands though (scripted or manually), so I dug a little deeper to see what was auto-configuring the device into a(n erroneous) power-saving state.
On my system at least (Ubuntu 22.04), it was TLP. Adding the following line to /etc/tlp.conf worked-around the immediate issue, and the Ethernet expansion begins working as expected upon insert, sleep, reboots etc:
/etc/tlp.conf
USB_DENYLIST="0bda:8156"
Where ā0bda:8156ā is the device id for the Ethernet expansion.
Of courseā¦ this now disables the auto-suspend for the Ethernet expansion (though Iām not sure of the power impact), so a proper solution would be to ensure the chipset/expansion behaves correctly with these power optimisations in the first place.
Ah, thatās more likely whatās causing the problem here, indeed. I was suspicious when powertop wouldnāt restore the bad behavior when re-enabling the power saving trick. It seems itās doing it differently than tlp.conf is maybe?
Anyways, I also have tlp setup, so that could also be the culprit in my case.
yeah, thatās what I told support tooā¦ I donāt think this issue is fixed just because we found the workaroundā¦
ok i have it now, after reading your comments, yes it most probably was tlp for me.
I installed it today, and did some other stuff, after a restart, the card wasnt working. i tried to edit the tlp.conf, but that didnt change it, only uninstalling tlp worked. so i will keep it uninstalled until the issue is solved. thanks for the help
Some lines of TP-Link, D-Link, and others provide a āgreenā ethernet technology which sometimes plays poorly with certain network configurations. While itās prudent to do our part in saving the planet, saving a couple watts over a year wonāt really help as much and will likely wind up with switches in ditches as people move to more traditional ethernet switches.
I thought Iād screen for that potential source of trouble, but if youāre experiencing this when plugged in to your router, then the point is moot.
