I have installed Lubuntu 20.04 on a Raspberry Pi 4 (using Ubuntu server) the installation went fine, everything seems to work except the ethernet connection (WiFi works without a hitch), it is puzzling because if I attempt to create a new ethernet connection it sees the card (eth0) and the MAC, during booting it gets an IP but when the Lubuntu desktop loads only WiFi works, what am I missing?
It is not the hardware because if for example I use Raspian ethernet works, also I didn’t have any problems during the installation using Ubuntu server.
Thanks for your reply, but the problem is not with Ubuntu Server but Lubuntu, because the OS (Lubuntu) is installed up and running, I can see and connect to any WiFi from Lubuntu but the ethernet port is the problem, to me, it seems a service or a driver for the ethernet is not loaded and I have no idea where to look.
Lubuntu is not unique relative to the other desktop flavors in terms of the kernel modules nor in terms of networking backends and configuration. Ubuntu Server is ultimately meant for more advanced users. I mean, jeez, look at the network configuration guide in the manual.
I haven’t played with it enough to know all of its nuances but its quite possible whatever you used initially to set the thing up during install is what it’s going to default to use unless you create your own fallback.
Well, the “Ubuntu Server” is nothing but a loader in this case, that been said, I’m not using Ubuntu Server at all just to install Lubuntu and the installation pretty much behaves like a normal Lubuntu install sans the Lubuntu installer, nothing is being tweaked or configured or setup to install Lubuntu on the Pi, in fact, after booting using the “Ubuntu Server” you just need to type: “sudo apt-get Install lubuntu-desktop” and that’s it, after the installation finishes you login into Lubuntu and you’re done, if you click on the tray (network) you will see the menu with Wifi networks but the Ethernet (wired network) doesn’t work, I do see a light on the port but that’s about it.
In short, in the case of Raspberries, you have to use the Ubuntu Server software JUST to install Lubuntu (or any other flavor of *buntu).
Ubuntu Server’s installer is totally separate from the installer that we use (Calamares) and the installer the other desktop flavors use (Ubiquity), so, sorry, but no.
And yes, you’re right, this is the only reasonable way to install on a Pi. We don’t really support Lubuntu on them. The images we had were supplied by a project which seems all but deprecated. In retrospect, they should likely be removed.
In any case, your solution should be to configure the network per the Ubuntu Server manual.
I understand if you don’t support Lubuntu on the Pi and I appreciate your help.
I will have then to do some research and get this corrected since Lubuntu runs like a charm on the Pi, the only thing missing is the wired connection, like I said before, it seems a non-running service or driver.
You can run lspci -nnk and look for the Ethernet card. If it’s got a kernel driver in use, it’s not a driver issue (unless it’s the wrong one which would be super bizarre). As for services, there’s only the networking service. There’s not a separate one for wifi versus Ethernet.
Yes, that’s the bizarre thing, if I attempt to create a new wired connection the ethernet shows (eth0) and even sees the MAC but no matter what you do it doesn’t connect, it is a puzzle indeed.
Might want to dig through the logs and see. Typically that would be like journalctl -u NetworkManager.service but Ubuntu Server might have something different going on so you probably want to dig through the units (systemctl list-units) and look for those units that have to do with networking or Ethernet and run journalctl -u against them.
00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2711] (rev 10)
Kernel driver in use: pcieport
01:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01)
Subsystem: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483]
Kernel driver in use: xhci_hcd
On the logs I see Ethernet but I will have to filter since there’s a lot of info and not sure what should I be looking for other that references to ethernet.
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10)
01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01)
Now journalctl -u NetworkManager.service reports this (just the first screen)
ay 10 18:51:10 ubuntu systemd[1]: Starting Network Manager…
May 10 18:51:10 ubuntu NetworkManager[20292]: [1589136670.7934] NetworkManager (version 1.22.10) is starting… (for the first time)
May 10 18:51:10 ubuntu NetworkManager[20292]: [1589136670.7936] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 10-globally-managed-devices>
May 10 18:51:10 ubuntu NetworkManager[20292]: [1589136670.7937] config: unknown key ‘wifi.cloned-mac-address’ in section [device-mac-addr-change-wifi] of file '/usr/lib/Net>
May 10 18:51:10 ubuntu NetworkManager[20292]: [1589136670.7937] config: unknown key ‘ethernet.cloned-mac-address’ in section [device-mac-addr-change-wifi] of file '/usr/lib>
May 10 18:51:10 ubuntu NetworkManager[20292]: [1589136670.8051] bus-manager: acquired D-Bus service “org.freedesktop.NetworkManager”
May 10 18:51:10 ubuntu systemd[1]: Started Network Manager.
May 10 18:51:10 ubuntu NetworkManager[20292]: [1589136670.8160] manager[0xaaaaf9074040]: monitoring kernel firmware directory ‘/lib/firmware’.
May 10 18:51:10 ubuntu NetworkManager[20292]: [1589136670.8170] monitoring ifupdown state file ‘/run/network/ifstate’.
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.3006] hostname: hostname: using hostnamed
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.3007] hostname: hostname changed from (none) to “ubuntu”
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.3014] dns-mgr[0xaaaaf905f290]: init: dns=systemd-resolved rc-manager=symlink, plugin=systemd-resolved
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.3048] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/platform/soc/fe300000.mmcnr/mmc_host/mmc1/mmc1:0001/m>
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.3055] manager[0xaaaaf9074040]: rfkill: Wi-Fi hardware radio set enabled
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.3055] manager[0xaaaaf9074040]: rfkill: WWAN hardware radio set enabled
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.3553] Loaded device plugin: NMAtmManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-ad>
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.3599] Loaded device plugin: NMWwanFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-w>
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.3612] Loaded device plugin: NMWifiFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-w>
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.3624] Loaded device plugin: NMBluezManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin->
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6385] Loaded device plugin: NMTeamFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-t>
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6414] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6417] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6420] manager: Networking is enabled by state file
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6423] dhcp-init: Using DHCP client ‘internal’
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6433] settings: Loaded settings plugin: ifupdown ("/usr/lib/aarch64-linux-gnu/NetworkManager/1.22.10/libnm-setting>
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6434] settings: Loaded settings plugin: keyfile (internal)
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6435] ifupdown: management mode: unmanaged
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6435] ifupdown: interfaces file /etc/network/interfaces doesn’t exist
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6456] device (lo): carrier: link connected
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6464] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6487] device (eth0): carrier: link connected
May 10 18:51:11 ubuntu NetworkManager[20292]: [1589136671.6501] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Well, that’s all I get when I run lspci and by the way, I’m on the Pi right now, as you can see I can connect to the internet but on WiFi I have the ethernet plugged in but it doesn’t show up.
This is the result of journalctl -u NetworkManager.service: Results file
Well I don’t have a Pi 4 to confirm that, but that’s bizarre behavior. Basically lspci should list everything connected to the PCI bus. Which is everything. But I don’t know. Pis are weird.
All I get from the logs is that it sees the interface but never uses it. Again, this gets at my feeling like it’s a matter of network configuration.
Incidentially, if you look at the official documentation, it shows an option of setting up wifi but to skip it if you’re doing Ethernet. It doesn’t necessarily say how to set up both. Since elsewhere I see folks manually configuring their networking and that’s what the documentation requires for wifi, this coincides with my feeling that you need to follow the Ubuntu Server guides. You might want to follow up on the aforementioned forum instead of here for a better answer since those folks are actually familiar with how Ubuntu Server works. We simply don’t have these problems in, well, any desktop version.
Well my friend, let me start by saying that I appreciate your time and help, but, after closer look, setting up Lubuntu on a Pi seems trickier than expected and above my pay rate, I figured out the problem with the ethernet, which is in fact working, what threw me off is that the network manager on the tray shows as ‘disconnected’ (and displays no wired connections available) but it is actually online, moreover, what also made me think I was offline is that when I ran Discover to perform updates I get an error saying that I cannot update because I’m offline but get this, if I use Muon there’s no problem, it seems Discover searches for a connection one way and Muon another, however, if I connect to WiFi then Discover works <?>, yes, Pis are WEIRD!.
There are other issues that are puzzling and made accept defeat and it’s installing software using Discover or Muon, I keep getting the ‘You are not authorized to install’ and errors like that, in other words, permissions, and no matter what I do I keep getting the same silly error.
Not all is lost, I’ve learned a few things but like I mentioned above, all this is above my pay rate.
Lubuntu rocks anyway and it’s a shame the Pi is not friendly to this awesome distro.
Yeah, well, Pis are hard because they’re so unique hardware wise. I’m a little baffled at how problematic all of these things are. Like I have never seen the whole Muon/Discover issue over different connections. Ever. The issue about permissions might make sense. Normally in Ubuntu the main user has admin permissions. They need to enter a password to do certain tasks, but they have permission. In the Debian world, this is not the case. Instead, you have to log in as the root user to do all of the stuff that requires elevated permissions. Maybe Ubuntu Server is like that?