[NanoPi Neo3 OS alternatives]

Hi,
I would like to note that for NanoPi Neo3 it is quite possible to use firmware from Nano Pi R2S, because they have almost identical hardware specs.
Excellent firmware can be found here https://sd-card-images.johang.se/boards/nanopi_r2s.html, these are unoffical, minimal, pure and up-to-date vanilla Debian/Ubuntu Linux SD card images...

[NanoPi R5S Armbian Image]

Happy to help. In this assembly, there is a very interesting situation with the order and names of network interfaces, please note that in this assembly, the kernel parameter net.ifnames=0 is applied during boot, original names eth0 is enp1s0, eth1 is enP1p1s0.

[NanoPi R5S Armbian Image]

@Dysmas this possible, add udev rule with name for example

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="rk_gmac-dwmac", KERNEL=="eth2", NAME="wan0"

 

drivers list are

eth0 : r8169
eth1 : r8169
eth2 : rk_gmac-dwmac

 

[NanoPi R5S Armbian Image]

Cornelius, thanks!

#4 succeeded only 50%, needs to be tweaked in the kernel NET_SCH_FQ_CODEL and NET_SCH_FQ options...

root@r5s:~# uname -a
Linux r5s 5.19.11 #4 SMP Mon Sep 26 17:57:58 EDT 2022 aarch64 GNU/Linux
root@r5s:~# sysctl net.core.default_qdisc=fq
sysctl: setting key "net.core.default_qdisc": No such file or directory
root@r5s:~# sysctl net.ipv4.tcp_congestion_control=bbr
net.ipv4.tcp_congestion_control = bbr

 

Found problem with creating a bonding interface:

root@r5s:~# modprobe bonding
modprobe: FATAL: Module bonding not found in directory /lib/modules/5.19.11

 

[NanoPi R5S Armbian Image]

Found that BBR congestion control (TCP_CONG_BBR) is not enabled in kernel (Linux r5s 5.19.11 #3 SMP Mon Sep 26 11:14:54 EDT 2022 aarch64 GNU/Linux), it is possible to enable this feature.

 

root@r5s:~# sysctl net.core.default_qdisc=fq
sysctl: setting key "net.core.default_qdisc": No such file or directory

root@r5s:~# sysctl net.ipv4.tcp_congestion_control=bbr
sysctl: setting key "net.ipv4.tcp_congestion_control": No such file or directory

 

[NanoPi R5S Armbian Image]

13.09.2022 в 15:16, Cornelius сказал:

...custom led patch for the eth ports.

Maybe it will help with leds if add such a file, for example /etc/udev/rules.d/nanopi-r5s-led.rules:

SUBSYSTEM=="leds", KERNEL=="green:wan", ACTION=="add", ATTR{trigger}="netdev", ATTR{device_name}="eth2", ATTR{link}="1" ATTR{rx}="1" ATTR{tx}="1"
SUBSYSTEM=="leds", KERNEL=="green:lan1", ACTION=="add", ATTR{trigger}="netdev", ATTR{device_name}="eth0", ATTR{link}="1" ATTR{rx}="1" ATTR{tx}="1"
SUBSYSTEM=="leds", KERNEL=="green:lan2", ACTION=="add", ATTR{trigger}="netdev", ATTR{device_name}="eth1", ATTR{link}="1" ATTR{rx}="1" ATTR{tx}="1"

 

[No way to get device serial number from /proc/cpuinfo or elsewhere.]

This should work:

# cat /proc/device-tree/serial-number