After finding out that Github@Inindev made a stable fully working (as far as I can tell by my first tests) build for these SBC’s with mainline Linux Support I thought creating a dedicated topic about getting DietPi off the Rockchip/FriendlyElec kernel for the R5S and R5C.
My tests showed that I could boot with no issue.
Linux nanopi-r5s-arm64 6.1.0-10-arm64 #1 SMP Debian 6.1.38-1 (2023-07-14) aarch64 GNU/Linux
lspci showed all Nics and my JMB585 Sata Controller too
This should hopefully fix the issues regarding kernel level wireguard and just bring longevity to these SBC’s
For my testing I put the prebuilt image on a micro sd card and booted holding down the maskrom button for around 5 secs before plugging the SBC back to power. Conveniently made a dd backup of the emmc and had no issue copying that image on a usb 3 thumb drive.
What I plan on doing next is run the dietpi script on the clean debian bookworm image as well as built an bullseye image and run the script on that (as I need OMV6 on my main R5S and that has no bookworm support)
Curious… can this effort be expanded to include the R6S, R6C and NanoPC-T6 SBCs? I’m interested because I am considering purchasing one of these units and would love to have mainline Linux Support vs the FriendlyElec kernel for long term support.
@CA_Lobo Can theoretically yes (and I hope so) but there’s no mainline support yet for the friendlyelec rk3588 sbc’s. Maybe someone will get to it at some point. The support for the R5S/C was there for the past 4 months but nobody had made a fully working image until recently. If more people get the RK3588 based ones I wouldn’t be surprised if they get mainline support too bc if I’d upgrade my R5S it would be to one of those
I tested on my R5S. It did not start. With or without masking the ROM, it does not start.
I tested on a SD card. Can it be the reason ? Is it necessary to copy it on the eMMC ?
I have the 4G RAM variant, with a 128GB SSD inside.
I’m not sure if it’s worth the time to make an image with the bullseye-backport 6.1 kernel instead of the actual mainline 5.10 kernel. I’d say we’ve already got every need covered by the DietPi-Bullseye image or the FriendlyElec Bullseye image that exist by now.
The focus should be on Debian 12 which has proper mainline support and DietPi-Bookworm to be based on the mainline kernel for the R5S/C
Totally agree with you!
I saw it as a nice to have when the option presented itself that it’s possible. When the software I run (mostly helt back by OMV) gets bookworm support I see no reason to keep the Debian 11 with (6.1) mainline effort up especially since 6.1 is already EOL and >6.3 is strived for.
As for DietPi Github@Inindev’s Image’s seem to be a fitting base to run the DietPi installer script on.
I saw that there’s a Bookworm Image available already for DietPi on the R5S but don’t know which Kernel it’s running on. Is it still the 5.10.x rockchip one or mainline?