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.

Checking in on Armbian, the installed raspi-firmware is 1.20250915-1~bookworm: $ apt list -a raspi-firmware raspi-firmware/trixie,trixie,now 1:1.20250915-1~bookworm all [installed] raspi-firmware/trixie,trixie 1:1.20250430-4~bookworm all raspi-firmware/trixie,trixie 1:1.20250430-3 all raspi-firmware/trixie,trixie 1:1.20250430-1 all raspi-firmware/stable 1.20240424+ds-6 all I do note there were upstream issues in this: https://github.com/raspberrypi/linux/issues/6753, but that does not 100% match, as we do not get the logs that imply that cause. And the hashes: $ shasum /boot/firmware/bootcode.bin fa4cd59207022a61a2cc645b6dfdf1d481bba07b /boot/firmware/bootcode.bin $ shasum /boot/firmware/start.elf bbd038d812d408c209005c9f8c2801ef1affc501 /boot/firmware/start.elf $ shasum /boot/firmware/fixup.dat 75e5543a3834b3fec1c9f598e2e9e9ae13e5b334 /boot/firmware/fixup.dat Latest Raspbian is using newer firmware: $ apt list -a raspi-firmware raspi-firmware/stable,stable,now 1:1.20260521-3 all [installed] raspi-firmware/stable,stable 1.20240424+ds-6 all And the Raspbian files are all different. Maybe I should try the Ubuntu Armbian and/or a minimal sid build and see how they play out.

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