I successfully flashed my vivid-unit board with the Debian 12 image and it seems to work OK - thanks.
I then downloaded the sources and followed the build instructions. I did all of this in a Debian 13 `chroot` environment specifically created for this build. However, the step
sudo ./vuos pack vivid-unit
breaks with the following error:
==> Running hook: boards/vivid-unit/hooks/30-vividunit-apt Hit:1 http://security.debian.org/debian-security bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Get:4 https://vividunit.com/apt bookworm InRelease [2091 B] Reading package lists... E: Could not read from /var/lib/apt/lists/partial/vividunit.com_apt_dists_bookworm_InRelease - getline (12: Cannot allocate memory) E: The repository 'https://vividunit.com/apt bookworm InRelease' provides only weak security information.
I can work around this installing `aptitude` first and run `aptitude update` instead of `apt update`. With this the build does succeed.
Alter flashing the resulting image though the touch screen doesn't work. The desktop shows up but no touch. Connecting via the console reveals the peripherals aren't working correcty. Other than `lo` there are no network devices and the boot process repeated errors are shown:
[FAILED] Failed to start vu-btattac…nitialize Broadcom Bluetooth UART. See 'systemctl status vu-btattach.service' for details.
vivid@vivid-unit:~$ systemctl status vu-btattach.service
● vu-btattach.service - Initialize Broadcom Bluetooth UART
Loaded: loaded (/etc/systemd/system/vu-btattach.service; enabled; preset: >
Active: activating (auto-restart) (Result: exit-code) since Wed 2026-05-13>
Process: 13242 ExecStartPre=/sbin/modprobe bluetooth (code=exited, status=1>
CPU: 13ms
vivid@vivid-unit:~$
Any idea what's going wrong and how to fix it?
Vivid Unit OS build system itself already uses chroot, and it expects a normal host environment. Building inside another chroot is unsupported and may not work properly.
It is not a good practise to install aptitude to workaround an issue without understanding it. You mentioned the build succeeded eventually, but it was not the case according to your test result.
We have tested to build the system in a newly installed VM running Debian 13, and it just works by following the build instructions. I would suggest to build it directly in the real Debian 13 machine, or in a VM running Debian 13.