The root cause of that is due to the Arm processor only supplying numbers instead of names in it's CPU id. The linux kernel won't convert the numbers to names because it doesn't contain conversion tables for all the manner of available cpus.
It should be possible to hardcode into the openwrt build, I guess. I'll hardcode it into the web page on my r2s when I find where that is.
Hi, I have noticed a strange thing, if I run R2S with OpenWRT snapshot and I touch or move R2S metal case it reset itself or it power off. If I use alternative firmware like Kelever1988 build based on FriendlyWRT this reset don't happening. Anyone else get this thing?
Hi, with the latest snapshot, I have some problems when I try to load some packages like openvpn-openssl / luci-app-ttyd / luci-app-statistics / wireguard..... . I have errors like missing package o incompatible packages. How can I solve this problem?
Snapshot is not stable, especially over time.. snapshot target boot images and snapshot packages are rebuilt daily. Even the next day, snapshot packages may no longer be compatible with the previous day's snapshot image. If you need/want to run a snapshot image and install packages at your leisure, you need to mirror the snapshot packages at the time you download the snapshot image. I hope all that is not too confusing
Check out this post for how I've created my own point-in-time mirror of snapshot: https://forum.openwrt.org/t/stable-openwrt-version-for-64-bit-arm-raspberry-pi4b/79062/6
I still keep an eye on the change logs, but now it's mostly for security announcements, bugs or features, rather than installation stability.
On my NanoPi R2S I my sensors output is not working.
I think I didn't include something when I did compiling, but I don't know what:
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
root@np0:~# cat /sys/class/thermal/thermal_zone0/type
root@np0:~# cat /sys/class/thermal/thermal_zone0/temp
Hi! I just received two of these from AliExpress. It took only 16 days for them to arrive so I guess I got lucky.
I'm hoping/planning to use these as Wireguard gateways to replace the current OpenVPN link I've got between our home and cottage.
I would greatly appreciate if someone who's had one of these for a longer time could give their opinion if they're reliable enough to survive some months without freezing up or crashing? The load won't be likely be much as the 4G connection at the cottage is around 20-25Mbps.
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?
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.
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?