-
Positions
-
Part time technical support
Position: Technical supportNumber of places: 12Applicants: 16 -
Single board computer maintainer
Position: Board maintainerNumber of places: 64Applicants: 76 -
Code reviewer
Position: Framework maintainerNumber of places: UnlimitedApplicants: 11 -
Test Automation Engineer
Position: Software integration test engineerNumber of places: 16Applicants: 10 -
Build framework maintainer
Position: Framework maintainerNumber of places: 16Applicants: 6
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Activity Stream
-
116
Armbian with preinstalled Home Assistant supervised
Sitrep / confirmed fix for “unhealthy: privileged” on Armbian Home Assistant Supervised After installing Home Assistant Supervised via Armbian on an Orange Pi 4 LTS, Supervisor was blocking add-on installation with: ‘AppManager.install’ blocked from execution, system is not healthy - privileged ha resolution info showed: unhealthy: privileged unsupported: os However Docker itself showed the Supervisor container was already privileged: docker inspect hassio_supervisor –format ‘{{.HostConfig.Privileged}}’ Output: true So the problem was not Docker missing –privileged. The Supervisor log also showed: Not privileged to run udev monitor! I checked the Supervisor AppArmor profile: sudo grep -n ‘deny network raw’ /var/lib/homeassistant/apparmor/hassio-supervisor It returned: 8: deny network raw, 70: deny network raw, Removing those deny network raw, lines from the AppArmor profile, reloading the profile, and restarting Supervisor fixed it. Commands used: sudo cp -a /var/lib/homeassistant/apparmor/hassio-supervisor /root/hassio-supervisor.apparmor.bak.$(date +%Y%m%d-%H%M%S) sudo sed -i ‘/^[[:space:]]deny network raw,[[:space:]]$/d’ /var/lib/homeassistant/apparmor/hassio-supervisor sudo apparmor_parser -r /var/lib/homeassistant/apparmor/hassio-supervisor sudo docker restart hassio_supervisor After restart: ha resolution info ha supervisor info Now shows: unhealthy: [] healthy: true unsupported: os supported: false I also tested the failing udev/netlink path directly: sudo docker exec hassio_supervisor python3 -c ‘import pyudev; pyudev.Monitor.from_netlink(pyudev.Context())’ It returned silently with no error. Conclusion: on this install, the “privileged” unhealthy state was caused by AppArmor blocking raw netlink access via deny network raw, in the hassio-supervisor profile. Docker was already privileged. Removing that AppArmor deny rule fixed Supervisor health and cleared the add-on install blocker. The remaining unsupported: os warning is expected for Armbian/Supervised and is separate from the privileged health failure. -
116
Armbian with preinstalled Home Assistant supervised
I've got error unhealthy system - not privileged, asked claude opus to fix it. now everything works. Aked to make script to repeat fixes, here it is: https://github.com/limorte/armbian_trixie_v26.2.1_6.12.71_orangepi3lts-fix_ha_unprivileged_error/blob/main/fix-hassio-privileged.sh can't confirm it working -
50
RK3566 and Armbian
I extracted DTB/DTS from the Android FW (files attached). For whatever reason they are signed in the image as rk3568. No ideas why. 02_dtbdump_rockchip,rk3568-evb.dtb 02_dtbdump_rockchip,rk3568-evb.dtb.dts Attention: They are for Android! Linux might not boot with them! -
46
Rupa X88 Pro 13 - RK3528 board with images
I have compiled debian trixie image from the repository of @johlnx for Vontar DQ08 4G+64G and flashed it to eMMC, also adjusting the DTB for wifi GPIOs. Wifi works with the brcm4335 firmware (at least in the 2.4GHz band), usb3.0 works too. Bluetooth does not work and there are still many nasty error messages in the 'dmesg' output. -
1
Rockchip: bare-metal Bootloader.bin: Open-sourced
Proprietary DDR and maskrom images from Rockchip Bare metall should provide DDR init replacement code, the only missing part in u-boot.
-
-
Member Statistics
