Active threads

Welcome to the latest Armbian Newsletter: your source for the latest developments, community highlights, and behind-the-scenes updates from the world of open-source ARM and RISC-V computing. The past two months have been particularly active for the embedded ecosystem. At EMBEDDED WORLD 2026, developers, hardware vendors, and open-source communities gathered to showcase the latest innovations shaping the future of embedded computing. In parallel, the Armbian project continues to evolve with new releases, expanded board support, and ongoing improvements to the build framework driven by the contributions of its global community and the growing demand for reliable Linux on ARM and RISC-V platforms. SPONSORED Join us in making open source better! Every donation helps Armbian improve security, performance, and reliability — so everyone can enjoy a solid foundation for their devices. Github HighlightsThis week in Armbian development saw a significant expansion of hardware support, including new board images and compatibility for devices such as the Ariaboard Photonicat 2, SpacemiT MUSE Book, NanoPC T6 Plus, and Mekotronics R58S2. Kernel patches were updated across multiple platforms, notably for Rockchip and Sunxi families, enhancing stabilityArmbian blogMichael RobinsonMy First embedded world and I Already Can’t Wait for the NextI’d been putting this off for years. Every March, I’d read someone else’s embedded world recap, tell myself “next year”, and go back to my terminal. This year I actually went and I’m still processing everything I saw. First things first: the team Before I talk about any stand orArmbian blogDaniele BriguglioArmbian Q1 2026: Technical Milestones and the Road to Embedded WorldThe first quarter of 2026 has been a period of significant technical consolidation for the Armbian project. Driven by the v26.02 (Goa) release cycle, the project has focused on three core pillars: aggressive framework refactoring, the stable rollout of the Linux 6.18 LTS kernel, and the maturation ofArmbian blogMichael RobinsonView the full article

The first quarter of 2026 has been a period of significant technical consolidation for the Armbian project. Driven by the v26.02 (Goa) release cycle, the project has focused on three core pillars: aggressive framework refactoring, the stable rollout of the Linux 6.18 LTS kernel, and the maturation of the Armbian Imager utility. Core Framework RefactoringA primary objective this quarter was the reduction of technical debt within the armbian/build repository. The development team initiated a systematic cleanup to improve build reliability and maintenance. Toolchain Optimization: Through a series of pull requests, including #9218, #9252, and #9256, significant "dead code" was removed from the internal toolchain. This refactoring simplifies the logic required to support a diversifying array of ARM and RISC-V architectures.mmdebstrap Transition: The framework has officially transitioned to mmdebstrap as the exclusive engine for rootfs creation (#9512). By deprecating the legacy debootstrap method, the project ensures faster, more consistent, and reproducible builds across varied host environments.Bash Modernization: Internal build scripts have been transitioned from POSIX to Bash syntax to leverage modern shell features and enhance overall script reliability.Kernel and Hardware IntegrationQ1 marked the broad adoption of the Linux 6.18 LTS kernel series, providing improved driver support and hardware abstraction for tier-1 platforms. Linux 6.18 LTS Rollout: Stable support for the 6.18.y kernel was merged for major families, including meson64, rockchip64, and UEFI targets (#9069, #9086).Hardware Support Expansion:SpacemiT MusePi Pro: Full integration and kernel patching were completed (#9422).Orange Pi RV2: Initial support and nightly build availability were established for this RISC-V target.Radxa Rock 4D & ODROID M2: These boards were elevated to the stable support tier within the 26.02 release.Firmware Updates: U-Boot was bumped to v2026.01 for several platforms. Notably, boot delays on the Orange Pi 5 series were addressed via updated U-Boot candidates (#9450).Ecosystem Tools: Armbian ImagerThe Armbian Imager has transitioned from a utility to a cornerstone of the project’s user experience, with a focus on security and onboarding efficiency. Cross-Platform Security: Code signing was implemented for both macOS and Windows artifacts to reduce installation friction for non-Linux users (imager#87).Performance Improvements: The utility now features optimized image decompression and enhanced device disconnect detection (imager#28).Automated Reporting: A new AI Actions Report workflow (armbian.github.io#165) was implemented to automate development highlights, providing greater transparency into the commit history for the community.Strategic Industry AlignmentThe technical trajectory of Q1 was intentionally aligned with Armbian’s presence at Embedded World 2026 in Nuremberg. By showcasing the framework and Imager as guests of Seeed Studio, the project demonstrated its readiness for industrial-scale deployment. The shift toward mainline kernel and U-Boot support—specifically targeting the retirement of vendor-specific bootloaders—remains a priority for long-term security and professional-grade stability. Contributors & Credits The progress in Q1 2026 is the result of sustained contributions from the Armbian Dev team and the wider community. Detailed changelogs and commit histories are available at github.com/armbian/build. View the full article

