RSS Bot

http://blog.armbian.com/content/images/2025/12/holiday1-1.pngFrom major kernel milestones to expanding our support for the latest ARM and RISC-V hardware, 2025 has been a year of growth and grit for Armbian. As we wrap up the final commits of the year, we’re looking back with gratitude at how far this project has come. The holiday season is our favorite time to reflect on the power of open source - where a global community comes together to make hardware work better for everyone. Thank you for being part of our story this year. Happy Holiday Hacking! Public beta: new Armbian OS image flasher. Clean, simple, open-source tool for flashing Armbian or any other disk image to your single board computer. Download for Linux / Window / MacOS Nanopi R76SThe ultimate travel router and secure hotspot Forget insecure hotel Wi-Fi. The NanoPi R76S, powered by the performance-optimized Armbian OS, is your ticket to a truly secure, high-speed mobile network. This pocket-sized device is built around the powerful Octa-core Rockchip RK3576 SoC and supports up to 16GB of LPDDR5 RAM,http://blog.armbian.com/content/images/icon/favicon-35.icoArmbian blogIgor Pecovnikhttp://blog.armbian.com/content/images/thumbnail/r67-1.jpgSponsored Post Armbian flashing toolWe’ve added a powerful new Image Flashing Tool to Armbian! You can now browse, download, and flash Armbian images directly to your device’s internal storage or boot media - no external tools required. Everything happens seamlessly inside armbian-config, making installation and re-installation faster, safer, and easier than ever.http://blog.armbian.com/content/images/icon/favicon-32.icoArmbian blogIgor Pecovnikhttp://blog.armbian.com/content/images/thumbnail/ChatGPT-Image-Dec-8--2025--11_11_38-PM.pngGithub HighlightsThis week in Armbian development saw significant progress across board support, kernel updates, and codebase improvements. Notable additions include support for the SpacemiT MusePi Pro and Friendlyelec NanoPi Zero2, alongside expanded compatibility for TI AM62x SoC boards. Multiple platforms, such as Rockchip, Meson64, and Sunxi, received kernel bumpst to newhttp://blog.armbian.com/content/images/icon/favicon-34.icoArmbian blogMichael Robinsonhttp://blog.armbian.com/content/images/thumbnail/highligts-2.pngView the full article

The ultimate travel router and secure hotspothttp://blog.armbian.com/content/images/2025/12/r67.jpgForget insecure hotel Wi-Fi. The NanoPi R76S, powered by the performance-optimized Armbian OS, is your ticket to a truly secure, high-speed mobile network. This pocket-sized device is built around the powerful Octa-core Rockchip RK3576 SoC and supports up to 16GB of LPDDR5 RAM, giving it the muscle to handle demanding, encrypted traffic effortlessly. 💡This device is officially supported by Armbian at the Platinum level, providing long-term maintenance, high reliability, and priority software support.Its core hardware is ideal for the road. The dual 2.5GbE Ethernet ports ensure you can maximize the speed of any high-bandwidth wired connection, while the M.2 E-Key slot allows for adding an optional Wi-Fi card to create a high-speed, personalized hotspot. More importantly, the powerful CPU is a VPN champion. With Armbian, setting up an encrypted connection is simple and utilizes the device's full potential. To create a persistent, secure tunnel for all your devices, just launch the terminal and run: sudo armbian-config. Navigate to Software and select the pre-packaged WireGuard install. This single step leverages the RK3576’s processing power for blazing-fast encryption and decryption, eliminating the speed slowdowns common with weaker travel routers. Finally, the USB 3.2 is perfect for attaching a portable SSD, instantly turning R76S into a secure, mobile NAS for backing up your files. This is just one example of usage. It can be served as a compact home or office server, Home Assistant hub, a high-performance network gateway with advanced firewalling and VPN termination, or a lightweight virtualization host for containers. Thanks to its dual 2.5 GbE interfaces, the R76S excels in scenarios where fast, reliable networking is essential. From segmented home labs and development environments to branch-office routing and monitoring. Combined with low power consumption and solid software support, it offers an impressive balance between performance, flexibility, and efficiency in a remarkably small form factor. Hardware specifications SoCRockchip RK3576 CPUOcta-core ARM (4× Cortex-A72 + 4× Cortex-A53) GPUARM Mali-G52 MC3 OpenGL ES 1.1 / 2.0 / 3.2, Vulkan 1.2, OpenCL 2.0 VPU8K@30fps H.265 / VP9 decoder 4K@60fps encoder NPU6 TOPS (INT8) Supports INT4, INT8, INT16, FP16, BF16, TF32 Memory2 GB / 4 GB LPDDR5 Storage32 GB eMMC microSD (UHS-I) Ethernet2 × PCIe-based 2.5 GbE WirelessOptional M.2 SDIO Wi-Fi USB1 × USB 3.2 Gen 1 Type-A HDMI HDMI 1.4 / 2.0 Up to 10-bit Deep Color Up to 1080p@120Hz or 4096×2304@60Hz 3D video support DebugUART (3-pin 2.54 mm, 3.3 V, up to 1.5 Mbps) GPIO1 × 8-pin GPIO connector Indicators3 × GPIO-controlled LEDs (SYS, LED1, LED2) ButtonsPower, User, MASK (eMMC update) RTC2-pin RTC battery connector (HYM8563TS) Power InputUSB-C, 5 V PCB8-layer PCB, 58 × 58 × 1.6 mm Operating Temperature0 °C to 70 °C View the full article

