I noticed same problem sometimes on X96_x4 rev. 1.3 on
CoreELEC 20.2 ng stable.
What helps, is to deacivate LAN in CoreELEC Settings, and activate it again after that. No reboot required.
Also i have switched off WLAN.
I have also deactivated WLAN. For me turning LAN ON/OFF in CoreELEC settings is not working so often. In my situation it works only when i pull out the LAN cable and plug it in again
I checked also dmesg in console to see what is causing that problem that the LAN Adapter is not detect during boot, but without luck yet.
I use the same cable with an RPI and never had a problem. I also thought about bad contacts in the new android box first, but the box is never loosing ethernet when it once booted successfully with LAN. I can stream videos without any issues then.
I guess this problem appears during the boot process. Is there any tool in CoreELEC to make a boot log? I just checked dmesg output, but have not found anything suspicious there. I want to find out which ethernet adapter is in the box exactly.
This is all i found in the dmesg output about the eth interface:
RX Checksum Offload Engine supported
COE Type 2
TX Checksum insertion supported
Wake-Up On Lan supported
Enable RX Mitigation via HW Watchdog Timer
libphy: stmmac: probed
eth%d: PHY ID 937c4032 at 0 IRQ POLL (stmmac-0:00) active
eth%d: PHY ID 937c4032 at 7 IRQ POLL (stmmac-0:07)
I have the S905X3 chipset, so you suggest i should flash the S905X4 image to my sd-card and try booting that?
My idea is to set it to 100mbit full-duplex without auto negotiation with ethtool but my autostart.sh is not working in CoreELEC and there exist not /etc/network/interfaces file in CoreELEC.
I googled about this JL2XXX chip and it seems the issue is really caused during boot. It was said that the box is booting to fast in that case no ip is assigned or just a 169.xxx.xxx.xxx ip is assigned.
My Box is a S905X3 Box, but it seems this JL2XXX chip is used in lots of modern S905X4 boxes. Is there hope this driver will still be developed and this boot bug gets solved?
I think in general this driver works, when i have a successful boot with ethernet it runs rock solid.