I'd been putting this off for years. Every March, I'd read someone else's embedded world recap, tell myself "next year", and go back to my terminal. This year I actually went and I'm still processing everything I saw. First things first: the teamBefore I talk about any stand or chip, I need to tell you what made this trip different from anything I've done before. There were five of us from the Armbian team at the show: Igor, Werner, Meko, amazingfate, and me. Five people. Four countries. Some of us had worked together for years and never met in person. You know how it is in open-source, you collaborate through GitHub, you argue about patches on the mailing list, you review each other's code at odd hours. But you don't always know the face behind the username. Meeting those people for real, shaking their hand, having a coffee together, that's something no pull request can replicate. And honestly, it was worth the trip on its own. The show itself: I wasn't ready for thisArriving at the Nuremberg Messe for the first time is a genuine shock. I knew embedded world was big. I did not know it was this big. Enormous halls, thousands of exhibitors, tens of thousands of attendees. On day one I got genuinely lost between the pavilions spent a solid half hour wandering with no idea where I was. I'm told this is a rite of passage. What surprised me most about the atmosphere is how concrete everything felt. This isn't a conference where people pitch vaporware from behind polished booths. Engineers and developers everywhere, talking about real problems, showing real hardware. You can walk from a giant like Qualcomm to a small team doing something fascinating with a handful of sensors and both conversations feel equally substantive. What we saw on the floorRockchip was a mandatory stop for us, and they didn't disappoint. On their stand: the RK3572 EVB an evaluation board we hadn't seen in person before. Reading specs in a datasheet is one thing. Seeing the board running, understanding its real-world size, its connectors, how it behaves, that's a completely different kind of knowledge. The kind you can only get by showing up. Rockchip Employees (Most left and right) and Jianfeng Liu, Mecid Urganci & Igor PecovnikSeeed Studio had live demos of AI Vision and AI Sound, and the one that genuinely impressed me was their AI camera with a built-in NPU doing real-time object recognition. I'm not talking about laggy, stuttering inference, it was smooth. Fluid. The kind of performance that makes you stop walking and just stare for a minute. Seeing that level of real-time AI running on a compact edge device was one of those moments where the future stops feeling abstract. Seedstudio x Armbian (Maximilian Riedl , Igor Pecovnik, Jianfeng Liu, Daniele Briguglio)Qualcomm brought the Arduino Ventuno Q, and this is where things got interesting and a little funny. meko had already run his benchmarks on the board when amazingfate noticed something: Chromium's hardware acceleration wasn't enabled. So he enabled it. Right there. Directly on the board. In front of the stand staff. The reaction from the Qualcomm team? Complete, genuine astonishment. They didn't see it coming. That's what happens when you bring a group of Armbian developers to a trade show, we don't just look at things, we poke at them. Armbian at the Foundries.io boothCollabora was present at the show, and amazingfate got to meet some of the team. Their kernel and GPU driver work is always relevant to what we do, so that conversation mattered even if I wasn't there for it personally. The moment that hit hardest: Armbian on the BeagleBadgeDuring a meeting with the BeagleBoard.org team inside the show, they showed us their brand new project: the BeagleBadge. Launched right there at embedded world 2026, it won Best in Show in the Wearables category; a Linux-powered wearable badge with a 4.2" ePaper display, dual-core ARM Cortex-A53, Wi-Fi 6, LoRa, and more sensors than I can list here. Built around the Texas Instruments AM62L32, manufactured by Seeed Studio. Impressive hardware. But here's the part that actually stopped me in my tracks: Armbian was running on it. There's an official "Armbian BeagleBadge demo for EW2026" image — Debian Trixie, Linux 6.12 — listed right on the BeagleBoard.org site. Our OS. On a Best-in-Show winning badge. At the world's biggest embedded show. That's not a small thing. That's the community's work showing up exactly where it matters. What embedded world taught me about where this industry is goingThree days of walking, talking, and observing gives you a pretty clear picture of the currents moving through the embedded world right now. Edge AI is not a trend anymore, it's infrastructure. Every major vendor had something running inference locally, without cloud, on modest hardware. This is real, it's shipping, and it's going to reshape what we expect embedded systems to do. Open-source has earned its seat at the table. I half-expected it to be the hobbyist corner of the show. It wasn't. Companies are building on Linux, on open stacks, on ecosystems maintained by communities like ours. That's not charity, it's strategy. And it means the work we do in Armbian matters more than we sometimes give ourselves credit for. The line between prototype and product is razor thin. At most stands you'd see a mix: shipping products, reference designs, things that will exist in six months. That gap is where the interesting information lives; what's coming, which platforms are getting serious investment, which vendors are committed to mainline Linux support. You don't learn that from a datasheet. You learn it by being there. Would I go back?Without a second thought. If you're an Armbian community member who's been putting this off the same way I was stop putting it off. The technical exposure is valuable. The networking is real. And meeting the people you build things with, face to face, is something that doesn't have a substitute. The show runs every year in Nuremberg. I'll be there. See you in 2027. 🇩🇪 View the full article

