RSS Bot

Abandoned vendor-provided BSP roadblocks can be overcome when mainline Open Source projects like the Linux kernel are integrated directly. Get your upstreamed BSPs from day one. View the full article

Next week, Collabora will be taking part in the 2025 edition X.Org Developer's Conference! Taking place in Vienna, our engineers will be presenting 6 talks and a workshop to help local students discover the embedded graphics stack! Join us! View the full article

Join us next week in Paris for Kernel Recipes! We're delighted to sponsor this kernel-focused event and contribute with a talk on GPU drivers. View the full article

AFBC support has been merged to PanVK and will be available in the Mesa 25.3 release! This new enablement reduces memory bandwidth and boosts performance. View the full article

Visit us at the STMicroelectronics booth, where Collabora will highlight how the STM32MP2 chip empowers edge AI solutions for industrial applications. View the full article

The Debian Trixie release is jam-packed with new features thanks to the efforts of many. See where Collabora contributed to upgraded GNOME components, newer PipeWire versions, and more! View the full article

Addressing the need for reliable hardware testing for RISC-V adoption, the RISE Project and Collabora added two RISC-V boards to Collabora's LAVA testing lab. View the full article

Collabora is headed to Amsterdam. Meet us at Booth A63 in Hall 14 as we showcase GStreamer Analytics combined with ML, hardware-accelerated video decoding in Dante Studio using GStreamer, remote rendering for standalone XR, and more! View the full article

Dear Armbians, I'm thrilled to announce the launch of this digest for our amazing community. For newcomers, Armbian is a lightweight Linux distribution that breathes life into ARM-based single-board computers, transforming tiny, affordable boards into powerful servers, workstations, and IoT devices. This newsletter is our way of keeping you in the loop, sharing the latest releases, celebrating community contributions, and diving into the technical insights that power your projects. Whether you're a tech enthusiast or just getting started with your first Orange Pi, there's something here for you. Thanks for being part of this incredible journey! Igor Armbian project manager v25.8.1 is here!Armbian v25.8.1 delivers Kernel 6.16, new board support, and official Debian Trixie compatibility.Armbian blogMichael RobinsonGithub highlightsArmbian’s latest updates bring critical ethernet fixes for Rockchip SoCs, enhanced hardware support for Banana Pi R4 and NanoPi M6, plus various build system improvements and kernel updates.Armbian blogInella JoomunStorage for SBCs: which media works bestFrom convenient microSD cards to high-speed NVMe drives, discover which storage solution will make or break your SBC project’s performance and reliability.Armbian blogMichael RobinsonView the full article

Hello Armbian community! Take a look at the latest developments and improvements in Armbian over the past weeks of August 2025. Our focus remains on enhancing stability, expanding hardware support, and streamlining the build process. HighlightsImproved ethernet stability for Rockchip SoCs A crucial workaround has been implemented to address gigabit Ethernet issues on several Rockchip SoCs when using the edge kernel, bringing more reliable network connectivity. PR #8515Enhanced BPI-R4 SFP support Fixes improve SFP (Small Form-Factor Pluggable) module support on the Banana Pi R4 and Filogic-based boards, ensuring better compatibility and functionality. PR #8517New featuresNanoPi M6 LCD support Added support for the YX35 LCD on the NanoPi M6 via the edge kernel, expanding display options. PR #8512Bug fixesCAN Module compilation fix Removed CONFIG_CAN_TI_HECC as it failed to compile, preventing build failures. PR #8534, PR #8527motd Alignment correction Another alignment fix for the Message of the Day (motd) display for a cleaner console experience. PR #8533Sunxi64 Edge build stability Fixed breakage in sunxi64 edge kernel builds. PR #8516Odroid XU4 patching consistency Ensured double-digit numbers in odroidxu4-6.6 and spacemit-6.6 patches are padded with a leading zero. PR #8522ImprovementsKernel Updates - Updated odroidxu4-current kernel to 6.6.102 (PR #8523)Build system & configuration - Temporarily disabled daily builds for Qualcomm Robotics RB5 (PR #8535) - Switched kde-neon to stable branch, adjusted support to csc (PR #8519) - Updated TI k3 configuration to use new official GitHub mirrors (PR #8530) - Changed preferred kernel order for Banana Pi M2+ to prioritize current and edge over legacy (PR #8524) - Dropped abandoned Collabora kernel support for RK3588 (PR #8532) - Removed rk3399-fix-pci-lanes.patch from the 6.16 kernel (PR #8526)Community contributionsBig thanks to our contributors this week: @igorpecovnik @leggewie @Grippy98 @EvilOlaf @tabrisnet@paolosabatino @efectn Get involvedWant to contribute to Armbian? Join the community! GitHub RepositoryArmbian ForumsSupport ArmbianView the full article