http://blog.armbian.com/content/images/2025/12/highligts-2.pngThis week in Armbian development saw significant progress across board support, kernel updates, and codebase improvements. Notable additions include support for the SpacemiT MusePi Pro and Friendlyelec NanoPi Zero2, alongside expanded compatibility for TI AM62x SoC boards. Multiple platforms, such as Rockchip, Meson64, and Sunxi, received kernel bumpst to new LTS 6.18.y and patch refinements, enhancing stability and hardware support. The team also improved consistency in function naming, streamlined vendor relations, and addressed driver issues for Rockchip64. Workflow enhancements were made to enforce image availability for new boards and reduce review noise. Additionally, legacy UEFI images for WSL2 were removed, and documentation output processes were refined. These updates reflect Armbian’s ongoing commitment to robust hardware support and development efficiency. Add board SpacemiT MusePi Pro and update linux patching. by @pyavitz in armbian/build#9058Add support for Friendlyelec NanoPi Zero2. by @sapphic-kitten in armbian/build#8886adjust function names for the sake of consistency. by @EvilOlaf in armbian/build#9108Board vendors adjustements for generic targets. by @igorpecovnik in armbian/build#9109Bump Rockchip edge to 6.18.y. by @igorpecovnik in armbian/build#9104CodeRabbit review noise reduction. by @igorpecovnik in armbian/build#9074compress-checksum: introduce COMPRESS_OUTPUTIMAGE=zst. by @rpardini in armbian/build#9101DevTree overlays to enable RK3308 UARTS. by @brentr in armbian/build#9072extensions/gen-sample-extension-docs: output Markdown to userpatches/extensions. by @rpardini in armbian/build#9075Fix missing board vendor relations. by @igorpecovnik in armbian/build#9110Fix PR comments for forked submissions. by @igorpecovnik in armbian/build#9089GHA: Enforce board and vendor image availability for newly added boards. by @igorpecovnik in armbian/build#9087meson64: 6.18: drop cacheref S922X fix patch as it landed on 6.18.2. by @rpardini in armbian/build#9100Meson64: linux-6.18.y: Improve 6.18.y support for G12/SM1. by @pyavitz in armbian/build#9070radxa-e24c: enable edge branch by picking from Kwiboo's WiP tree. by @rpardini in armbian/build#9102rockchip64: Fix IEP driver. by @fwolter in armbian/build#9107rpi4b: bump legacy, current and edge to new major version. by @EvilOlaf in armbian/build#9097rpi4b: enable EXTRAWIFI again for edge. by @EvilOlaf in armbian/build#9073sunxi: adjust patch for H616 overlays. by @EvilOlaf in armbian/build#9096sunxi: bump current and edge to latest minor, rewrite patches. by @EvilOlaf in armbian/build#9103sunxi: bump edge to 6.18. by @EvilOlaf in armbian/build#9049sunxi: fix missing dt overlays. by @EvilOlaf in armbian/build#9094TI SK-AM62-SIP Remove Edge Target. by @Grippy98 in armbian/build#9105ti: configs: boards: Add additional AM62x SoC board support. by @jonaswood01 in armbian/build#9081ti: configs: family: k3: Update baseline to 11.02.08. by @jonaswood01 in armbian/build#9091Update odroidxu4-current to 6.6.119. by @belegdol in armbian/build#9037WSL2: Drop UEFI images designed specially for WSL2. by @igorpecovnik in armbian/build#9098View the full article

This week’s Armbian development saw a series of notable updates focused on expanding hardware support and improving system stability. Key highlights include the addition of new board configurations, such as the Radxa E24C and rk3566-box-demo, as well as enhancements to device tree files for improved hardware control. Kernel updates were prominent, with fixes for AV1 and VP9 decoding, expanded support for kernel 6.18, and a rewrite of Rockchip kernel patches. Installation processes were streamlined with the introduction of a direct flashing method, while sound card and display support received targeted improvements. The team also deprecated EFI/Grub in favor of a more robust u-boot flow for Genio devices. Overall, these changes reflect Armbian’s ongoing commitment to broadening compatibility and refining user experience. Add BOARD_VENDOR to board configs. by @igorpecovnik in armbian/build#9063Add Radxa E24C; vendor kernel and vendor u-boot only for now. by @rpardini in armbian/build#9038Add support for rk3566-box-demo. by @andyshrk in armbian/build#9008dts: rockchip: rk3399-fine3399: adjust pwm-fan control strategy. by @Lemon1151 in armbian/build#9036Enable direct flashing method in armbian-install menu. by @igorpecovnik in armbian/build#9022Fixed SOC_RT5651 build. by @iamdrq in armbian/build#9052Genio: Deprecate EFI/Grub in favor of proper uboot flow. by @HeyMeco in armbian/build#9040jethubj200: update JetHub D2 DT file for I2C display and GPIO expande…. by @QwaSeeK in armbian/build#9048lib / rootfs-create: make rm command more robust. by @leggewie in armbian/build#9060nanopct6: Add ALSA sound card configuration. by @SuperKali in armbian/build#9045nanopi-r76s: move patch to board specific folder. by @EvilOlaf in armbian/build#9062qcs6490: VP9 fix backported from mailing list. by @HeyMeco in armbian/build#9055Rock-5B-Plus: Fix Mainline u-boot. by @HeyMeco in armbian/build#9039rockchip-current: rewrite kernel patches. by @EvilOlaf in armbian/build#9054rockchip64-6.18: add patch to fix av1 decoding on rk3588. by @amazingfate in armbian/build#9042rockchip64-edge: enable CONFIG_ROCKCHIP_DW_DP. by @amazingfate in armbian/build#9047rtw88: Add kernel 6.18 support and clean up patch logic. by @SuperKali in armbian/build#9041sunxi-current: bump to latest 6.12.y version. by @EvilOlaf in armbian/build#9053sunxi: bump current to latest minor. by @EvilOlaf in armbian/build#9066Watchdog extension. by @iav in armbian/build#9044View the full article

