stranger

That's because last Armbian kernels were using mainline r8153 driver (1.11.11). Now it's replaced with 2.14 driver that causing troubles with rk3328. I'm don't know about main repository but it's already in beta. So it will start failing again when you will upgrade kernel.

In this case Armbian is just impossible to use for Nanopi R2S. Router that losing lan interface every couple of hours is pretty bad. Maybe it's possible to add 2.14 driver as dkms package for dedicated boards instead of replacing buildin kernel driver for rockchip64? It would've fixed all problems.

I tested this quirk and it doesn't help. Nanopi R2S is still failing with r8152 2.14. You definitely should use mainline r8152 for this board.

Armbian kernel works fine on ArchlinuxARM, but r8152 start failing again with 2.14 driver as expected. In current state this kernel is bad for NanoPi R2S. I will try to add rk3399's quirck as overlay and will report later.

Yes, AUR package have it https://aur.archlinux.org/packages/linux-rockchip64/. I just need to know that this version was patched.

Does this https://beta.armbian.com/pool/main/l/linux-5.10.11-rockchip64/linux-image-current-rockchip64_21.02.0-trunk.78_arm64.deb kernel have patch built in? I can install it on my Nanopi R2S from AUR and test dwc3 quircks without messing my home net too much.

Well it's used as my main router and it's running Archlinux ARM right now so it's not not so easy to test this stuff without messing my home net for a while, but maybe I will look into it. Btw when I previously tested driver I found out that I was getting consistent r8152 2.13+ driver fail when I was opening https://browserleaks.com/dns in firefox browser on computer connected to Nanopi R2S. Maybe it will be useful for testing.

But you have patched only rk3399.dtsi. Will it work with rk3328?

Last FriendlyElec nanopi-r2s image has hardware rng, what about adding it to Armbian? For my nanopi-r2s I patched dtb, compiled kernel module with dkms and managed to make it work with rngd. Amount of enthropy increased from ~2000 with haveged/jitterenthropy to ~4000. The only problem is FIPS failures so I had to run rngd with --ignorefail flag. Here is links to FE github: https://github.com/friendlyarm/kernel-rockchip/blob/2ea3d37e1de559b9af2cd24a71bb538dddc1365a/arch/arm64/boot/dts/rockchip/rk3328.dtsi#L250-L259 https://github.com/friendlyarm/kernel-rockchip/blob/2ea3d37e1de559b9af2cd24a71bb538dddc1365a/arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2-common.dtsi#L436-L438 https://github.com/friendlyarm/kernel-rockchip/blob/nanopi-r2-v5.4.y/drivers/char/hw_random/rockchip-rng.c

There is some problem with r8152 v2.13. I tested my nanopi r2s with armbian stable, armbian trunk, openwrt, friendlywrt and arch linux: in Armbian r8152 v2.13 is always failing, in OpenWrt and FriendlyWrt with mainline v1.11.11 it works fine, in Arch Linux it works fine with 1.11.11 and failing with 2.14 just like Armbian. Friendly Elec in their last FriendlyWrt changelong for nanopi r2s noted that they reverted from 2.13 to 1.11.11 because of instability.