Elclaudio

HI Guidol Thanks for taking the time to test on your board. We don't have the same revision but I doubt it has an impact on this particular issue according to the hardware revision change. Your log showed that you are connected through a 100Mbps link only. I tried to do the same with an old switch but it didnt change anything. I tried also to boot without the ethernet cable attached, here again, no changes. For me Old armbian works: Linux odroidc2 4.19.69-meson64 #5.95 SMP PREEMPT Mon Sep 2 01:21:39 CEST 2019 aarch64 GNU/Linux latest armbian don't.

I understand. still if you have an sdcard around you could put latest stable armbian to it and boot, just to see if the network is working. You don't have to configure anything, just ping another host. In mine, I see eth0 with "ip a" but I can't communicate at all. If you feel this doesn't worth it, don't do it.

You appear to use the DEV branch no ?? We are talking about the stable one, the one that is proposed at download, at least I do. Could you just fresh download the lastest stable on a sd card https://redirect.armbian.com/odroidc2/Buster_current And report back ?

Thanks for reporting the problem, hopefully this will trigger interest because in this situation the odroid c2 is UNUSABLE with ARMBIAN except if used with a thrid party usb ethernet dongle. HELLO DEVS ??? COULD WE HAVE YOUR ATTENTION PLS ?

maybe related ? https://lists.denx.de/pipermail/u-boot/2019-March/362840.html

HI Sorry for not responding sooner, as a new member, I can only post 1 time every 24h... Just to make it clear, I have the latest C2 hardware revision, rev0.2 20171114 @Igor: thanks for your response. What I found strange is the fact that the network is not detected / initialized at the U-boot stage (before kernel is even loaded). I connected an USB to serial to see the U-boot messages and this is what I saw: U-Boot 2021.01-armbian (Feb 04 2021 - 00:08:45 +0100) odroid-c2 Model: Hardkernel ODROID-C2 SoC: Amlogic Meson GXBB (S905) Revision 1f:c (0:1) DRAM: 2 GiB MMC: mmc@72000: 0, mmc@74000: 1 In: serial Out: serial Err: serial Net: Could not get PHY for ethernet@c9410000: addr -1 No ethernet found. So the issue is maybe related to uboot or the dtb file ? Ps: could you unlock my account so I can post without waiting 24h? @blacki2: you have indeed the same problem, same error messages etc, this prove that the latest armbian odroid c2 images are broken. For a moment, it worked for me when replacing the armbian dtb with the meson-gxbb-odroidc2.dtb found on this site but not anymore and I don't know why. You can give it a try. This device is essential to me, it control lights, sms alerts, sensors, remote sockets, kodi etc in the house. Right now, I'm back to an old armbian version and I can't update without breaking the beast...So my question is Which device could you recommend as an upgrade to the c2 which is well supported and also bug free ? I've looked at the new C4 or the N2+ but now I fear even worse problems with thoses. Or may be a raspberry 4, however it appear to run quiet hot and underperforming compared to the odroids ?

Hi there, I've an odroid C2 device used for home automation and running armbian (uname -a) : Linux odroidc2 4.19.69-meson64 which is running stable with no problem. Yesterday, I've downloaded a fresh image of latest armbian for odroid C2, named Armbian_21.02.1_Odroidc2_buster_current_5.10.12.img.xz. Put it on a new SD card and booted. It booted correctly but I've NO network. The LAN chip doesnt work at all, altough it appear in the device list I've theses entries in dmesg: [ 2.217600] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found [ 2.217611] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found [ 2.217694] meson8b-dwmac c9410000.ethernet: PTP uses main clock [ 2.218292] random: fast init done [ 2.218418] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37 [ 2.218426] meson8b-dwmac c9410000.ethernet: DWMAC1000 [ 2.218431] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported [ 2.218435] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported [ 2.218439] meson8b-dwmac c9410000.ethernet: COE Type 2 [ 2.218443] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported [ 2.218446] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported [ 2.218538] meson8b-dwmac c9410000.ethernet: Normal descriptors [ 2.218543] meson8b-dwmac c9410000.ethernet: Ring mode enabled [ 2.218547] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer ... [ 10.568311] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.568329] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.615619] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.615634] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.716190] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.716207] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.735509] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.735535] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) the first message I see when I boot (while plug in the power) is: Net: Could not get PHY for ethernet@c9410000: addr -1 No ethernet found The device is working with older armbian version but not the latest ? Could anyone look at it because the image available for download seem's broken and should not be distributed like this. I've reverted back to my old image (that's why I don't have the full log) and lost my week end on it, trying to sort it out without success. Could this be related to the .dtb ?? Thanks you