This section is not coming from Collabora, it’s just some information I got from a few trustee third parties and some speculation. It should be taken with a grain of salt, and I’ll update it if I get feedback from Rockchip or companies using RK3588. I was told Rockchip no longer considers RK3588 to be an “open source” chip. In practice, that means Rockchip no longer contributes RK3588 code to open-source projects (not sure when the TF-A code mentioned above was released) and they also decided not to sell RK3588 directly to SBC vendors. The latter is not a big issue, since they may be able to source chips from resellers, but it may increase prices. You may also have read that Joshua Riek who worked on Ubuntu Rockchip decided to take a break. While the reason given is mostly burnout and lack of funding, what we are discussing here may potentially explain why he was not able to get access to the Rockchip SDK.
Has anyone encountered intermittent XHR timeout in luci? I have been getting it even when I was on friendlyWRT. Flashed RC4 last night and I am still having that issue. No ping drops to the device but somehow getting that XHR timeout issues. I dont see anything suspect in the logs as well
already have uhttpd connection reuse set to 0. But
From another post I saw someone quoted that RockChip has upstreamed another patch about 10 days ago, so it doesn't look like they are stopping open source?
Are any proprietary BLOBs required for the r6s or is everything available as open source?
In any case, the two 2.5 GBe NICs are supported as OpenSource.
Only talking about the 2x2.5GbE NIC here means nothing.
The NICs are using PCI-E from RK3588, so the first thing is to find a driver to enable PCI-E driver otherwise nothing will work, folks are still working hard to get things open source as much as possible but it's not there yet (quite a number of devices usable but "not everything")
I plan to use r6s between isp and my current router orbi rbk50 which would be used as AP once setup is done.
Would openwrt provide traffic/bandwidth stats for each device connected to my orbi or it would show stats on just at orbi level? I need to monitor traffic on each wireless device as well.
Vnstat monitors traffic at the interface level and can display usage per hour, per day, and per month. Nlbwmon monitors traffic per MAC address but only displays charts per “accounting period”. The accounting period defaults to monthly, but is reconfigurable.
Assuming orbi is operating in ap mode, openwrt would show per client; you could think of the ap as a switch in this setup where it just provides physical layer connectivity (maybe L2 as well…it’s been a while). Openwrt would be issuing IP addresses and in turn be aware of all MAC addresses. If the orbi is setup to operate as a router or otherwise put its devices behind a NAT it would likely hide the downstream devices connected to it (I’d avoid this).
I did what you suggested: USB-C connected to host PC (Debian x86-64), USB-A connected to R6S (tried both USB-A ports). Can't see any serial port appear on the host (no /dev/ttyUSB*). Is there something I need to run on the R6S to make it use a host USB-A port as serial?
There is no HDMI support in OpenWrt as explained. If your network goes wrong, you can just flash another SD card with a clean OpenWrt image and restore your config backup.
Alternatively you can use the OpenWrt failsafe mode, but I don't know if it is working with R6S since it depends on mapping the MASK button (others can confirm it OpenWrt failsafe mode works with the R6S).
you can just flash another SD card with a clean OpenWrt image and restore your config backup
If you stick to running the OS from an SD card, yes. But as soon as you run the OS from the internal eMMC, the device will always head there first and ignore the SD card. This quickly gets awkward: if you want to re-flash the eMMC, you need to erase the bootloader from the running OS itself to force booting from SD again. And if that fails, the other alternative involves using a USB-A to USB-A cable and the vendor's software (on Windows). Talking from experience: my latest attempt to update using owut ended up badly, I failed to properly erase the bootloader and got stuck with a bricked device and no chance to alternate boot from SD card.
Adding support for USB keyboard and HDMI is possible, it has been done for Nanopi R5C/R5S. Agreed, it is not strictly necessary as you can use the internal serial port. I was merely pointing out it would be nice to support those directly accessible HDMI and USB sockets out of the box, like FriendlyWRT. I guess this should anyway improve over time as kernel versions increase and that support hopefully comes with newer kernels. Patience is a virtue