What is the different between openwrt and friendlywrt?
Yeah, button was pressed. Solid Red LED with no activity. Can flash it through the terminal with FriendlyWRT already installed but it renders the device unserviacable after rebooting. This is with the new 4GB model.
@Andy-Voigt FriendlyWRT is FiriendlyArm's fork of OpenWRT. I have yet to dive into the the detail of the changes they've made. One thing I have noticed with their image is that Wireguard doesn't work- even after the kmod package is reinstalled.
I found some security flaws on friendlywrt kernel debug .
7.332820] ********************************************************************
[ 7.332826] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
[ 7.332832] ** **
[ 7.332838] ** WRITEABLE clk DebugFS SUPPORT HAS BEEN ENABLED IN THIS KERNEL **
[ 7.332844] ** **
[ 7.332849] ** This means that this kernel is built to expose clk operations **
[ 7.332854] ** such as parent or rate setting, enabling, disabling, etc. **
[ 7.332859] ** to userspace, which may compromise security on your system. **
[ 7.332864] ** **
[ 7.332869] ** If you see this message and you are not debugging the **
[ 7.332874] ** kernel, report this immediately to your vendor! **
[ 7.332880] ** **
[ 7.332885] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
[ 7.332890] ********************************************************************
| __| _(_)___ _ _ __| | |_ \ \ / / _| |_
| _| '_| / -_) ' \/ _` | | || \ \/\/ / '_| _|
|_||_| |_\___|_||_\__,_|_|\_, |\_/\_/|_| \__|
|__/
-----------------------------------------------------
FriendlyWrt 21.02.3, r16554-1d4dea6d4f
-----------------------------------------------------
root@FriendlyWrt:~#
In the latest version of FriendlyWrt they fixed wireguard error. Now it's working.
1 Like
I fixed on my latest build , now we need a tool so that user can easily flash the firmware on the eMMC, the friendlywrt tool doesn't work because use a different partition, to flash the firmware to eMMC we need;
1- check the name of the device fdisk -l
2- cp the firmware to /tmp
3- dd if=openwrt-rockchip-armv8-friendlyelec_nanopi-r5s-ext4-sysupgrade.img of=/dev/mmcblk* bs=10MB ( replace * with the eMMC name 0,1,2.)
1 Like
Is there an easy way to upgrade from Friendly eMMC to your firmware with SSH?
root@NanoPi-R5S:~# fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mmcblk2: 7.28 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F0250000-0000-492E-8000-6A280000480F
Device Start End Sectors Size Type
/dev/mmcblk2p1 16384 24575 8192 4M unknown
/dev/mmcblk2p2 24576 32767 8192 4M unknown
/dev/mmcblk2p3 32768 40959 8192 4M unknown
/dev/mmcblk2p4 40960 73727 32768 16M unknown
/dev/mmcblk2p5 73728 155647 81920 40M unknown
/dev/mmcblk2p6 155648 221183 65536 32M unknown
/dev/mmcblk2p7 221184 286719 65536 32M unknown
/dev/mmcblk2p8 286720 1490943 1204224 588M unknown
/dev/mmcblk2p9 1490944 15269854 13778911 6.6G unknown
so what are * in your step 3 in my case? Is it
dd if=openwrt-rockchip-armv8-friendlyelec_nanopi-r5s-ext4-sysupgrade.img of=/dev/mmcblk2p1 bs=10MB
Thank you
Try with a sd card method first, by pressing the mask button, connect the usb power cable, release the button after 5 sec, if boot , then do the upgrade, yours is 2 (/dev/mmcblk2)
This is .img format easier to flash https://github.com/mj22226/openwrt/releases/download/rockchip-5.19/r5s.img
dd if=r5s.img of=/dev/mmcblk2 bs=10MB
2 Likes
how did you make the wan port work? i tried everything and still had issues bringing up the eth
I was wondering why the topic title is "R68s" and most of the comments are about the R5S...
1 Like
2 Likes
I think is because you are using the old bootloader and sysupgrade do not overwrite, try with a full upgrade dd if=r5s.img of=/dev/mmcblk2 bs=10MB
Image worked perfectly here!
1 Like
@mj82 first of all thanks for sharing your work.
Are you planning to upstream your changes adding support to R5S to the official OpenWrt repository?
4 Likes
Do you find that with the newer kernels the nftables and fw4 builds don't really work? Is that why you reverted to default iptables?
I moved my builds to fw4 with the new kernel 6.0.
4 Likes
So, what works with your 6.0 image for R5S, and what doesn't? Only WAN port?
I'm testing right now, all ports are working.
1 Like
Can someone please help me how to increase the / directory in the images of @mj82? I am using image with squahfs.
@mj82 Thanks for yor work! 
thanks for all the hard work. the builds work really well. everything is working, firewall and wan port also working
1 Like
I just did a custom build for the R5S from your "linux-6.0" branch. So far everything seems to be working OK.
Once again thanks a lot for your work!