Allo USBridge Sparky nor GUI

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | cG_DIETPI_VERSION_CORE=9
    G_DIETPI_VERSION_SUB=18
    G_DIETPI_VERSION_RC=1
    G_GITBRANCH=‘master’
    G_GITOWNER=‘MichaIng’
    G_LIVE_PATCH_STATUS[0]=‘applied’
  • Distro version | bullseye
  • Kernel version | Linux DietPi 3.10.38 #22 SMP PREEMPT Fri Dec 22 10:45:41 IST 2017 armv7l GNU/LinuxArchitecture | dpkg --print-architecture
  • SBC model | sparky
  • Power supply used | 5V 3A
  • SD card used | SanDisk ultra

Additional Information (if applicable)

  • Software title | (EG: Nextcloud)
  • Was the software title installed freshly or updated/migrated?
  • Can this issue be replicated on a fresh installation of DietPi?
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID

Steps to reproduce

  1. Login to GIU via Webbrowser
  2. …

Expected behaviour

  • Login

Actual behaviour

  • SQLSTATE[HY000] [2002] No such file or directory (SQL: select * from `users` where `email` = admin@allo.com limit 1)

Extra details

  • Im not able to get a login while SSH runs fine
2

Screenshot 2025-11-06 142057
Screenshot 2025-11-06 1420571334×772 176 KB

3

This seems to be an extreme old system running Debian Bullseye and Linux kernel 3.x. was this a fresh install?

4

This was a fresh install on SD card. As i know the sparky will boot from sd card when plugged in?!

Maybe the internal emmc is still alive. I will desamble the USbridge will check undplug the emmc.

This was the download for dietpi SparkySBC-ARMv7-Bullseye

5

Joulinar, thanks for your reply.

I’ve now installed a new DietPi GUI on the eMMC. Unfortunately, with the same result.

Screenshot 2025-11-06 203319
Screenshot 2025-11-06 2033191896×1264 101 KB

Screenshot 2025-11-06 203531
Screenshot 2025-11-06 2035312079×1412 357 KB

6

Thhe sparky kernel is stuck at kernel 3.16 (see https://dietpi.com/forum/t/dont-panic-xpressreal-t3-and-radxa-e54c/24500/9?u=jappe)
Debian Bookworm and Trixie need at least 4.x

And I bet also the SQL server needs now some features which kernel 3.16 can not provide. So no ALoo GUI anymore possible?!
@MichaIng what do you think?

7

I talked to @MichaIng yesterday. We will drop support for Bullseye and Sparky with DietPi v10, that is planned for beginning of next year. It’s simple to old hard and software

8

Thanks for your continued support.

Is it possible to revert to older software until then? Is there an archive of previous, stable versions?

Even in headless mode, it’s not running smoothly now. Squeezelite stutters when music is playing.

9

First of all, the Allo Sparky SBC and the Allo web GUI are dedicated things, not directly related to each other:

  • The Allo Sparky SBC never got an (upstream) kernel version upgrade from Allo, so it was sadly doomed to become unusable at some point. And now Allo itself does not exist anymore. If anyone wants to try to rebase support for this SBC onto more recent Linux versions, here is their source code: GitHub - sparkysbc/Linux: Sparky linux source
  • The Allo web GUI is a result of a collaboration between Allo and Daniel (DietPi founder) from a long time ago. I updated it to work with more recent Debian and DietPi versions, and it is supposed to work on Debian Bullseye, as well as I am not aware that MariaDB would have issues with Linux 3.10.y. I’ll test it.
10

Thanks for the information. It would be a shame to lose the USBridge, and not very sustainable of Allo, I must say. I’ll try installing an older Bullseye first.

Thanks anyway for your efforts.

Grüße aus Berlin

11

So generally the Allo GUI works on Bullseye. I can login. Can you check MariaDB logs in your case?

journalctl -u mariadb
12

not even able to start mariadb

root@DietPi:~# journalctl -u mariadb
– Journal begins at Thu 2025-11-06 22:17:01 UTC, ends at Fri 2025-11-07 21:02:04 UTC. –
Nov 07 20:57:51 DietPi systemd[1]: Starting MariaDB 10.5.29 database server…
Nov 07 20:57:51 DietPi systemd[592]: mariadb.service: Failed to apply ambient capabilities (before UID change): Operation not supported
Nov 07 20:57:51 DietPi systemd[592]: mariadb.service: Failed at step CAPABILITIES spawning /usr/sbin/mariadbd: Operation not supported
Nov 07 20:57:51 DietPi systemd[1]: mariadb.service: Main process exited, code=exited, status=218/CAPABILITIES
Nov 07 20:57:52 DietPi systemd[1]: mariadb.service: Failed with result ‘exit-code’.
Nov 07 20:57:52 DietPi systemd[1]: Failed to start MariaDB 10.5.29 database server.