Active threads

So I received my USB-PD trigger board, set it to 15V and it does nothing, the situation is still the same. I also ordered a USB tester to see the voltage and amperage, basically the board never draw more than 3 to 4W With Aarch64 UEFI image with EDK2 on the SPI flash, Linux starts to boot but then fails and I get a black screen

After finally getting my TV box to boot Armbian, I'd like to provide some beginner-friendly pointers in addition to @Chiều Nhạt Nắng's installation note 4.2, Full install to NAND / eMMC: As someone who's completely new to Android TV box modding, this step took me a while to get through. What it actually means is not to literally boot your TV box into its original firmware, but to enter either Loader Mode or Maskrom Mode. If you've built or tried to poke around your PC, they are sort of like the BIOS or UEFI (technically BIOS and UEFI live on the motherboard, not CPU... but I digress), or if you have done Nintendo Switch modding, it's like entering RCM. It's not the guide's fault because there are so many ways to get your chip to enter a "maintenance/recovery mode" on so many different boards even with the same chip, it's basically impossible to list all the ways to put it into a malleable state. The way to enter Loader or Maskrom mode typically requires you to do something to the TV box while it is actively booting up, which will interrupt the process and enter the respective mode. For my TV Box (2016 - 2020 ish, Huawei EC6108V9A, RK312X), to enter Loader Mode, I need to repeatedly tap the "Front Page" or "Home" button on my TV box remote as soon as I connect the OTG USB port to my PC (the OTG port is typically the USB port that's the closest to the Ethernet port), I didn't need to plug in the barrel power connector since the board draws power through the same USB connection. If you found yourself in an Android system recovery <3e> page, this is not what we want, you might be tapping the wrong button like "Standby" or "Sleep" button. For my board, once I successfully enter Loader Node, aside from the Windows notification and the Bold text saying "Found ____ Device" at the bottom of the RKDevTool/AndriodTool, it was also showing a static logo screen through HDMI. If you do not have the TV Box's remote, or if you have messed up the install and have to redo, you will almost definitely need to take apart the Box's outer shell and gain access to the PCB itself to enter Maskrom Mode instead. (Images found online) To enter Maskrom Mode, you will need to short two specific pins (or pin holes, or capacitor pads like the first image) as you plug the USB connector from the PC to the USB OTG port on your board (The official way is to short Clock (CLK) to Ground (GRD or any metal connector housing) but good luck finding those if they're not labeled). In my experience, tweezers are the best for this. Since everyone's board looks different, there are different ways to do it, but do not try to short anything on your board before you're absolutely certain that the image of the board matches the one on your hand exactly. Unfortunately these info are incredibly niche and hard to find, your best bet is to search your TV Box's model number along with your chip's name (RK3128 in our case) on google and bilibili, there's a good chance you'll end up on a Chinese forum and have to dig through it with google translate. (Do NOT take an AI's word for it!) In case the first step in the quote isn't clear enough, you have to click the EraseLBA button after typing in these addresses below it to erase sectors. It is also worth noting that you have to be in Loader Mode to EraseLBA or use any "Read____" buttons. If your device is in Maskrom Mode because you lost the remote or botched an install, you can't directly do all that aside from Download Image. The workaround is to hit the "..." button to the right of "Boot:", select rk3128_loader_v2.12.263.bin and hit Download. Now you can use most of the Advanced Functions while in Maskrom! In Chieu's attached image for this step, there is actually an error. If you are using the files from their 20260430 release (A26-release-20260430.zip), you will need to set Boot sector's address at 0x00006000, NOT 0x00010000. I strongly encourage you to open parameter.txt and verify the addresses yourself. My setup looks like this: 0x00000000 | Loader | rk3128_loader_v2.12.263.bin 0x00000000 | parameter | parameter.txt 0x00002000 | uboot | uboot.img 0x00004000 | trust | trust.img 0x00006000 | root | armbian_rootfs_26.2.img By the way, you can click on the empty box to the right of paths to find the files. Right click - Del item to delete any extra default entries you don't need. Now before you click Run, I strongly recommend you to connect the board to a monitor/TV via HDMI and your router via Ethernet with known good cables/connections! Your board's first boot into Armbian happens immediately after Download Image finishes, therefore it's incredibly difficult to monitor the progress without them. I'm honestly not sure if the setup can complete without Ethernet because I tried to flash my board without connecting Ethernet twice and failed twice. Miscellaneous Notes: If you're 100% positive that you have done the steps to enter Loader Mode or Maskrom Mode correctly but your PC is refusing to pick up the connection, try installing the driver "Rockchip_DriverAssitant_v4.2" (should be the first result on google). Some online sources might tell you to diagnose via UART with a USB-to-ttl adapter. It did not work on mine (was completely silent during boot). Conversely, not seeing anything from UART doesn't necessarily mean your board is bricked. The board should always be able to enter Maskrom if you have access to the PCB. After your board has gone through the first boot, you will see a prompt on the HDMI output asking you to set a password for the root user. You can connect to the board via SSH at this point with IP address shown during the boot sequence; you do not need to connect a physical keyboard to the board. A handy software to manage all your UART and SSH connections is MobaXterm. The settings are straightforward and there is a portable version if you don't like installing stuff. From OP's screenshots I think Chieu is using it too!

Hi, take a look at the build doc: https://docs.armbian.com/Developer-Guide_Build-Preparation/ You could try to build the kernel only, typically you get the latest version of the stable branch ./compile.sh kernel EXPERT="yes" BOARD=helios64 ARTIFACT_IGNORE_CACHE='yes' BRANCH=current

I am encountering similar issue in Allwinner-H618 based Kickpi-K2B board. Over the time, the video play stops with frozen frame display. The freeze is caused by the audio clock drifting from the video clock over time — and that drift happens during the video segments. have you (anyone) found the solution for this?

@Alex Ling That's weird. It's about 15% performance bump in theory. How GPU lock was show in...like Mangohud?

I tried editing /boot/boot.cmd and recompiling. my changes did persist (I saw 'echo' worked) but it doesn't seem like my scsi scan trick worked. interrupting boot and just going straight into the above steps worked. so i think I need to edit boot.cmd to skip all the boot code for hc4 and just 'scan' then 'boot'. https://docs.armbian.com/User-Guide_Advanced-Configuration/

Still doesn't work for me.. USB works fine, only wifi is bugging and I don't have any other wifi card # sudo cp aic_btusb.ko aic_load_fw.ko aic8800_fdrv.ko /lib/modules/$(uname -r)/kernel/drivers/net/wireless/aic8800 # sudo depmod -a depmod: ERROR: failed to load symbols from /lib/modules/7.1.0-.ko: Invalid argument l/drivers/net/wireless/aic8800/aic_btusb.ko: Invalid argument-rc4-next-20260518-edge-rockchip64/kernel/drivers/net/wireless/aic8800/aic_btusb.ko: Invalid argument # sudo rm /lib/modules/7.1.0-rc4-next-20260518-edge-rockchip64/kernel/drivers/net/wireless/aic8800/aic_btusb.ko # sudo depmod -a depmod: ERROR: failed to load symbols from /lib/modules/7.1.0-aic8800/aic_load_fw.ko: Invalid argument depmod: ERROR: failed to load symbols from /lib/modules/7.1.0-rc4-next-20260518-edge-rockchip64/kernel/drivers/net/wireless/aic8800/aic8800_fdrv.ko: Invalid argument

Try this google AI search instead: create overlay on armbian orangepione for Nokia 5110 / PCD8544 LCD You might also need to add to armbianEnv.txt after enabling spi-spidev root@orangepione:~# more /boot/armbianEnv.txt verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 rootdev=UUID=f39623a3-f9cf-4fa1-be36-6854d244c378 rootfstype=ext4 overlays=spi-spidev param_spidev_spi_bus=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u root@orangepione:~# On successful startup of spi you should have a device: root@orangepione:~# ls /dev/spidev0.0 /dev/spidev0.0 root@orangepione:~#

So the wifi works on my tablet and to get it working you need to compile dkms package from https://github.com/radxa-pkg/aic8800/releases i used aic8800-sdio-dkms_5.0+git20260123.5f7be68d-5_all.deb i got the firmware files from stock firmware. You'd want to do this on x86 machine you are preparing the image because you need internet probably for it.

Do a PR.

Use Armbian Imager to create SDcard with curent Release. Connect HDMI Monitor and USB Keyboard. Put Sdcard into sdcard Slot and Power the Box. Follow instruction on Monitor

I ran memtester and found memorie errors, which is probably the cause of the problem I report med earlies. Hopefully this can be solved by changing voltage er timing settings.

Let me know. I had hopes the commiter would provide upstreaming effort proof but nothing there yet.

That's very useful. I'm nowhere near as practiced with this, so it'll take some time to digest and plan a way forward. It does fit with what seemed to be the case, though: it's device-level issues. I'll start poking around in the specific device differences and see what shows. The great hint you've found is that this is likely affecting all CSI cameras, not just the IMX708. That's most useful. I'm not at all worried about networkmanager, because the only tweak I made in the custom build was to use systemd-networkd, which (for me, anyway) is more straightforward for embedded/minimal/CLI usage. What I haven't yet done, and probably should, is switch to debugging this in something more vanilla, like a Pi 4. At least then I can compile libcamera and friends directly on the device. The Zero 2W should be the same -- he says, hopefully.

Greetings ### [Follow-up Update] Boot Deep-Dive via Cubie-A5E DTB Masking Following up on my previous boot freeze post, I (with some assistance from Gemini - who formatted this post) managed to force the Armbian kernel to initialize by masking the sister chip profile (`sun55i-a523-cubie-a5e.dtb`) over the broken `sun55i-t527-orangepi-4a.dtb` target and injecting `clk_ignore_unused` / `irqpoll` parameters. This got us past the initial handoff hang and successfully spawned the 8-core CPU array initialization and initramfs launch (`Run /init as init process`), but the system eventually hit a permanent deadlock during the device probe phase. I don't think I can get this to go any further without some many hours spent looking at how these things work and its currently 35 degrees C here in the UK so time for a beer methinks! #### Full Boot Log Paste Link: - this is the log before using irqpoll parameter (which eventually caused a deadlock) - I can post the irqpoll logs although i wouldn't have thought irqpolling is the way to go ? https://pastebin.com/TvxTxdbp ### Either way - having just read that this post refers to irqpoll then this is the boot logfile with irqpoll added an an extraparm https://pastebin.com/TNS3DDTC #### Key Technical Takeaways from the Log Dump: 1. **PMIC / I2C Communication Failures:** The kernel initializes the AXP717 and AXP323 power chips but encounters standard timeout errors right away: ```text axp20x-i2c 0-0034: AXP20x variant AXP717 found axp20x-i2c 0-0034: Failed to set masks in 0x40: -6 axp20x-i2c 0-0034: failed to add irq chip: -6 ``` 2. **MMC / Storage Controller Deadlock:** Because the AXP717 framework drops out and the Cubie pin definitions do not line up with the Orange Pi 4A's physical board wiring, the kernel enters an endless loop waiting for internal voltage rails (`cldo3` and `bldo1`) to power up the storage controller: ```text platform 4020000.mmc: deferred probe pending: platform: wait for supplier /soc/i2c@7081400/pmic@34/regulators/cldo3 platform 4021000.mmc: deferred probe pending: platform: wait for supplier /soc/i2c@7081400/pmic@34/regulators/bldo1 ``` This prevents the storage device slot from spinning up, trapping the system right as it attempts to mount the root filesystem. Hopefully this helps isolate the unaligned power configuration loops and clock tables in the current `armbian-imager` source profile for the OPi 4A!

Kraid is a new Rust-based compiler for Panfrost that replaces the aging Bifrost-rooted compiler stack with a cleaner, more flexible design for modern Mali GPUs, improving IR structure, register allocation, hardware testing, and long-term maintainability. View the full article

I usually make a quick backup before running bigger updates, especially on systems that are already working well. It also helps to reboot after the update and check armbianmonitor -u if anything seems off afterward. That can provide useful information if you need to troubleshoot.

Hello experts and members, Any possibility of multi booting armbian via petitboot from microsd card or usb or emmc in odroid n2 among other OSs.

Hi ! I have a FriendlyElec NanoPi M5 and I want to play movies with it. But I want to squeeze everything out of this SBC ! So, I need hardware acceleration. I tested first with a OS image downloaded from FriendlyElec and mpv and (almost) everything works well. The mpv working configuration is: hwdec=rkmpp, vo=gpu, gpu-api=opengl. But I don't like that OS for other reasons, so I switched to Armbian. I installed the image "Armbian 26.5.1 KDE Wayland (Ubuntu 26.04 - vendor 6.1.115)", then I installed mpv, but when I try to play movies, it says: marus@nanopi-m5:/mnt/NAS/WDRed1/Samples/FullHD$ mpv --hwdec=rkmpp --vo=gpu --gpu-api=opengl H265.8bit.FullHD.1920x816.24fps.10Mbps.SDR.mkv ● Video --vid=1 --vlang=eng 'Carlito's Way 1993' (hevc 1920x816 23.976 fps) [default] ● Audio --aid=1 --alang=eng 'DDP 5.1 ch 640 Kb/s' (eac3 6ch 48000 Hz) [default] Unsupported hwdec: rkmpp AO: [pipewire] 48000Hz 5.1(side) 6ch floatp VO: [gpu] 1920x816 yuv420p AV: 00:00:14 / 00:01:59 (12%) A-V: 0.000 Cache: 104s/146MB Exiting... (Quit) It seems that this mpv doesn't know about rkmpp's existence... Strange ! What can I do ? Has anyone managed to play movies with mpv and full hardware acceleration on NanoPi M5 and Armbian OS?

OK so the fix is working'ish. Unique problem, well more of an inconvenience, with sound. I applied the fix and works. I run, systemctl --user restart pipewire wireplumber pulseaudio and it system sounds working! Then I open Chromium and it won't play and says I need to restart my device... just a spinning circle. So while Chromium is still open I run, systemctl --user restart pipewire wireplumber pulseaudio again and the video plays and I have sound! Until I pause the video or watch a new video. The I have to run systemctl --user restart pipewire wireplumber pulseaudio AGAIN. Any ideas?

@li20034 just a reply in general. I had no issues with this method after updating to the latest on 6/20/26. Wondering if there is something I may have installed that would have made it work for me?

I managed to download an old image from a torrent archive found in a Reddit thread, where the author mentioned that Armbian was running on the Retroid Flip 2. I flashed the image: Armbian_community_26.2.0-trunk.162_Retroidpocket-rp5_noble_current_6.12.63_gnome_desktop.img However, I encountered the same error. It’s possible that something has changed in the newer console revisions or in the new bootloader.

Welcome to the latest Armbian Newsletter: your source for the latest developments, community highlights, and behind-the-scenes updates from the world of open-source ARM and RISC-V computing. This week: the desktop installer in armbian-config has been rebuilt from the ground up tiered installs, clean uninstalls, and snap-free native browsers across all architectures. Armbian Imager 2.0 is out, rewritten interface and flashing engine, with boards that boot already configured (username, Wi-Fi, timezone) and byte-for-byte write verification. And the NanoPi M5 becomes the first RK3576 board to boot end-to-end from UFS on mainline U-Boot, with no proprietary image in the loop. SPONSORED Join us in making open source better! Every donation helps Armbian improve security, performance, and reliability — so everyone can enjoy a solid foundation for their devices. Github HighlightsThis week’s work centers on board portfolio expansion, kernel and U-Boot version bumps, and CI and infrastructure hardening across the build and documentation pipelines. Board support saw notable growth with the introduction of the SpacemiT K3 Pico-ITX and Luckfox Nova (RK3308B), alongside a new generic uefi-arm64-dt family and board intendedArmbian blogMichael RobinsonNative UFS boot lands on the NanoPi M5Armbian’s next release boots the FriendlyElec NanoPi M5 end-to-end from UFS on a mainline U-Boot, with no proprietary recovery image in the loop. It is the first RK3576 board in the catalogue to reach this state, and the integration pattern paves the way for the others. UFS, the storage classArmbian blogDaniele BriguglioMeet our new Armbian Imager 2.0We’re releasing Armbian Imager 2.0. We rebuilt the whole thing, the interface and the flashing engine underneath it. The part you’ll notice first: your board boots already set up. Username, password, Wi-Fi, timezone, language. You tell Imager once, it writes that into the image, and the board comes upArmbian blogDaniele BriguglioWe rewrote how Armbian installs desktops. Here’s what changedA friendlier, faster, snap-free desktop install in armbian-config If you’ve installed a desktop environment with armbian-config over the last few months, you may have noticed things feel different: there’s a tier you can pick, the browser actually works on every arch, uninstall doesn’t take half your system with it, andArmbian blogIgor PecovnikView the full article

Welcome to the latest Armbian Newsletter: your source for the latest developments, community highlights, and behind-the-scenes updates from the world of open-source ARM and RISC-V computing. This week: the desktop installer in armbian-config has been rebuilt from the ground up tiered installs, clean uninstalls, and snap-free native browsers across all architectures. Armbian Imager 2.0 is out, rewritten interface and flashing engine, with boards that boot already configured (username, Wi-Fi, timezone) and byte-for-byte write verification. And the NanoPi M5 becomes the first RK3576 board to boot end-to-end from UFS on mainline U-Boot, with no proprietary image in the loop. SPONSORED Join us in making open source better! Every donation helps Armbian improve security, performance, and reliability — so everyone can enjoy a solid foundation for their devices. Github HighlightsThis week’s work centers on board portfolio expansion, kernel and U-Boot version bumps, and CI and infrastructure hardening across the build and documentation pipelines. Board support saw notable growth with the introduction of the SpacemiT K3 Pico-ITX and Luckfox Nova (RK3308B), alongside a new generic uefi-arm64-dt family and board intendedArmbian blogMichael RobinsonNative UFS boot lands on the NanoPi M5Armbian’s next release boots the FriendlyElec NanoPi M5 end-to-end from UFS on a mainline U-Boot, with no proprietary recovery image in the loop. It is the first RK3576 board in the catalogue to reach this state, and the integration pattern paves the way for the others. UFS, the storage classArmbian blogDaniele BriguglioMeet our new Armbian Imager 2.0We’re releasing Armbian Imager 2.0. We rebuilt the whole thing, the interface and the flashing engine underneath it. The part you’ll notice first: your board boots already set up. Username, password, Wi-Fi, timezone, language. You tell Imager once, it writes that into the image, and the board comes upArmbian blogDaniele BriguglioWe rewrote how Armbian installs desktops. Here’s what changedA friendlier, faster, snap-free desktop install in armbian-config If you’ve installed a desktop environment with armbian-config over the last few months, you may have noticed things feel different: there’s a tier you can pick, the browser actually works on every arch, uninstall doesn’t take half your system with it, andArmbian blogIgor PecovnikView the full article

This week's work centers on board portfolio expansion, kernel and U-Boot version bumps, and CI and infrastructure hardening across the build and documentation pipelines. Board support saw notable growth with the introduction of the SpacemiT K3 Pico-ITX and Luckfox Nova (RK3308B), alongside a new generic uefi-arm64-dt family and board intended to standardize UEFI device-tree targets. Qualcomm enablement advanced through Radxa Dragon Q6A and Q8B work, including UFS provisioning for Kodiak, EDL-based UFS flashing in the imager, and audioreach topology firmware for sc8280xp. Catalog assets were extended for the MaaXBoard 8ULP, Mellow Fly C5, Xiaomi Sheng, and the new Radxa and SpacemiT boards. On the kernel and bootloader front, rockchip64, meson64, and rpi4b edge branches were promoted to the stable 7.1 series, with the rtl8192eu driver rebuilt and re-enabled against the new tree. U-Boot was refreshed on cm3588-nas, nanopik2-s905, and the Luckfox Nova, while updated DDR, BL31, and BL32 blobs landed for RK3528 and new SPL loaders were published for RV1103, RV1106, and RK3506. Targeted kernel-config work restored md/RAID modules on sunxi, enabled MIPI DBI panels on sunxi64, and added CPUFreq support for the SpacemiT K1. Infrastructure changes focused on resilience and resource control. The git-trees workflow gained bounded retries, escalating timeouts, and Google mirror fallbacks; Docker base-image pulls now retry transient GHCR failures and split host dependencies into per-group apt layers. Image compression caps xz memory and thread usage, the info-gatherer no longer exhausts file descriptors, and a new CI policy enforces transparent backgrounds and object-size limits for board and vendor logos, with offending assets re-cropped. #Armbian #EmbeddedLinux #UBoot #Qualcomm #Rockchip ChangesActions: Disable debugsym builds. by @vidplace7 in armbian/MorseMicro-DKMS#7Add Board & Vendor logo for the Mellow Fly C5. by @deece in armbian/armbian.github.io#324Add board SpacemiT K3 Pico-ITX. by @pyavitz in armbian/build#10001Add board: Luckfox Nova (RK3308B). by @crackerjacques in armbian/build#9985Add K3 Pico ITX. by @igorpecovnik in armbian/armbian.github.io#341Add Luckfox Nova board image. by @crackerjacques in armbian/armbian.github.io#332Add MaaXBoard 8ULP board image and Avnet vendor logo. by @govindsi in armbian/armbian.github.io#340Add Radxa Dragon Q8B board image. by @SuperKali in armbian/armbian.github.io#342Add spl_loader bins for RV1103, RV1106, RK3506. by @vidplace7 in armbian/rkbin#46Add Xiaomi Sheng board image. by @code002-2 in armbian/armbian.github.io#337armbian-install: fix boot on UEFI systems. by @EvilOlaf in armbian/build#9945armbian-upgrade: use apt-get to silence apt CLI-warning noise. by @igorpecovnik in armbian/build#9998artifact-uboot: opt-in cache-bust via UBOOT_HASH_EXTRA for prebuilt blobs. by @igorpecovnik in armbian/build#9995board assets: fix 10 board-image dimensions + square the Huawei logo. by @igorpecovnik in armbian/armbian.github.io#334ci: board-asset validation — transparent background + object-size + full monthly scan. by @igorpecovnik in armbian/armbian.github.io#333ci: bound each retry attempt with a 10-minute timeout. by @rpardini in armbian/shallow#8ci: double retry timeout each attempt; fetch from Google mirrors. by @rpardini in armbian/shallow#9ci: enforce MAX_OBJECT_PCT=50 + re-crop the two over-limit board images. by @igorpecovnik in armbian/armbian.github.io#335ci: make git-trees workflow resilient to network failures. by @rpardini in armbian/shallow#7ci: push image-info data branch direct to github (bypass git cache proxy). by @igorpecovnik in armbian/armbian.github.io#338ci: vendor logos must be transparent + ≤80% object fill (+ fix the 6 opaque ones). by @igorpecovnik in armbian/armbian.github.io#336cm3588-nas: u-boot: bump to v2026.07-rc3. by @rpardini in armbian/build#9975docker: retry transient ghcr base-image pulls; guard the auto-pull cronjob. by @igorpecovnik in armbian/build#10006docker: split host deps into per-group apt layers in generated Dockerfile. by @rpardini in armbian/build#9999Feature/sunxi mainline stmmac ac300. by @deece in armbian/build#9952fix(images): hide UFS images from the catalog. by @SuperKali in armbian/imager#157fix(profiles): keep the flash profile picker in sync with Settings. by @SuperKali in armbian/imager#156Flash UFS images to Qualcomm boards over EDL. by @SuperKali in armbian/imager#158image: cap xz compression memory and lower the thread cap. by @igorpecovnik in armbian/build#10005info-gatherer: fix 'Too many open files' from cpu*4 parallel workers. by @igorpecovnik in armbian/build#10014introduce new family uefidt and new board uefi-arm64-dt. by @amazingfate in armbian/build#9923Kodiak: add Radxa Dragon Q6A UFS provisioning XML. by @SuperKali in armbian/qcombin#2luckfox-rk3308b-nova: bump U-Boot to v2026.07-rc4. by @crackerjacques in armbian/build#10010meson64: bleedingedge: enable CONFIG_GPIO_CDEV_V1. by @adeepn in armbian/build#9979nanopik2-s905: bump u-boot to v2026.04. by @igorpecovnik in armbian/build#9989PocketBeagle 2 - Fix NCM Networking w/ACM for Serial. by @Grippy98 in armbian/build#10007qcom/qcs6490: replace Radxa Dragon Q6A adsp/cdsp with linux-firmware. by @SuperKali in armbian/firmware#129qcom/sc8280xp: add Radxa Dragon Q8B audioreach topology. by @SuperKali in armbian/firmware#128radxa-cubie-a5e: tidy BOARD_NAME to "Cubie A5E". by @igorpecovnik in armbian/build#9990remove bleedingedge from all boards. by @EvilOlaf in armbian/build#10016rk3528: updated rkbins ddr/bl31/bl32 for rk3528. by @rpardini in armbian/rkbin#47rockchip64 & meson64: bump edge to stable 7.1. by @EvilOlaf in armbian/build#9980rpi4b: bump edge to 7.1.y. by @EvilOlaf in armbian/build#9982rtl8192eu: fix build against 7.1 and re-enable. by @EvilOlaf in armbian/build#10009SpacemiT K1: Update CPUFreq support EDGE. by @pyavitz in armbian/build#9981sunxi64: Enable CONFIG_DRM_PANEL_MIPI_DBI=m for current and edge configs. by @d93921012 in armbian/build#9984sunxi: restore md modules (software raid modules). by @k-popov in armbian/build#9992Update MorseMicro suite to 1.17.9. by @vidplace7 in armbian/MorseMicro-DKMS#8Update odroidxu4-current to 6.6.143. by @belegdol in armbian/build#10018View the full article