I started to experiment with kernel 5.10, that seems it will be the next LTS kernel, it is running well on the R2S, I noticed that it boot faster on 5.10 .
not so good. the ethernet driver is bad, and eat too much cpu time. also, it is so hot that active cooling is necessary.
although it runs at a much higher frequency than ipq40xx(1300MHz vs 717MHz), its actually network performance is just a little better.
Have anyone tried to measure the idle power consumption of the NanoPi R2S?
I saw that xiaobo in #27 mentioned 5W although I think that sounds ridiculous. I have a RockPi S which consumes approx 45mA at 5V USB-C which is 0.2W at idle (Ethernet connected, and measured using the excellent Ruideng UM25C USB meter).
I know the RockPi S is a RK3308 Cortex-A35 and the NanoPI R2S is an RK3328 Cortex-A53 but at idle I would expect them both to be very frugal.
But then again, everyone is reporting high temperatures on the R2S so something must surely be misconfigured in some PMIC driver or something?
I ran some tests on mine today with a UM34C
TL;dr Running iperf3 on both interfaces and stress -c4 draws 3.86W, 0.81A
Idle with WAN and LAN connected draws 1.45W, 0.29A
- Fresh image on SD
- connect LAN,WAN
- Power on and boot
- log in ssh, luci : install packages, permit iperf3 on wan and lan
- iperf3 LAN 3minutes (16:47) 940 Mbits/sec
- iperf3 WAN 3minutes (16:54) 940 Mbits/sec
- iperf3 LAN & WAN 3minutes (16:58) (WAN:737 Mbits/sec;LAN:571 Mbits/sec)
- stress -c 4 (17:02)
- openssl speed (17:07)
- openssl speed, stress -c2 (17:16)
- openssl speed, stress -c3 (17:19)
- openssl speed, stress -c3, iperf3 LAN & WAN (17:21) (WAN:466 Mbits/sec;LAN:601 Mbits/sec)
- stress -c1 (17:24)
- idle (17:27)
- insert usb drive (17:32)
- bonniexx -d /mnt -u nobody (17:37)
- stop services, remove wan, lan and usb (17:55)
- halt (17:59)
6 Likes
That's what I call a detailed measurement session! Very nice work!
Idling at 1.45W is much better than the 5W previously indicated. But isn't kind of odd that it consumes 300mA doing almost nothing?
Anyway, with these number I'm gonna buy one at antratek. Otherwise I would have gone with a PC Engines APU which idles at 6W.
@xiaobo do you have network issues during your reboot issue?
I experience a frequent reboot issue where the R2S becomes unreachable after a reboot. It happens both with FriendlyWRT (20200904) and OpenWRT (snapshots). The issue I see is that after a reboot, either reboot through LuCI menu or reboot command from shell, the R2S is no longer reachable on the LAN interface - I haven't yet confirmed how the WAN behaves during the issue. The issue can be cleared by rebooting a couple of times - it doesn't always clear after the first reboot. The issue can also be cleared by unplugging the ethernet cable from the LAN port for a minute - unplugging and re-plugging the cable quickly doesn't always clear it either.
Once when trying to analyse the problem, I had a ping running to the LAN interface, I noticed that very occasionally some packets got a reply. Upping the ping timeout to 20seconds got replies to most packets in the 7-14 seconds range.
I've started gearing up to analyse the issue further by connecting to the serial debug port and also monitoring the power consumption. When the issue is occurring I can now see that where I thought the R2S had crashed or failed to boot, it is running normally with zero load.
I've also noticed that the power usage is abnormal during the issue. In my post above outlining the various power usage, the issue is occurring during the first 15 minutes on the graph while I'm pinging, plugging and unplugging LAN cable and generally double-checking the networking. The power consumption should have been at the idle level.
This has had a whiff of hardware issue to me due to the issue happening with multiple operating systems. After seeing the impact on the power level, I'm more certain of that. It's like the hardware is not reseting properly. I wonder if it's to do with the USB3 bus for that interface. I'll post more results when I get time for more testing.
Hi, @poddmo
I guess the network problem is probably related to USB3 Bus (LAN), or you try switching wan and LAN, Using the openwrt Master Latest firmware I compiled, I found that the SD card failed to automatically restore boot frequency during reboot.
I noticed a strange thing, the green led on the WAN port (link led) is not always on but blinking. However, the link between router and R2S seems stable. Is this a simple led activation problem or is this a USB 3 to Gigabit driver stability problem?
Cheers zWolf
It usually means data is being sent or received on the port. It's entirely normal.
Hey friends. Thank you for getting OpenWRT on this device.
I could use some help making it boot. I downloaded the latest images, dd'd them on my sdcard, but they refuse to boot. The sys light never starts flashing, the network lights don't turn on.
Things I've tried:
- Flashed both ext4 and squashfs versions
- Tried jayanta525's build
- Tried flashing the image with etcher instead of dd
- Checked that the SD card actually has partitions and files.
- Flashed FriendlyWRT on the same card and it works fine (I'm posting this "through" it, actually)
Help?
Hi fxxr,
I just tried using https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/openwrt-rockchip-armv8-friendlyarm_nanopi-r2s-ext4-sysupgrade.img.gz from December 2nd and etcher for mac to burn to SD card.
I don't get flashing SYS light but I do get a DHCP address and can connect to 192.168.1.1 over SSH (not HTTP).
SYS and LAN are solid for me.
Try this image
1 Like
Hi, someone has tried USB2LCD module with lcd4linux packages to show some information (IP, CPU...) on lcd?
zWolf
Ran a snapshot build as my main router for a few weeks. First stint, after a few days, it wouldn’t come back up after a reboot, which I attributed to an old and possibly dying microSD card, but that’s just my guess. Second time ran fine for two weeks or so, and then one night DNS stopped working. Reboot didn’t solve issue, and other household members needed the internet, so I swapped back in my old Archer C7. I’ll probably wait until this is in a stable release before jumping back in, as diagnosing and fixing the issue is above my capabilities. When it was working, it was a great little device
Thanks for sharing your experiences! I still have the two I bought waiting on my desk weighing if it's worth the trouble at this stage as people seem to have mixed experiences. Two week uptime would definitely not be reliable enough for my planned purpose. 
. Theoretically I might have one of them unattended for several months during the winter.
Is this particular build by any chance proven to run somewhat stable (compared to just flashing the latest snapshot)?
@edwrap @ristomatti Mine R2S is up to 120 days or so without needing a reboot.
1 Like
@xiaobo With the image you linked? That sounds more like it! Hmm but if it is an earlier snapshot, how could I install additional packages? Primarily I'll be needing WireGuard but might also come up with other uses.
@ristomatti Here are some commonly used packages (and WireGuard) that hope will help you.
R2S images and packages all in one
2 Likes
Hello,
I'm running openwrt on the box for weeks without any issues. The box did reboot only because i had electricity problem and it happened 3 times.
For now, the box is up for 38days.
Thanks! I'm getting more optimistic about this 
. I haven't yet had time to check the image xiabo linked but just to have options - did you use a snapshot build or perhaps the one shared by xiabo? If snapshot, how recent was it?