Yesterday I flashed a new sd card (more space) for my rockpi-4b but after switching to the stable channel `armbian-config --cmd STABLE` the update keeps failing: $ sudo apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org trixie-security InRelease Get:3 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB] Hit:4 http://deb.debian.org/debian trixie-backports InRelease Hit:5 https://github.armbian.com/configng stable InRelease Get:6 http://armbian.lv.auroradev.org/apt trixie InRelease [39.4 kB] Get:7 http://armbian.lv.auroradev.org/apt trixie/trixie-utils arm64 Packages [21.4 kB] Get:8 http://armbian.lv.auroradev.org/apt trixie/trixie-desktop arm64 Packages [68 33 B] Fetched 115 kB in 2s (69.5 kB/s) 1 package can be upgraded. Run 'apt list --upgradable' to see it. $ sudo dpkg --configure -a $ sudo apt --fix-broken install Summary: Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 1 $ sudo apt upgrade Upgrading: armbian-firmware Summary: Upgrading: 1, Installing: 0, Removing: 0, Not Upgrading: 0 Download size: 0 B / 141 MB Space needed: 99.3 MB / 59.9 GB available Continue? [Y/n] y (Reading database ... 26869 files and directories currently installed.) Preparing to unpack .../armbian-firmware_26.2.1_all.deb ... Unpacking armbian-firmware (26.2.1) over (26.2.0-trunk.703) ... dpkg: error processing archive /var/cache/apt/archives/armbian-firmware_26.2.1_all.deb (--unpack): unable to open '/lib/firmware/qcom/sm8550/ayn/odin2mini/a740_zap.mbn.dpkg-new': No such file or directory Errors were encountered while processing: /var/cache/apt/archives/armbian-firmware_26.2.1_all.deb Error: Sub-process /usr/bin/dpkg returned an error code (1) For now I am doing `sudo apt-mark hold armbian-firmware`. Switching to rolling, updating there works (26.2.0-trunk.722). But the issue persists when switching back to stable. As there have been recent changes https://github.com/armbian/firmware/pull/117 and https://github.com/armbian/firmware/pull/119 and I couldn't find other error reports on the forum, I guess this is an issue of the image packaging. I also plugged back in the old sd card and that system updated without issues.

Good morning. root_key.pem (after compilation) is located in not in u-boot* (root directory). Is that right? Thanks in advance.

@tim zeng sure, but that's not - directly - related, since the Orange PI5 and the Orange Pi3 are different SOCs/SBCs. The only common trait is the poor SW support offered by the vendor.

I am experiencing an issue where the Intel BE200 Wi-Fi module stops working on the NanoPi R5C after upgrading to the latest Armbian v26.2.1 with newer kernels. The iwlwifi driver fails to initialize the device due to a missing configuration profile. Environment: Board: NanoPi R5C OS Version: Armbian v26.2.1 Wi-Fi Module: Intel BE200 Failing Kernels: v6.19.0-edge-rockchip64, v6.18.10-current-rockchip64 Working Kernel: 6.12.58-current-rockchip64 Actual Behavior & Logs: When booting with v6.18.10-current-rockchip64 or v6.19.0-edge-rockchip64, the Wi-Fi interface does not show up. Checking dmesg reveals the following iwlwifi probe failure (error -22): [ +0.001360] iwlwifi 0000:01:00.0: Detected crf-id 0x2001910, cnv-id 0x2001910 wfpm id 0x80000000 [ +0.000070] iwlwifi 0000:01:00.0: PCI dev 272b/00f4, rev=0x472, rfid=0x112200 [ +0.000012] No config found for PCI dev 272b/00f4, rev=0x472, rfid=0x112200 [ +0.026664] iwlwifi 0000:01:00.0: probe with driver iwlwifi failed with error -22 pi@nanopi-r5c:~$ ls /lib/firmware/iwlwifi-gl-c0-fm-c0* /lib/firmware/iwlwifi-gl-c0-fm-c0-100.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-96.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-100.ucode.zst /lib/firmware/iwlwifi-gl-c0-fm-c0-96.ucode.zst /lib/firmware/iwlwifi-gl-c0-fm-c0-101.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-97.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-101.ucode.zst /lib/firmware/iwlwifi-gl-c0-fm-c0-97.ucode.zst /lib/firmware/iwlwifi-gl-c0-fm-c0-83.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-98.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-83.ucode.zst /lib/firmware/iwlwifi-gl-c0-fm-c0-98.ucode.zst /lib/firmware/iwlwifi-gl-c0-fm-c0-86.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-c101.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-86.ucode.zst /lib/firmware/iwlwifi-gl-c0-fm-c0-c101.ucode.zst /lib/firmware/iwlwifi-gl-c0-fm-c0-90.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-c102.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-90.ucode.zst /lib/firmware/iwlwifi-gl-c0-fm-c0-c102.ucode.zst /lib/firmware/iwlwifi-gl-c0-fm-c0-92.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-c103.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0-92.ucode.zst /lib/firmware/iwlwifi-gl-c0-fm-c0.pnvm /lib/firmware/iwlwifi-gl-c0-fm-c0-94.ucode /lib/firmware/iwlwifi-gl-c0-fm-c0.pnvm.zst /lib/firmware/iwlwifi-gl-c0-fm-c0-94.ucode.zst Workaround: Downgrading the kernel to 6.12.58-current-rockchip64 via armbian-config completely resolves the issue, and the BE200 module works as expected. It seems there might be a regression or missing iwlwifi config definitions for the BE200 in the recent rockchip64 kernel builds. I would appreciate it if you could look into this. Thank you!

Hello, I have H96 Max TV box with RK3528 chip (4GB RAM, 64GB eMMC, Android 13, build RZX.V01.20240924). Board: RK3528_DDR3_8X4_V12. Problem: Box does not boot from TF card at all. No HDMI output, no DHCP lease, nothing. What I have: TF card slot on the box 1x USB 2.0 port, 1x USB 3.0 port No serial/UART adapter (DEBUG header visible on PCB but not connected) Android 13 still working on EMMC ADB access with root What I tried: Built Armbian with BOARD=rk3528-tvbox BRANCH=legacy BUILD_MINIMAL=yes RELEASE=trixie Extracted DTB from Android boot partition, added to image Wrote image to TF card with dd Verified RKNS header at sector 64 - correct Tried replacing idbloader with one from our custom U-Boot build Original U-Boot on EMMC appears to ignore TF card completely Question: How to make original U-Boot boot from TF card? Or is there a way to install Armbian to EMMC safely while keeping ability to recover? Device AIDA64 info: Model: H96_Max_RK3528 Device: rk3528_box Hardware: rk30board Thank you!