http://blog.armbian.com/content/images/2025/12/ChatGPT-Image-Dec-8--2025--11_11_38-PM.pngWe’ve added a powerful new Image Flashing Tool to Armbian! You can now browse, download, and flash Armbian images directly to your device’s internal storage or boot media - no external tools required. Everything happens seamlessly inside armbian-config, making installation and re-installation faster, safer, and easier than ever. Key featuresModule pulls data from the official download infrastructure JSON stream and uses simple and robust components to provide a seamless "search & flash" experience. 1. Interactive image browserFinding the right image is now significantly easier. Forget about slow web browsing. The tool includes a robust filtering system that allows users to select images based on: Kernel branch: choose between different kernel branches (legacy, current, edge).Image variant: select specific desktop environments, server or minimal builds.Stability: a specific "stability" filter allows users to toggle production-ready or daily builds.Preinstalled applications: filter for specific software stacks.UX enhancements: Promoted builds: recommended images are highlighted with a star (★).File size: image sizes are clearly displayed in MB.2. Enhanced Safety MeasuresFlashing operating systems always carries a risk of data loss if the wrong drive is selected. This update introduces critical safety checks: System drive protection: The tool automatically hides any disk that contains active system partitions (e.g., /, /boot, or /boot/efi).3. Improved Download ExperienceThe download and flash process has been polished to deliver clearer progress information and a smoother workflow. Automatic fast mirror selection: The tool intelligently selects the fastest available Armbian download mirror to ensure optimal throughput and minimal latency.Accurate progress bars: Leveraging pv (Pipe Viewer), the flashing workflow provides precise, real-time progress indicators for both download and write operations.Graceful fallback: If pv is not available on the system, the tool automatically falls back to curl’s native progress meter, preserving usability without compromising reliability.How to use?New functionality has been added to armbian-config and armbian-install CLI tools. armbian-config --cmd FLASH1View the full article

This week, we spotlight the latest progress surrounding the Armbian 25.11 release. Development continues at a steady pace, with new board enablement work, kernel refinements, and package updates rolling in from contributors across the community. From single-board computers powering homelabs to lightweight systems deployed at the edge, Armbian 25.11 aims to deliver a cleaner, faster, and more reliable experience. If you're upgrading existing installations or preparing images for new hardware, this release ensures that your boards stay efficient, secure, and ready for whatever you build next. v25.11 Improving the base, unlocking new optionsThanks to our amazing community and partners, this release brings mainline U-Boot support to more boards, adds dozens of new devices, and introduces powerful build framework improvements.http://blog.armbian.com/content/images/icon/favicon-29.icoArmbian blogIgor Pecovnikhttp://blog.armbian.com/content/images/thumbnail/release.png SPONSORED http://blog.armbian.com/content/images/2025/10/ChatGPT-Image-Oct-17--2025--07_29_49-AM.png 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. Thermal paste vs. Thermal padsThermal pads are convenient, but thermal paste can drop your SBC’s temperature by 5-8°C under load. Learn why switching to paste creates better heat transfer and prevents throttling, especially during intensive tasks.http://blog.armbian.com/content/images/icon/favicon-30.icoArmbian blogMichael Robinsonhttp://blog.armbian.com/content/images/thumbnail/photo-1569615313731-7407da4f4594How to test a USB-C power supply when your SBC has power issuesPower problems are one of the most common causes of instability, boot failures, or random restarts in single board computers (SBCs). Because many modern boards use USB-C connectors for power, it’s important to verify that your power supply is delivering the correct voltage and current before assuming there’shttp://blog.armbian.com/content/images/icon/favicon-31.icoArmbian blogMichael Robinsonhttp://blog.armbian.com/content/images/thumbnail/photo-1758578070291-0c22ff555df9View the full article

