Would you consider building a r2s version with r8152 driver v1.11.11 instead of current v1.10.11 ?
And perhaps with hardware watchdog support?
I've tried to find an answer to what ImmortalWrt, and how I compares to vanilla openwrt, but so fare I've found nothing. @anaelorlinski do you know more?
I will have a look. Do you know a build that has those features enabled and I then I could get patches from ?
It seems that immortalwrt includes a build of r8152 driver from realtek, at least I will add this one to start.
ImmortalWrt states "The best opensource OpenWrt variant for mainland China users.". There are many new packages and updates over vanilla to achieve various purposes, but I don't know their integration policy and release cycle.
I personally prefer to stick to stable vanilla openwrt as much as possible hence my builds, just including their great work to integrate NanoPi r2s and r4s devices.
1 Like
FriendlyWRT uses both of these:
https://wiki.friendlyarm.com/wiki/index.php/How_to_Build_FriendlyWrt#RK3328_Based_Boards
[ 17.407349] r8152 5-1:1.0 (unnamed net_device) (uninitialized): DT mac addr 06:0c:09:c1:31:94
[ 17.430906] r8152 5-1:1.0: load rtl8153b-2 v1 10/23/19 successfully
[ 17.481690] r8152 5-1:1.0 eth1: v1.11.11
[ 2.888707] rockchip-thermal ff250000.tsadc: Missing tshut mode property, using default (cru)
[ 2.889687] rockchip-thermal ff250000.tsadc: Missing tshut-polarity property, using default (low)
[ 2.892489] dw_wdt ff1a0000.watchdog: No valid TOPs array specified
Thanks for your efforts. I've found mt7662 and mt7601u firmwares within your image. Does it mean you have a positive experience of using some WiFi card/dongle with R4S as AP? My rtl8814bu is too unstable and is almost unusable as AP for several reasons.
I did not succeed to backport r8152 driver v1.11.11 that does not kernel panic. Might give another try during the next days.
Allright. Thanx anyway!
@anaelorlinski - I'm trying to compile OpenWrt using your source. It looks like the .config file is not there. Can you share your menuconfig file as an example?
Never mind, I was able to find the sample ao.seed file under seed dir and compiled OpenWrt from the source.
Made new builds for R2S / R4S that seem much more stable, (no immediate kernel oops while booting or during coremark). Here is the link : https://github.com/anaelorlinski/OpenWrt-NanoPi-R2S-R4S-Builds
I have tested the builds and they're really cool. In the 20210430 one the ssh is not working for me (though it shows up as operational over web interface). in both 20210429 builds it's working fine. Thanx for the 1.11.11 r8152 driver.
I can see there's a watchdog device in /dev/ so i tested it:
ubus call system watchdog '{"stop": true}'
After stopping the watchdog system runs for some 20-30 seconds and then hangs, requiring power cycle, instead of rebotting. I assume this means that watchdog is not supported in the build?
In any way, really thanx for your work and effort.
Did you test on R2S or R4S ? ssh not working in the latest build is strange. You can add details in a github issue if you can reproduce, it's a better place to discuss issues of my builds.
And regarding the watchdog I added the config options patches, but the driver still fails finding it, will give another try later.
I have tested it on r2s. Will give it a try on r4s over the weekend.
Allright, will report on github.
Hello community
I have had a problem with the 4GB NanoPi R4S, in which it turns on but does not start, and when it does, the following happens, it has problems with the SD card, I have tried several and the same problem happens, here I leave the dmesg of an occasion that if I start, what could it be?
Gratitude
I looked at the messages and found the following:
[ 0.606495] mmc_host mmc0: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0)
[ 0.659071] Waiting for root device PARTUUID=5452574f-02...
[ 0.876466] dwmmc_rockchip fe320000.dwmmc: Successfully tuned phase to 180
[ 0.877109] mmc0: new ultra high speed SDR104 SDHC card at address 0001
It tries to run the SD Card with 150MHz (if I am reading correctly). That could be the problem, because for this frequency, the design of the board must be very good. Could you try, if an older card not supporting such high speed or a forced lower speed in the device tree (DT) solves the problem? Usually 50MHz is fine.
The inode errors are due problems in a prior boot and non proper shutdown of the SD card.
Hello, thanks for your answer, where is the path to modify it?
Gratitude
I do not have the HW, but I am looking to buy this board. In the device tree file there should be something like this (with different values, since I found this for a different board):
&sdmmc {
clock-frequency = <100000000>;
clock-freq-min-max = <100000 100000000>;
If you lower the maximum frequency, you could give it a try.
I want to test this build on the r2s but have s question about updates. After setting this up, can I easily update or do I need to re-configure all over again?
you can update preserving config with sysupdate -c
1 Like