All Activity
- Past hour
-
BTT Pi - ethernet not working after upgrade from 6.12.68 to 6.18.33
Igor replied to ilmarietto's topic in BIGTREETECH CB1
It should be / it was reported fixed a week ago, but you need to make image on your own or use nightly automated builds. - Today
-
Maybe not the right place but the same happened on my OP5Ultra. The latest kernel stopped the internal WiFi module. Falling back to again 6.1.115 did the trick. So both Radxa 5B plus and OP5 ultra suffer the same problem when installing the latest Armbian Ubuntu. I assume other boards have similar problems... Ernst-Jan
-
This week's updates center on new hardware enablement, a broad U-Boot v2026.07 modernization, and build system hardening for toolchain and infrastructure changes. Board support expanded across multiple SoC families, including the X88 PRO RK3566 TV box, Avnet MaaXBoard 8ULP (i.MX8ULP), EASY EAI Nano (RV1126), and the AYN Odin3. The Youyeetoo R1 v3 was promoted to standard support with named audio outputs, while the Radxa Dragon Q8B gained an edge kernel (7.1) target. Rockchip work included RK3588 CAN support for kernels 6.18/7.1/7.2, HDMI-RX fixes on the OrangePi 5 Ultra, and Mixtile Blade3 refinements on the 7.2 bleeding edge. A coordinated U-Boot bump to v2026.07 landed across Helios4, Odroid HC4/M1, Turing RK1, Radxa E52C, Qidi X6, Mekotronics R58X-Pro, and the Espressobin/Macchiatobin (paired with TF-A 2.14.0). This surfaced toolchain issues on Trixie, addressed through SWIG 4.3 pylibfdt compatibility, demotion of gcc 14 int-conversion and implicit-declaration errors to warnings, and related pin cleanups. Infrastructure work strengthened build reliability and CI. The rootfs stage gained DNS fallback and apt retry hardening for chroot operations, armbian-firstlogin received power-loss recovery with atomic writes, and armbian-install now reports bootloader write failures explicitly. Docker framework updates enable native riscv64 image generation on trixie and noble runners, while new extensions introduce sysrq serial trigger, kernel-debug tiers, ram-boot via rkusbboot, and generic SATA park-on-shutdown enabled by default on the Odroid HC4. #Armbian #EmbeddedLinux #UBoot #Rockchip #RISCV ChangesAdd support for X88 PRO RK3566 TV box. by @Ovaday in armbian/linux-rockchip#500Add AI-driven README updater (central, cross-repo). by @igorpecovnik in armbian/armbian.github.io#359Add Avnet MaaXBoard 8ULP (i.MX8ULP) support. by @govindsi in armbian/build#9991Add AYN Odin3 firmware. by @kasimling in armbian/firmware#136Add ayn-odin3 board image. by @kasimling in armbian/armbian.github.io#358Add board: EASY EAI Nano RV1126. by @hqnicolas in armbian/build#10154Add minimal SWT6621S firmware support for KICKPI K3B. by @retro98boy in armbian/firmware#134armbian-firstlogin: power-loss recovery and atomic writes. by @mingzhangqun in armbian/build#9954armbian-install: report bootloader write failures instead of "Done.". by @iav in armbian/build#10204artifact-rootfs: surface git-log failure when computing configng hash. by @igorpecovnik in armbian/build#9849board: aml-c400-plus: Fix eMMC boot format and partition layout. by @jomadeto in armbian/build#9911boards/easy-eai-nano: enable usb and brcm wifi. by @hqnicolas in armbian/build#10177brcm: add brcmfmac firmware aliases for easy-eai nano (rv1126). by @igorpecovnik in armbian/firmware#133bsp: generic SATA park-on-shutdown (HDD_PARK_ON_SHUTDOWN), enable on Odroid HC4. by @igorpecovnik in armbian/build#10191bsp: use kernel version argument in ABL postinst scripts (fixes #10108). by @rorystandley in armbian/build#10109can: rockchip: add RK3588 CAN support (for kernel v6.18 / v7.1 / v7.2). by @lch08 in armbian/build#10184ci(board-assets): don't check out fork head under pull_request_target. by @igorpecovnik in armbian/build#10194cix-acpi: bump edge to 7.1.y. by @EvilOlaf in armbian/build#10167Cleanup patches. by @EvilOlaf in armbian/build#10174csc board: NORCO EMB-3531: Do not reset LTE moden. by @retro98boy in armbian/build#10222docker/framework: build riscv64 images on native runners (trixie, noble). by @igorpecovnik in armbian/docker-armbian-build#34docker/framework: generate riscv64 images (trixie, noble, resolute). by @igorpecovnik in armbian/docker-armbian-build#33docker/riscv64: fix cross-compiler availability for generate-dockerfile. by @igorpecovnik in armbian/build#9589docker: allow overriding host_arch for foreign-arch Dockerfile generation. by @igorpecovnik in armbian/build#10211docs: refresh README (AI-assisted). by @igorpecovnik in armbian/ci#29Enable memory compaction and RK630 PHY on Rockchip vendor kernels . by @lukaszsobala in armbian/build#10175Enable pwm gpio. by @frank-f in armbian/build#10238extensions/nvidia: per-distro version detection + runtime auto-disable on no-GPU hosts. by @igorpecovnik in armbian/build#9845extensions/radxa-aic8800: use local dir as download cache. by @rpardini in armbian/build#10156extensions/rkusbboot: easy ramboot mainline u-boot on Rockchip devices. by @rpardini in armbian/build#10158feat(extensions): sysrq-serial-trigger + kernel-debug-tiers (on-device kernel debugging via serial console). by @iav in armbian/build#9776feat(flash): keep the success screen when verification is cancelled. by @SuperKali in armbian/imager#166Fix build for Linux 7.1. by @EvilOlaf in armbian/bcmdhd-dkms#7fix hdmi rx on orangepi5 ultra by adding hpd-gpios. by @pdapandapda in armbian/build#10172fix Radxa U-Boot ITB dependency. by @yisding in armbian/build#10196Fix sata2 target-supply for Orange Pi 3B and Station M2. by @dust-7 in armbian/build#10137fix the hdmirx HPD patch against kernel6.18 & kernel 7.1. by @pdapandapda in armbian/build#10180fix(offline): honor OFFLINE_WORK in git-ref2info and memoize TTL. by @iav in armbian/build#9797gha: disable build cronjobs (moved to armbian/ci). by @igorpecovnik in armbian/os#482git: match safe.directory literally, not as a regex. by @igorpecovnik in armbian/build#10223git: silence spurious SUBSHELL error annotation from safe.directory check. by @igorpecovnik in armbian/build#10225helios4: bump u-boot to v2026.07. by @iav in armbian/build#10183helios4: drop stale u-boot patch dir v2025.10/board_helios4. by @iav in armbian/build#10189input: remotectl: rockchip-pwm: prefer dedicated channel-3 IRQ. by @rpardini in armbian/linux-rockchip#503k3: sk-am62-lp: shrink R5 SPL to fit SRAM + silence k3 cp noise. by @igorpecovnik in armbian/build#10230luckfox-lyra-ultra-w: Add spidev overlay with 2 CS. by @vidplace7 in armbian/linux-rockchip#505mainline: bump bleedingedge to v7.2-rc3. by @EvilOlaf in armbian/build#10181mekotronics-r58x-pro: u-boot: bump to v2026.07. by @rpardini in armbian/build#10232mixtile-blade3: edge: u-boot: fancy it up (lwIP, mbedTLS, efi, btrfs, etc). by @rpardini in armbian/build#10234mvebu64: modernize EspressoBin/MacchiatoBin firmware (u-boot 2026.07 + TF-A 2.14.0 + A3720 fixes). by @igorpecovnik in armbian/build#10213odroidhc4: u-boot: bump to v2026.07, drop upstreamed patch. by @rpardini in armbian/build#10233odroidm1: bump u-boot to v2026.07. by @iav in armbian/build#10201Qidi X6: update to u-boot 2026.07. by @Shadowrom2020 in armbian/build#10228radxa-dragon-q8b: add edge kernel (7.1) target. by @SuperKali in armbian/build#10215radxa-e52c: bump uboot to v2026.07. by @okrc in armbian/build#10135Rk3588 es8388 codec silence log. by @CT1IQI in armbian/build#10198rockchip64-6.18: rework rk3588-0010-fix-clk-divisions to avoid patching include/linux/math.h. by @rpardini in armbian/build#10207rockchip64-7.2: bleedingedge: enable REALTEK_PHY_HWMON. by @rpardini in armbian/build#10206rockchip64-7.2: rk3588-mixtile-blade3, many fixes and additions. by @rpardini in armbian/build#10203rootfs-image: move pre_install_distribution_specific inside install_distribution_specific(). by @rpardini in armbian/build#10157rootfs: DNS fallback for build-time chroot resolv.conf. by @igorpecovnik in armbian/build#10205rootfs: harden chroot apt against transient fetch failures (retries + fail-fast update). by @igorpecovnik in armbian/build#10202rootfs: pin tar for resolute kernel deb install (all families). by @igorpecovnik in armbian/build#10187rootfs: revert resolute tar pin (#10187) — fixed upstream. by @igorpecovnik in armbian/build#10209runner-clean: drop stale amlogic FIP source caches. by @igorpecovnik in armbian/actions#28runner-clean: ensure tree is installed on the host. by @igorpecovnik in armbian/actions#27runner-clean: register qemu binfmt handlers on the host. by @igorpecovnik in armbian/actions#26sc8280xp: fix wrong LINUXCONFIG name for the sc8280xp branch. by @igorpecovnik in armbian/build#10227SpacemiT: Defconfig: Enable CONFIG_PWM_PXA. by @fkpwolf in armbian/build#10182sun55iw3-syterkit: skip TF-A build (SyterKit is self-contained). by @igorpecovnik in armbian/build#10214targets: drop resolute from riscv64 userspace builds (RVA23 vs RV64GC). by @igorpecovnik in armbian/ci#27turing-rk1: bump u-boot v2024.04 → v2026.07 (fix SWIG 4.3 build break on trixie). by @igorpecovnik in armbian/build#10216u-boot: bump 2026.07-rc4/rc5 pins to final v2026.07. by @igorpecovnik in armbian/build#10186u-boot: don't error on implicit declarations (gcc ≥ 14 / trixie). by @igorpecovnik in armbian/build#10221u-boot: fix old pylibfdt build against SWIG ≥ 4.3 (trixie). by @igorpecovnik in armbian/build#10217u-boot: sync btrfs zstd short-extent fix into shadowed board/pool copies. by @iav in armbian/build#10208uboot: demote int-conversion & incompatible-pointer-types to warnings (gcc 14). by @igorpecovnik in armbian/build#10224Up rtw8822b to v30.20.0. by @farwayer in armbian/firmware#135update Helios4 BSP postinst. by @leggewie in armbian/build#9065workflows: add Delete Old Releases (copied from os). by @igorpecovnik in armbian/ci#26workflows: enable build cronjobs (taking over from armbian/os). by @igorpecovnik in armbian/ci#25youyeetoo-r1-v3: bump mainline u-boot to v2026.04. by @SuperKali in armbian/build#10219youyeetoo-r1-v3: promote to standard support and name audio outputs. by @SuperKali in armbian/build#10220View the full article
-
This week's updates center on new hardware enablement, a broad U-Boot v2026.07 modernization, and build system hardening for toolchain and infrastructure changes. Board support expanded across multiple SoC families, including the X88 PRO RK3566 TV box, Avnet MaaXBoard 8ULP (i.MX8ULP), EASY EAI Nano (RV1126), and the AYN Odin3. The Youyeetoo R1 v3 was promoted to standard support with named audio outputs, while the Radxa Dragon Q8B gained an edge kernel (7.1) target. Rockchip work included RK3588 CAN support for kernels 6.18/7.1/7.2, HDMI-RX fixes on the OrangePi 5 Ultra, and Mixtile Blade3 refinements on the 7.2 bleeding edge. A coordinated U-Boot bump to v2026.07 landed across Helios4, Odroid HC4/M1, Turing RK1, Radxa E52C, Qidi X6, Mekotronics R58X-Pro, and the Espressobin/Macchiatobin (paired with TF-A 2.14.0). This surfaced toolchain issues on Trixie, addressed through SWIG 4.3 pylibfdt compatibility, demotion of gcc 14 int-conversion and implicit-declaration errors to warnings, and related pin cleanups. Infrastructure work strengthened build reliability and CI. The rootfs stage gained DNS fallback and apt retry hardening for chroot operations, armbian-firstlogin received power-loss recovery with atomic writes, and armbian-install now reports bootloader write failures explicitly. Docker framework updates enable native riscv64 image generation on trixie and noble runners, while new extensions introduce sysrq serial trigger, kernel-debug tiers, ram-boot via rkusbboot, and generic SATA park-on-shutdown enabled by default on the Odroid HC4. #Armbian #EmbeddedLinux #UBoot #Rockchip #RISCV ChangesAdd support for X88 PRO RK3566 TV box. by @Ovaday in armbian/linux-rockchip#500Add AI-driven README updater (central, cross-repo). by @igorpecovnik in armbian/armbian.github.io#359Add Avnet MaaXBoard 8ULP (i.MX8ULP) support. by @govindsi in armbian/build#9991Add AYN Odin3 firmware. by @kasimling in armbian/firmware#136Add ayn-odin3 board image. by @kasimling in armbian/armbian.github.io#358Add board: EASY EAI Nano RV1126. by @hqnicolas in armbian/build#10154Add minimal SWT6621S firmware support for KICKPI K3B. by @retro98boy in armbian/firmware#134armbian-firstlogin: power-loss recovery and atomic writes. by @mingzhangqun in armbian/build#9954armbian-install: report bootloader write failures instead of "Done.". by @iav in armbian/build#10204artifact-rootfs: surface git-log failure when computing configng hash. by @igorpecovnik in armbian/build#9849board: aml-c400-plus: Fix eMMC boot format and partition layout. by @jomadeto in armbian/build#9911boards/easy-eai-nano: enable usb and brcm wifi. by @hqnicolas in armbian/build#10177brcm: add brcmfmac firmware aliases for easy-eai nano (rv1126). by @igorpecovnik in armbian/firmware#133bsp: generic SATA park-on-shutdown (HDD_PARK_ON_SHUTDOWN), enable on Odroid HC4. by @igorpecovnik in armbian/build#10191bsp: use kernel version argument in ABL postinst scripts (fixes #10108). by @rorystandley in armbian/build#10109can: rockchip: add RK3588 CAN support (for kernel v6.18 / v7.1 / v7.2). by @lch08 in armbian/build#10184ci(board-assets): don't check out fork head under pull_request_target. by @igorpecovnik in armbian/build#10194cix-acpi: bump edge to 7.1.y. by @EvilOlaf in armbian/build#10167Cleanup patches. by @EvilOlaf in armbian/build#10174csc board: NORCO EMB-3531: Do not reset LTE moden. by @retro98boy in armbian/build#10222docker/framework: build riscv64 images on native runners (trixie, noble). by @igorpecovnik in armbian/docker-armbian-build#34docker/framework: generate riscv64 images (trixie, noble, resolute). by @igorpecovnik in armbian/docker-armbian-build#33docker/riscv64: fix cross-compiler availability for generate-dockerfile. by @igorpecovnik in armbian/build#9589docker: allow overriding host_arch for foreign-arch Dockerfile generation. by @igorpecovnik in armbian/build#10211docs: refresh README (AI-assisted). by @igorpecovnik in armbian/ci#29Enable memory compaction and RK630 PHY on Rockchip vendor kernels . by @lukaszsobala in armbian/build#10175Enable pwm gpio. by @frank-f in armbian/build#10238extensions/nvidia: per-distro version detection + runtime auto-disable on no-GPU hosts. by @igorpecovnik in armbian/build#9845extensions/radxa-aic8800: use local dir as download cache. by @rpardini in armbian/build#10156extensions/rkusbboot: easy ramboot mainline u-boot on Rockchip devices. by @rpardini in armbian/build#10158feat(extensions): sysrq-serial-trigger + kernel-debug-tiers (on-device kernel debugging via serial console). by @iav in armbian/build#9776feat(flash): keep the success screen when verification is cancelled. by @SuperKali in armbian/imager#166Fix build for Linux 7.1. by @EvilOlaf in armbian/bcmdhd-dkms#7fix hdmi rx on orangepi5 ultra by adding hpd-gpios. by @pdapandapda in armbian/build#10172fix Radxa U-Boot ITB dependency. by @yisding in armbian/build#10196Fix sata2 target-supply for Orange Pi 3B and Station M2. by @dust-7 in armbian/build#10137fix the hdmirx HPD patch against kernel6.18 & kernel 7.1. by @pdapandapda in armbian/build#10180fix(offline): honor OFFLINE_WORK in git-ref2info and memoize TTL. by @iav in armbian/build#9797gha: disable build cronjobs (moved to armbian/ci). by @igorpecovnik in armbian/os#482git: match safe.directory literally, not as a regex. by @igorpecovnik in armbian/build#10223git: silence spurious SUBSHELL error annotation from safe.directory check. by @igorpecovnik in armbian/build#10225helios4: bump u-boot to v2026.07. by @iav in armbian/build#10183helios4: drop stale u-boot patch dir v2025.10/board_helios4. by @iav in armbian/build#10189input: remotectl: rockchip-pwm: prefer dedicated channel-3 IRQ. by @rpardini in armbian/linux-rockchip#503k3: sk-am62-lp: shrink R5 SPL to fit SRAM + silence k3 cp noise. by @igorpecovnik in armbian/build#10230luckfox-lyra-ultra-w: Add spidev overlay with 2 CS. by @vidplace7 in armbian/linux-rockchip#505mainline: bump bleedingedge to v7.2-rc3. by @EvilOlaf in armbian/build#10181mekotronics-r58x-pro: u-boot: bump to v2026.07. by @rpardini in armbian/build#10232mixtile-blade3: edge: u-boot: fancy it up (lwIP, mbedTLS, efi, btrfs, etc). by @rpardini in armbian/build#10234mvebu64: modernize EspressoBin/MacchiatoBin firmware (u-boot 2026.07 + TF-A 2.14.0 + A3720 fixes). by @igorpecovnik in armbian/build#10213odroidhc4: u-boot: bump to v2026.07, drop upstreamed patch. by @rpardini in armbian/build#10233odroidm1: bump u-boot to v2026.07. by @iav in armbian/build#10201Qidi X6: update to u-boot 2026.07. by @Shadowrom2020 in armbian/build#10228radxa-dragon-q8b: add edge kernel (7.1) target. by @SuperKali in armbian/build#10215radxa-e52c: bump uboot to v2026.07. by @okrc in armbian/build#10135Rk3588 es8388 codec silence log. by @CT1IQI in armbian/build#10198rockchip64-6.18: rework rk3588-0010-fix-clk-divisions to avoid patching include/linux/math.h. by @rpardini in armbian/build#10207rockchip64-7.2: bleedingedge: enable REALTEK_PHY_HWMON. by @rpardini in armbian/build#10206rockchip64-7.2: rk3588-mixtile-blade3, many fixes and additions. by @rpardini in armbian/build#10203rootfs-image: move pre_install_distribution_specific inside install_distribution_specific(). by @rpardini in armbian/build#10157rootfs: DNS fallback for build-time chroot resolv.conf. by @igorpecovnik in armbian/build#10205rootfs: harden chroot apt against transient fetch failures (retries + fail-fast update). by @igorpecovnik in armbian/build#10202rootfs: pin tar for resolute kernel deb install (all families). by @igorpecovnik in armbian/build#10187rootfs: revert resolute tar pin (#10187) — fixed upstream. by @igorpecovnik in armbian/build#10209runner-clean: drop stale amlogic FIP source caches. by @igorpecovnik in armbian/actions#28runner-clean: ensure tree is installed on the host. by @igorpecovnik in armbian/actions#27runner-clean: register qemu binfmt handlers on the host. by @igorpecovnik in armbian/actions#26sc8280xp: fix wrong LINUXCONFIG name for the sc8280xp branch. by @igorpecovnik in armbian/build#10227SpacemiT: Defconfig: Enable CONFIG_PWM_PXA. by @fkpwolf in armbian/build#10182sun55iw3-syterkit: skip TF-A build (SyterKit is self-contained). by @igorpecovnik in armbian/build#10214targets: drop resolute from riscv64 userspace builds (RVA23 vs RV64GC). by @igorpecovnik in armbian/ci#27turing-rk1: bump u-boot v2024.04 → v2026.07 (fix SWIG 4.3 build break on trixie). by @igorpecovnik in armbian/build#10216u-boot: bump 2026.07-rc4/rc5 pins to final v2026.07. by @igorpecovnik in armbian/build#10186u-boot: don't error on implicit declarations (gcc ≥ 14 / trixie). by @igorpecovnik in armbian/build#10221u-boot: fix old pylibfdt build against SWIG ≥ 4.3 (trixie). by @igorpecovnik in armbian/build#10217u-boot: sync btrfs zstd short-extent fix into shadowed board/pool copies. by @iav in armbian/build#10208uboot: demote int-conversion & incompatible-pointer-types to warnings (gcc 14). by @igorpecovnik in armbian/build#10224Up rtw8822b to v30.20.0. by @farwayer in armbian/firmware#135update Helios4 BSP postinst. by @leggewie in armbian/build#9065workflows: add Delete Old Releases (copied from os). by @igorpecovnik in armbian/ci#26workflows: enable build cronjobs (taking over from armbian/os). by @igorpecovnik in armbian/ci#25youyeetoo-r1-v3: bump mainline u-boot to v2026.04. by @SuperKali in armbian/build#10219youyeetoo-r1-v3: promote to standard support and name audio outputs. by @SuperKali in armbian/build#10220View the full article
-
@eselarm: First off, thanks for your extensive answer and the effort you've put to read and answer to my question. I'm by far not such an expert like you yet, but to start with, I can tell you the following: I had two Le Potato SBC laying around doing nothing and I wanted to give them some work to do. I was already looking for a while to start with HA (I have currently an own written home automation system that works together with openHAB through MQTT). The Le Potato has (at least mine) 2GB of RAM on board, twice as much as all of my Raspberry Pi's I currently have or in use, or laying around doing nothing. So I think that should be sufficient to do what I want to do with HA. Le Potato is not a racing car, but I don't think this is necessary for me. Unless you have so many add-ons like you have. That's another story. I want to use Zigbee as a protocol for my sensors. I bought recently a whole bunch of them: presence detection, door and room sensors, temperature sensors. All of them from Aqara. I also bought a Sonoff Zigbee 3.0 USB Dongle P (later on, I read that I should have taken the E version but yeah, that's the "learning price" you pay if you step into an unknown world...) Next to that, I also bought presence detectors from another brand (HOBEIAN, model ZB-PL/ZB-p: this seems to be a Tuya clone), just to see how HA can cope with all those different brands. Finally, I also bought 4x 2PM GEN4 Shelly boxes to contol roller shutters later on. The nice thing about those is that they "understand" quite a few protocols, among others, Zigbee I also want to be able to "listen" to what the Zigbee components are sending to HA. Therefore, I want to use Zigbee2MQTT in HA instead of Zigbee Home Assistant itself. It's for Zigbee2MQTT that I really wanted a HA version with supervisor capabilities to be able to add Zigbee2MQTT through the Add-ons feature. Alas... that's not seem to work... So, my Le Potato should only be able to run HA in combination with MQTT and Zigbee2MQTT. The specs of Le Potato should be sufficient to cope with this I guess (I hope). And if the future demands me to add more features, well, then we'll see. But my first goal is to learn HA and its surroundings. And since I anyhow had those SBCs doing nothing.... So, since the "official" Armbian Home Assistant image didn't have the Add-ons feature, I took a brave and daring move: I went the HA docker way... Therefore, I took another SD card and flashed Armbian 26.2.1 Minimal to it. Just to have a very bare bone Linux distro (I have to admit that I do know something about Linux, I'm just not a HA expert yet...). After installing the distro on the SD card and doing the necessary "Armbian onboarding" stuff (create root password, create new user, and so on), I first installed Docker. Again: I have no experience yet with Docker, so again another big gamble. But I like challenges, so I don't mind. After installing Docker, I installed the HA docker image. I then opened the HA web UI and could also start creating a "first user" (which is apparently given administrator rights). But of course, again not the Add-ons feature in the Service section. But this time I could understand; this is normal since I didn't use the real, official HA repo. I could install ZHA, however, which I did. Just to see if my Sonoff dongle was detected and used by HA. After installing ZHA, I activated some of my devices and yes, they were detected! But that only proved my Zigbee dongle was working fine. Nothing more, nothing less. Still, very important! Then I installed Zigbee2MQTT "the Docker way". This was absolutely not a walk in the park, but in the end I got it up and running. My devices are getting detected, I know now how to change topics. I can receive MQTT topics on my MQTT broker running on another Raspberry Pi, I can filter the MQTT JSON objects so that I only receive what I would like to receive (by default, the JSON object exposes all entities of a device, but I'm not interested in all of them), I can convert the standard MQTT topic "prefix" used by Zigbee2MQTT on the fly and so on. Overall, I'm very satisfied with what I currently have and I will continue to follow that road. Maybe until Armbian has a fully supported HA image for Le Potato that contains the Add-ons section. Maybe I will switch to a more powerfull server too in the future. I read on the inet that a lot of people are switching from a RPi4 to a so-called Intel NUC server (whatever that is, no experience with it, no idea about its specs) for performance reasons and they're very satisfied. Maybe I'll do that too in the future, only God knows... We'll see, but still lots to learn about HA and its overall environment for the moment. Thanks again! Best, --Geert
-
hate to bump this thread, but anyone have any luck with hardware decoding in latest Armbian? Tried with 26.5.1 vendor kernel with both gnome and kde. None of the guides seem to work with hardware decoding. Tried the above posted fork as well, but seems 26.6.1 doesn't ship with g610-g24p0-wayland-gbm. Installing it from here just gave me a black screen at boot. Not sure what else to try, I had moonlight working with hardware decoding in 24.8.1 a couple years ago here.
-
Hardware video acceleration with recent armbian/mainline kernel (Kodi)
eselarm replied to XXXBold's topic in Orange Pi 5
A difference between FriendlyElec image and Armbian image is U-Boot ( bootloader/firmware ) variant I think. For my NanoPi-R6C, HDMI audio does not work if I boot from SD-card where an image with a U-Boot from 2026 is written in the boot area (between main GPT and 1st partition). If I wipe that U-Boot by zeroing that area, the OS will take EDK2 UEFI v1.1 that I have written to eMMC. Then there is HDMI sound, on Armbian and Opensuse Tumbleweed. I need to check if I run it in hybrid ACPI+DeviceTree mode or just DeviceTree mode. The setting is anyway 'mainline kernel' DT, which should be about 6.10 or later. If I select 'vendor kernel', it can only run Armbian 6.1.115, but I don't remember if KDE6 Wayland does work then. I only did that to check if I idle power consumption was still < 1.5 Watt, which was the case. Else it is 3 Watt and min clock is 1GHz instead of 480MHz and more differences. I remember I saw some U-Boot version scrolling by when I messed up partitions on eMMC (might just be corrupt 2nd backup GPT), I think the UEFI code did fall back to some build-in U-Boot. Now I did check certain things: # gunzip < rk3588-sd-debian-trixie-gnome-wayland-desktop-6.1-arm64-20260629.img.gz | dd count=32k status=none | grep -FUzi "U-Boot SPL 20" U-Boot SPL 2017.09-g50821b3c8bd-241113 #fa (Jan 02 2025 - 16:53:42) # cat nanopi-r6c_UEFI_Release_v1.1.img | dd count=32k status=none | grep -FUzi "U-Boot SPL 20" U-Boot SPL 2017.09-g5f53abfa1e-221223 #zzz (Dec 26 2022 - 09:10:09) So the EDK2 seems to contain some old base U-Boot and also the FriendlyElec image same U-Boot base, however, it can be different and certainly is incompatible with mainline recent year U-Boot and also likely the vendor tagged one from Armbian. FriendlyElec could do various HW initialization in a different way and on top of that or mixed with it, EDK2 again does things. It needs rebuild EDK2 from source or so in order to gain more know-how and check. I also see the kernel version string in the FriendlyElec image is '6.1.141' (Armbian is '6.1.115-vendor-rk35xx' ), what that means I don't know, kernel.org is at 6.1.177 (2026-07-04). I am using 7.1.3+deb14-arm64-16k #1 SMP PREEMPT Debian 7.1.3-1 (2026-07-04) from Debian Sid repo, userspace is Armbian Trixie. So no HW accel, at least not in KDE6 with FireFox. The added RKMPP libs are 1 thing, the DMA devices are another. Names like 'uncached' and 'dma32' are important hints on how and what is implemented, wrapping tactics etc. The whole issue with those FriendlyElec images is, at a Debian minor update for example, those libav* files get overwritten. In addition, kernel sources w.r.t RKMPP are banned from github. So those images from FriendlyElec are a 1-time shot, works as longs as you don't update. I spent a lot of time to build RPI kernels and their ffmpeg/libav variant. It changed several times, now I don't use it anymore in a generic way, mainly because the HW encoder is fairly limited and does also not work anymore with Jellyfin ffmpeg build (for transcoding on-the-fly). Same for OpenSuse, they are strict on MPEG licensing/royalties, so no MPEG2,H264,HEVC etc, you extra need other repo to make it work. To come back to OP topic title, LibreElec (so dedicated Kodi) worked fine HW accel for HEVC, H264, H265, AV1 and partly for VP9. Was about 9 months ago I ran that dedicated from separate SD-card, so LE's own U-Boot and kernel etc, all mainline based. But is only decoders, so playing video on a usually larger HDMI monitor. So the kernel can do it, it is just many different API's and protocols. FireFox focuses on VAAPI AFAIK, so known to work fine on Intel HW, but needs then tweaks to work with v4l2_m2m AFAIK. Maybe look at RPi's FireFox patches, although I think it is proprietary for their Broadcom tailored kernel, so won't work with mainline Linux nor Rockchips stuff on RK3588. -
Helios64 - Armbian Trixie with linux 6.18 (incl. opp-microvolt patch)
BipBip1981 replied to ebin-dev's topic in Rockchip
Hello, I make two away with both kernel version. With officiel 6.18.35 and a build by me 6.18.37 with armbian build framework. see here: For the moment, i freeze to version kernel 6.18.10 and DTB file patch and all is Okok. Have a good day. -
BTT Pi - ethernet not working after upgrade from 6.12.68 to 6.18.33
Werner replied to ilmarietto's topic in BIGTREETECH CB1
Should work on all devices -
Hi Igor, This worked! Falling back to 6.1.115 and a working internal WiFi... Ernst-Jan
-
Hardware video acceleration with recent armbian/mainline kernel (Kodi)
Igor replied to XXXBold's topic in Orange Pi 5
Totally undestand, just I probably know less then you about those things ... mpv is the king, I know that. But most people don't and they will keep asking why VLC, Totem or whatever player doesn't support accelerated video. Every SoC family has its own tricks to get this working ... -
Hardware video acceleration with recent armbian/mainline kernel (Kodi)
MMGen replied to XXXBold's topic in Orange Pi 5
@Igor, @robertoj: Update: Friendlyelec image uses its own libav* libraries, not the Debian ones: # ls -1 /usr/local/lib/aarch64-linux-gnu libavcodec.so libavcodec.so.61 libavcodec.so.61.19.101 libavfilter.so libavfilter.so.10 libavfilter.so.10.4.100 libavutil.so libavutil.so.59 libavutil.so.59.39.100 It also has the following packages, not in Armbian: # dpkg -l *mpp* ... ii librockchip-mpp-dev 20260226-2 arm64 Media Process Platform ii librockchip-mpp1 20260226-2 arm64 Media Process Platform ii libv4l-rkmpp 1.8.0-1 arm64 A rockchip-mpp V4L2 wrapper plugin for chromium video dec and enc ii rockchip-mpp-demos 20260226-2 arm64 Media Process Platform Demos I copied the relevant files from Friendlyelec system to Armbian system (both are Trixie), ran ldconfig, and ran `strace mpv my.mp4` on both systems. Comparison of strace output revealed that certain apparently required device files under /dev/dma_heap are missing on Armbian, plus incorrect permissions on /dev/mpp_service: On Friendlyelec: # ls -l /dev/dma_heap total 0 crw-rw-r-- 1 root video 251, 4 Jul 20 06:48 cma crw-rw-r-- 1 root video 251, 5 Jul 20 06:48 cma-uncached crw-rw-r-- 1 root video 251, 0 Jul 20 06:48 system crw-rw-r-- 1 root video 251, 1 Jul 20 06:48 system-dma32 crw-rw-r-- 1 root video 251, 2 Jul 20 06:48 system-uncached crw-rw-r-- 1 root video 251, 3 Jul 20 06:48 system-uncached-dma32 # ls -l /dev/mpp_service crw-rw-rw- 1 root video 241, 0 Jul 20 06:48 /dev/mpp_service On Armbian: # ls -l /dev/dma_heap total 0 crw------- 1 root root 251, 0 Jul 19 19:41 system crw------- 1 root root 251, 1 Jul 19 19:41 system-uncached # ls -l /dev/mpp_service crw------- 1 root root 241, 0 Jul 20 06:48 /dev/mpp_service Removing the cma= arg from the kernel cmdline gave me /dev/dma_heap/cma, and I manually fixed up the permissions, but still no video accel for mpv. Something else is apparently required, perhaps the remaining missing device files under /dev/dma_heap. -
Hardware video acceleration with recent armbian/mainline kernel (Kodi)
MMGen replied to XXXBold's topic in Orange Pi 5
@Igor: Update: I have HW accel with sound for chromium with my minimal trixie/vendor image, which I installed xfce on top of. This is the image from armbian.org as opposed to the latest release from Github, which is what I tested in my review of Gnome images above. However Chromium doesn’t support AC3 audio, which means it can’t play the majority of the files in my video collection with sound: https://issues.chromium.org/issues/41253735 And there's a good deal besides that Chromium cannot do. This is why Chromium is not enough and we need mpv/ffmpeg/libav* support. mpv plays literally every media file you can throw at it. -
@BipBip1981In your first post you wrote that 6.18.10 works, while 6.18.35 and 6.18.37 don't. Did you test both the new Armbian overlay and the old DTB with 6.18.35, or only one of them? I'm trying to find out whether the DTB makes any difference on 6.18.35.
-
512M seems too low: [ 70.791346] containerd: page allocation failure: order:1, mode:0x40820(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=containerd.service,mems_allowed=0 [ 70.791404] CPU: 1 UID: 0 PID: 1727 Comm: containerd Not tainted 6.18.10-current-meson64 #1 PREEMPT [ 70.791410] Hardware name: linux,dummy-virt (DT) [ 70.791414] Call trace: [ 70.791417] show_stack+0x20/0x38 (C) [ 70.791427] dump_stack_lvl+0x74/0x90 [ 70.791436] dump_stack+0x18/0x28 [ 70.791441] warn_alloc+0x134/0x1c0 [ 70.791449] __alloc_frozen_pages_noprof+0x780/0xe70 [ 70.791457] alloc_pages_mpol+0xbc/0x1c8 [ 70.791463] alloc_frozen_pages_noprof+0x50/0xd0 [ 70.791468] new_slab+0x2ec/0x3a8 [ 70.791474] ___slab_alloc+0x654/0xbb8 [ 70.791480] __slab_alloc.isra.0+0x50/0xa8 [ 70.791485] __kmalloc_noprof+0x410/0x638 [ 70.791491] virtqueue_add_sgs+0x2e4/0x6d0 [ 70.791499] virtblk_add_req+0xb8/0x130 [ 70.791507] virtio_queue_rq+0x80/0x208 [ 70.791513] blk_mq_dispatch_rq_list+0x104/0x6f0 [ 70.791521] __blk_mq_sched_dispatch_requests+0x45c/0x570 [ 70.791527] blk_mq_sched_dispatch_requests+0x38/0x88 [ 70.791532] blk_mq_run_hw_queue+0x25c/0x2d0 [ 70.791538] blk_mq_dispatch_list+0x110/0x420 [ 70.791545] blk_mq_flush_plug_list+0x5c/0x190 [ 70.791551] __blk_flush_plug+0xf0/0x158 [ 70.791559] blk_finish_plug+0x40/0x60 [ 70.791565] read_pages+0x130/0x2c8 [ 70.791573] page_cache_ra_unbounded+0x1e4/0x300 [ 70.791580] page_cache_ra_order+0x41c/0x488 [ 70.791586] filemap_fault+0x5d8/0xb68 [ 70.791592] __do_fault+0x44/0x240 [ 70.791599] __handle_mm_fault+0x9e4/0x18a0 [ 70.791604] handle_mm_fault+0x194/0x2e0 [ 70.791609] do_page_fault+0x110/0x6f8 [ 70.791616] do_translation_fault+0x54/0x80 [ 70.791623] do_mem_abort+0x4c/0xa8 [ 70.791630] el0_ia+0x50/0xd0 [ 70.791637] el0t_64_sync_handler+0xe0/0xe8 [ 70.791644] el0t_64_sync+0x198/0x1a0 [ 70.791650] Mem-Info: [ 70.791832] active_anon:11944 inactive_anon:39978 isolated_anon:0 [ 70.791832] active_file:11107 inactive_file:13422 isolated_file:0 [ 70.791832] unevictable:0 dirty:0 writeback:8 [ 70.791832] slab_reclaimable:5622 slab_unreclaimable:10672 [ 70.791832] mapped:6999 shmem:423 pagetables:2117 [ 70.791832] sec_pagetables:0 bounce:0 [ 70.791832] kernel_misc_reclaimable:0 [ 70.791832] free:912 free_pcp:426 free_cma:29 [ 70.791874] Node 0 active_anon:47776kB inactive_anon:159912kB active_file:44428kB inactive_file:53688kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:27996kB dirty:0kB writeback:32kB shmem:1692kB shmem_thp:0kB shmem_pmdmapped:0kB anon_thp:0kB kernel_stack:6016kB pagetables:8468kB sec_pagetables:0kB all_unreclaimable? no Balloon:0kB [ 70.791907] Node 0 DMA free:3648kB boost:4096kB min:6768kB low:7436kB high:8104kB reserved_highatomic:2048KB free_highatomic:56KB active_anon:47776kB inactive_anon:159912kB active_file:44428kB inactive_file:53460kB unevictable:0kB writepending:32kB zspages:76228kB present:524288kB managed:484516kB mlocked:0kB bounce:0kB free_pcp:1960kB local_pcp:908kB free_cma:116kB [ 70.791945] lowmem_reserve[]: 0 0 0 0 [ 70.791963] Node 0 DMA: 276*4kB (MEC) 54*8kB (MEH) 90*16kB (MEH) 20*32kB (UE) 2*64kB (U) 0*128kB 1*256kB (U) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 4000kB [ 70.792025] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB [ 70.792038] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=32768kB [ 70.792051] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [ 70.792063] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=64kB [ 70.792076] 24919 total pagecache pages [ 70.792084] 33 pages in swap cache [ 70.792091] Free swap = 184kB [ 70.792098] Total swap = 242256kB [ 70.792105] 131072 pages RAM [ 70.792112] 0 pages HighMem/MovableOnly [ 70.792119] 9943 pages reserved [ 70.792126] 32768 pages cma reserved [ 70.792133] 0 pages hwpoisoned [ 70.792140] SLUB: Unable to allocate memory on CPU 1 (of node 0) on node -1, gfp=0x820(GFP_ATOMIC) [ 70.792154] cache: kmalloc-8k, object size: 8192, buffer size: 8192, default order: 3, min order: 1 [ 70.792168] node 0: slabs: 29, objs: 116, free: 0 ... and many OOM killer actions to follow, but could type: poweroff It might be that is no zram swap and swap on disk, that is could work, but from some earlier HA topic here I remember that was a swapping hell on a 4-core Cortex-A53 and SD-card, way too slow. My KVM is image on NVME on ROCK5B, so fastest available more or less for 'cheap' ARM64 SBC. To compare: Domoticz did run OK with about the same amount of objects on a NanoPi-NEO (4x Cortex-A7, 512MiB, SD-card). It still does, but I moved most objects to a 2x Cortex-A55 1G RAM (KVM on same ROCK5B). # free -m total used free shared buff/cache available Mem: 963 330 77 2 635 632 Swap: 981 45 936 BUT I see also something with 'containers' when ZigBee in my google search. I would maybe see what exactly is needed. After many years, I also figured out that my 433MHz transceiver internally is just a 38k4 serial thing tied to an serial-to-USB chip. It was driven as serial port by Domoticz via USBIP on that NanoPi-NEO, but that needs explicit sync/reconnect actions at reboot. Now done via ser2net, swapping/replacing the device from serial to LAN in Domoticz, same database history, no actions at reboot/powercycle and with ser2net point-to-multipoint, also also available to multiple softwares in the home LAN or VPN etc if needed. Of course respecting write/send operations to be exclusive, just one. Same ser2net trick with electricity meter, that is why I can easily run HA/HAOS simultaneously with my normal home automation software stuff.
-
I changed allocated RAM for the virtual machine from 2G to 1G, still 4x Cortex-A55 vCPUs from RK3588 ROCK5B yesterday. At reboot and first login, it showed on 2 container, while earlier it showed a lot more. So now manual stats: root@lepotato:/etc/update-motd.d# ./10-armbian-header ; ./15-ap-info ; ./25-containers-info ; ./30-armbian-sysinfo _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v26.2.1 for Le potato running Armbian Linux 6.18.10-current-meson64 Packages: Debian stable (trixie) Containers: hassio_multicast, hassio_audio, hassio_dns, hassio_cli, homeassistant, hassio_observer, hassio_supervisor Performance: Load: 5% Uptime: 12h 18m Memory usage: 64% of 975M Zram usage: 56% of 487M Usage of /: 79% of 7.8G RX today: 54 MiB Only thing it really does is showing energy page, is 4x 10s sampled data (2x solar and power and delivery). Various Tasmota modules via MQTT don't claim that much resources I think. But strange is a rather constant regular dmesg like this: [44265.955953] hassio: port 2(vethf224414) entered disabled state [44265.957193] vethed7ef10: renamed from eth1 [44266.109287] hassio: port 2(vethf224414) entered disabled state [44266.116189] vethf224414 (unregistering): left allmulticast mode [44266.116262] vethf224414 (unregistering): left promiscuous mode [44266.116357] hassio: port 2(vethf224414) entered disabled state [44266.186986] docker0: port 1(veth76765bf) entered disabled state [44266.187218] veth1a28eaf: renamed from eth0 [44266.285174] docker0: port 1(veth76765bf) entered disabled state [44266.292147] veth76765bf (unregistering): left allmulticast mode [44266.292219] veth76765bf (unregistering): left promiscuous mode [44266.292256] docker0: port 1(veth76765bf) entered disabled state [44268.119635] docker0: port 1(veth51c04e7) entered blocking state [44268.119726] docker0: port 1(veth51c04e7) entered disabled state [44268.119797] veth51c04e7: entered allmulticast mode [44268.120352] veth51c04e7: entered promiscuous mode [44268.245380] eth0: renamed from veth916ebeb [44268.251728] docker0: port 1(veth51c04e7) entered blocking state [44268.251798] docker0: port 1(veth51c04e7) entered forwarding state [44268.384290] hassio: port 2(vethaf9bc59) entered blocking state [44268.384376] hassio: port 2(vethaf9bc59) entered disabled state [44268.384423] vethaf9bc59: entered allmulticast mode [44268.384986] vethaf9bc59: entered promiscuous mode [44268.513343] eth1: renamed from veth48fb602 [44268.520780] hassio: port 2(vethaf9bc59) entered blocking state [44268.520872] hassio: port 2(vethaf9bc59) entered forwarding state [44274.819685] audit: type=1400 audit(1784532963.305:477): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="hassio-supervisor" pid=35485 comm="apparmor_parser" [44274.819758] audit: type=1400 audit(1784532963.305:478): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="hassio-supervisor///usr/bin/gdbus" pid=35485 comm="apparmor_parser" [44274.819829] audit: type=1400 audit(1784532963.305:479): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="hassio-supervisor///usr/bin/git" pid= Maybe that is because the minimal KVM QEMU arguments: if ! test -f /usr/lib/u-boot/qemu_arm64/u-boot.bin ; then apt install u-boot-qemu fi cd /local/s0/vmimg taskset --cpu-list 0-3 qemu-system-aarch64 -M virt -cpu host -enable-kvm -m 1024 -smp 4 \ -bios /usr/lib/u-boot/qemu_arm64/u-boot.bin \ -drive if=none,file=armimg.img,format=raw,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -netdev bridge,id=hn1 -device virtio-net,netdev=hn1 \ -nographic I think I will further limit to 512M and see if it still works; My older own HA Supervised used Btrfs as rootfs (compress-force=zstd:3 mount option), for this fake/KVM lepotato still Ext4 and I did: truncate -s8G armimg.img before 1st boot. For reference, I initially did change boot.cm/boot.scr to something rather static I had done long time ago for virtualizing ROCK3A, but it is more effective if this extlinux method is added to the image (need loopmount it before 1st boot, it assumes extlinux overrides boot.scr method): root@lepotato:/boot# cat extlinux/extlinux.conf menu title Select the kernel variant DEFAULT default TIMEOUT 80 LABEL default KERNEL /boot/Image INITRD /boot/uInitrd APPEND root=LABEL=armbi_root rootwait rw earlyprintk loglevel=7
-
Looks like I accidentally erased most of my u-boot from SPI flash since I don't have much experience with it. Are there any ways to restore it and what soft- and hardware do I need, apart from having a Linux PC and UART?
- Yesterday
-
Updating U-Boot was the solution, kernel is now up to date!!! Thanks everyone for the tips, learned a few new things and the UART cable is really usefull!
-
@Werner @SteeMan Hah, I legit didn't know about the armbian-install command. I updated the bootloader and I guess I'm more up to date now U-Boot on boot is now U-Boot 2026.04_armbian-2026.04-S88dc-P3cfe-H5025-V315b-Bd0d2-R448a (May 30 2026 - 05:51:20 +0000) odroid-n2/n2-plus Gonna try to update the kernel now
-
Much to my chagrin I have had to do a similar dance today after running updates./. I tried sudo dpkg-reconfigure aic8800-usb-dkms but no joy. This time was easier and it was just a matter of getting the firmware and usb module directly from radxa's repo. ```wget https://github.com/radxa-pkg/aic8800/releases/download/5.0%2Bgit20260123.5f7be68d-6/aic8800-firmware_5.0+git20260123.5f7be68d-6_all.deb wget https://github.com/radxa-pkg/aic8800/releases/download/5.0%2Bgit20260123.5f7be68d-6/aic8800-usb-dkms_5.0+git20260123.5f7be68d-6_all.deb``` Then install both of them ```sudo dpkg -i aic8800-firmware_*.deb aic8800-usb-dkms_*.deb``` and then remapping the hardware and restarting ```sudo depmod -a sudo reboot``` Leaving this there... for next time I do an update
-
Much to my chagrin I have had to do the same dance today. I tried
-
I want to compile a matching build for: https://armbian.com/boards/odroidhc4 Debian 13trixie Minimal (CLI)—current6.18.33 https://dl.armbian.com/odroidhc4/Trixie_current_minimal Matching the img is fine (rather than the img.xz). I haven't compiled a matching build yet. I am doing this to debug my issue with the stock builds. Running: ./compile.sh BOARD=odroidhc4 BRANCH=current RELEASE=trixie BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=no Logs forthcoming.
-
I have the same on my 2 year old HA Supervised install I did once on a Debian Bookworm installation (Aarch64). I actually first did the same as you, not on a real HW Lepotato SBC, but as a KVM QEMU U-Boot. One only needs to change boot.scr in the (Amlogic) image, the kernel runs on virtio devices. I can confirm the 15-min waiting, or longer, I haven't looked at it, is a bit strange, but it magically still works this Supuervised. I did restore a backup from my Debian HA install, so very little effort. But it shows as problem that the OS is unsupported and also unsupported install method. The later is known and on HA Wiki/docs, supervised it not mentioned anymore, only the own HAOS en Container. I think 'Add-ons' are now called 'Apps' and also Container does not seem to support it. So for MQTT I anyhow have mosquito as Debian package installed. But teh Zigbee bridge is then a showstopper I see / I think. But also check yourself. I have no ZigBee HW and also HA is only testing for mee, see it it does things better than my current home automation softwares (mostly Node-RED based). The only option I see then is to put HAOS as KVM on Lepotato. It is 4x Cortex-A53 I see, so it can work. But not sure how RAM will work out. If 1GB RAM, then maybe 512M host and 512M guest. I have done that on RPI3 to run a router instance using VLANs.
