RSS Bot

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

Single board computers running Armbian offer incredible flexibility and power, but like any mini-computer, they can occasionally hit a snag. When your trusty SBC goes quiet or acts erratically, a systematic approach to troubleshooting can save you hours of frustration. Here are some fundamental steps to get your Armbian-powered device back on track. 1. The power supply: often the culpritBefore you dive into complex software diagnostics, always, always check your power supply. Undervoltage is perhaps the most common cause of instability, random reboots, and even failure to boot on SBCs. Avoid cell phone chargers: While many cell phone chargers feature a USB output and provide 5V, they are generally not recommended for powering SBCs. Phone chargers are designed primarily for charging batteries, which have different power draw characteristics. They often lack the stable voltage regulation required by SBCs, especially under fluctuating loads. This can lead to voltage sags, causing instability, corruption of your storage medium, and unreliable operation. Always opt for a dedicated power supply designed for SBCs, or a high-quality regulated power supply that meets or slightly exceeds your board's recommended voltage and amperage.Verify voltage and amperage: While most boards are rated for 5V, in practice, many SBCs actually perform better with a slight overvoltage, typically around 5.1V or 5.2V. This compensates for voltage drops across cables, connectors, and the board's own circuitry. Even official power supplies for popular boards like the Raspberry Pi and Orange Pi often provide this subtle increase. Ensure your power supply meets the current (amperage) requirements specified by your board's manufacturer, as many consumer USB chargers may not deliver sufficient stable current under load.Cable quality: Don't overlook the USB cable itself. Thin or long cables can introduce significant voltage drop, even if your power adapter is robust. Opt for short, thick cables designed for both data and power.LED indicators: Pay attention to any status LEDs on your board. A consistently lit red LED (often indicating power) might be good, but a rapidly blinking or absent one could signal a power issue. Some boards also have green or blue LEDs that indicate activity; if these are absent, it could point to a boot failure.2. The storage medium: a common point of failureAs discussed previously, microSD cards, while convenient, are prone to issues. eMMC and NVMe are more robust, but can still encounter problems. Re-seat the card/drive: For microSD cards, remove and re-insert it firmly. For eMMC modules or NVMe drives, ensure they are properly seated in their respective slots.Test the storage: If you suspect the storage, try flashing the Armbian image to a different, high-quality microSD card (Class 10, A1, or A2 rated is recommended). Tools like H2testw (Windows) or F3 (Linux) can verify the integrity and true capacity of your microSD card, weeding out fakes or faulty units.Re-flash the image: Sometimes, an image write can be corrupted. Re-flashing Armbian to your storage device using a reliable tool like USBImager can resolve boot issues.File system corruption: Abrupt power cuts can corrupt the file system, especially on microSD cards. While Armbian includes some resilience, a deeply corrupted card might prevent booting.3. First boot and initial access: getting connectedIf your board seems to power on but you get no display or remote access, consider these points: Display output (HDMI): While many SBCs come with an HDMI connector, having the port is not a guarantee that it will be immediately or reliably functional. On some boards, especially those with newer System-on-Chips (SoCs), HDMI drivers might still be in active development, or there could be specific kernel or firmware dependencies. If you're encountering display issues, first try a different HDMI cable and a different monitor or TV. If the problem persists, recognize that the HDMI output might not be stable for your specific Armbian build or board revision.Resolution issues: If you can gain access via SSH (see below) or by mounting the SD card on another machine, you might need to manually edit /boot/armbianEnv.txt to force a lower resolution (e.g., hdmimode=1080p) if it's a resolution compatibility problem.Network (SSH/Ethernet/Wi-Fi):Ethernet connection: This is the most reliably verified working method for initial access and troubleshooting on Armbian. Ensure your Ethernet cable is securely plugged in and the port LEDs are active. Check your router's connected devices list for your SBC's assigned IP address.Wi-Fi issues: If using Wi-Fi, ensure your armbian-config settings (accessible via sudo armbian-config if you have serial or keyboard/monitor access) are correct, including SSID and password. Sometimes, Wi-Fi drivers require specific firmware that might not be active, or kernel updates can temporarily break Wi-Fi functionality. It's also worth noting that some Wi-Fi modules may require the armbian-firmware-full package to be installed for proper operation.SSH credentials: For initial SSH access, Armbian typically uses root with password 1234. You'll be prompted to change this on first login. If "Connection Refused" appears, ensure the SSH service is running (it usually is by default). Check for firewall rules on your network or the SBC that might be blocking port 22.4. Advanced debugging: the serial consoleWhen an SBC fails to boot, provides no display output, and isn't accessible over the network, the debug serial console becomes your most powerful diagnostic tool. It offers direct, low-level communication with the board, allowing you to see boot-up messages, kernel errors, and login prompts even when the system is otherwise unresponsive. What you need:A USB-to-TTL serial adapter (e.g., based on FTDI FT232R, CP2104, or CH340 chips). The CP2104 is often preferred as it reliably supports higher baud rates (like 1.5Mbaud for some Rockchip SoCs), while older CP2102 chips might be limited to 115200 baud, which is common for Amlogic and Allwinner. Ensure your adapter is a 3.3V model, as 5V adapters can permanently damage your SBC.Jumper wires to connect the adapter to your SBC.A host computer (Windows, macOS, Linux) with a terminal emulator program.Connecting:Locate the UART (Universal Asynchronous Receiver-Transmitter) pins on your SBC's GPIO header. You'll typically look for Tx (Transmit), Rx (Receive), and GND (Ground) pins.Connect GND on the adapter to GND on the SBC.Connect Tx on the adapter to Rx on the SBC (cross-over connection).Connect Rx on the adapter to Tx on the SBC (cross-over connection).Crucially, do NOT connect the VCC/3.3V/5V pin from the adapter to your SBC unless your SBC explicitly needs it for the UART to function, which is rare. The SBC should be powered by its primary power supply.Accessing the console:Plug the USB-to-TTL adapter into your host computer. Drivers might install automatically or require manual installation.Identify the serial port (e.g., COMx on Windows, /dev/ttyUSBx or /dev/tty.usbserial-xxxx on Linux/macOS).Open your terminal emulator (e.g., PuTTY on Windows, Minicom or screen on Linux/macOS).Configure the serial connection: Baud rate is typically 115200 (for Amlogic, Allwinner) or 1.5Mbaud (1,500,000) for some newer Rockchip boards, 8 data bits, no parity, 1 stop bit (8N1).Power on your SBC. You should immediately start seeing bootloader messages (U-Boot, GRUB) followed by kernel boot messages. This output can pinpoint exactly where the boot process is failing, providing invaluable clues for debugging.5. Software and configuration deep diveIf the basic checks pass, the issue might lie within the Armbian software configuration. Kernel updates: While updates bring improvements, sometimes a new kernel version can introduce regressions for specific hardware. If a problem appeared after an apt upgrade, consider if it was a kernel update. Armbian allows managing kernel versions, though this is an advanced step.armbian-config: This invaluable tool, run via sudo armbian-config, provides a text-based interface to manage many system settings, including networking, boot options, and installing software. It's often your first stop for diagnosing and fixing configuration issues.Log files: When you can gain access (via SSH or serial console), review system logs for clues. Commands like dmesg (kernel messages), journalctl -xe (systemd journal), and logs in /var/log can reveal errors.Troubleshooting an SBC with Armbian often involves a blend of hardware checks and software diagnostics. By systematically ruling out common issues, you can efficiently pinpoint the root cause and get your single board computer project back on track. For further assistance and community support, you can find help on the official Armbian forum and their Discord server. When seeking help, it is always beneficial to include the output of armbianmonitor -u which provides crucial system information to diagnose your issue. View the full article