X98H PRO ------ WIFI AW869A ------ WIFI 6

mirror.aarnet.edu.au is still listed on that page

I know this might get ignored, but honestly, I don’t really mind. I just want to report something I noticed a few days ago, which I initially thought was caused by my previous setup. I was running a Radxa CM5 with a Waveshare CM4 Nano-C board, using an Armbian image for the Rock 5A. This was the only way I could get it working with mainline support. I’m aware this setup is far from standard I’m essentially using the wrong image but that’s because the Radxa CM5 IO board isn’t compatible with the Waveshare Nano board. On top of that, Armbian doesn’t officially support the CM5 RPi-CM4 IO board provided by Radxa (which does work with the Waveshare Nano, but their image is extremely unstable updating it to Trixie bricks the system). The main issue I noticed was with Wi-Fi (using a USB Wi-Fi AC dongle). By default, it’s broken. I managed to restore it using armbian-config and network setup, but even then, the system doesn’t show any Wi-Fi options in Network Manager, despite being connected and working. I didn’t report this earlier because my setup is quite unusual, and I couldn’t be sure if the issue was specific to me. However, today I tested something else. I revived my MSI GS73VR (a 2017 x86 laptop with a GTX 1060) and tried several Linux distributions. I ended up installing Armbian UEFI (the x86 version of Armbian Trixie). As a side note, the Trixie download link on the website is broken—you have to dig through the internal download pages to find it. After installing it on an NVMe drive and completing the setup, everything initially worked fine. But after one reboot, I encountered the same Wi-Fi issue: freezing and inconsistent behavior. This time, I hadn’t used armbian-config or any network tweaks. The system doesn’t properly detect or display Wi-Fi in GNOME settings, even though it is actually connected and working in the background. So this seems to be a broader issue, not just related to my ARM setup. I don’t know exactly what’s wrong with Armbian, but my main criticism has always been Wi-Fi support—especially for USB dongles. It feels poorly maintained and lacks consistency. I was told years ago that mainline support would resolve these issues, but Armbian UEFI on x86 should already be at that stage, shouldn’t it? Something clearly isn’t right here. It’s frustrating because this feels like the last missing piece for an otherwise solid system. Despite my criticism, I’ll admit Armbian has grown on me. On x86, there are better alternatives like Fedora, but on ARM, Armbian is still one of the best options. Anyway, apologies if this is posted in the wrong place. The official channels require logs, and I don’t feel like rebuilding my old broken setup just to gather them. If no logs means no help, then so be it. Maybe I’m the only one experiencing this—but I doubt it. Most people probably just plug in Ethernet and avoid dealing with Wi-Fi altogether. It is what it is.

