Some of those other rockchip devices are another story, but for R4S the only unofficial patches I use are the immortalwrt reboot fix and and a 1.6/2.0 overclock, neither of which should be submitted to official openwrt. If we can get the new friendlywrt uboot patches upstream that properly fix the reboot issue, the R4S will be in good shape for official builds (at least the 4GB, not sure if the 1GB version needs additional patches).
1 Like
Can you confirm that patches 301 and 302 will solve the reboot issue? I use to do my own builds from OpenWrt official repository, and while waiting for my new R4S to be delivered I will prepare my image.
Since I understand that current OpenWrt code has a reboot issue, I would like to add these patches from FriendlyElec to my OpenWrt builds to have this issue solved (until these patches are officially added to OpenWrt repository).
In terms of me squinting at this image, you have an a72 core pegged at the 500Mbit setting with SQM enabled?
I keep hoping to get back "flent" results from testing things more coherently (torrent is a good choice, btw), would it be possible for y'all to run the test outlined over here w/without SQM?
I don't own a R4S so I can't confirm that, I was just doing my homework on potential new router options to see how well they were supported by stock OpenWrt and how much work I'd be stuck doing if I had to maintain a private branch.
1 Like
Completely stock OpenWrt on the R4S 4GB is perfectly fine as long as you are not planning on running docker applications from your SD card and don't care about overclocking. The official patch does fix the reboot issue, but it does it by completely disabling high speed signaling on the SD card. If you are not running docker apps from the SD card, then you would probably never notice the speed difference and there would be no need to maintain a private branch.
1 Like
R4S should be getting CE extentions with next release. (Its been merged to master so snap shots should have it "soon(tm)" )
1 Like
The R4S wiki page has a section on load balancing and setting IRQs but there is now a main page on the openwrt wiki explaining in more detail.
4 Likes
Maybe it's me, but the image at https://downloads.openwrt.org/releases/22.03.0-rc1/targets/rockchip/armv8/openwrt-22.03.0-rc1-rockchip-armv8-friendlyarm_nanopi-r4s-ext4-sysupgrade.img.gz is corrupt, and gives a (useless) error when expanding it with Ubuntu or a Windows utility. Downloaded uniquely on each.
wasted a bit of time before I then downloaded the FreindlyELEC version, and successfully got the unit to boot.
I know I can build my own image, but wanted to start with something of a known quantity.
I like the box, runs nicely. But want to be on the official OpenWRT builds. I've not followed this target, so does anyone know if the next 22.03 RC has all the goodies needed for a stable box?
It is not corrupted, as you can confirm by validating the checksum against the provided sha256 hash. These images append image meta data behing the gzipped payload, while your decompressor might complain about that, it will ignore the extra 'garbage' and do the job - sysupgrade will use this data to confirm image validity and more though.
1 Like
Hey folks,
Can someone give me some numbers of the SMB performance? Really unhappy with my numbers here (~22MB/s write - ~48MB/s read) and I am searching everywhere for clues.
1 Like
SMB should max out gigabit LAN. I don't have this yet (ordered the R5S), but my WRT32X is 5 years old and sustains 120 MB/s read and write with Samba4 on a USB3 external drive. Use it all the time streaming movies over the network to Kodi on Shield TV and some other things.
What file system are you using? If it's ntfs-3g driver it needs some tweaks that's on the wiki, most other file systems work well with default settings. exFAT is even kernel level driver supported as of kernel 5.10. NTFS will add that too when the project moves to kernel 5.15.
1 Like
Using EXT4. The problem doesn't appear to be LAN or the USB:
# lsusb -t
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=, Driver=usb-storage, 5000M
(...)
Using DD to write to the HD = ok. iperf3 = ok between my PC and the server. I think the best approach is to wait for 22.x to land and then just nuke everything.
1 Like
hello, someone knows why it stays flashing sys light in version rk3399-sd-friendlywrt-5.15-20220510. I find it strange to see that light flashing and I don't understand the reason. Thank you
Cause friendlyelec left that way? You can easily change that in System -> LED Configuration and make it stay always on.
Honestly, thanks for letting me know this has launched. Seems like an amazing improvement and I need the NVME slot!
1 Like
Ok, I'll try it tonight and tell you if it's fixed.
Can you please explain this package:
dockerd with ext4 support ?
In make menuconfig, it's under Utilities > dockerd > Storage > Enable support for ext3 or ext4 as the backing filesystem
1 Like
for people looking for (non representative) benchs.
Downloading on steam at maximum bandwidth, 1Gb/s ; my r4s serve as ISP router and also does under the hood VLAN tagging/untaging + IPv4 encapsulation into IPv6 via 'map' package (ISP requirements)
Results: 47% + 69% for two cores load, 4 other cores are at zero.
OpenWrt 22.03 alsomost bare image (with realtek r8168 driver + reboot patch).
note: I inversed usage of eth ports: I'm using the original "LAN" port as the WAN one, and the original "WAN" port as the LAN one (because original WAN port doesn't handle well VLANs)
1 Like
As expected, default openwrt only saturates the two big a72 cores, as i explained here:
Also did you re-test the vlan situation with the wan port? Cause i saw that your report about this situation is from over an year ago. I don't use vlans on the wan my self but i know at least 3 other ppl that do use them with the R4S and they did not find issues... So i am curious to know if you re-test it before going strait to inverting the ports? To see if the situation remains even now? Also does this issue occur with friendlywrt?