Odroid C2 : no eth0 with latest image


Recommended Posts

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

Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

I don't know if this is related, but I just made a fresh build from current master for Odroid HC4.

 

The networking works fine in initramfs (for cryptroot unlock) but after full boot I can't seem to get the interface up no matter what I try (it stays DOWN, no error messages or anything).

 

e.g. ifconfig eth0 up, ip link set dev eth0 up, and then either static (ip a add) or dhclient, nothing. With or without NetworkManager.

 

initramfs picks up dhcp fine, though. I'll try to rebuild a tagged release and see if anything changes (as this is working fine on my C4s built from an older commit)

Link to post
Share on other sites

Hi,

 

I got the same problem on my ODROID-C2 as Elclaudio.

 

Older images with Linux 3.x or 4.x kernel are working fine, but on all recent images with Linux 5.x eth0 seems to just not work.

On the not working images I also see as first message during boot: "Net: Could not get PHY for ethernet"

 

I already tested the following images:

 

working:
Armbian_5.49_Odroidc2_Debian_stretch_default_3.16.57.img
Armbian_5.95_Odroidc2_Debian_buster_next_4.19.69_minimal.img

not working:
Armbian_20.08.22_Odroidc2_buster_current_5.9.6.img
Armbian_20.11.10_Odroidc2_bullseye_current_5.9.14.img
Armbian_20.11.10_Odroidc2_buster_current_5.9.14.img
Armbian_21.02.1_Odroidc2_bullseye_current_5.10.12.img
Armbian_21.02.1_Odroidc2_buster_current_5.10.12.img
 

Here more info on the latest working and latest not working image:


Armbian_5.95_Odroidc2_Debian_buster_next_4.19.69_minimal.img
uname -a: Linux odroidc2 4.19.69-meson64 #5.95 SMP PREEMPT Mon Sep 2 01:21:39 CEST 2019 aarch64 GNU/Linux
System diagnosis information armbianmonitor -u: http://ix.io/2Qxu

 

Armbian_21.02.1_Odroidc2_buster_current_5.10.12.img
uname -a: Linux odroidc2 5.10.12-meson64 #21.02.1 SMP PREEMPT Wed Feb 3 21:06:36 CET 2021 aarch64 GNU/Linux
System diagnosis information armbianmonitor -u: http://ix.io/2Qxx

 

Let me know if I can provide any more info (logs etc.).

 

Greetings,

Chris

Link to post
Share on other sites

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 ?

Link to post
Share on other sites

Hi,

 

I now also tried the focal image "Armbian_21.02.1_Odroidc2_focal_current_5.10.12.img", with the same result as the 5.10.x buster image:

uname -a: Linux odroidc2 5.10.12-meson64 #21.02.1 SMP PREEMPT Wed Feb 3 21:06:36 CET 2021 aarch64 aarch64 aarch64 GNU/Linux

System diagnosis information armbianmonitor -u: http://ix.io/2R7V

 

My ODROID-C2 board revision is the same as Elclaudios: rev0.2 20171114

 

