As I’m running a project on my ancient 2012 RPi that needs fast network IO, this light-weight, headless OS called DietPi seemed interesting and I decided to try it.
So, I flashed the image, booted it up, did the setup, installed the things I needed thanks to the super easy to use setup wizard, and after it completed, it asked for a reboot. All is fine.
However, after a reboot - Ethernet stopped working. The Pi has three LEDs (FDX, LNK, 10M) related to Ethernet. From a cold boot, all three LEDs are on, however, after a couple of seconds, only the FDX light is on.
FDX light is on even if I unplug Ethernet.
I tried messing around in dietpi.txt, nothing helped.
However, after a few power cycles, somehow Ethernet LEDs stayed on and I was able to successfully join via SSH.
OS is blazing fast, and transferring a video file over Ethernet from the Pi to my PC, the speed is 10.5 MB/s (this is with an overclock, but damn - Raspberry OS only managed 3.5MB/s with the same OC)
I tried rebooting the Pi again, and alas - only the FDX LED is lit. No IP, no nothin’. Re-plugging the Ethernet cable makes no difference.
It feels like the OS is not properly turning on the eth0 device. That’s my best guess.
- My router doesn’t see the Pi.
- I’m using DHCP.
- Raspberry Pi OS doesn’t and never had this problem on my particular Pi.
- Confirmed that NET_ETHERNET_ENABLED=1 and NET_WIFI_ENABLED=0
- Tried different NET_ETH_FORCE_SPEED settings
- Tried different CONFIG_BOOT_WAIT_FOR_NETWORK settings too
The problem seems to happen randomly, and thus I do not know what could be causing it.
Tried a few times to flash a fresh image to SD. Ethernet always works on first boot, but after a first reboot - stops working. Took me a good amount of power cycles to get it going, but after another power cycle - same issue.
Other than that, loving the OS. Great work.