rpi4 lost eth0

Problems with packages? Post here, using [tags] of the package name.

rpi4 lost eth0

Postby bloke » Fri Nov 18, 2022 8:49 am

Hi Guys,

I just did a pacman -Syu on rpi4 armv7h

These are some of the packages:
linux-firmware-20221109.60310c2-1
linux-firmware-whence-20221109.60310c2-1
linux-rpi-5.15.78-1

I now only have lo nic:
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 682 bytes 69612 (67.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 682 bytes 69612 (67.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

$this->bbcode_second_pass_code('', '$ ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: end0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether e4:5f:01:59:a5:b9 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether e4:5f:01:59:a5:ba brd ff:ff:ff:ff:ff:ff
')

I believe this is something to do with the compute module? Don't really know....
I just know my eth0 is gone. Do i go ahead and change network settings toward end0?

Is this a known problem?
bloke
 
Posts: 19
Joined: Thu Jun 25, 2020 1:06 am

Re: rpi4 lost eth0

Postby bloke » Fri Nov 18, 2022 9:28 am

Ok, i went ahead and did that and returned the system back to service

$this->bbcode_second_pass_code('', '
$ cp eth0.network end0.network
$ cat end0.network
[Match]
Name=end0

[Network]

Address=192.168.0.7/24
Gateway=192.168.0.1
DNS=192.168.0.1

$ ifconfig
end0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.7 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::e65f:1ff:fe59:a5b5 prefixlen 64 scopeid 0x20<link>
ether e4:5f:01:59:a5:b5 txqueuelen 1000 (Ethernet)
RX packets 604 bytes 58034 (56.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 179 bytes 63982 (62.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 2 bytes 140 (140.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2 bytes 140 (140.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

$ uname -a
Linux pi4server 5.15.78-1-rpi-ARCH #1 SMP Fri Nov 11 10:28:12 MST 2022 armv7l GNU/Linux
')

Why has eth0 changed to end0? Thanks in advance.
bloke
 
Posts: 19
Joined: Thu Jun 25, 2020 1:06 am

Re: rpi4 lost eth0

Postby armandleg » Fri Nov 18, 2022 1:26 pm

Same issue here. Not sure what caused this. This is what journalctl shows me during boot:

$this->bbcode_second_pass_code('', '<date> <hostname> kernel: bcmgenet fd580000.ethernet end0: renamed from eth0')
armandleg
 
Posts: 3
Joined: Sun Feb 06, 2022 3:23 pm

Re: rpi4 lost eth0

Postby markmc » Fri Nov 18, 2022 4:55 pm

same issue here, after update to 5.15.78-1 eth0 is missing and I see end0 instead
markmc
 
Posts: 3
Joined: Fri Nov 18, 2022 4:51 pm

Re: rpi4 lost eth0

Postby Oznerol256 » Fri Nov 18, 2022 7:25 pm

Same here.

Extremely annoying as i am running a headless system.
It would just not connect back to the network.
Oznerol256
 
Posts: 2
Joined: Wed Jan 05, 2022 10:40 pm

Re: rpi4 lost eth0

Postby graysky » Fri Nov 18, 2022 8:40 pm

Must be part of systemd (251.7-1 -> 252.1-1) but I didn't see anything in their changelog.

Stating the obvious here but setup the following in your systemd-networkd profile:
$this->bbcode_second_pass_code('', '
[Match]
Name=e*
')

You can force the old name by a few methods, see: https://www.freedesktop.org/wiki/Softwa ... faceNames/

Also, the current ArchARM tarball (checked aarch64 anyway) is already supplying a compatible network config for this change. This will strike users running systems based on older images.
$this->bbcode_second_pass_code('', '% cat image/etc/systemd/network/en.network
[Match]
Name=en*

[Network]
DHCP=yes
DNSSEC=no

% cat image/etc/systemd/network/eth.network
[Match]
Name=eth*

[Network]
DHCP=yes
DNSSEC=no
')
graysky
Developer
 
Posts: 1727
Joined: Sun Jun 26, 2011 6:56 am
Location: /run/user/1000

Re: rpi4 lost eth0

Postby bulletmark » Fri Nov 18, 2022 11:34 pm

Another day, another failure to boot after update on Arch ARM :(

This only happened on my RPi4, not on my RPi2. I addressed it by adding `net.ifnames=0` to `/boot/cmdline.txt` to disable network device renaming.
bulletmark
 
Posts: 98
Joined: Tue Oct 13, 2015 10:17 pm

Re: rpi4 lost eth0

Postby graysky » Fri Nov 18, 2022 11:40 pm

No one is forcing you to run this distro, you're welcome to use something else.
graysky
Developer
 
Posts: 1727
Joined: Sun Jun 26, 2011 6:56 am
Location: /run/user/1000

Re: rpi4 lost eth0

Postby bulletmark » Fri Nov 18, 2022 11:45 pm

@graysky, don't worry, I am looking at the alternatives! Any suggestions?
bulletmark
 
Posts: 98
Joined: Tue Oct 13, 2015 10:17 pm

Re: rpi4 lost eth0

Postby Andalusia » Fri Nov 18, 2022 11:49 pm

$this->bbcode_second_pass_quote('graysky', 'S')tating the obvious here


For me none of this was obvious, so just to help others that come across this thread, the files to edit are in /etc/systemd/network. I did as per the OP, and copied eth0.network to end0.network, and changed the reference to eth0 to end0 in the modified file. Fortunately an easy fix with a headless system; just pull out the drive.

@bulletmark alternatively you could contribute to testing. Personally, I am very much appreciative of this FOSS distro, and the quick response on the forums. Thanks all.
Andalusia
 
Posts: 7
Joined: Fri Nov 15, 2019 10:55 pm

Next

Return to Packages

Who is online

Users browsing this forum: No registered users and 9 guests

cron