Armbian, a leading Linux distribution tailored for single-board computers (SBCs), has officially announced the release of v25.8.1, a significant update that landed on August 2025. This release marks another stride in the project's mission to deliver a reliable, high-performance, and versatile Linux ecosystem for ARM-based devices. The latest version is a testament to the power of community-driven development, packing a wealth of improvements, expanded platform support, and robust kernel and bootloader updates that will benefit developers and enthusiasts alike. Kernels, Bootloaders, Firmware At the core of the August release is a strong focus on reinforcing the operating system’s foundation. The Armbian team has delivered extensive updates across both the Linux kernel and bootloader components. Most platforms have advanced to Kernel 6.16 on their EDGE branches, while the STABLE branch remains on the long-term supported Kernel 6.12. These upgrades go beyond new features bringing critical security patches, performance improvements, and broader hardware compatibility for Armbian users. In addition to kernel updates, this release also refreshes key firmware components. U-Boot and Arm Trusted Firmware (ATF) have been updated across multiple boards, enhancing the reliability of the boot process. These low-level improvements are essential to delivering a smooth and consistent user experience especially when supporting the wide variety of SBC hardware in the Armbian ecosystem. Board Support One of the most exciting aspects of any Armbian release is its growing hardware support and v25.8.1 is no exception. This release introduces new Platinum-supported boards, including the Mekotronics R58 HD and NanoPi R3S LTS, alongside several community-supported targets such as the CAINIAO CNIoT-CORE, KickPi K2B, Radxa Cubie A5E, Banana Pi R4, and Orange Pi 5 Pro. These additions highlight Armbian’s ability to keep pace with the fast-moving SBC market, while also reflecting the collaborative contributions of its community. Beyond new hardware, the release delivers important fixes and driver updates across existing platforms. Thermal sensors are now enabled on the Rock-5C, audio functionality has been restored on the RockPi-S, and the Wake-on-LAN service has been fixed on the Helios4. Driver support has been bolstered with new additions for the Realtek RTL8822CS and Innosilicon USB3 PHY, a touchscreen driver for the NanoPi M6 in mainline kernel, and key fixes for DSI displays on the Raspberry Pi 5. Together, these improvements strengthen Armbian’s position as a practical and versatile platform for everything from DIY smart home setups to demanding industrial applications. Userspace, Framework, armbian-config This release also brings a set of userspace, build framework, and configuration utility improvements. A key milestone is the official addition of Debian Trixie as a supported release, with this cycle focused on ensuring Trixie images are ready and stable. At the same time, a minimal Debian Bookworm image is kept for each target to maintain compatibility where needed. Other highlights include package adjustments on Trixie, correcting login screen alignment, updating the boot logo, and ensuring signing key management by keeping a symlink to the old location for compatibility. The build framework was also extended with support for the new loong64 architecture. The configuration framework (armbian-config) has also seen major updates. Networking features were expanded with improved WireGuard support, covering both client setups and LAN routing, while Pi-hole integration was improved with Unbound, and general bugfixes. Overlay management was made more reliable, and Docker installations became more robust. Continuous integration and testing were strengthened with better duplicate module detection and automated container cleanup, ensuring smoother development workflows. New functionality was added as well, including Cockpit support with KVM integration, and new modules such as Ghost CMS. Full changelogSee the full list of changes. Community ContributionsThanks to everyone who contributed to this release, including: @igorpecovnik @pyavitz @FantasyGmm @HeyMeco @leggewie @rafayahmed317 @EvilOlaf @vascoguita @chainsx @schmiedelm @amazingfate @jclds139 @juanesf @gbrdead @belegdol @c127dev @paolosabatino @efectn @retro98boy @mdziekon @SuperKali @Ayush1325 @ZjemCiKolege View the full article