@Elclaudio: I tried the dtb file you suggested but it did not make a change, still no ethernet :(

Link to post
Share on other sites
14 hours ago, blacki2 said:

Hi,

 

I now also tried the focal image "Armbian_21.02.1_Odroidc2_focal_current_5.10.12.img", with the same result as the 5.10.x buster image:

uname -a: Linux odroidc2 5.10.12-meson64 #21.02.1 SMP PREEMPT Wed Feb 3 21:06:36 CET 2021 aarch64 aarch64 aarch64 GNU/Linux

System diagnosis information armbianmonitor -u: http://ix.io/2R7V

 

My ODROID-C2 board revision is the same as Elclaudios: rev0.2 20171114

 

@Elclaudio: I tried the dtb file you suggested but it did not make a change, still no ethernet :(

 

thanks for you feedback blacki2 and your test of focal variant, it will spare me some time messing around.. I'm more and more conviced the issue is related either to uboot and/or the dtb.

 

 

Link to post
Share on other sites
8 hours ago, Dbrooks said:

Same problem here, ODROID-C2 - worked when I built it off the image Armbian_21.02.1_Odroidc2_focal_current_5.10.12_desktop.img, but after a couple of apt updates the ethernet is gone.  Currently working around with a USB network dongle... far from ideal.

 

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 ?

Link to post
Share on other sites

I dont know which revision my C2-board has, but it does work with ethernet and since many apt-updates ;)

 

  ___      _           _     _    ____ ____
 / _ \  __| |_ __ ___ (_) __| |  / ___|___ \
| | | |/ _` | '__/ _ \| |/ _` | | |     __) |
| |_| | (_| | | | (_) | | (_| | | |___ / __/
 \___/ \__,_|_|  \___/|_|\__,_|  \____|_____|

Welcome to Armbian 21.02.2 Buster with Linux 5.10.15-meson64

package bsp-kernel[21.02.0-trunk] u-boot[21.02.1] dtb   [21.02.0-trunk]
firmware          [21.02.2]       config[21.02.2] branch[dev]

System load:   2%               Up time:       8 days 6:04
Memory usage:  7% of 1.86G      IP:            192.168.6.3
CPU temp:      31°C             Usage of /:    6% of 29G

root@odroid-c2(192.168.6.3):~# dmesg|grep -i phy
[    1.716216] libphy: Fixed MDIO Bus: probed
[    2.153195] libphy: stmmac: probed
[    6.620887] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[    7.055166] meson8b-dwmac c9410000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=46)
[    7.069497] meson8b-dwmac c9410000.ethernet eth0: configuring for phy/rgmii link mode

 

armbianmonitor -u
System diagnosis information has been uploaded to http://ix.io/2Rc2 
 

Link to post
Share on other sites
20 minutes ago, guidol said:

I dont know which revision my C2-board has, but it does work with ethernet and since many apt-updates ;)

 


  ___      _           _     _    ____ ____
 / _ \  __| |_ __ ___ (_) __| |  / ___|___ \
| | | |/ _` | '__/ _ \| |/ _` | | |     __) |
| |_| | (_| | | | (_) | | (_| | | |___ / __/
 \___/ \__,_|_|  \___/|_|\__,_|  \____|_____|

Welcome to Armbian 21.02.2 Buster with Linux 5.10.15-meson64

package bsp-kernel[21.02.0-trunk] u-boot[21.02.1] dtb   [21.02.0-trunk]
firmware          [21.02.2]       config[21.02.2] branch[dev]

System load:   2%               Up time:       8 days 6:04
Memory usage:  7% of 1.86G      IP:            192.168.6.3
CPU temp:      31°C             Usage of /:    6% of 29G

root@odroid-c2(192.168.6.3):~# dmesg|grep -i phy
[    1.716216] libphy: Fixed MDIO Bus: probed
[    2.153195] libphy: stmmac: probed
[    6.620887] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[    7.055166] meson8b-dwmac c9410000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=46)
[    7.069497] meson8b-dwmac c9410000.ethernet eth0: configuring for phy/rgmii link mode

 

armbianmonitor -u
System diagnosis information has been uploaded to http://ix.io/2Rc2 
 

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 ?

Link to post
Share on other sites
3 minutes ago, Elclaudio said:

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 ?

Thats a bit problematic, because my C2 is my primary PiHole-Server ;)
But in the past DEV was also at 5.10.12 and did work fine - because (I think) old dev will become current? :)
and I do also user Buster

Link to post
Share on other sites
24 minutes ago, guidol said:

Thats a bit problematic, because my C2 is my primary PiHole-Server ;)
But in the past DEV was also at 5.10.12 and did work fine - because (I think) old dev will become current? :)
and I do also user Buster

 

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.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...