Hey! i saw you guys advanced a lot in this. I tried to re-solder the wires to see if i could get RX/TX, but no dice.

Hi all, I have an RK3318 TV box (A95X R2_V20). The front panel controller is TM1628. I’m running Armbian 23.11.1 with kernel 6.19.0‑edge‑rockchip64. Problem: tm16xx is not enabled in this kernel (CONFIG_TM16XX_* not set), and there is no rk3318x-config in this image. I tried to locate tm16xx sources in current Armbian kernel trees and mainline, but the driver is missing, so I can’t build it from the local headers. I have active Docker projects (avito-bot) on this box and don’t want to reinstall the system, and previous two reinstalls ended with apt issues, so I’d prefer to avoid a fresh image. Question: Is there a known external tm16xx driver repo (or patch) that can be built as an out‑of‑tree module for RK3318? If yes, could you point me to the source and any required device‑tree overlay/pin mapping for TM1628? I already posted board photos and dtb above (my post is still unanswered), so please refer to that if needed. Thanks!

The flashing guide points to a github repo which mentions only xiaomi but not oneplus. Can I follow that?

I don't know. I don't maintain this board. Perhaps the maintainer knows which is alexl83. I don't know if he has a forums account though. Try via Github

I'm using Ubuntu 24.04 noble armbian distribution, the branch I used for ffmpeg is https://code.ffmpeg.org/Kwiboo/FFmpeg/src/branch/v4l2request-v3 The ffmpeg included in the distribution does not matter, but regardless it is version 6.1.1. The mpv is built against the locally compiled ffmpeg with libplacebo from https://code.videolan.org/videolan/libplacebo.git

After upgrade to 7.0.0-rc6-edge-sunxi64 wlan is shown in interfaces. Gigabit Ethernet does not work yet.

Based on Debian 13 (Trixie), Apertis v2026 delivers updated system libraries, development tools, compilers, and core services, alongside a new default Wayland compositor, a reworked SDK, and smarter packaging pipelines. View the full article

Just a quick update for those who are following this thread, looks like there was a pull request for U-Boot with this fix (2026-02-02): https://github.com/armbian/build/pull/9333 Waiting for the U-Boot update i guess (i'm using `linux-u-boot-odroidm1-edge/sid` currently).

Usual User, the information you linked about Linux 6.19 seems like there's progress for Rockchip. However, is there any indication that Allwinner H618 could get H265/HEVC decoding acceleration working too?

I maintain it and can take a look this week. Just need to find a spare nvme somewhere

duplicate

@m1zfs I am willing to test as i have an m1 odroid with 4GB ram. What do i need to do ? I tried your dkms package installed it and rebooted but system never turned up after reboot.

It seems that the problem with the computer not booting on first boot returned with kernel 6.18.x. I have to restart the computer twice (power cycle) to get it to boot. The computer always started on first boot on Armbian 26.x with kernel 6.12.x, but after updating ArmBin when the 6.18.x kernels were released, the problem returned: OZPI v1 doesn't always start on the first try, and I have to turn it off and on again. Of course, when there's a kernel update, I run amrmbian-install, but that doesn't solve the recurring problem.

