Rock 4C Plus Dietpi Install problem

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

April 26, 2026. I tried installing DietPi images for the Radxa Rock4CPlus.

All 3 versions did not initiate install (no activity, just green light)
Search previous workaround Dietpi installation on Rock4C Plus

tried to download “fixed” image provided by MichaIng

directory available, but when link clicked, nothing downloads (when clicked goes to top of page/parent directory)

if the image worked in 2025, why its not working in 2026? what changed?

the SBC works using the rock-4c-plus_bookworm_kde_r2.output_512.img.xz image downloaded from Radxa site. But its a desktop image. I wanted to run the unit as a dietpi driven headless unit.

Thank you for your attention on this matter.

2

hmm, its been a month and no solution yet…
am I correct to assume DietPi support for this board has expired?
or maybe I need a few more months?

just asking…

3

@MichaIng can you have a look please

4

This version of course has long been moved to stable builds. Requests to images which do not exist (a “testing” image in this case) are rewritten to the images directory, so one might find there what one is looking for.

No reason to get spiteful, all support is best efforts. But sorry that we missed your topic.

I had a look through build logs, packages, the image, Armbian sources, and reviewed the fix we applied that you linked: Looks all good, and the fix still applies the same way. U-Boot sources have not changed below it, aside of a patch for Btrfs filesystem when compression is used, which however does not apply on our ext4 image.

Hence I would need serial console output to know what is going wrong. Do you have a UART adapter? I sadly do not own this board myself to test.

I hope this v1.41 revision is not a new one which differs too much to boot with those U-Boot sources :roll_eyes:. I could do a test build with U-Boot bumped to latest upstream version, though I see no real changes in the build config or mainline device tree, or anything indicating a new revision.