A common and effective way to use multiple kernels on a single-board computer (SBC) running Armbian is to use separate SD cards. This approach is especially useful for testing new kernels, experimenting with different kernel versions, or even trying out other Linux distributions all without risking your main, stable system. Since most SBCs prioritize booting from an SD card, this method keeps things simple and reliable. In this tutorial, we’ll walk through how to set up multiple SD cards with different Armbian kernels. PrerequisitesBefore getting started, make sure you have: Your SBC - e.g., Orange Pi, Rock Pi, Odroid, or another supported board.Multiple SD cards - one per kernel/system. Choose reliable, high-speed cards from a reputable brand to minimize boot problems.A computer to write images to the SD cards.A stable power supply for your SBC.Armbian images - downloaded for your board, each with the desired kernel (e.g., current, edge, or legacy). You can grab these from the official Armbian download page.Step 1: prepare the SD cards Each SD card will be flashed with a different Armbian image. Download imagesHead to the Armbian download page and find images for your SBC model. For example, download one with the current kernel and another with the edge kernel. Flash the SD cardsYou can use BalenaEtcher (GUI) or dd (CLI) to flash your cards. Using BalenaEtcher: Insert your SD card into the computer.Open Etcher, select the downloaded Armbian image.Select your SD card as the target.Click Flash!Repeat for each SD card and kernel image.Using dd (Linux/macOS): Unzip the .xz Armbian image file.Identify your SD card device name (lsblk or diskutil list). Example: /dev/sdX.Run: sudo dd if=/path/to/armbian-image.img of=/dev/sdX bs=1M status=progress && syncReplace /path/to/armbian-image.img and /dev/sdX with your actual image and device name. Be careful: choosing the wrong device can overwrite your computer’s storage. Step 2: initial boot and configuration Each flashed SD card is now a standalone system. Insert one card into your SBC and power it on.Armbian will run initial setup: resizing the filesystem and prompting you for a root password and new user.Once done, shut down the SBC safely.Swap to your next SD card and repeat the setup process.Every card remains completely independent, with its own configuration. Step 3: managing multiple kernels Now that you have multiple cards, you can swap between them as needed: Switching kernels: Power off the SBC, swap the SD card, and power it back on. The bootloader handles the rest.Testing and development: Keep a stable, “production” kernel on one card and experimental kernels on others. If something breaks, just pop the stable card back in.Isolation advantage: While armbian-config can switch kernels on one installation, using separate SD cards provides complete isolation. This prevents conflicts and makes troubleshooting far easier.Conclusion Running multiple kernels with Armbian doesn’t require advanced bootloader tweaks or complicated configuration. By simply preparing separate SD cards, you gain flexibility, reliability, and peace of mind while testing new kernels or exploring different setups on your SBC. View the full article

Collabora is heading to Amsterdam with talks, demos, and workshops covering Embedded Linux, KernelCI, Bluetooth & Auracast, mainline video capture for Rockchip, and more. Join us to see our latest open source work in action! View the full article

The Mesa 25.2 release introduces support for AFBC compressed YUV textures in the Panfrost driver for ARM Mali GPUs, enabling more efficient memory bandwidth and power usage in video playback and real-time texture processing. View the full article

Single Board Computers (SBCs) have revolutionized embedded computing, offering powerful capabilities in compact, low-power packages. However, unlike traditional desktops with their readily swappable hard drives, storage on SBCs comes in various forms, each with its own trade-offs in terms of performance, cost, and reliability. Understanding these differences is crucial for any project, from a simple home automation hub to a demanding edge AI device. microSD cards: the ubiquitous entry point For many, the microSD card is the first encounter with SBC storage. Its low cost and universal compatibility with most boards, including the popular Raspberry Pi series, make it an accessible entry point. Installing an operating system like Armbian is as simple as flashing an image to the card. However, microSD cards have significant limitations. They are generally the slowest of the common SBC storage types, with varying read/write speeds depending on the card's class. More critically, they are less resilient to the constant read/write cycles that an operating system demands. This means they can degrade and fail relatively quickly, particularly in applications with frequent logging or database operations. For casual use, a good quality A1 or A2-rated microSD card is often sufficient, but for anything critical or performance-sensitive, alternatives are strongly recommended. eMMC: the embedded workhorse Embedded MultiMediaCard (eMMC) represents a significant step up from microSD cards. Often found soldered directly onto the SBC's board, or available as a module, eMMC storage integrates the flash memory and a dedicated controller into a single chip. This integrated controller handles wear-leveling and error correction, significantly improving both performance and endurance compared to raw microSD cards. eMMC typically offers faster sequential read and write speeds, often comparable to older SATA SSDs. This translates to quicker boot times, snappier application loading, and overall better system responsiveness. Its embedded nature also provides a more robust and physically secure storage solution, making it ideal for industrial or high-reliability applications where vibration or accidental removal are concerns. While more expensive than microSD, the enhanced durability and performance often justify the cost for more demanding projects. NVMe: the speed demon For the ultimate in SBC storage performance, Non-Volatile Memory Express (NVMe) reigns supreme. With the introduction of PCIe interfaces on more advanced SBCs, such as the Raspberry Pi 5, NVMe SSDs have become a game changer. These drives communicate directly with the CPU via the high-speed PCIe bus, bypassing the bottlenecks of traditional storage interfaces. NVMe offers dramatically faster read and write speeds often an order of magnitude or more greater than eMMC or microSD cards. This is critical for applications that involve large data transfers, intensive database operations, or running complex software that constantly accesses storage. Think of a local AI inference server, a high-throughput network-attached storage (NAS) device, or a system requiring rapid boot-up and application launch. While NVMe drives and the necessary adapters (often HATs for Raspberry Pi) add to the overall cost, the performance gains can be transformative for projects where speed is paramount. Choosing the right storage for your SBC project means balancing budget, performance requirements, and reliability needs. While microSD cards offer an easy entry, eMMC provides a more robust and performant solution for general use, and NVMe delivers uncompromised speed for the most demanding applications. Understanding these distinctions ensures your SBC project has the solid foundation it needs to succeed. View the full article