This week in Armbian development saw a significant expansion of hardware support, including new board images and compatibility for devices such as the Ariaboard Photonicat 2, SpacemiT MUSE Book, NanoPC T6 Plus, and Mekotronics R58S2. Kernel patches were updated across multiple platforms, notably for Rockchip and Sunxi families, enhancing stability and performance. Several new modules were introduced in the configuration framework, including browser-based code-server, memory management, Docker log viewing, and subscription tracking. Improvements to documentation, security hardening, and code formatting were also implemented. Notable fixes addressed USB, Ethernet, and device-specific issues, while ZFS functionality and tuning interfaces received updates. The release continues Armbian’s commitment to broad hardware support and robust system features. Changesaction: fix typos, update defaults, and harden GPG signing. by @igorpecovnik in armbian/build#9613Add Ariaboard Photonicat 2 support for rockchip64-6.18. by @HackingGate in armbian/build#9535Add container_type field to Uptime Kuma config. by @igorpecovnik in armbian/configng#776Add image and reusable slug for Qidi X-4. by @Shadowrom2020 in armbian/armbian.github.io#262Add Laptop SpacemiT MUSE Book. by @pyavitz in armbian/build#9591Add line breaks to improve .md rendering. by @igorpecovnik in armbian/configng#784Add NanoPC T6 plus image. by @igorpecovnik in armbian/armbian.github.io#266Add radxa-dragon-q6a to nightly release blacklist. by @igorpecovnik in armbian/armbian.github.io#260add recomputer rk3588-devkit support. by @ackPeng in armbian/linux-rockchip#460add rockchip patch for fusb302 to support aw3561. by @ackPeng in armbian/linux-rockchip#456add rockchip zbit mtd spi flash support. by @ackPeng in armbian/linux-rockchip#464Add rtl8710bufw_SMIC.bin for RTL8188GU WiFi USB. by @Shadowrom2020 in armbian/firmware#121add support for imx708 raspberry pi v3 camera. by @ackPeng in armbian/linux-rockchip#457Add trixie and noble to nightly manual targets. by @igorpecovnik in armbian/armbian.github.io#263Add xfce desktop for riscv64 legacy branch in stable builds. by @igorpecovnik in armbian/armbian.github.io#264aic8800-dkms extension. by @Shadowrom2020 in armbian/build#9578arm64: dts: rockchip: add Mekotronics R58S2. by @HeyMeco in armbian/linux-rockchip#461armbian-kernel: improve code documentation and formatting. by @igorpecovnik in armbian/build#9559Board image: Add Mekotronics R58S2. by @igorpecovnik in armbian/armbian.github.io#265Board: Add Mekotronics R58S2. by @HeyMeco in armbian/build#9610Bump geekyeggo/delete-artifact from 5 to 6. by @igorpecovnik in armbian/os#443docs: expand GitHub Actions section with examples and inputs reference. by @igorpecovnik in armbian/documentation#900docs: reorganize ZFS documentation with proper tab formatting. by @igorpecovnik in armbian/configng#779docs: simplify code-server documentation footer. by @igorpecovnik in armbian/configng#792Dozzle: Proper image. by @igorpecovnik in armbian/configng#775families: sm8550: Limit kernel version to 6.18.18. by @kasimling in armbian/build#9604feat: add code-server module for browser-based VS Code. by @igorpecovnik in armbian/configng#790feat: add comprehensive memory management module. by @igorpecovnik in armbian/configng#781feat: add Dozzle Docker log viewer module. by @igorpecovnik in armbian/configng#773feat: add Wallos subscription tracker module. by @igorpecovnik in armbian/configng#785feat: ZFS pool import and scan functionality. by @igorpecovnik in armbian/configng#782Fix Docker image configuration for GitHub Actions. by @igorpecovnik in armbian/docker-armbian-build#12fix: force destroy VMs when graceful shutdown fails. by @igorpecovnik in armbian/configng#793fix: improve kvmtest module security, UI, and add channel selection. by @igorpecovnik in armbian/configng#789fix: resolve mixed indentation in prometheus heredoc. by @igorpecovnik in armbian/configng#794framework artifact-rootfs - remove the last vestige of LEGACY_DEBOOTSTRAP. by @tabrisnet in armbian/build#9599HACK: Enable PCIe switch on RK3399. by @retro98boy in armbian/build#9574KDE Neon: add more packages for touchscreen devices. by @kasimling in armbian/build#9551mkspi: fix devicetree opp voltage settings. by @redrathnure in armbian/build#9603nanopi-zero2: add USB support for RK3528 (current + edge). by @rubycomm in armbian/build#9500OrangePi5Pro: Comprehensive HW Support: YT6801 PCIe-Eth, Codec ES8388 Audio, eFUSE & U-Boot v2025.10. by @c127dev in armbian/build#9600qcom/sc8280xp: sync microsoft blackrock (windows dev kit 2023) latest firmware for mainline kernel. by @rbqvq in armbian/firmware#122Qidi X-6: fix devicetree opp voltage settings. by @Shadowrom2020 in armbian/build#9577refactor: update KVM test images to latest releases. by @igorpecovnik in armbian/configng#783rock-3a: bump uboot to v2026.04-rc4. by @EvilOlaf in armbian/build#9576rockchip-rv1106: Enable (=m) Realtek 8188EU wifi. by @vidplace7 in armbian/build#9607rockchip64-6.18: rewrite kernel patches against 6.18.20. by @EvilOlaf in armbian/build#9587rockchip64: rk3528: fix USB OTG and ethernet for NanoPi Zero2. by @rubycomm in armbian/build#9597sm8550-6.18: Fix TF card IO performance regression. by @kasimling in armbian/build#9546SpacemiT MUSE Book: Fixup SRC_CMDLINE var. by @pyavitz in armbian/build#9612stmmac: Refactor Phytium ethernet patches into modular components. by @igorpecovnik in armbian/build#9585style: simplify markdown formatting in Wallos footer. by @igorpecovnik in armbian/configng#787sunxi-6.18: rewrite kernel patches against 6.18.20. by @EvilOlaf in armbian/build#9611sunxi: drm/gem-dma: Support dedicated DMA device for allocation. by @EvilOlaf in armbian/build#9605sunxi: edge: bump to 7.0. by @EvilOlaf in armbian/build#9549sunxi: Enable device mapper snapshot support. by @frank-f in armbian/build#9590sunxi: fix iommu driver patch to allow compilation. by @EvilOlaf in armbian/build#9592sunxi: fix Unhandled Exception in EL3. and/causing secondary cpus not coming online. by @EvilOlaf in armbian/build#9586sunxi: remove BSP GMAC/EPHY patch that breaks H6 internal EMAC. by @igorpecovnik in armbian/build#9609uefi edge: bump to 7.0. by @EvilOlaf in armbian/build#9547uefi-arm64-6.12: fix stmmac compilation errors. by @igorpecovnik in armbian/build#9596uefi-x86-6.18: rewrite kernel patches against 6.18.20. by @EvilOlaf in armbian/build#9588update seeed studio rk3576 devkit camera and dp overlay. by @ackPeng in armbian/linux-rockchip#463Update some board csc file. by @retro98boy in armbian/build#9573Update ZFS tuning recommendations and remove settings view. by @igorpecovnik in armbian/configng#780ZFS Performance Tuning Interface. by @igorpecovnik in armbian/configng#777[2026.5] - framework rootfs-create: remove LEGACY_DEBOOTSTRAP, use only the upstream mmdebstrap. by @tabrisnet in armbian/build#9512View the full article

