I recently plugged my L5 into the Kensington dock that I use every day with my Windoze laptop. Amazingly, all the devices “magically” worked! (keyboard, mouse, monitor). I believe it was necessary to ‘ip addr add’ a local private LAN IP address, but even networking was functioning correctly.
After that one time, I cannot get usb0 to wake up. It seems constantly in “NO-CARRIER” state. I’ve tried a USB-C LAN dongle as well, same thing. The Settings->Network dialog shows “cable unplugged”. Again, this dongle works fine with other devices.
What am I missing? Did I inadverntently hork up the networking?
But seriously, just a stab a t the dark here, your setting of ip may have become “permanent” ip for the device, as when you normally connect to a network there should be a DHCP server that assign your device an ip. Which it can’t do, if you have an ip assigned to your L5 already. That would make this simple, but it could be your situation is more complex. Check to see what ip you have (and if it’s same with all network devices - is the situation same with all of them, can you get online?). Check online for details but I think its something like ip addr del to remove that ip. As for, if the network returns to normal with just that, I’m not sure - more details may be needed.
Things are going downhill. Used to be that usb0 wouldn’t re-appear after removing and re-inserting the USB-C Ethernet adapter. Now after upgrading to the latest kernel 6.12.0, the device doesn’t even show up after a fresh boot. Nothing under either nmcli dev (except lo device) or lsusb.
I know the adapter was working with the first insertion under the 6.6.83 kernel. 6.6.122 has the same problem as 6.12.0, adapter is not even listed under the lsusb command.
I just plugged my Ethernet adapter in to my phone and it worked correctly as usual, so I’m afraid at least one of you will have to put a bit of effort and at least show some logs, as I don’t have psychic abilities to access them remotely and debug stuff this way
Also, usb0 is completely unrelated to whatever you’re plugging in there. It’s the phone gadget’s interface, the one that’s used when you plug the phone to a PC. Your adapter will have a different interface name.
I don’t know whether it helps but plugging an ethernet USB dongle in to my phone …
ifconfig shows a new interface named enxHHHHHHHHHHHH where HHHHHHHHHHHH is the MAC address of the dongle. I can ping the IP address that is assigned to that dongle from another computer on the local network. The Librem 5 can ping the IP address of another computer on the local network. The low metric even means that by default traffic should be using the ethernet interface and, eyeballing the dongle, that appears to be the case. That is to say, with superficial testing, everything appears normal.
sudo dpkg-query --list | grep linux-image-6.6.0-1-librem5 ii linux-image-6.6.0-1-librem5 6.6.122pureos1~byz1
As such therefore I wonder whether downgrading may not achieve the desired result i.e. something else is wrong, perhaps some setting.
Although it is difficult to tell these days, I don’t think I have the same dongle as you i.e. not a Realtek.
For fault isolation, have you tried this dongle in another computer and confirmed that it works at all‽
Neither do I. Even my ethernet dongle is USB-A. I just use a USB-C M to USB-A F adapter (it is very small).
(Actually I do have USB-C portable drives and they work fine with the Librem 5. But I kind of meant USB thumb drive - because who doesn’t have a heap of those sitting around? - and I don’t have any USB-C thumb drives.)
I just had this issue today. Description and my accidental resolution:
TLDR: I had to plug the EMPTY Realtek ethernet to usb-c adapter first, THEN plug the ethernet cable into the adapter to get Librem5 to recognize it as an ethernet adapter.
Description:
I was using a Realtek ethernet to usb-c adapter to try and get a network connection. I was getting the USB0 carrier not detect type of error.
Keep in mind that my Librem5 is now a couple of years old and well used and the usb-c port is now a bit wiggly, so that is probably contributing to the issue.
I had the ethernet cable plugged into the adapter AND THEN I was plugging it into the Librem5.
I was swapping ethernet cables thinking it was a cable issue, but every time I would plug the ethernet cable INTO the adapter FIRST and then plug it into the usb-c port.
Each time ip and ifconfig would provide that error message or similar. It also did not show up in networking settings as a network device. THIS IS A BIG HINT.
Then, I accidentally plugged the ethernet adapter first and noticed that it showed up in the networking settings as an ethernet adapter so I plugged the ethernet cable in and I got internet access.
… NOTE: The big hint is in #3 above, but I had another hint shortly thereafter ….
just before #4 above, I decide to try and charge up the battery but the L5 refused and provided the useful flashing red light that say, the battery / device is too hot, I am not charing, power it off and let it cool down before you proceed. This is the second hint.
DIAGNOSIS: I think what was happening was that as long as an ethernet cable was plugged into the usb-c ethernet adapter and plugged into a switch, the phone was going into “into recharge mode” instead of turning off that circuit and enabling the networking circuitry.
REASONING: This is probably one of those issues where either I am misdagnosing the issue but still got it to work, maybe my wiggly usb-c port on the L5 is allowing for a short of some sort under specific cirumstances or perhpas it is a fault ethernet adapter. Hard to tell. However the big clue above was not showing up as a networking device and the L5 getting hot with a flashing red light indicates to me circumstantially that it was somehow trying to charge over the ethernet cable as probably there was too much current being fed into the usb-c port and triggering the recharge circuitry. Pluging in the adapter into the usb-c port without an ethernet adapter probably removed the current, allowed the device to be recognized as a networking device and that circuit was activated so that I could plug an ethernet cable in and network.
Detailed explanation that, hopefully, helps someone or helps others tell me why I am wrong and provide additional triage and testing options.
As a side point, I need to get a replacement for the bit that holds the usb-c port I think.