Power problems are one of the most common causes of instability, boot failures, or random restarts in single board computers (SBCs). Because many modern boards use USB-C connectors for power, it’s important to verify that your power supply is delivering the correct voltage and current before assuming there’s a hardware fault. Check the basicsStart by confirming that your USB-C cable and adapter are rated for your board’s requirements. Most SBCs need 5 V at 3 A (15 W). Some boards, like the Orange Pi 5 or Raspberry Pi 5, may negotiate 9 V or 12 V via USB Power Delivery (PD), depending on their design. If you’re using a phone charger or low-power adapter, it may not provide enough current, even if it fits physically. Use a USB power meterA simple USB-C inline power meter is the easiest way to test. Plug the meter between your power supply and SBC, then read the live voltage and current: Voltage should stay close to 5.0 V (or the PD voltage) even under load.Current draw will vary, but if it exceeds your adapter’s rating, the voltage may drop and cause instability. If you see voltage dropping below 4.8 V, your cable or power brick is likely under performing.Test with a known good supplyIf possible, test the board with a different high-quality USB-C PD charger or a dedicated SBC power adapter. Avoid cheap generic units some fail to maintain stable output when current spikes during CPU or GPU activity. Check for cable quality issuesUSB-C cables vary widely in thickness and resistance. A thin or data-only cable can limit current flow. Look for cables rated for 3 A or 5 A charging. Measure with a multimeter (optional)For a deeper check, you can measure voltage directly at the SBC’s power input pads or test points using a multimeter. This reveals if voltage drops occur between the connector and the board. Monitor behavior under loadBoot your SBC and run a stress test (for example, stress-ng or sbc-bench). Watch for throttling, reboots, or USB devices disconnecting signs that the power source can’t keep up. Bottom line: A stable USB-C power supply should maintain consistent voltage under load, use a properly rated cable, and meet your SBC’s full current requirements. Testing with a meter or swapping components systematically can quickly reveal whether power, not the board, is the real culprit. View the full article

Keep your SBC running cool and fastHeat is the enemy of performance. When your SBC gets too hot, it automatically slows down to prevent damage through thermal throttling. While most heatsinks come with pre-applied thermal pads for convenience, switching to quality thermal paste can significantly improve cooling and keep your board running at full speed. Why what's between your chip and heatsink mattersBoth thermal paste and thermal pads serve the same purpose: filling microscopic air gaps between your chip and heatsink. Air is one of the worst heat conductors, so eliminating these gaps is crucial for efficient cooling. Thermal paste wins because it's thinner and conforms better: Perfect conformity: Paste spreads thin under pressure, filling every microscopic imperfection and scratch on both surfacesMinimal thickness: Thermal pads are solid sheets (0.5mm-3mm thick), while paste creates an ultra-thin layer with much lower thermal resistanceReal-world results: Switching from pad to paste can drop temperatures by 5-8°C under load often the difference between throttling and full performanceWhen pads make senseThermal pads aren't bad they're just optimized for different priorities: Easy installation: Peel-and-stick application with no mess or skill requiredManufacturing friendly: Fast assembly for mass productionElectrical safety: Most pads are non-conductive, protecting against accidental shorts if the heatsink shiftsReliable out of the box: No risk of improper application or pump-outPads work well for low-power components like VRMs or memory chips, but your main SoC generates the most heat and benefits most from paste's superior heat transfer. The bottom lineIf you're running intensive tasks, media servers, or pushing your SBC hard, quality thermal paste is worth the upgrade. It creates a near-perfect thermal connection that keeps your chip cooler, reduces throttling, and maintains peak performance. Just make sure to use non-conductive paste to avoid any risk of shorts on your board. View the full article

