https://forum.armbian.com/rss/1-armbian-posts.xml/New postsenMy bad I didn't specify. On Windows. I lost 4h on it. I needed to use dd on a Mac to create a bootable SD card. Arbian Imager didn't help, it killed my Window stuck on storage finding and couldn't be killed. on Mac made a bad job of flashing, didn't even started boot. Btw on Windows, all methods I used (Raspberry Imager, Etcher, Rufus) all made like 50ish small 0 bite partitions and one big unallocated. Somehow it started booting, Armbian logo on, but then it failed.Sat, 18 Apr 2026 12:08:55 +0000The install process is the same from the beginning of the project, you're confused.Sat, 18 Apr 2026 10:59:55 +0000https://paste.armbian.com/hicilanono Works just fineSat, 18 Apr 2026 04:07:41 +0000Hi, Just an update on this issue. Upgraded to kernel-7.0.0-edge-rockchip64-26.2.0-trunk.733, still no audio output on Analog Headphone/Audio Jack.Sat, 18 Apr 2026 03:27:38 +0000Hey there, I try to install Armbian on my Arduino UNO Q (2 GB), but it fails with all three images Armbian_community_26.2.0-trunk.703_Arduino-uno-q_trixie_edge_6.19.0_minimal.tar.xz Armbian_community_26.2.0-trunk.703_Arduino-uno-q_noble_edge_6.19.0_gnome_desktop.tar.xz Armbian_community_26.2.0-trunk.703_Arduino-uno-q_noble_edge_6.19.0_kde-neon_desktop.tar.xz The error message: .\arduino-flasher-cli.exe flash .\Armbian_community_26.2.0-trunk.703_Arduino-uno-q_trixie_edge_6.19.0_minimal.tar.xz WARNING: flashing a new Linux image will erase any existing data that you have on the board. Do you want to proceed and flash .\Armbian_community_26.2.0-trunk.703_Arduino-uno-q_trixie_edge_6.19.0_minimal.tar.xz on the board? (yes/no) yes Unzipping Debian image arduino-images/ arduino-images/disk-sdcard.img.esp arduino-images/disk-sdcard.img.root arduino-images/flash/ arduino-images/flash/imagefv.elf arduino-images/flash/zeros_1sector.bin arduino-images/flash/multi_image.mbn arduino-images/flash/gpt_main0.bin arduino-images/flash/gpt_backup2.bin arduino-images/flash/featenabler.mbn arduino-images/flash/boot.img arduino-images/flash/prog_firehose_ddr.elf arduino-images/flash/tz.mbn arduino-images/flash/xbl.elf arduino-images/flash/rawprogram0.xml arduino-images/flash/gpt_both0.bin arduino-images/flash/gpt_empty0.bin arduino-images/flash/gpt_backup1.bin arduino-images/flash/xbl_feature_config.elf arduino-images/flash/rawprogram0.nouser.xml arduino-images/flash/gpt_main2.bin arduino-images/flash/km4.mbn arduino-images/flash/gpt_backup0.bin arduino-images/flash/zeros_33sectors.bin arduino-images/flash/gpt_main1.bin arduino-images/flash/abl.elf arduino-images/flash/rpm.mbn arduino-images/flash/storsec.mbn arduino-images/flash/devcfg.mbn arduino-images/flash/cdt.bin arduino-images/flash/hyp.mbn arduino-images/flash/qupv3fw.elf arduino-images/flash/patch0.xml arduino-images/flash/uefi_sec.mbn panic: runtime error: index out of range [0] with length 0 goroutine 1 [running]: github.com/arduino/arduino-flasher-cli/internal/updater.Flash({0x7ff7f72e8c08, 0xc0000e9e50}, 0xc000288130, {0xc0000a8060, 0x54}, 0x1?, 0x0, {0x0, 0x0}, 0x0) D:/a/arduino-flasher-cli/arduino-flasher-cli/internal/updater/flasher.go:95 +0x757 github.com/arduino/arduino-flasher-cli/cmd/arduino-flasher-cli/flash.runFlashCommand({0x7ff7f72e8c08, 0xc0000e9e50}, {0xc000288110, 0x1?, 0x1?}, 0x0, 0x0, {0x0, 0x0}) D:/a/arduino-flasher-cli/arduino-flasher-cli/cmd/arduino-flasher-cli/flash/flash.go:117 +0x349 github.com/arduino/arduino-flasher-cli/cmd/arduino-flasher-cli/flash.NewFlashCmd.func1(0xc00002c908, {0xc000288110, 0x1, 0x1}) D:/a/arduino-flasher-cli/arduino-flasher-cli/cmd/arduino-flasher-cli/flash/flash.go:74 +0x94 github.com/spf13/cobra.(*Command).execute(0xc00002c908, {0xc0002880e0, 0x1, 0x1}) C:/Users/runneradmin/go/pkg/mod/github.com/spf13/cobra@v1.9.1/command.go:1019 +0xae7 github.com/spf13/cobra.(*Command).ExecuteC(0xc00002c608) C:/Users/runneradmin/go/pkg/mod/github.com/spf13/cobra@v1.9.1/command.go:1148 +0x465 github.com/spf13/cobra.(*Command).Execute(...) C:/Users/runneradmin/go/pkg/mod/github.com/spf13/cobra@v1.9.1/command.go:1071 github.com/spf13/cobra.(*Command).ExecuteContext(...) C:/Users/runneradmin/go/pkg/mod/github.com/spf13/cobra@v1.9.1/command.go:1064 main.main() D:/a/arduino-flasher-cli/arduino-flasher-cli/cmd/arduino-flasher-cli/main.go:71 +0x3f0 .\arduino-flasher-cli.exe flash latest works as expected, so it seems to be an issue with these images. Or do I use the wrong installation method? The problem is reproducible under Windows 11 and Linux. Installation over Armbian Imager also fails https://paste.armbian.com/fowidugipo https://paste.armbian.com/ogekaqalaqFri, 17 Apr 2026 23:04:12 +0000@usual user can we achieve in browser video hardware acceleration now, and how? I tried many combinations with no success. Any suggestions are highly appreciated!Fri, 17 Apr 2026 21:26:19 +0000Hi, did you find any legacy rk3318 image?Fri, 17 Apr 2026 20:03:59 +0000Yeah, I’ve looked into the patch file. It doesn’t work with latest u-boot at all. It looks for dtb file, whereas latest u-boot includes mostly dtbi files. I think I’ll have to look into slightly newer than 2020.07 u-boot. I’m guessing it would be easier to port that patch.Fri, 17 Apr 2026 19:34:39 +0000Zero 3E, all images, same UUID/initramfs error on boot. Tried different flashing methods, sd cards. All the same fail. Board works with the old Joshua riek dist.Fri, 17 Apr 2026 19:11:28 +0000Thank you very much for your reply, Werner - and indeed for all the tremendous work you do! The drive is listed as an /dev/nvme0n1p1, so I think I did choose the right overlay. Rootfs UUID is correct. I tested SPI/MTD boot with Armbian 26.2.1, rootfs on NVMe. I erased and reflashed the SPI flash manually: ``` shell sudo flash_eraseall /dev/mtd0 sudo dd if=/usr/lib/linux-u-boot-vendor-orangepi5/u-boot-rockchip-spi.bin \ of=/dev/mtdblock0 bs=1M conv=fsync status=progress sync ``` I then verified that the running system was still using /boot from the SD card: ``` shell findmnt /boot ``` which returned: ``` shell /boot /dev/mmcblk1p1[/boot] ``` I mounted the NVMe rootfs and compared /boot on SD vs NVMe: ``` shell sudo mkdir -p /mnt/nvme sudo mount /dev/nvme0n1p1 /mnt/nvme ls -la /boot ls -la /mnt/nvme/boot ``` The NVMe /boot contents were older/stale compared with the SD /boot, so I synchronized them: ``` shell sudo rsync -aHAX --delete /boot/ /mnt/nvme/boot/ sync ``` I then powered the board off completely, removed the SD card, and tested booting from SPI + NVMe again but it still won't boot without the SD card. I watched your video on UART debugging, but unfortunately, my serial cable is too slow, so I'll get one of those you recommend and try again. Thanks again!Fri, 17 Apr 2026 18:58:09 +0000The install process seems to have changed a lot and the automated setup lets you pick mxq specifically, do I still follow the steps in this thread or is the automatic setup good enough now?Fri, 17 Apr 2026 17:27:14 +0000You need to apply the patch to newer sources to build a newer uboot. But the patch will need to be modified (ported) to newer sources as code in uboot changes. That is the whole point of the suggestions I'm this thread. Port the patch to newer uboots and build them to see if newer uboots fix the problem.Fri, 17 Apr 2026 16:55:09 +0000This one. The patch from “/build-u-boot/“ directory. That contains mentioned readme.txt. Tried to build u-boot with that patch and newer binaries of u-boot. It failed though. I’m going to try with older version maybe later. As long as Armbian boots from SD card, I’m fine. Justwas curious about it, when it failed to flash into emmc.Fri, 17 Apr 2026 16:17:40 +0000@tiobily no worries. you can still interrupt u-boot. In u-boot shell you can try calculating crc32 of memory regions to test memory. memtester tool does not seem to be working.Fri, 17 Apr 2026 15:52:46 +0000Please be specific, what patch are you referring to?Fri, 17 Apr 2026 15:47:32 +0000@tiobily https://radxa.com/community Try these forums.Fri, 17 Apr 2026 15:41:05 +0000@qq20739111 thks, official community = github? https://github.com/radxa-docs/docs/ i asked claude to make a summary of my project with npu: We use the vendor's ACUITY toolkit inside a Docker container (ubuntu-npu:v2.0.10.1) to convert ONNX → quantized .nb files. - Pipeline: onnxsim → pegasus_import → pegasus_quantize → pegasus_export, uint8 quantization, deployed to ~/npu_models/ via push.sh. - Runtime: custom npu_server.c (pre-allocated input buffer, no per-call mmap) that the Python app talks to. - Hard lesson #1 — quantization: only pure Conv+BN+ReLU survives uint8. Attention, SE blocks, hard-swish, LayerNorm all collapse to constant outputs. So no MobileNetV3+, no transformers. - Hard lesson #2 — concurrency hang: NPU IRQs get lost when camera ISP DMA runs in parallel (shared memory bus). Fix: suppress GStreamer buffer copies during inference. Never STREAMOFF/ON the sunxi-vin driver — instant kernel crash. - Result: 12 models running (9 NPU + 3 CPU) at ~40ms/inference.Fri, 17 Apr 2026 15:36:00 +0000movedFri, 17 Apr 2026 14:11:30 +0000Hello Armbian Community, I am currently running the following image on my Orange Pi 5 Max: Armbian_community_26.2.0-trunk.668_Orangepi5-max_noble_edge_7.0.0-rc6_kde-neon_desktop Unfortunately, I'm struggling with WiFi and Bluetooth issues: WiFi: No wireless interfaces are detected (no option in network settings). Bluetooth: The service is active, but it cannot scan or find any devices. What I’ve tried so far: Installed armbian-firmware and full-mirror-armbian-firmware. Verified that common wireless tools and relative packages are up to date. Checked rfkill list, but the adapters don't seem to be initialized correctly. I noticed a similar discussion on the DietPi forums regarding the OPi 5 Max Bluetooth (link:DietPi), but I'm unsure if those specific workarounds apply to the current Armbian Edge kernel (7.0-rc6). I understand that maintaining support for newer boards and edge kernels is a huge task. Could anyone point me in the right direction? Are there specific firmware blobs or device tree overlays I need to manually enable for this board? Thank you for your time and for all the hard work on the Armbian project!Fri, 17 Apr 2026 13:34:37 +0000BitNet-style ternary brings LLM inference to ExecuTorch via its Vulkan backend, enabling much smaller, bandwidth-efficient models with portable GPU execution on edge devices. Presented at PyTorch Conference Europe 2026. View the full articleFri, 17 Apr 2026 12:02:28 +0000@tiobily You can post your issue on the official community as long as you haven't done any hardware modifications yourself. By the way, How did you get the NPU running on this board?Fri, 17 Apr 2026 11:27:17 +0000But wifi does not work, although armbian-config sees my wifi network and saves password for it. rk322x-config shows Wifi device: unknown - Device ID: 024c:b723. dmesg: r8723bs: module is from the staging directory, the quality is unknown... r8723bs: unknown parameter 'rtw_enusbss' ignored lsmod shows module as unused: r8723bs 405504 0 Could changing led-confs help?Fri, 17 Apr 2026 11:15:53 +0000Hello, I’ve got the same issue with s905x. After going through this topic, I’ve compiled u-boot with newer sources, and it seems not resolving this at all. There was patch mentioned. Do I use it to compile u-boot (instead of the one provided in the u-boot repo) ?Fri, 17 Apr 2026 08:22:04 +0000@MMGen First, thanks for a great tutorial! I have a question about gpt. I maintain shrink-backup and I use dd to copy "boot sector" and rsync the rest (VERY easily described) But I do not distinguish any difference between if it's mbr or gpt when using dd, I just copy everything before root partition with dd (and a few MiB extra) then format root, rsync, yadayadayada... (not important) So I got curious why you skip the first 64 512b blocks in the dd for gpt? (for others reading, the 512 is because fdisk ALWAYS returns 512b blocks, even though gpt is actually 4k blocks) dd if=$(echo *.img) of=/dev/sda bs=512 skip=64 seek=64 count=32704 Can you explain why? I tried to find something online referencing the first 64 512b blocks of a gpt partition table, but could not find anything. I would really appreciate you educating me, or some links where I can read up on the reason. Thank you!Fri, 17 Apr 2026 02:37:54 +0000@chris178 im using this image ( r5 512 ) with the mem=4g param i tried the nick A image too, same problem. ( i tried the r4, r1, 512 and 4096 ) i didnt tried a different microsd, im going to buy a new one and make a new test maybe i got a faulty board. (im using npu and a lot of cpu, everything running fine) Srry about my poor english, is not my native language 😅Fri, 17 Apr 2026 01:07:21 +0000@tiobily Ram detect and training looks just fine above.... you could interrupt the boot and test memory. what OS image did you use above? I could try it on my device (also 8GB but modded). Did you try different microSD cards? Just tried @Nick A image and u-boot section is very similar. However boot continues with linux kernel at the point your debug stalled.... I can't see much clue as to why you're having that issue from the log above unfortunately... Just tried https://github.com/radxa-build/radxa-a733/releases/download/rsdk-r5/radxa-a733_bullseye_cli_r5.output_512.img.xz on a 8GB moded A7Z and it boot fine and free mem as expected...Thu, 16 Apr 2026 21:20:04 +0000Thanks, I ran from sdcard and these options work on Dolamee D5: overlays=cpu-hs emmc emmc-ddr-ph45 led-conf-defaultThu, 16 Apr 2026 20:44:51 +0000Thu, 16 Apr 2026 20:11:30 +0000Hi Igor, Thank you for your reply. I build an Image for Mekotronics R58V2, but I leaned today we dont have the R58S2 (yet) our current device is the R58s, with a build provided by Mekotronics and the HW decoding works with QT-Multimedia as playback back-end, This is this build: v26.02 rolling for Mekotronics R58S running Armbian Linux 6.1.84-vendor-rk35xx. This device is not yet supported, at least I could not find it here. I will discuss with Mekotronics to get also at least Standard support from Armbian in future. I do have also Mekototronics R58X and R58HD devices we want to use also in ffuture the have better support level here as well. I could not find any Forums related to Mekotronics devices and seams can not open one or add threads to the Rockchip rk35xx section, there loads of OragePi stuff but I could not see that officially you support any of them, anyway I gave up with them cause they are ...lets say below expectations ;-). Please give me a hint. As Iam new here please excuse if you get sometimes strange question, but Iam working with arm boards already for a while. Using CLI is not an option, we actually install LX-Qt together with the application. Thanks for helping!Thu, 16 Apr 2026 15:24:51 +0000Booting from mtd/nvme should just work. Most common problems: - dirty mtd/emmc. vendor/unmatching boot loader can cause issues. - mixup between m.2 sata and actual nvme. Correct overlay/dt must be used - wrong rootfs uuid in armbianEnv.txt after running armbian-install (after done, do not reboot but mount freshly written nvme to a random folder and check if the uuid is correct)Thu, 16 Apr 2026 14:40:24 +0000Hi everyone, I just got an Orange Pi 5 and am experiencing the same issue as the OP. I've since then installed the bootloader on the SD card and the rootfs on the NVME drive. I don't really understand what came out of the discussion here: is it possible to boot from the MTD? Thanks a lot! EVThu, 16 Apr 2026 08:34:14 +0000Gnome (wayland) desktop with kernel 6.18.y Probably this way? apt install mpv mpv --hwdec=auto test.mkv (+) Video --vid=1 (*) (hevc 1920x816 25.000fps) (+) Audio --aid=1 --alang=mul (*) (aac 2ch 48000Hz) AO: [alsa] 48000Hz stereo 2ch float VO: [gpu] 1920x816 yuv420p But something is still missing ... not hw accelerated. Sorry, not an expert here. I am happy when Chromium says it.Thu, 16 Apr 2026 06:23:14 +0000Thu, 16 Apr 2026 03:04:28 +0000Thu, 16 Apr 2026 03:04:28 +0000Waiting for the delivery of the USB-to-TTL converter. My old USB-serial adapter didn' t work.Thu, 16 Apr 2026 00:26:24 +0000Can you post logs of both working and not working boards? If they are exactly the same software, it sounds like a hardware issue. If the HardKernel images works as expected, perhaps you've updated all 3, but not rebooted the working one yet?Wed, 15 Apr 2026 23:38:28 +0000@tiobily Is your a7z factory 8GB or modded out of curiosity (lpddr4 or lpddr5) ? Are you able to connect serial console onto uart0 (pb9, pb10) header pins (3.3V TTL uart adapter) and see right after power is applied to the board the debug of dram detection and training? Debug will show if full 8GB is being detected - once this is confirmed, we can take it from there.Wed, 15 Apr 2026 22:37:58 +0000I got into similar situation and Loader mode is not working now. How did you manage to restore the box? Have you found the correct pins to short? Thank you a lot in advance :)Wed, 15 Apr 2026 21:05:56 +0000@ioncube Were you able to use VPU with Jellyfin?Wed, 15 Apr 2026 19:13:02 +0000If anybody needs a simple way to check text on the web or extract text from online PDFs on low‑spec SBCs, here is surf.py. It’s a tiny Python‑based terminal browser designed for boards like Orange Pi Zero, so you’re not completely blind internet‑wise even without a full browser. Starts with: ./surf.py domain.com Dependencies outside standard library: requests, PyPDF2. surf.pyWed, 15 Apr 2026 16:38:33 +0000Hello, you can only boot from sdcard with that device if you follow the rockchip boot sequence, ie: you have to pack u-boot and trust.img using loaderimage tool from rockchip rkbin repository. That tools decorates the uboot/trust.img binaries with some signature and checksum, then you have to put on specific positions on your sdcard and the miniloader, residing in the emmc, will boot from sdcard once it validates correctly the binaries you supplied. You may take a look to my multitool github project for some reference. I have you same box and it boots on mine. Unfortunately on this particular box, the manufacturer disabled the sdcard boot at SoC/hardware level: this means that the trick to erase the internal flash to boot from sdcard, which worked fine for older SoCs, does not always work with rk3528-based (and probably other rk35xx) boardsWed, 15 Apr 2026 15:56:36 +0000@Igor Thanks for the answer! So you run the latest Armbian to test? https://armbian.com/boards/orangepi5 from here? Which image? Would using the CLI version also work (I don't need a desktop). Can you maybe also verify if HEVC works? (H264 works also quite okay in pure CPU iirc).Wed, 15 Apr 2026 15:47:42 +0000oDroid M2 is now in Standard suuport ! Thanks to the Armbian Team 👍Wed, 15 Apr 2026 14:21:01 +0000Anyone has a working image with GPU / VPU support? In the official Jammy I am using VPU is supported via gstreamer / CEDRA https://github.com/defencedog/orangepi4A/tree/main/GPU_VPUWed, 15 Apr 2026 14:19:25 +0000hello i have ths a7z with 8gb ram. Actualy im using with only 4gb (ok for my application). I can boot only if i set mem=4g. Any workaround for that? i tried all images ive found and no one can boot with 8gb.Wed, 15 Apr 2026 13:01:16 +0000movedWed, 15 Apr 2026 12:48:06 +0000Heads up i dont have pc if the process needs it mainly if there's any other way do let me knowWed, 15 Apr 2026 11:44:33 +0000Hello guys i want to use linux on mx pro tv box from pendrive when i flash armbian image to pendrive and click the secret button on box nothing boots up can any one guide me on this thankyou:)Wed, 15 Apr 2026 11:38:20 +0000moved to tvboxesWed, 15 Apr 2026 11:15:22 +0000Reserved for updates.Wed, 15 Apr 2026 10:31:10 +0000