All Activity

Hey there! I’ve been running Home Assistant Supervised on Armbian for a while, but lately I keep seeing a repeat issue after system upgrades (Docker or kernel updates). After upgrading, some HA containers stop unexpectedly, for example: odroid-c2-homeassistant:2025.12.2 exits with code 137 aarch64-addon-configurator:5.8.0 exits with code 143 My current setup runs on Helios64/RK3399 · kernel 6.12.58-current-rockchip64 · Docker CE 29.1.3 (f52814d). After digging a bit, I noticed this line in dmesg right after the failures -> apparmor="DENIED" operation="signal" profile="hassio-supervisor" signal=kill I also found the small watchdog script (supervisor_fix.sh) that restarts the Supervisor when it reports unhealthy, but the upgrade breakage seems to slip through. I’m just thinking out loud here, but maybe something like a post-upgrade AppArmor refresh, or some other small adjustment, could help ? Not sure what makes the most sense, so any input would be really appreciated. Thanks for your time and for all the work you put into Armbian!

I've tested niri, hyprland, sway and i3, all of them should work if properly configured.

Hi there, I also tried to see what happens when I set the DIP to SATA0, but to my surprise, the serial console does not give any indication of a boot attempt from SATA: BootROM - 1.73 Booting from SPI flash BootROM: Bad header at offset D4000000 BootROM: Bad header at offset D4200000 BootROM: Bad header at offset D4400000 BootROM: Bad header at offset D4600000 BootROM: Bad header at offset D4800000 BootROM: Bad header at offset D4A00000 BootROM: Bad header at offset D4C00000 BootROM: Bad header at offset D4E00000 Trying Uart And yes, DIP was set to SATA0. To note: there was a blinking red LED prior to the output on the serial console. When I re-set the DIP to SPI, it boots up without issue: Booting from SPI flash U-Boot SPL 2025.10_armbian-2025.10-Se50b-Pee16-H9530-V9a59-Bbf55-R448a (Nov 23 2025 - 08:27:54 +0000) High speed PHY - Version: 2.0 Detected Device ID 6828 board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 6 | SATA0 | | 1 | 5 | USB3 HOST0 | | 2 | 6 | SATA1 | | 3 | 6 | SATA3 | | 4 | 6 | SATA2 | | 5 | 5 | USB3 HOST1 | -------------------------------- High speed PHY - Ended Successfully mv_ddr: 14.0.0 DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR Training Sequence - Start scrubbing DDR3 Training Sequence - End scrubbing mv_ddr: completed successfully Trying to boot from SPI U-Boot 2025.10_armbian-2025.10-Se50b-Pee16-H9530-V9a59-Bbf55-R448a (Nov 23 2025 - 08:27:54 +0000) SoC: MV88F6828-A0 at 1600 MHz DRAM: 2 GiB (800 MHz, 32-bit, ECC enabled) Core: 32 devices, 21 uclasses, devicetree: separate MMC: mv_sdh: 0 Loading Environment from SPIFlash... SF: Detected w25q32 with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Helios4 Board: Helios4 ... It almost appears that the DIP is not read out properly? What does your console say when you set the DIP to SATA0? Groetjes,

Thank you so much! Read it right away!

You can follow this guide to getting started https://gist.github.com/JeodC/aa89f7b387d9dd7976d39bf585e471fd

On an ARM computer: cat Armbian_25.11.1_Odroidn2_noble_current_6.12.58_xfce_desktop.img.xz.sha 1f3816553377dd63a12e46a476f7ff20b8c5118f63f879f8d3d7d27073c97b35 Armbian_25.11.1_Odroidn2_noble_current_6.12.58_xfce_desktop.img.xz unxz Armbian_25.11.1_Odroidn2_noble_current_6.12.58_xfce_desktop.img.xz losetup --show -fP Armbian_25.11.1_Odroidn2_noble_current_6.12.58_xfce_desktop.img mount /dev/loop0p2 2 passwd -d root --root $(pwd)/2/ systemd-nspawn -bD 2 Only as root login. Browsers are installed: Creating a new user account. Press <Ctrl-C> to abort Desktop environment will not be enabled if you abort the new user creation Please provide a username (eg. your first name): ^C Disabling user account creation procedure root@odroidn2:~# apt list --installed | grep -i -e firefox -e chromium WARNING: apt does not have a stable CLI interface. Use with caution in scripts. chromium-browser/noble,now 2:1snap1-0ubuntu2 arm64 [installed] firefox/noble,now 1:1snap1-0ubuntu5 arm64 [installed,upgradable to: 9:133.0+build2-0ubuntu0.24.04.1~mt1armbian1] Running as a container without DE is very minimal, but packages are there and also networking is up. Things might go wrong when starting DE for the first time, the the occasions I had that in the past decade are rare an due to bad storage or so or something failing with graphics HW/stack. You should maybe specifically look at what is managing network and what is managing DNS. Math permutation leads to 4 possibilities already if I look at what is installed. That is excluding all sorts of options you may have with your router or LAN.

How do you use proton/wine. I download the archieve file and after extraction, there are bin & lib files, how can I use them ? set some environment variables？

I am using X11 (XFCE), make sure you installed the driver.

The one time I used my iPad autocorrect comes to bite me

Only if you hand over the Arab money: https://song.link/s/6X0U1NIujkYExpcho01OXG

@Werner we should include the „new“ Arabian blog here

Looks like the tar file is broken. Try unpacking it with one other program and see if you can getting the .IMG file extracted OK. Also downloading it more times and see if its being OK or the server is having one corupt file.

For this device, ttyS2 is used for BT, but the problem was that the system was trying to use it for logging. After modifying that part in boot.cmd and rebooting, the firmware came up.

Are you using X11 or wayland? I am not able to run wayland while under X11 it is very slow

After installing the firmware shown in the link and requesting modifications by decompiling your dtb, there's been some progress, but it's still not working yet. However, I'm hopeful that with a little more effort, it should work.

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + FEX-Emu 2510 + hangover-10.18 (https://github.com/AndreRH/hangover/releases/tag/hangover-10.18) + Zink 30~60fps@720p Crysis x64 (dx10)

Thank you for sharing these!

well, so it does indeed sound like you DO have network issues on the Odroid N2+. Something related to the network is not working right in noble for you.

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + DXVK-stripped v1.7.1 ~60fps@1080p Ori and the Blind Forest: Definitive Edition

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + DXVK-stripped v2.6.2 >=60fps@1080p Shovel Knight Dig

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + DXVK-stripped v2.6.2 >=60fps@1080p Blasphemous 2

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + DXVK-stripped v2.6.2 >=60fps@1080p Blasphemous

Hello everyone, i`m trying to flash the multitool into the sd card, but all images that i tried from the server, are showing this errors on the balena etcher

Works just fine on last version. Thanks a lot !!! <pre> $ zcat /proc/config.gz | grep DP| grep ROCK CONFIG_ROCKCHIP_ANALOGIX_DP=y CONFIG_ROCKCHIP_CDN_DP=y CONFIG_ROCKCHIP_DW_DP=y CONFIG_PHY_ROCKCHIP_DP=y CONFIG_PHY_ROCKCHIP_DPHY_RX0=m CONFIG_PHY_ROCKCHIP_INNO_CSIDPHY=m CONFIG_PHY_ROCKCHIP_INNO_DSIDPHY=m CONFIG_PHY_ROCKCHIP_SAMSUNG_HDPTX=m CONFIG_PHY_ROCKCHIP_USBDP=m CONFIG_PHY_ROCKCHIP_DP=y </pre>

SCSI works fine with linux Mainline at least (6.16, 6.17 & 6.18) since few month now.