A more reliable release process - made togetherhttp://blog.armbian.com/content/images/2025/11/release.png Each release cycle brings us closer to a smoother, more predictable, and more professional workflow—and this cycle was no exception. Our release process continues to evolve with better tooling, clearer procedures, and an increasing ability to deliver consistent results across a rapidly expanding and diverse hardware ecosystem. Despite having a significant amount of automated testing in place, the most reliable testing remains manual testing. Every image in this release was manually validated for basic functionality. This is a massive undertaking that requires time, discipline, access to hardware, and many helping hands. Our long-term hope is to one day achieve full test automation, with a dedicated test farm performing these checks end-to-end. But building and maintaining such a system is still beyond our current resources. For now, Armbian relies on the goodwill of volunteers, contributors, and donors who believe in what we are doing. One of the most inspiring aspects of Armbian is the community itself—a remarkable mix of long-term team members, returning contributors, and unexpected heroes who appear out of nowhere to fix something crucial, test an obscure board, or improve parts of the codebase or documentation. This blend of sustained commitment and spontaneous support is one of our greatest strengths. And finally, I cannot express enough gratitude to our partners, whose support keeps the project moving forward. Khadas, Mekotronics, Texas Instruments, SinoVoip (Banana Pi), Inovato, Radxa, FriendlyElec, FUTO, netcup, JetHome, Libre Computer, Toolcraft, Maximum Settings, AtomoNetworks—along with several smaller partners and many individual donors—all play an essential role. Their contributions, whether hardware, infrastructure, engineering, or financial, enable us to continue improving the ecosystem, expanding hardware support, and keeping Armbian accessible to everyone. Igor Project Manager Changes overview This release advances Armbian on three fronts: more boards now run on mainline-based firmware with BTRFS boot support; hardware coverage has grown significantly across multiple vendors; and the build framework has been upgraded with mmdebstrap, the lowmem extension, first-boot configuration injection, improved release logging, and more robust keyring and mirror handling. Destination mainline In our continued push toward mainline kernel support across our board portfolio, this release marks a significant milestone: the progressive retirement of vendor-specific boot loaders on several boards. This strategic shift moves away from proprietary, heavily patched boot loaders toward cleaner and modern solutions. By embracing and contributing to mainline U-Boot and kernel efforts, Armbian ensures greater long-term stability, security, and easier maintenance for our users, paving the way for a more unified and future-proof embedded ecosystem. Incoming Hardware Texas Instruments: AM62P Starter Kit, AM62L EVM (TMDS62LEVM) FriendlyElec: NanoPi R76S, NanoPi M5 Radxa: Radxa ROCK 4D, Radxa CM4 IO Board, Radxa E54C, Radxa Dragon Q6A ArmSoM: ArmSoM Forge1 SinoVoip (Banana Pi): Banana Pi M5 Pro Mekotronics: Mekotronics R58 HD, Mekotronics R58-4X4 XpressReal: XpressReal T3 9Tripod: 9Tripod X3568 v4 LuckFox: Pico Mini (RV1103), Lyra Plus, Lyra Ultra W, Lyra Zero W, Pico Pro (RV1106), Pico Max (RV1106) Hardkernel: ODROID M1S Note: This list includes boards across all support tiers; officially supported, standard, and Community Supported (CSC). Support level varies by vendor and device maturity. Software, framework, and user space On the user-facing side, we’ve added support for Debian Forky, Ubuntu 25.10, and Ubuntu 26.04 as Community Supported targets. The build framework has also received several important enhancements. We introduced mmdebstrap across the build pipeline, enabling faster and more reliable rootfs generation. A major kernel config rewrite automation now keeps the configs in good shape with fewer conflicts, while splitting the kernel build and install steps improves caching and reduces overall build time. Our GitHub infrastructure gained a new release-log generator covering the entire Armbian organization. We also added the lowmem extension to better support systems with under 256MB RAM and introduced user-provided first-boot configuration injection directly at build time. To improve traceability, a new inventory-artifacts CLI was added, and overall build reliability was increased through more resilient keyring and mirror fetching routines. For a complete list of changes and technical details, visit our Github. A heartfelt thanks! This release wouldn’t be possible without the tireless efforts of our dedicated contributors - the developers, testers, and community members who share their expertise and passion. Every line of code, every bug report, and every helpful comment moves Armbian forward - and strengthens the entire single-board computer ecosystem. We also extend our deepest gratitude to our sponsors and donors. Your financial support is crucial, it directly enables us to cover infrastructure costs, acquire new hardware for testing, and sustain the project’s continued growth. Your contributions make all of this possible. View the full article

Collabora will be at Embedded Software Engineering Kongress! Catch our talk as we share our expertise in training large open source models. View the full article

LE Audio introduces a modern, low-power, low-latency Bluetooth® audio architecture that overcomes the limitations of classic Bluetooth® profiles. Get a detailed look at its features, how its supported on Linux, and what lies ahead. View the full article

The Tyr prototype has now progressed from basic GPU job execution to running GNOME, Weston, and full-screen 3D games like SuperTuxKart, demonstrating a functional, high-performance Rust driver that matches C-driver performance! View the full article

Collabora’s long-term leadership in KernelCI has delivered a completely revamped architecture, new tooling, stronger infrastructure, and deeper integrations—modernizing the entire ecosystem and enabling reliable, scalable upstream kernel testing. View the full article

