@c0rnelius then the GPU probably works, since without GPU e.g the Bianbu first time wizard (language, kbd, timezone, user) needs 20 minutes while uptime reports load=10. I'm damn sure you have noticed an extraslow GUI

Yes usermod -aG docker yourusername , then reboot, was what I needed to let the armbian build script continue Warning: if you forget the "a" in -aG, you will get locked out being admin in your own computer Second roadblock: I needed to install qemu as per: https://forum.armbian.com/topic/52127-running-armbian-build-on-x86-64/#findComment-219019 Thank you Werner!

I’m really happy to share that I finally managed to port the SV6256P (SSV6X5X) SDIO Wi-Fi driver from the legacy Linux 4.4 kernel to modern kernels. This repository contains my working port for Linux kernel 6.12 and newer, with updated mac80211/cfg80211 integration so the driver can build and run on recent Armbian systems. The chipset is commonly used in many low-cost TV boxes and embedded devices, but the original driver only supported legacy kernels (4.4). Now it’s functional again on modern systems, at least on my tested hardware (Allwinner H616 / X96 Q via SDIO). Repository link: https://github.com/cdhigh/armbian_sv6256p I’m quite excited to finally see this old Wi-Fi chip working on a 6.x kernel 🙂 [ 4.774151] ssv6x5x: importing configuration from /lib/firmware/ssv6x5x-wifi.cfg [ 4.778281] tu_ssv6xxx_sdio_init, probe @(____ptrval____) [ 4.779483] TU_SSV6XXX_SDIO mmc3:0001:1: Probing SDIO bus [ 4.779513] ssv6xxx_set_sdio_clk: set sdio clk 25000000Hz [ 4.799668] TU_SSV6XXX_SDIO mmc3:0001:1: vendor = 0x3030 device = 0x3030 [ 4.825421] TU_SSV6XXX_SDIO mmc3:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 4.849181] TU_SSV6XXX_SDIO mmc3:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 4.849530] TU_SSV6XXX_SDIO mmc3:0001:1: CHIP ID: SSV6006C0 [ 4.850373] ssv6x5x ops chk: tx=1 start=1 stop=1 config=1 add_if=1 rm_if=1 conf_filter=1 wake_txq=1 [ 4.850402] ssv6x5x chanctx chk: any=1 all=0 emulate=1 add=1 rm=1 chg=1 assign=0 unassign=0 [ 4.850409] ssv6x5x chanctx ops set but not complete [ 4.850424] Attach SSV6006 family HAL function [ 4.858285] MAC address from e-fuse [ 4.858311] EFUSE configuration [ 4.858315] Read efuse chip identity[79000000] ip link show: 6: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff

This morning, the difference is not as big as yesterday, but it is still there. Why isn't it synchronized via NTP? sudo date -s “2026-02-10 04:13:00” Tue, Feb 10, 04:13:00 CET 2026 root@cubietruck ~ > date Tue, Feb 10, 06:11:41 CET 2026

I installed Filebrowser via armbian-config but it didn't work. The container was restarting and there was: Using database: /database/filebrowser.db Error: open /database/filebrowser.db: permission denied in the .log file. The developers of Filebrowser explained they introduced some breaking changes and documented the changes that have to be made to avoid that error: - User: File Browser no longer runs as root, but as user with PID 1000 and GID 1000. You can still change this by using Docker's --user flag [https://www.docker.com/blog/understanding-the-docker-user-instruction/]. - Volumes: the volumes with the database and configuration are now aligned with the s6-overlay images. Instead of mounting the files themselves, which leads to frequent issues, you now mount the surrounding directory. Unfortunately, these are breaking changes and will require updates on your side. Assuming you have a database.db, a .filebrowser.json and the data in /data, do the following: 1. Change the path of database in .filebrowser.json to /database/filebrowser.db 2. Rename database.db to filebrowser.db 3. Rename .filebrowser.json to settings.json 4. Put them in the same directory locally, let's say /app/filebrowser/ 5. Change the permissions of both directories: sudo chown -R 1000:1000 /app/filebrowser /data 6. Mount with the flags -v /app/filebrowser:/database -v /app/filebrowser:/config - you can also choose to put them in separate directories, but it is not needed. If you are still getting errors, please make sure that the paths/volumes you are mounting have read-write permission for user 1000:1000. For more up to date information regarding how you should use the Docker image, check filebrowser.org/installation.html#docker [https://filebrowser.org/installation.html#docker] But how exactly to apply those changes after the container already has been created and started via armbian-config?