Upgrading cubox-i Buster from Kernel 5.7.y to 5.8.y breaks ethernet


Recommended Posts

Armbianmonitor:

Upgrading cubox-i Armbian Buster from kernel 5.7.x to Kernel 5.8.y breaks ethernet and I'm unable to get it connected again. Works fine again downgrading back to 5.7.y. This occurs on multiple cubox-i devices.

 

System diagnosis information will now be uploaded to http://ix.io/2zH6

 

dmesg | grep eth0
[    4.667327] fec 2188000.ethernet eth0: registered PHC device 0
[   22.369472] fec 2188000.ethernet eth0: Unable to connect to phy


nlcli
wlan0: connected to sketch-wlan
        "Broadcom BCM4330"
        wifi (brcmfmac), 6C:AD:F8:1D:36:25, hw, mtu 1500
        ip4 default
        inet4 10.1.0.41/22
        route4 0.0.0.0/0
        route4 10.1.0.0/22
        route4 169.254.0.0/16
...
eth0: unavailable
        "eth0"
        ethernet (fec), D0:63:B4:00:87:DD, hw, mtu 1500
...

nmcli con
NAME              UUID                                  TYPE      DEVICE          
br-4ba53c1beb78   580cd8d0-4b87-432d-b072-7b2191fc3dc8  bridge    br-4ba53c1beb78
br-667404d55215   21ae2dad-0462-4880-98f2-8b56ae09dafa  bridge    br-667404d55215
br-7d46b681eda0   3dc1b651-2795-45fe-9821-7b33111d038c  bridge    br-7d46b681eda0
my-wlan           5d87696c-418b-404b-a6be-a85fd10c89cf  wifi      wlan0           
Armbian ethernet  0a5bb1f6-799d-476f-9fe4-2ecc7f4fe055  ethernet  --

nmcli con up 'Armbian ethernet'
Error: Connection activation failed: No suitable device found for this connection (device eth0 not available because device has no carrier).

sudo ip a
...
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether d0:63:b4:00:87:dd brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 6c:ad:f8:1d:36:25 brd ff:ff:ff:ff:ff:ff
    inet 10.1.0.41/22 brd 10.1.3.255 scope global dynamic noprefixroute wlan0
       valid_lft 85910sec preferred_lft 85910sec
...

sudo ip link set eth0 up
RTNETLINK answers: No such device

 

EDIT: this is link to armbianmonitor after downgrading back to 5.7.15 and ethernet (eth0) working once again

http://ix.io/2zHa

Edited by Armbian_User
Add link to diagnostics after downgrade back to working version
Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

On 10/4/2020 at 7:23 PM, Igor said:

I would suspect bug in Network Manager app since our Cubox-i in auto-testing facility - with Ubuntu Focal based Armbian - shows no troubles - no. 14:

 

https://beta.armbian.com/autotest.html

 

Upgrading Network Manager by hand or switching to some other network tooling? Did you try clean build?

Hello Igor,

 

Thanks for your response. I've had a chance to try your suggestions. None worked for me.

 

Here is a link to the armbianmonitor from a new, clean install using a fresh download of Armbian_20.08.1_Cubox-i_buster_current_5.8.5.img.xz

http://ix.io/2AvJ

and another after apt-get update && apt-get upgrade -y

http://ix.io/2AvL

 

Just to clarify, all my cubox-i's are the cubox-14x4 variant and all exhibit this issue.

 

Do you have any further suggestions I could try?

 

Thanks

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...