Armbian Weekly Highlights: Enhanced Compatibility and Toolinghttp://blog.armbian.com/content/images/2025/11/githubhighlights-2.png This week in Armbian development saw a range of significant updates and improvements across the project, focusing heavily on expanding hardware support and refining the build framework. Major Highlights The Armbian ecosystem saw significant expansion into the emerging micro-compute camera space, notably adding support for new Rockchip RV110x variants, alongside major U-Boot version bumps and the introduction of a dedicated low-memory build architecture. New Low-Memory Build Extension: Introduced the LowMem extension to optimize builds specifically for boards with less than 256MB of RAM.LowMem extension (for boards with < 256MB RAM) (#8839)RV1106: Limit udev children to prevent early OOM (#8915)LowMem: Slim down initramfs and set /run size (#8904)Expanded Rockchip RV110x/RV3506 Support: Added initial support for the new Rockchip visual processing chip family and several specific boards built around them.family: rockchip: add rv1103/rv1106 + first board 'LuckFox Pico Mini' (#8797)rockchip: Add CSC board Luckfox Lyra Plus + adjust RK3506 BOOT_SOC (#8841)rockchip: Add CSC board Luckfox Lyra Ultra W (RK3506B) (#8862)rockchip: Add CSC board Luckfox Pico Pro / Pico Max (RV1106) (#8893)Kernel Update: Bumped the mainline edge kernel version to 6.18-rc5.bump mainline edge to rc5 (#8908)New FeaturesNew hardware support and key functional additions have been merged across the project. New Board SupportAdd support for Hardkernel ODROID M1S (#8846)add new board radxa-e54c (#8849)rockchip: add 9tripod x3568 v4 support (#8823)Radxa Zero 3W: Add ext antenna overlay (#8894)rockchip64: add rk3318-box overlay for T98_RK3318 boards (#8848)BTRFS IntegrationBTRFS: move btrfs support packages from additional to main package list (#8888)odroidm1: u-boot: bump to 2025.10; enable BTRFS support (#8857)odroidhc4: u-boot: bump to v2025.10; enable BTRFS support (#8880)nanopct6(-lts): u-boot: enable BTRFS support (#8856)Networking & Modulesadd Debian Forky as CSC target (#8814)Enable AX25 Kernel Modules (#8882)Enable ath12k module for edge kernel configs (#8812)Security & Storageadd CRYPTROOT_AUTOUNLOCK option and fix CRYPTROOT for uefi builds (#8805)Bug FixesSeveral user-facing and deep-level build fixes were introduced, improving stability and usability. Armbian install progress bar wasn't working for awhile (#8900)fix(armbian-firstlogin): Enable wlan dhcp by default (#8809)IMX8: fix ATF build error (again) (#8843)Revitalize Espressobin - fix atf compilation bug, bump kernels (#8873)config: kernel: linux-sunxi-*: Set CONFIG_PWRSEQ_EMMC=y (Fixes eMMC power sequencing) (#8877)meson64/edge(6.18): .config: recover EXT4 manually (#8868)meson64-6.18: temporary patch for pcie vs aspm woes on Amlogic (#8867)station-p2: fix pcie (#8819)extensions/image-output-utm: fix serial console ttyAMA0 for arm64 (#8851)ImprovementsFramework and board maintenance focused on optimization, reliability, and modernizing U-Boot adoption. Build System & FrameworkKernel config rewrite: use our strong servers for matrix generation (Significantly faster config processing) (#8859)Implement option to skip certain kernel configs that don't want to play along (#8896)Improve first login for automated builds (#8899)framework mmdebstrap, fetch_distro_keyring - use cached keyring pkgs from armbian.github.io (#8881)U-Boot & FirmwareMultiple boards bumped to U-Boot v2025.10 final, enhancing stability and feature sets.qemu-uboot-{x86|arm64}: bump u-boot to v2025.10 final (#8801)cm3588-nas: bump u-boot to v2025.10 final (#8799)RPI: Increase UEFISIZE from 256 MiB to 512 MiB (#8842)uboot: uboot-config now prints diff with pre-menuconfig defconfig (#8855)nanopi-m6: add support for mainline uboot (#8793)khadas-edge2: add support for mainline uboot (#8796)Board Maintenanceyouyeetoo-r1: Add custom ALSA state configuration (#8818)rockchip: x3568 v4: sync changes from mainline and fixes phy leds (#8887)Community ContributionsThank you to all contributors who submitted pull requests this cycle! @igorpecovnik, @vidplace7, @glneo, @EvilOlaf, @HeyMeco, @rpardini, @pyavitz, @tabrisnet, @rbqvq, @F4FXL, @Jookia, @jonaswood01, @kamilsaigol, @paolosabatino, @Jojo-A, @schmiedelm, @chainsx, @SuperKali, @timsurber, @mahdibx, @sylv-io, @belegdol, @sashasimkin, @efectn. Want to dive deeper into the code or contribute? Check out our GitHub repositories! View the full article

Collabora extended the AdobeVFR dataset and trained a FasterViT-2 font recognition model on millions of samples. The result is a state-of-the-art model for fine-grained font identification that can also be used for downstream tasks. View the full article

As a trusted partner of industry leaders like CLAAS, Ag Leader, and CCI, we are delighted to exhibit for the first time at one of the world’s leading agricultural trade fairs, taking place November 9–15. Meet us at the Digital Farm Center in Hall 21! View the full article

This week in Armbian: We're gearing up for the 25.11 release with a code freeze approaching November 20th, while development continues with new board support and kernel updates. We're also exploring the JetHub D1+ as a professional automation solution, understanding safe operating temperatures for SBCs, and highlighting the critical role of SPI flash in modern single board computers. Here's what's new: Armbian 25.11 release is comingArmbian 25.11 code freeze begins November 20th. Maintainers should test boards, resolve critical issues, and join the coordination meeting on November 8th.http://blog.armbian.com/content/images/icon/favicon-25.icoArmbian blogIgor Pecovnikhttp://blog.armbian.com/content/images/thumbnail/photo-1613677135043-a2512fbf49fa SPONSORED http://blog.armbian.com/content/images/2025/11/D1_v3_face_antenna-2-1.png JetHub D1+, a clean alternative to DIY SBC builds for automation! Learn more Github highlightsThis week’s Armbian updates include new board support for Radxa E54C and ODROID M1S, kernel bumps to 6.17 and 6.18, enhanced U-Boot BTRFS support, and critical bug fixes for IMX8 and BPI-R4 builds.http://blog.armbian.com/content/images/icon/favicon-26.icoArmbian blogMichael Robinsonhttp://blog.armbian.com/content/images/thumbnail/githubhighlights-2.pngSafe operating temperatures for Single board computersSBCs operate safely up to 80°C but throttle at 85°C. Keep temperatures under 70°C with heatsinks, airflow, and monitoring for optimal performance and longevity.http://blog.armbian.com/content/images/icon/favicon-28.icoArmbian blogMichael Robinsonhttp://blog.armbian.com/content/images/thumbnail/armbian_safe-operating.pngView the full article

