Allwinner H313 - trying to convert working armbian

Troubleshooting
1

The working secure boot armbian image works on x96q, q1 and z1 tv boxes.

Required Information

  • DietPi version | cat /boot/dietpi/.version
  • Distro version | "Armbian-unofficial 24.11.0-trunk noble
  • Kernel version | Linux x96q 6.6.44-current-sunxi64 #1 SMP Sat Aug 3 06:54:42 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux
  • Architecture | arm64
  • SBC model | Q1-V3.0 Allwinner H313
  • Power supply used | 5V 2.5A
  • SD card used | Samsung EVO Plus A2

Steps to reproduce

  1. Applied newly provided image to boot armbian
  2. Followed steps to convert to DietPi

Expected behaviour

  • Script Completion

Actual behaviour

  • Script Failure
  • Preparing to unpack ā€¦/base-files_13.5_arm64.deb ā€¦
    dpkg-divert: error: ā€˜diversion of /lib32 to /.lib32.usr-is-merged by base-filesā€™ clashes with ā€˜diversion of /lib32 to /lib32.usr-is-merged by base-filesā€™
    dpkg: error processing archive /tmp/apt/archives/base-files_13.5_arm64.deb (ā€“unpack):
    new base-files package pre-installation script subprocess returned error exit status 2

Extra details

  • ā€¦
2

Dont use ubuntu based image, for converting use debian based armbian.

1 Like
3

oh thanks. I was not aware armbian was using both. I have asked the dev that made this image to share with me a debian based version if possible.

4

ok - so I now got a debian version of the image, and the script ran nearly all the way.

my issue now is that I get hung up here:
[ ā€¦ ]A dependency job for serial-getty@ttyS2.service failed. See ā€˜journalctl -xeā€™ for details.
[FAILED] DietPi-Set_hardware | systemctl start serial-getty@ttyS2

it disables all the ttysX and then appears to be re-enabling them.

Does that make sense?
[ OK ] DietPi-Set_hardware | Setting in /boot/dietpi.txt adjusted: CONFIG_SERIAL_CONSOLE_ENABLE=0
[ OK ] serialconsole disable | Completed
[ SUB1 ] DietPi-Set_hardware > serialconsole (enable)

edit: script will run all the way if I choose a different hardware profile instead of the generic selection. however, it will not boot after, understandably. This image, is a ā€œsecure bootā€ armbian image that loads great on the H313 based Q1 (tv-box). So my question would be, if I can get the generic to complete properly, should it respect the existing secure boot?

5

@MichaIng

development is not in my skill set - but quick question. for the dietpi-installer script, is it possible to have it leave the current components for booting in-place? The armbian image I am trying to convert to dietpi is custom compiled for this H313 and secure boot. Itā€™s a simple and cheap tv-box that would make for great piholes and additional functions. Otherwise I can just rely on the armbian config, but would love to get dietpi functional and share an sd-image.

Is there a way to preserve this? If not, can they be re-copied or re-stored post dietpi-install ?

Or will it cause too much conflict?

Cheers!

6

Why would you break Armbian apart???

7

edit: nevermind - I see from your post history you just troll the comments providing no value, apparently just here to hate on dietpi.

I am no trying to break anything.

I am trying to get dietpi-installer to successfully run on this.

The dietpi-installer is what breaks it.

There seem to be plenty of guides online that indicate it should be doable, or is only debian/raspbian the only recommended starter images? I donā€™t see anything stating that implicitly.

2 Likes