Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

rock pi e, getting second NIC to work

Featured Replies

Hi,

 

I am struggling to get the second NIC (1Gbit) to work. The wireless and first NIC (100Mbit)  works

All NIC's connected

 

I am using Armbian 22.11.0-trunk Bullseye

 

root@rockpi-e:~# ifconfig -a
eth0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 9a:9c:84:a1:77:63  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 41

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.150.1.153  netmask 255.255.255.0  broadcast 10.150.1.255
        ether 9a:9c:84:a1:77:83  txqueuelen 1000  (Ethernet)
        RX packets 511  bytes 40303 (39.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 154  bytes 14296 (13.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 42

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlx60fb004c1ad0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.86.37  netmask 255.255.255.0  broadcast 192.168.86.255
        inet6 fe80::87c1:1dc5:ab7:6e70  prefixlen 64  scopeid 0x20<link>
        ether 60:fb:00:4c:1a:d0  txqueuelen 1000  (Ethernet)
        RX packets 4101  bytes 919466 (897.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 747  bytes 336966 (329.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@rockpi-e:~#

 

root@rockpi-e:~# nmcli connection show
NAME                UUID                                  TYPE      DEVICE
Wired connection 2  2824d9e9-002b-3206-a9e3-56101ea54125  ethernet  eth1
mesh                0f22274b-554b-47b6-899e-2ae5e1ec9e1a  wifi      wlx60fb004c1ad0
Armbian ethernet    f8b4ca43-7e6f-464a-ab38-9c8744b0dc16  ethernet  --
Wired connection 1  c7d498a6-cbdd-3daa-b1fe-c71c23dc7e70  ethernet  --
root@rockpi-e:~#

 

root@rockpi-e:~#
root@rockpi-e:~# nmcli connection up c7d498a6-cbdd-3daa-b1fe-c71c23dc7e70
Error: Connection activation failed: The device could not be readied for configuration
Hint: use 'journalctl -xe NM_CONNECTION=c7d498a6-cbdd-3daa-b1fe-c71c23dc7e70 + NM_DEVICE=eth0' to get more details.
root@rockpi-e:~#

 

root@rockpi-e:~# journalctl -xe NM_CONNECTION=c7d498a6-cbdd-3daa-b1fe-c71c23dc7e70 + NM_DEVICE=eth0
Journal file /var/log/journal/f5dd17308a32431b9d72c3f4257db559/system@488569ec21fd40be8b54f2a0c0f5271d-0000000000000001-0005ec5fc6f64b22.journal is truncated, ignoring file.
Dec 21 17:36:07 rockpi-e NetworkManager[622]: <info>  [1671640567.3994] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 21 17:36:07 rockpi-e NetworkManager[622]: <info>  [1671640567.4061] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 21 17:36:07 rockpi-e NetworkManager[622]: <info>  [1671640567.4106] device (eth0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
Dec 21 17:36:07 rockpi-e NetworkManager[622]: <warn>  [1671640567.4252] device (eth0): Activation: failed for connection 'Wired connection 1'

 

dmesg show:

[ 1519.182778] rk_gmac-dwmac ff540000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 1540.887807] rk_gmac-dwmac ff540000.ethernet eth0: no phy at addr -1
[ 1540.887850] rk_gmac-dwmac ff540000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

 

Anyone know how to solve it?

Having the same issue with board revision 1.21 - the 1Gbit NIC doesn't work.

Unfortunately I am not versed enough to patch this myself and compile my own version. In addition to that, it may break with future updates, doesn't it?

Maybe someone can implement this in the main repository so it will work for all devices?

Edited by FabulousGee
Added more information

I also have the problem that the 1000BaseT interface end0 cannot be activated on the Rock Pi E. 😞

 

I was hoping to solve the problem with the overlay mentioned in the previous post.

However, the application of the command does not work for me. Unfortunately, I have no experience with this "overlay" technology, so I can only type in the commands and hope for success. 😉

me@myhost:~$ sudo armbian-add-overlay rk3328-r8211f.dts
[sudo] password for me:
Compiling the overlay
Error: rk3328-r8211f.dts:7.1-2 syntax error
FATAL ERROR: Unable to parse input tree
Error compiling the overlay

Any suggestions?

That overlay did import fine for me, but still no luck, so currently im using older build whit older kernel (Armbian_24.5.3_Rockpi-e_bookworm_current_6.6.36_minimal) that works whit frozen updates.

Edited by maigonis

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.