http://blog.armbian.com/content/images/2025/11/armbian_safe-operating.pngSingle Board Computers (SBCs) like the Raspberry Pi, Orange Pi, and Rockchip-based boards pack impressive computing power into compact designs but with that power comes heat. Keeping temperatures within a safe range is critical for performance, stability, and longevity. Most SBCs are designed to operate safely between 0°C and 80°C (32°F to 176°F), though the ideal range depends on the processor and workload. For example, ARM-based chips such as the RK3588 or Broadcom BCM2711 typically idle between 35°C and 50°C, and can safely run under sustained loads up to 70°C-75°C. Once the temperature reaches around 80°C-85°C, many boards begin to throttle, automatically lowering CPU frequency to prevent overheating. Prolonged operation near or above these limits can lead to degraded performance and, over time, shorten component life. To maintain safe temperatures: Provide airflow: Use open cases or add a small fan.Use heatsinks: Aluminum or copper heatsinks on the CPU dramatically reduce peak temps.Monitor regularly: Tools like sbc-bench, glances, or built-in thermal sensors help track heat trends.Avoid enclosed or sunlit areas when running high workloads.In general, keeping your SBC under 70°C during typical use ensures efficient operation and prevents thermal throttling. With proper cooling and monitoring, these small computers can run reliably for years even under heavy workloads. View the full article

http://blog.armbian.com/content/images/2025/11/D1_v3_face_antenna-2.pngBuilding a serious automation system shouldn’t mean spending days wiring SBCs, shields, USB dongles, level shifters and external power protection. JetHub D1+ offers a clean alternative: a compact, integrated, production-ready controller built for smart buildings, industrial automation, energy management, BMS, dispatching, and reliable IoT deployments. This device is developed and manufactured by JetHome and comes ready for the field: no breadboards, no compatibility guessing, no driver hunting. Every interface is engineered, tested, and electrically protected. Software support includes Armbian Linux or Home Assistant OS out of the box. Why JetHub D1+ instead of SBC + modules?Unlike assembled DIY stacks, JetHub D1+ provides: Integrated and tested hardware – Zigbee, RS-485, isolated I/O and relays work out of the box2. Electrical resilience – galvanic isolation, EMI-safe design, stable power deliveryDIN-rail housing – ready for electrical panels and server cabinetsIndustrial interfaces – RS-485 (Modbus), relay outputs, digital I/OReliable software base – Armbian support and update infrastructureSilent 24/7 operation – fanless and stable in long-term deploymentsThis is hardware you can deploy both at home and in production environments without improvisation. Hardware overviewPowered by the Amlogic A113X quad-core Cortex-A53 SoC, JetHub D1+ delivers efficient performance with a stable thermal profile suitable for enclosure-based installations. Specification Details CPU Amlogic A113X, quad-core Cortex-A53 RAM 2 GB DDR4 Storage 32 GB eMMC Wireless Dual-band Wi-Fi + Bluetooth 5.0 (RTL8822CS) Zigbee Zigbee 3.0 module (EFR32MG21) Ethernet 10/100 Mbit/s USB USB 2.0 Mounting DIN-rail Cooling Fanless Power 9–56 V DC Automation interfaces for real projectsJetHub D1+ includes interfaces needed in the real world ready for direct field connection without adapters: Interface Purpose 4 × Digital Inputs (isolated) Sensors, buttons, automation signals 3 × Relay Outputs (5 A / 250 V) Lighting, contactors, low-power loads 2 × isolated RS-485 buses Modbus RTU, PLCs, industrial devices 1-Wire (DS2482) Temperature sensors Internal temperature sensor CPU thermal control Software: Armbian or home Assistant – Your ChoiceJetHub D1+ ships with a preinstalled OS of your choice: ArmbianFull Linux environmentSSH access, Debian ecosystemIdeal for automation gateways, custom servicesDocker, MQTT, Node-RED, Python supportHome assistant OSReady-to-use smart home controllerBuilt-in Zigbee2MQTT compatibilityAdd-ons ecosystemPerfect for automation integratorsBoth are officially supported images from JetHome with regular updates available. Connectivity for modern automationJetHub D1+ provides native Zigbee (no USB dongles required) and can seamlessly combine both wireless and wired field devices in a single automation network: Pair Zigbee sensors and switches nativelyIntegrate RS-485 meters, relays and PLCsCombine Zigbee2MQTT + Modbus + MQTT in one systemRemote control via VPN or SSHMQTT ready gateway functionDocumentation and supportFull documentation is available, including schematics, API interfaces and wiring examples: Technical docs: JetHub D1+ Full Specifications Support community: https://t.me/jethome_iot AvailabilityThe JetHub D1+ is now available for worldwide shipping through JetHome’s official AliExpress store. Order JetHub D1+ on AliExpress https://jethome.aliexpress.com JetHub D1+ is a reliable controller for automation deployments where stability matters more than cable experiments. With Armbian support, tested hardware integration and industrial I/O, it bridges the gap between DIY flexibility and professional-grade engineering. Whether you’re building: Smart home hubs, Industrial monitoring, Energy management systems, IoT gateways, BMS / HVAC automation, Remote telemetry controllers, JetHub D1+ is a strong foundation to build on. View the full article

