RPi4B running RaspiOS Buster Desktop „lite“
StromPi3 FW 1.72 (not flashed yet) + LiFePo Pack – nothing soldered yet – minicom & gui access working
I am randomly losing IPv4 Ethernet connection to my Pi which does not seem to happen when I remove the StromPi3. Disconnects happen after 30 Minutes to 2-3 days. This is happening on TWO RPi4Bs only when the StromPi3 is attached. Solution: reboot
Running on stock image from raspberry pi (Desktop w/o recommended software). Bluetooth disabled, WiFi disabled, Ethernet IP address configured statically (dhcpcd.conf) and only samba client and xrdp installed.
journalctl shows something (MAC address) claiming my ip-address. This does not happen when the StromPi3 is not attached.
Now I know this sounds strange to attribute to the StromPi3 but i have tested this on 2 RPi4Bs and they both behave the same way (same StromPi3 – I only own one). Right now my RPi4 has an uptime of almost 5 days without the StromPi3, never managed more than 2 days without losing connection. Anyone else experienced this?
It is working!!
Almost 4 days uptime and not a single drop of the ethernet connection from which it would have to recover and could potentially fail.
Solution: disabled „Energy Efficient Ethernet“ – add to /boot/config.txt:
I have no idea why this problem isn’t more widespread. I found this setting in a thread concerning an RPi3 with a very similar problem:
I didn’t have the same entries in my logs but that might be because I was using journalctl instead of syslog.
Even though most Pi users might use wifi, and of those using ethernet even fewer might use a static IP configuration like I do (all assumptions) but still the sheer amount of Pi’s out there should amount to more people experiencing this. Especially since I am using the raspi stock image and have installed almost nothing on top. Maybe a hardware issue – I will test that second pi4 again once I have it at my disposal. Maybe it was always only the one pi and I mixed them up at some point… i have an RPi3B+ with the same stock image of buster running with the same ethernet configuration and it has never shown this behaviour.
Very esoterical at this point ^^
Thanks for the advice and „seelischen Beistand“ Nils!