Hey everybody
I was hoping to get some info from the collective knowledge of the forum. I have a Radxa cm3 paired with a sourcekit pitray, no it is not 100% compatible, but i was able to flash and boot up the stock Radxa image without issues.
Now comes the tricky part:
It is intended to run as a portable lan server/private gaming server for luanti. It needs to run headless and have minimal resource usage, hence the diet pi route. If someone has managed to flash a cm3 successfully, what image did you use? I have seen numerous os images for the RK3566 but i am unsure of the RK3568. If all fails, can the conversion script trim the recommended radxa debian image down to a minimal, headless os, or because the image is large to begin with, the final image will also be large?
Any and all help, assistance and advice will greatly be appreciated
Thanks everyone
You can try to use a standard manufacturer Debian image and modify it with the DietPi Install script. Then select Generic Device. This should eventually get you where you want to go.
Thanks, the image i used was the one recommended by Radxa for the cm3, that is the one that boots. My only concern is that the image is 8 times the size of the diet pi image and, should it be trimmed down with the diet pi script, will it be able to achieve a “barebones” os? I will look into finding the smallest debian image available and trim it down as well and compare size, resource usage and functionality (if it boots)
I need to find ways to be efficient and as effective as possible to run a luanti server for my two kids as well as managing the device. I should be able to cram heimdall, ntfy, glances, luanti and cockpit into it with a bit of headroom before i run out of resources, but this depends on me managing to get dietpi to work.
Normally, the conversion script removes a whole series of packages during installation. In any case, you will need to try it, because there is a guarantee that the conversion will work.
I got round to trying the script, but failed at dbus removal. I used the generic device, master branch, generic/other device (as the radxa cm3 was not listed), choose to keep wifi config, selected the stable bookworm version, verified the keys and the script ran up to dbus removal where it timed out after 30 minutes.
I have seen that this was a issue in the past on the radxa zero, but the hardware is not identical to my cm3 and i am not sure what to do next?
Best to share a log or error message
| Removing radxa-sddm-theme (0.1.1) ...^M
│ rm: cannot remove '/usr/share/sddm/themes/breeze/Main.qml': No such file or directory^M
│ dpkg: error processing package radxa-sddm-theme (--remove):^M
│ installed radxa-sddm-theme package post-removal script subprocess returned error exit status 1^M
│ dpkg: too many errors, stopping^M
│ Errors were encountered while processing:^M
│ radxa-sddm-theme^M
│ Processing was halted because there were too many errors.^M
│ W: Target Packages (main/binary-arm64/Packages) is configured multiple times in
│ /etc/apt/sources.list.d/70-radxa.list:1 and /etc/apt/sources.list.d/radxa.list:1
│ W: Target Packages (main/binary-all/Packages) is configured multiple times in
│ /etc/apt/sources.list.d/70-radxa.list:1 and /etc/apt/sources.list.d/radxa.list:1
│ E: Sub-process /usr/bin/dpkg returned an error code (1)
i hope this is the correct information. I flashed an updated Radxa image and this is the error i get when running the script
You have 2 apt source configurations containing duplicate Debian sources
/etc/apt/sources.list.d/radxa.list
/etc/apt/sources.list.d/70-radxa.list
You would need to check and correct this. Maybe one to delete