As the Armbian 25.11 release approaches, development is entering its final phase with emphasis on testing, stabilization, and release coordination. A code freeze will begin on November 20th, limiting merges to critical fixes and release-essential changes only. Following the freeze period, maintainers will have the flexibility to release once standard validation and review processes are complete. Here's an overview of coordination priorities and upcoming milestones. Coordination meetingA brief coordination session will be held before the freeze to ensure alignment: When: Saturday, 8 November 2025, at 16:00 CET / 10:00 EST Where: Release Coordination Event Agenda: Review open blockers and critical prioritiesMaintainer status by boardLabel triage and deferrals to next release (26.02 milestone)Final checklist before freezeRelease tasks and timeline PrioritiesFocus on stability and core functionality: networking, boot reliability, display, and user-space tools.Prioritize platinum and supported boards first; community targets come next.User-space: armbian-firstrun, armbian-install, armbian-configPlanningUse GitHub labels to keep scope realistic: Keep 25.11-labeled items that you can complete before the freeze.Move everything else to the 26.02 milestone.Stay focused and collaborative; each resolved issue brings us closer to a stronger, more polished release.Board maintainer checklistTest your boards using vendor and current kernels, with at least one desktop image recommendedResolve or document any open issues before the freeze.If testing confirms stability, prepare images for final release validation.For support status changes:Promote: .csc → .confDeprecate: .conf → .cscUpdate maintainer info in the board config.Key dates overview MilestoneDateNotesCoordination Meeting8 November 2025Release prep and blocker reviewCode Freeze20 November 2025Only critical fixes merged25.11 ReleaseLate November 2025Release at will after freeze Thank you! Every contribution keeps Armbian improving and moving forward. Let’s make 25.11 another solid, reliable release. View the full article

http://blog.armbian.com/content/images/2025/11/githubhighlights.pngThis week’s Armbian development saw significant progress across multiple fronts, including expanded hardware support and key software enhancements. Notable additions include support for new boards such as the Radxa E54C and Hardkernel ODROID M1S, as well as the integration of Debian Forky as a CSC target. Kernel updates were prominent, with bumps to versions 6.17 and 6.18, alongside improved configuration management for various devices. Bootloader improvements were made, including enhanced BTRFS support and more reliable local version settings in U-Boot. Several bug fixes addressed build errors and kernel configurations, particularly for IMX8 and Filogic/BPI-R4. The release also featured updates to documentation and board maintenance, ensuring smoother development workflows and broader compatibility. add CRYPTROOT_AUTOUNLOCK option and fix CRYPTROOT for uefi builds. by @sashasimkin in armbian/build#8805add Debian Forky as CSC target. by @timsurber in armbian/build#8814add description for .conf. by @EvilOlaf in armbian/build#8847add new board radxa-e54c. by @kamilsaigol in armbian/build#8849Add support for Hardkernel ODROID M1S. by @Jojo-A in armbian/build#8846change from frank-w's tree to just a git-format-patches from his tree. by @tabrisnet in armbian/build#8850filogic/bpi-r4 - fix edge kernel config. by @tabrisnet in armbian/build#8772Ghost: use latest version v6. by @igorpecovnik in armbian/configng#692grub: don't set CLOUD_INIT_CONFIG_LOCATION. by @rpardini in armbian/build#8852IMX8: fix ATF build error (again). by @schmiedelm in armbian/build#8843mainline-kernel: bump 6.18 to 6.18-rc3. by @rpardini in armbian/build#8830Move kernel config changes from board to kernel config. by @igorpecovnik in armbian/build#8858nanopct6(-lts): u-boot: enable BTRFS support. by @rpardini in armbian/build#8856odroidm1: u-boot: bump to 2025.10; enable BTRFS support. by @rpardini in armbian/build#8857rockchip64: add rk3318-box overlay for T98_RK3318 boards. by @paolosabatino in armbian/build#8848rpi maint: bump edge to 6.17.y. by @EvilOlaf in armbian/build#8837rpi4b: bump edge to 6.18. by @EvilOlaf in armbian/build#8845RPI: Increase UEFISIZE from 256 MiB to 512 MiB. by @igorpecovnik in armbian/build#8842thinkpad-x13s: 6.17: .config: NFS_V4_2, ISCSI_TCP, NFSD =m. by @rpardini in armbian/build#8853ti: configs: boards: Update maintainer on board configs. by @jonaswood01 in armbian/build#8838uboot: set CONFIG_LOCALVERSION more reliably on script/config-enabled uboot sources. by @rpardini in armbian/build#8854uboot: uboot-config now prints diff with pre-menuconfig defconfig. by @rpardini in armbian/build#8855View the full article

Collabora has advanced Monado's accessibility by making the OpenXR runtime supported by Google Cardboard and similar mobile VR viewers so that even more can benefit from OpenXR. View the full article

By resolving critical synchronization bugs in Zink’s Vulkan–OpenGL interop, Faith Ekstrand paved the way for Zink+NVK to become the default OpenGL implementation for Nouveau. View the full article

Collabora and MediaTek are advancing upstream Linux support for the latest Genio IoT boards and Chromebook Plus laptops, enabling full hardware functionality, improved security, and broader access to the open source community. View the full article

Collabora is proud to sponsor this year's annual GStreamer conference, taking place in London, UK. Join us as we showcase the latest with machine learning analytics, WirePlumber, and more. View the full article