Hello Armbian community! Here's a summary of the key developments and improvements in the Armbian project from July 20th to July 27th, 2025. HighlightsNew board support for MediaTek Filogic: Added initial community support for the MediaTek Filogic device, specifically the BananaPi R4 Router, expanding Armbian's reach to new and powerful networking hardware.add community support for MediaTek Filogic device (BananaPi R4 Router) (#8407)New featuresSMART AM40: Added PHY LED configuration.SMART AM40: add PHY LED configuration (#8431)Rock-5C: Enabled thermal sensors for the current kernel.rock-5c: Enable thermal sensors for current (#8430)LCKFB-Taishanpi: Updated U-Boot patches and added support for current and edge kernels.lckfb-taishanpi: update u-boot patches, add current&edge kernel support (#8428)Cloud images: Incorporated WireGuard support on the kernel side.cloud-images: add wireguard support kernel side (#8426)Station-M3: Introduced current kernel support and updated U-Boot patches.station-m3: add current kernel, update u-boot patches (#8424)Sunxi64: Enabled additional CONFIG_NET* and CONFIG_PPS_CLIENT_* kernel modules, enhancing network and time synchronization capabilities.Sunxi64: Enable additional CONFIG_NET* modules (#8418)Sunxi64: Enable CONFIG_PPS_CLIENT_* (#8409)Bug fixesRockchip EDGE: Resolved a broken patch affecting Rockchip EDGE kernel builds.Rockchip EDGE: fix broken patch (#8427)Rockchip64 EDGE: fix broken patch (#8414)UWE5622 Driver: Fixed an issue with the uwe5622 patch for kernel v6.16.Fix uwe5622 patch for v6.16 (#8416)First Login: Corrected an issue where password creation failed during first login on Sid.fix firstlogin failed to create password on sid (#8415)Desktop Builds: Removed apt-xapian-index and pavumeter from newer desktop builds to prevent "Failed To Build From Source" (FTBFS) errors.drop apt-xapian-index and pavumeter from newer desktop builds (FTBFS) (#8356)ImprovementsBuild system stability: Implemented more packaging fixes to address FTBFS issues in the CI/CD pipeline.more packaging fixes to address FTBFS in CI/CD pipeline (#8413)Kernel updates:BananaPi BPI-F3: Updated linux-6.6.95 to 6.6.99.BananaPi BPI-F3: Update linux-6.6.95 to 99 (#8411)General kernel bumps: Updated kernels for imx6, mvebu, xu4, and moved wdk2023 to End-Of-Service (EOS).Bump kernels for imx6, mvebu, xu4 and move wdk2023 to eos (#8410)Edge Kernel: Bumped the edge kernel version to 6.16.0-rc7.bump edge to 6.16.0-rc7 (#8406)Wireless drivers: Updated commit hashes for wireless drivers and added deprecation information.Wireless drivers: bump commit hash, add information about deprecation (#8408)Luckfox ROCK3566: Consolidated the configuration for Luckfox ROCK3566.consolidate luckfox rock3566 config. Closes: #8230 (#8404)Build host dependencies: Made the installation of gcc-arm-linux-gnueabi conditional, relaxing host dependencies and optimizing the build process.lib / prepare-host: make installation of gcc-arm-linux-gnueabi conditional (#8401)Qualcomm RB5: Updated Plasma Workspace package definitions for Qualcomm RB5.config: update plasma-workspace packages definition for Qualcomm RB5 (#8357)Community contributionsThank you to all contributors who helped improve Armbian this past week! @retro98boy @mdziekon @chainsx @igorpecovnik @SuperKali @pyavitz @amazingfate @leggewie @EvilOlaf View the full article

This week brings significant kernel updates, security enhancements, and important board-specific improvements. HighlightsKernel 6.16 arrives: A major update to Kernel 6.16 has been rolled out across several platforms, including mainline, UEFI ARM64, and Rockchip edge, bringing the latest features, performance improvements, and bug fixes to a wider range of Armbian devices.Enhanced security for BananaPi BPI-M4-Zero: Kernel Address Space Layout Randomization (KASLR) has been enabled, significantly improving the board’s resilience to memory-based attacks.U-Boot 2025.07 released: Both BananaPi BPI-M4-Zero and Orange Pi 5 Pro received updated U-Boot firmware, improving eMMC support and platform stability.New featuresBPI-M4-Zero: Add KASLR Support and re-enable h616 RTC patches on currentSunxi64: Enable more I2C, IIO, SENSORS and other misc bitsBug fixesFix NanoPi R6S udev network mappingOrangePi 5 Pro: Fix incorrect GRF node name in DTSMinor spelling mistakesImprovementsMainline kernel: Bump to 6.16 releaseUEFI ARM64: Bump to 6.16Rockchip Edge: Updated to kernel 6.16Odroid XU4: Updated to 6.6.100BPI-M4-Zero: Add default overlay for WiFi/BTBPI-M4-Zero: Update DTS and U-Boot to v2025.07OrangePi 5 Pro: U-Boot v2025.07 with eMMC supportAvoid copying id_ecdsa when not neededDebian: Remove obsolete security repo from package listBullseye: Drop non-existent backports repoCommunity contributors@pyavitz @amazingfate @leggewie @gbrdead @igorpecovnik @belegdol @c127dev @paolosabatino @efectn Stay tuned for next week's highlights. Want to contribute? Visit the Armbian GitHub repository and get involved! View the full article

This second post in the Tyr series dives deeper into GPU driver internals by using the Vulkan-based VkCube application to explain how User Mode Drivers (UMDs) and Kernel Mode Drivers (KMDs) work together to execute GPU workloads. View the full article

Starting with Mesa 25.2, NVK will now advertise support for Blackwell (RTX 50xx series) and Kepler (most GT and GTX 600 series, most GTX 700 series, and some GTX 800 series) GPUs. View the full article

The latest Linux kernel brings enhanced MediaTek Platform enablement, Rockchip performance, and more. Collabora contributed to this release with no less than 22 authored contributors! View the full article

PanVK has reached another milestone and will be officially supporting Vulkan 1.4 on V10! We're up-to-date with the latest version and are well caught up for this release. View the full article

Welcome to your weekly dose of Armbian insights. From thermal management to industry trends, here's what the community is talking about this week. GitHub Highlights GitHub highlightsWeekly Armbian development highlights including expanded board support for DshanPi A1, Raspberry Pi kernel updates to 6.16, and build system improvements.Armbian blogMichael RobinsonHands-on ! Self-host your photos with Immich and ArmbianImmich is a sleek, self-hosted alternative to Google Photos offering powerful features like mobile uploads, facial recognition, and full privacy. With Armbian, setting it up on your own device is simple and efficient.Armbian blogInella JoomunTips & tricks Power mattersWhy choosing the correct input voltage and stable power supply is important for your single board computer’s reliability.Armbian blogMichael RobinsonStay coolWhy heatsinks are essential for SBC performance and longevity.Armbian blogMichael RobinsonState of the SBC & embedded computing industry (2025)The SBC and embedded computing market is projected to reach $3.6 billion by 2030, growing at 6-7% annually. ARM systems dominate with 40% market share, while RISC-V emerges as a compelling open-source alternative.Armbian blogMichael RobinsonThat's a wrap for this week's Armbian updates. Keep your boards cool, your power stable, and your projects running smoothly. Sign up for Armbian blog Embedded Linux, Open Source, and the Armbian Community Subscribe Email sent! Check your inbox to complete your signup. No spam. Unsubscribe anytime. View the full article

Single Board Computers (SBCs) like the Orange Pi 5, Radxa Rock 5, and others powered by modern SoCs are more powerful than ever. But that performance comes with a cost heat. Without proper thermal management, these boards can throttle, crash, or suffer long-term damage. Whether you’re running a server, media center, or developer workstation, adding a simple heatsink can dramatically improve stability, performance, and device lifespan. Why heat is a problem for SBCsAll computers generate heat and SBCs are no exception. The CPU, GPU, RAM, and power management chips on an SBC work hard, and as a result, temperatures rise quickly under load. Unlike laptops and desktops, most SBCs lack active cooling. Many ship with no heatsink at all, relying entirely on the board’s surface area and ambient airflow for cooling. This may work fine for light workloads, but during high CPU or GPU use, it simply isn’t enough. When temperatures exceed a safe threshold (typically between 70°C and 95°C, depending on the chip), the system protects itself with thermal throttling automatically reducing CPU frequency to lower heat. In extreme cases, it may reboot or shut down entirely to avoid permanent damage. Thermal throttling: The silent performance killerThrottling is often subtle and can go unnoticed. Tasks may take longer, video playback may stutter, or system responsiveness may drop but without clear warning messages. Typical signs of thermal throttling include: CPU frequencies dropping significantly under loadSluggish performance during intensive tasksGradual degradation in responsiveness over timeThese symptoms are easy to misdiagnose as software issues. But in many cases, they can be resolved simply by cooling the SoC properly and that starts with a heatsink. Real-world example: Orange Pi 5 without a heatsinkConsider the Orange Pi 5 with the RK3588S SoC. Under sustained load, it can reach temperatures over 85°C. Without a heatsink, users commonly report: CPU throttling within 30–60 seconds of full loadUnstable system behavior during multitaskingIdle temperatures in the high 60s to low 70s °C in warm environmentsA basic aluminum heatsink can drop idle temperatures by 15–20°C and reduce load temperatures by 25–30°C. Larger finned models or full heatsink kits keep the board stable even during stress testing. Types of cooling solutionsPassive heatsinks: Made from aluminum or copper, these rely on surface area and ambient airflow to dissipate heat. They’re silent, durable, and usually sufficient for moderate loads.Active cooling (Heatsink + Fan): Adds a small fan to improve airflow across the heatsink. Great for keeping temperatures low under heavy load, but introduces noise and moving parts.Heatsink cases and enclosures: Some cases act as the heatsink themselves, with thermal pads that transfer heat from the SoC to the case. Others feature built-in fans and vents. Avoid sealed plastic enclosures that trap heat.Tips for effective heatsink useUse thermal interface material: A heatsink without thermal paste or a thermal pad is only half effective. Apply a thin, even layer to bridge the gap between the chip and the heatsink.Clean the SoC surface: Remove dust or residue with isopropyl alcohol to ensure good contact.Ensure proper mounting: The heatsink must make tight, flush contact with the chip. Loose or uneven mounting leads to poor cooling.Consider additional components: Some SBCs benefit from heatsinks on RAM, PMICs, or USB controllers especially if your workload is heavy or your board runs 24/7.Choose quality materials: Copper conducts heat better than aluminum, but aluminum is lighter and often sufficient. Large finned designs increase surface area and effectiveness.Why it mattersEffective cooling isn’t just about preventing crashes it preserves performance and extends hardware lifespan. Performance: A cooled CPU can maintain full frequency, giving you faster compile times, smoother video, and more responsive interaction.Stability: Preventing overheating reduces the risk of kernel panics, application errors, and filesystem corruption.Longevity: Prolonged heat exposure shortens the life of electronic components. Keeping things cool helps ensure your SBC runs reliably for years to come.ConclusionIf you’ve invested in a capable SBC, don’t let heat undermine your project. A simple heatsink often costing just a few dollars can unlock the board’s full potential and prevent hours of frustrating troubleshooting. Whether your SBC is headless or running a full desktop environment, thermal management is essential. Keep it cool, and your board will reward you with consistent, stable, and long-lasting performance. View the full article

Greetings, Armbian community! Here's a concise overview of the key developments and improvements merged into our build system this past week. HighlightsExpanded board support: We've added initial support for the DshanPi A1 (RK3576), broadening Armbian's reach to more hardware.Kernel updates: The edge kernel for Raspberry Pi 4B has been updated to 6.16, bringing the latest features and fixes to the platform.Build system robustness: Important adjustments were made to ensure more reliable U-boot source fetching and improved patch application processes.New featuresNew board and variant support:Add support for DshanPi A1 (RK3576) (#8380)Add BPI-M4-Zero to Sunxi64 device tree directory and enable related graphics drivers (#8394)Add current-rt branch support for PocketBeagle 2 (#8371)K3-Beagle series enhancements:Enable M4 remoteproc for linux-k3-beagle-current-rt (#8395)Enable M4 remoteproc for linux-k3-beagle (#8378)Sunxi64 general input support:Enable keyboard support (CONFIG_KEYBOARD_*) (#8387)Add touchscreen and miscellaneous input support (INPUT_TOUCHSCREEN and INPUT_MISC) (#8385)Bug fixesMeson64 Patch Adjustment: Adjusted a broken patch for Meson64 Current kernel configurations. (#8393)U-boot Source Fix: Resolved issues with fetching U-boot sources from the Denx Git repository. (#8402)Sunxi64 RTC Configuration: Updated defconfigs and addressed H616 RTC-related patches. (#8368)ImprovementsKernel version bump:Bump Raspberry Pi family edge kernel to 6.16 (#8390)Configuration refinements:Remove unused kernel configurations for a leaner build (#8392)Update CAN and CPU frequency configurations for Sunxi64 (#8383)Improve UEFI x86 current and edge defconfigs (#8367)Add cloud branch to UEFI arm64 board configuration (#8376)Documentation & aesthetics:Cleaned and updated the build repository README file, including a new logo. (#8391)Added the most recent Armbian logo as the Plymouth boot logo (#8381)Enabled Armbian auto-patching for Sunxi64 configurations (#8394)Community contributors@Ayush1325 @chainsx @EvilOlaf @igorpecovnik @pyavitz @ZjemCiKolege View the full article

Getting into kernel development can be daunting. There are layers upon layers of knowledge to master, but no clear roadmap, especially when it comes to debugging drivers or navigating userspace-kernel issues. View the full article

Immich is a high-performance, self-hosted photo and video backup solution, ideal for individuals and families seeking an alternative to cloud-based services like Google Photos or iCloud. It offers a private, secure space to store, browse, and share memories without sacrificing modern features or user experience. With Armbian, deploying Immich on single-board computers is easy whether you're using a RockPro64, Raspberry Pi, or Odroid running Armbian. What makes Immich stand out?Immich combines a sleek interface with powerful functionality: Automatic mobile uploads for seamless backupFacial recognition and machine learning search to organize contentMulti-user support for families or small teamsA modern web and mobile interface that feels familiar and intuitiveSupport for HEIC, RAW, and other formats photographers appreciateWhy use Armbian?Armbian provides a lightweight, optimized Linux environment for ARM-based boards. It’s stable, community-driven, and ideal for home server projects. Using armbian-config, installing software like Immich becomes a single-step operation. There's no need to manually clone repos, edit .env files, or orchestrate Docker Compose stacks. It's simply: Using armbian-config, installing Immich is as simple as: armbian-config → Software → Immich → Install That’s it. No Compose files, no manual setup. Uninstalling is just as quick. All containers use a centralized data storage path at /armbian, making backup and restore straightforward no need to go through scattered volumes or configs. This simplicity is built-in, so you can focus on your apps, not infrastructure. If you’re looking to break free from cloud dependence and run your own media solution, Immich on Armbian is a project worth exploring. Check the official Armbian guide here: Immich on Armbian View the full article

Choosing the right input voltage and ensuring stable power supply for SBCsWhen working with single board computers (SBCs) like those supported by Armbian, one of the most overlooked but critical factors for performance and system reliability is the power supply. Whether you're running a lightweight server, a development environment, or a complex home automation system, power instability can lead to frustrating and difficult-to-diagnose problems. Understanding the correct input voltage and ensuring a stable power supply is essential for the long-term health of your SBC. Why Power Supply Issues Are So CommonUnlike desktop systems that come with regulated internal power supplies, SBCs rely entirely on external power adapters. These small boards are expected to do a lot run desktop environments, manage network traffic, operate storage devices, or even handle video output and all of it depends on steady power. Many users assume that any 5V adapter or USB-C charger will suffice. This assumption often leads to problems like: Random rebootsFailed bootsUSB peripherals disconnectingSD card corruptionOverheating from inefficient voltage conversionWhat’s worse, these symptoms are often mistaken for software bugs, when in reality, the board is simply not getting the power it needs. The importance of voltage AaccuracyMost SBCs supported by Armbian require a 5V input, but not just any 5V. The tolerance for voltage drop is narrow often less than ±5%. A supply that delivers 4.75V under load may already be too low, especially when additional peripherals draw current. For boards like the Orange Pi 5/5 Plus or Rockchip RK3399-based systems, this becomes more critical. These boards include CPUs that demand bursts of current during processing spikes. If your power supply cannot maintain a solid 5.1–5.2V under load, you’ll start seeing intermittent failures or throttling. Boards that support USB-C PD (Power Delivery) can negotiate for higher voltage levels (e.g., 9V or 12V), but this only works correctly if the power supply and USB-C cable both support PD and follow the standard. If they don't, the board may only receive 5V or nothing at all. Current (Amperage) capacityVoltage is only half the story. You also need enough current (measured in amps, or A). For most SBCs: Lightweight boards (like Orange Pi Zero) require at least 1–2A.Mid-range boards (like Orange Pi 3 LTS, RK3328) should have at least 3A.High-performance boards (RK3588, RK3399, etc.) often need 4–5A, especially under load or when powering peripherals.A common mistake is to use a "fast charger" designed for phones. These may list high amperage (like 3A), but they rely on USB Power Delivery protocols. If the board doesn't negotiate the higher voltage profile, it may default to 5V @ 500mA which is far too low. How to test your power supplyThe best way to confirm your power supply is adequate is by using a multimeter or USB voltage/current meter: Check idle voltage: Connect the power supply to your board. Using a multimeter, probe the 5V and GND pins (or use a USB tester). You should see between 5.1V and 5.25V. Less than 5.0V is a warning sign.Test under load: Stress the CPU (e.g., with stress-ng or compiling software). Watch the voltage. A good supply should not drop below 5.0V. If it does, expect instability.Measure at the board, not the adapter: Long or thin cables can cause voltage drop even if your adapter is good. This is especially true with Micro-USB or low-quality USB-C cables. Always test at the input connector on the board itself.Recommendations for stable powerUse a quality PSU: Avoid generic adapters. Use brands known for clean power delivery (e.g., Mean Well, Anker, official Raspberry Pi or Orange Pi supplies). A 5V/4A supply with a barrel jack or PD support is ideal for high-end SBCs.Prefer barrel jack over Micro-USB: Micro-USB is notorious for unreliable power delivery due to thin connectors and cable resistance.Use short, thick cables: The longer the cable, the more voltage drops across it. Choose 18AWG or thicker cables, especially if using USB.Avoid USB hubs for power: Even powered hubs often introduce noise or underperform when multiple devices draw current.Monitor system logs: Look for undervoltage warnings in dmesg or Armbian’s armbianmonitor output. This is an early sign that your supply may not be sufficient.ConclusionPower issues are one of the leading causes of instability and hardware failure in SBC projects. Armbian users can save countless hours of troubleshooting by investing in a good power setup from the start. Always ensure you're providing the correct input voltage (typically 5.1–5.2V) and enough current (up to 4–5A for high-performance boards). Measure voltage under load, use high-quality adapters and cables, and stay vigilant for undervoltage signs. A stable SBC starts with stable power it’s the foundation of everything else. View the full article

The single-board computer (SBC) and embedded computing market is seeing steady expansion, with a projected valuation of $3.6 billion USD by 2030, growing at a compound annual growth rate (CAGR) of 6–7% ¹². Growth is largely driven by the rising demand for edge computing, IoT, industrial automation, and AI-enabled systems. ARM-based systems dominate the market due to their low power consumption and cost efficiency, accounting for over 40% of deployed SBCs ¹. However, RISC-V is emerging as a compelling open-source alternative, particularly in industrial and academic sectors, while x86 remains important for legacy and high-performance use cases ². Asia-Pacific leads global growth, particularly in China and India, due to smart infrastructure and 5G deployments. Meanwhile, North America remains dominant in terms of revenue share, especially in healthcare, defense, and industrial sectors ³. Key players like Raspberry Pi, Advantech, Kontron, and Hardkernel continue to innovate. Raspberry Pi Ltd., now a public company, reports that over 70% of its 68 million units sold are deployed in industrial or commercial use cases ⁴. View the full article

This past May, we met with the community at the GStreamer Spring Hackfest in Nice, France, and were able to make great strides, including the integration of AI/ML workflows in GStreamer. View the full article

Collabora is proud to sponsor this year's annual Debian conference, taking place in Brest, France. Join us as we showcase the latest with Apertis, discuss Debian running on mobile devices, and more. View the full article

The last year has seen substantial progress on the DRM infrastructure required to write GPU drivers in Rust. Developed in collaboration with Arm and Google, Tyr is a new Rust-based DRM driver targeting CSF-based Arm Mali GPUs. View the full article