@Efe Çetin I am using Orange Pi 5b, and I am not able to use the USB Type-C port or the USB 2.0 on Armbian edge kernel 6.19. The 2 USB 3.0 ports do work properly. Below is the relevant usb related output from dmesg. Any idea on if this is an issue specific to Orangepi 5b? From the dtsi it seems 5 and 5b largely share the common code related to type-c. I am looking forward to being able to use my Type-C hub on this board and in the future have display out. [ 0.000000] Kernel command line: root=UUID=829dfbd2-5b37-4927-a185-af2d592d8118 rootwait rootfstype=ext4 splash plymouth.ignore-serial-consoles console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=b255b69e-8e14-4261-aebc-56249e9516c1 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=256M cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory [ 0.064272] /i2c@fec80000/usb-typec@22/connector: Fixed dependency cycle(s) with /usb@fc000000 [ 0.064928] /i2c@fec80000/usb-typec@22/connector: Fixed dependency cycle(s) with /phy@fed80000 [ 0.064966] /usb@fc000000: Fixed dependency cycle(s) with /phy@fed80000 [ 0.064994] /phy@fed80000: Fixed dependency cycle(s) with /i2c@fec80000/usb-typec@22/connector [ 0.080439] usbcore: registered new interface driver usbfs [ 0.080460] usbcore: registered new interface driver hub [ 0.080476] usbcore: registered new device driver usb [ 0.310308] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.19 [ 0.310319] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.310325] usb usb1: Product: xHCI Host Controller [ 0.310329] usb usb1: Manufacturer: Linux 6.19.10-edge-rockchip64 xhci-hcd [ 0.310334] usb usb1: SerialNumber: xhci-hcd.3.auto [ 0.310885] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 0.310942] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.19 [ 0.310949] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.310953] usb usb2: Product: xHCI Host Controller [ 0.310958] usb usb2: Manufacturer: Linux 6.19.10-edge-rockchip64 xhci-hcd [ 0.310962] usb usb2: SerialNumber: xhci-hcd.3.auto [ 0.311435] usbcore: registered new interface driver usb-storage [ 0.311658] ehci-platform fc880000.usb: EHCI Host Controller [ 0.311672] ehci-platform fc880000.usb: new USB bus registered, assigned bus number 3 [ 0.311678] ohci-platform fc8c0000.usb: Generic Platform OHCI controller [ 0.311725] ohci-platform fc8c0000.usb: new USB bus registered, assigned bus number 4 [ 0.311752] ehci-platform fc880000.usb: irq 60, io mem 0xfc880000 [ 0.311870] ohci-platform fc8c0000.usb: irq 63, io mem 0xfc8c0000 [ 0.311880] ehci-platform fc800000.usb: EHCI Host Controller [ 0.311894] ohci-platform fc840000.usb: Generic Platform OHCI controller [ 0.311914] ehci-platform fc800000.usb: new USB bus registered, assigned bus number 5 [ 0.311933] ohci-platform fc840000.usb: new USB bus registered, assigned bus number 6 [ 0.312063] ehci-platform fc800000.usb: irq 61, io mem 0xfc800000 [ 0.312094] ohci-platform fc840000.usb: irq 62, io mem 0xfc840000 [ 0.315120] /i2c@fec80000/usb-typec@22/connector: Fixed dependency cycle(s) with /phy@fed80000 [ 0.315157] /i2c@fec80000/usb-typec@22/connector: Fixed dependency cycle(s) with /usb@fc000000 [ 0.323135] usbcore: registered new interface driver usbhid [ 0.323139] usbhid: USB HID core driver [ 0.326360] ehci-platform fc880000.usb: USB 2.0 started, EHCI 1.00 [ 0.326663] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.19 [ 0.326682] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.326696] usb usb3: Product: EHCI Host Controller [ 0.326707] usb usb3: Manufacturer: Linux 6.19.10-edge-rockchip64 ehci_hcd [ 0.326719] usb usb3: SerialNumber: fc880000.usb [ 0.338294] ehci-platform fc800000.usb: USB 2.0 started, EHCI 1.00 [ 0.338591] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.19 [ 0.338610] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.338624] usb usb5: Product: EHCI Host Controller [ 0.338636] usb usb5: Manufacturer: Linux 6.19.10-edge-rockchip64 ehci_hcd [ 0.338647] usb usb5: SerialNumber: fc800000.usb [ 0.370528] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.19 [ 0.370551] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.370565] usb usb4: Product: Generic Platform OHCI controller [ 0.370577] usb usb4: Manufacturer: Linux 6.19.10-edge-rockchip64 ohci_hcd [ 0.370588] usb usb4: SerialNumber: fc8c0000.usb [ 0.372081] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.19 [ 0.372093] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.372099] usb usb6: Product: Generic Platform OHCI controller [ 0.372104] usb usb6: Manufacturer: Linux 6.19.10-edge-rockchip64 ohci_hcd [ 0.372108] usb usb6: SerialNumber: fc840000.usb [ 0.586348] usb 5-1: new high-speed USB device number 2 using ehci-platform [ 0.732000] usb 5-1: New USB device found, idVendor=0bda, idProduct=c820, bcdDevice= 2.00 [ 0.732030] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 0.732044] usb 5-1: Product: 802.11ac NIC [ 0.732055] usb 5-1: Manufacturer: Realtek [ 0.732066] usb 5-1: SerialNumber: 123456 [ 0.882361] usb 4-1: new full-speed USB device number 2 using ohci-platform [ 1.101467] usb 4-1: New USB device found, idVendor=08bb, idProduct=2902, bcdDevice= 1.00 [ 1.101498] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.101511] usb 4-1: Product: USB PnP Sound Device [ 1.101523] usb 4-1: Manufacturer: C-Media Electronics Inc. [ 1.108324] input: C-Media Electronics Inc. USB PnP Sound Device as /devices/platform/fc8c0000.usb/usb4/4-1/4-1:1.2/0003:08BB:2902.0001/input/input0 [ 1.163106] hid-generic 0003:08BB:2902.0001: input,hidraw0: USB HID v1.00 Device [C-Media Electronics Inc. USB PnP Sound Device] on usb-fc8c0000.usb-1/input2 [ 6.294737] systemd[1]: Reached target usb-gadget.target - Hardware activated USB gadget. [ 6.609966] usbcore: registered new interface driver btusb [ 6.711216] usbcore: registered new interface driver snd-usb-audio [ 7.100868] usbcore: registered new interface driver rtw88_8821cu A full dmesg is also attached. dmesg.log

@chaitan3 It depends on the games; I have to try around to find what is best. I usually try 1.7.3, 1.10.3, 1.6.1 then 2.x versions.

Kernel 3.4 was the last known version supporting NAND boot. Since its deprecation nearly a decade ago, equivalent NAND support has not been integrated into mainline kernels.

Hi @KV1 looks like you are hitting this issue: https://github.com/MarvellEmbeddedProcessors/A3700-utils-marvell/issues/35 As you can see, Marvell is not very active in these repos. So you have two choices: 1) use older binutils/gcc (probably the easiest option), or 2) fix the issue with the source code. The fixes I'm seeing look simple enough to implement, and I will likely need to include them in the future when/if I update the github runners used to build releases. See also: https://community.arm.com/support-forums/f/compilers-and-libraries-forum/57077/binutils-2-44-and-gcc-15-1-0---dangerous-relocation-unsupported-relocation-error-when-trying-to-build-u-boot https://lists.denx.de/pipermail/u-boot/2025-May/589102.html

Thanks a lot for all responses to my query. I'm afraid I haven't had the time to tinker on this issue long enough to find a solution. However, as I don't need to use Armbian Imager that often. So I can live with those rare cases of starting Windows as admin and running the program as such.