Hello,
I am having an issue on my Raspberry Pi 4B using the aarch64 version of ArchLinux.
My setup is up to date and I am facing the issue since I have installed Arch a few weeks ago. I was using Ubuntu 20.04 (kernel 5.4) before and never had this issue so I am raising it here.
The issue is the following:
Most of the time when I am rebooting my Raspberry, the ethernet connection (eth0) stays down. I can see that the ethernet leds gets turned on after the initial boot sequence, but they are not blinking.
When it is working, the ethernet leds are turned off for a few seconds, and when they are back, it's working correctly.
For reference, I am on:
$this->bbcode_second_pass_code('', 'Linux pi 5.8.9-2-ARCH #1 SMP Tue Sep 15 00:48:59 UTC 2020 aarch64 GNU/Linux')
After more investigation, I managed to determine the following:
- When the issue occurs, the interface is down (link down). Manually setting it up afterwards $this->bbcode_second_pass_code('', 'ip link set up eth0') works but unfortunately this is something that you cannot do via SSH since you cannot connect to the machine in the first place.
- systemd-networkd reports an issue telling that "there is no such device" as eth0
- I had a look at dmesg and found the following relevant logs:
$this->bbcode_second_pass_code('', '
bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
libphy: bcmgenet MII bus: probed
could not attach to PHY
bcmgenet fd580000.ethernet eth0: failed to connect to PHY')
After some research, it seems that I am facing the same issue as reported here:
https://www.raspberrypi.org/forums/viewtopic.php?p=1725123
What I have also determined is the following:
- Rebooting via command line will most of the time trigger the issue
- Unplugging and plugging back the power cable just after will also trigger the issue
- However, if I unplug the power cable, wait for a few seconds and plug it back, the connection will set up fine and the issue won't happen
- Unplugging and plugging back the ethernet cable has no effect
This is as far as I managed to go.
I have read here and there potential solutions - delaying the ethernet connection on boot, write a script to turn it up manually after a delay etc..., but I was wondering if anybody else got a similar issue? Did anyone find a solution/workaround for this?
Could it be something to be fixed on Arch side as I did not have this issue on Ubuntu nor Raspbian?