Image | Radxa ROCK 3 Model A

[cbake886]

I am wondering if we can get a port of DietPi for one of Radxa's new SBCs, the ROCK 3 Model A (https://wiki.radxa.com/Rock3/hardware/3a)?

ROCK 3A is basically a little brother of ROCK Pi 4, with some improvements from the experience on ROCK Pi 4, the main features are:

• RK3568 based, Quad A55 up to 2GHz, Mali G52 GPU, 0.8T NPU
• pluggable eMMC module, 2/4/8GB LPDDR4 3200MT/s, dram controller frequency up to 1560MHz
• QC/PD power support, with a new generation QC/PD protocol IC
• Two USB2 same as ROCK Pi 4, two USB3(1x OTG+1x HOST), the two USB3 can be configured in SATA mode with a SATA breakout cable
• GbE with PoE support
• M.2 M key for NVMe with PCIe 3.0 x2 lanes
• M.2 E key for connectivity with PCIe 2.0 x1/SDIO/UART, support WiFi 6 cards
• 1x MIPI DSI, 1x MIPI CSI, compatible with ROCK Pi 4
• 40P GPIO mostly compatible with ROCK Pi 4

[MichaIng]

Many thank for your request.

Indeed that would be great. I'll ask Radxa for a developer sample.

[Joulinar]

As far as I know we never received a single sample from Radxa. Even if they promised more than once.

[MichaIng]

I didn't ask for ROCK3 samples because the Radxa Zero's didn't arrive. However, there is a supported Armbian image, so using that as basis is should be easy to implement without testing our end necessarily required: https://www.armbian.com/rock-3a/

[cbake886]

If you can put something together I can test. Let me know. Thanks.

Edit: I donated a few cups of coffee to help move this along. :)

[cbake886]

I installed Armbian 22.08 Jammy Kernel 5.19.y from https://www.armbian.com/rock-3a/ and ran your "dietpi-installer" script. Had to choose "Generic device". Only error i got was:

Err:4 https://deb.debian.org/debian bookworm InRelease │ │ The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 │ │ NO_PUBKEY 0E98404D386FA1D9

I opened a subshell and ran the following script to resolve:

#!/bin/sh -e
tmp="$(mktemp)"
sudo apt-get update 2>&1 | sed -En 's/.*NO_PUBKEY ([[:xdigit:]]+).*/\1/p' | sort -u > "${tmp}"
cat "${tmp}" | xargs sudo gpg --keyserver "hkps://keyserver.ubuntu.com:443" --recv-keys  # to /usr/share/keyrings/*
cat "${tmp}" | xargs -L 1 sh -c 'sudo gpg --yes --output "/etc/apt/trusted.gpg.d/$1.gpg" --export "$1"' sh  # to /etc/apt/trusted.gpg.d/*
rm "${tmp}"

Upon reboot i got the following:

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
-dash: 2: /etc/profile.d/01-locale-fix.sh: /usr/bin/locale-check: not found

Tried to rebuild locale but that did not get rid of error. Had just a # as a prompt. So i installed zsh and set hostname to DietPi per /etc/hosts.

Does not seem as if the DietPi install script worked.

[ravenclaw900]

You'll have to use the Bullseye image, not Jammy.

[Joulinar]

DietPi is based on Debian and not Ubuntu. Therefore, you would need to use the Bullseye image and not Jammy https://redirect.armbian.com/region/EU/rock-3a/Bullseye_edge

Ah and you need to use DietPi Installer from development branch as we have a small issue on master that will create root user with incorrect dash shell.

[MichaIng]

Right, actually the installer should have exited automatically on distro detection, when not finding a supported Debian version 🤔.

[cbake886]

It gave me to option to select bookworm.

[MichaIng]

It should not have exited before the target distro selection is offered here: https://github.com/MichaIng/DietPi/blob/master/.build/images/dietpi-installer#L176

Only Bookworm was offended? Then this Ubuntu image seems to contain an /etc/debian_version file containing bookworm/sid 🤔.

[cbake886]

Yea it warned me about using bookworm that its bleeding edge.(when i was using the ubuntu image*)

I used the dev branch install script and the bullseye image that Joulinar linked above. Selected "generic device" when installing and it seems to be running fine. I have docker with portainer + ELK stack running with great performance. Here is a dump from dmesg attached.

dmesg_dump.txt

[MichaIng]

PR up: #5823
It has a FAT boot partition and GPT partition table like the Armbian image, to work around issues with SPI bootloader (as far as I understood). It uses "edge" kernel/u-boot branch, i.e. mainline kernel which will be upgraded not only to new LTS versions but e.g. Linux 6.0, 6.1 etc. Once next Linux LTS release is up, I guess Armbian will provide "current" branch kernel/u-boot packages, so it makes sense to switch then.

The first testing image will be also DietPi dev branch, so only to see whether boot and main functionality works, i.e. there is no rough bug in build code. Once this is verified, I'll release master branch images, also after the DietPi v8.10 release tonight.

[MichaIng]

Images ready: https://dietpi.com/downloads/images/

[MichaIng]

There was a bug in our last image, not booting because of the rootfs UUID wasn't updated in our build scripts. Solved with latest image, however, would still be great if someone could verify that all works as expected: https://dietpi.com/#download

[Fgabz]

I've tried the last image and unfortunately it didn't boot. I didn't have time right now to get some logs. I will try later

[MichaIng]

Thanks for testing. Found and fixed it: 3c9ba5b
Fixed images uploaded.

[Fgabz]

Thanks looks like it's working. I was able to boot and log in SSH

[MichaIng]

Great, again, thanks for testing!

[MichaIng]

@cbake886 @Fgabz
Has one of you time and mood to test a new image? I want to check whether it can boot without a dedicated boot partition, or even with MBR partition table instead of GPT. Image with MBR + single ext4 partition would be here: https://dietpi.com/downloads/images/testing/
If this does not boot, I'd create another one with GPT partition table but still a single ext4 filesystem only. If you have a UART adapter, that output would of course be very helpful.

[RadxaYuntian]

I was able to boot the kernel, but there was only kernel message over the serial, no login console. HDMI also had no output.

[MichaIng]

Hmm, this cannot have something to do with the partitioning if the kernel is booting already. Is it the same with the current stable image from here?

I compared both, and everything (relevant) seems to be identical apart of partitioning, especially kernel version and boot configs are the same. Also a login console should be enabled on ttyS2 (being the default debug console port, right?). Note that it may take a while before the login prompt appears on serial console due to first boot setup steps which are shown only on the main console (tty1), i.e. on HDMI. To have all boot messages on serial console, one needs to switch the two console= values in /boot/dietpiEnv.txt consoleargs= line. The one named last is the one one used for all init system logs.

[MichaIng]

New images built: https://dietpi.com/downloads/images/testing/

[wiedehopf]

Hey do you still need testing on this?
I've got one on the way as they were on sale for 20 euros with shipping: https://www.amazon.de/dp/B09NFQG69F

[MichaIng]

It should work just fine. I have not heard of any issues and we have quite a bunch of recent ROCK 3A systems running DietPi reported.