Active threads

Neither we do full hardware validation. That is only done in military grade software support and this is community open source development Thank you for your input. We don't have much time so in case we don't find a fix in <1h, broken images will be removed. Which is already a good added value. It is interesting that Gnome works and KDE don't. I did several tests on x86 platform and KDE always worked ... But I think we need to be realistic and happy if one desktop works solid.

root@nanopi-m5:~# grep BTRFS /usr/lib/u-boot/nanopi-m5-rk3576_defconfig # CONFIG_CMD_BTRFS is not set # CONFIG_FS_BTRFS is not set So no direct Btrfs rootfs support. It is image Armbian_26.5.1_Nanopi-m5_trixie_current_6.18.33_minimal.img run as container quick test. # gdisk -l Armbian_26.5.1_Nanopi-m5_trixie_current_6.18.33_minimal.img GPT fdisk (gdisk) version 1.0.10 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk armbian.img: 3252224 sectors, 1.6 GiB Sector size (logical): 512 bytes Disk identifier (GUID): 1F37D403-5DE7-4F81-AB22-D9825AE1EFEB Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 2048, last usable sector is 3252190 Partitions will be aligned on 2048-sector boundaries Total free space is 32735 sectors (16.0 MiB) Number Start (sector) End (sector) Size Code Name 1 32768 3250175 1.5 GiB 8305 rootfs There is no 4K sector 'awareness', that is the whole reason I ran this testing; If that is an issue with the M5, I don't own and don't know, but I have encountered quite some issues in Linux in general w.r.t. that, so I would for sure scan armbian-install script to see what is done. Risk with 6.1.115 kernel is that is messes up 512/4k things when Btrfs as kernel 6.7 or later is needed to handle it transparently. Check all yourself, as is long time ago I checked it and I use mostly latest Linux, so kernel > 6.18 currently.

The first iteration of mainline kernel driver support has just been posted. So a kernel build with this patch set applied should give a playground for initial experiments.

moved to off-topic since 3rd party os. and nobody will care about a wall of text written by ai

Hi, I need help with flashing my tv box or installing it on linux. I would also be happy if you could run an armbian or similar minimal system. I would like to run a website on it at home. I already did it for an old venz v10 for a friend and installed armbian on it and he really liked it, but my couldn't install it with a memory card, the on new box 1. System Information Google Android Tv Box - Android 14 Android Version: 14 (Upside Down Cake) API Level: 34 Android Security Patch Level: 2025-01-01 Rooted Device: No Android ID: 5c4aa62950194797 Build ID: rk3528_box_32-userdebug 14 UTT2.241219.001 eng.hxws.20260124.163421 release-keys Codename: REL Fingerprint: google/blueline/blueline:14/UTT2.241219.001/eng.hxws.20260124.163421:userdebug/release-keys ID: UTT2.241219.001 Incremental: eng.hxws.20260124.163421 Java Runtime Version: Android Runtime 0.9 Java Virtual Machine Version: ART 2.1.0 Java Virtual Machine Heap Size: 128 MB Kernel Architecture: armv7l Kernel Version: 6.1.118 (hxws@PowerEdge-R720-8) (Android 10087095, +pgo, +bolt, +lto, -mlgo, based on clang 17.0.2 of r487747c (https://android.googlesource.com/toolchain/llvm-project d9f89f4d16663d5012e5c09495f3b30ece3d2362), LLD 17.0.2) #124 SMP PREEMPT Wed Jan 21 10:25:12 CST 2026 Tags: release-keys Type: userdebug Google Play Services Version: < None > Huawei Mobile Services Version: OpenSSL 1.1.1 (compatible; BoringSSL) OpenSSL Version: 1.2.13 ZLib Version: 1.2.13 2. Hardware and Processor (CPU/Device) Device Type: TV Manufacturer: Google Model: android_tv_box Brand: google Motherboard: RK3528 Device: blueline Hardware: rk30board Platform: rk3528 Product: blueline Processor: RK3528, 4 cores SoC Model: RockChip RK3528 Core Architecture: 4x ARM Cortex-A53 @ 2016 MHz Instruction Set: 64-bit ARMv8-A (32-bit mode) CPU Version: r0p4 CPU Cores: 4 CPU Clock Range: 408 - 2016 MHz CPU Utilization: 5% Scaler Controller: Interactive Supported ABIs: armeabi-v7a, armeabi Supported 32-bit ABIs: armeabi-v7a, armeabi AES/ASIMD/NEON/PMULL/SHA1/SHA2: Supported 3. Memory and Storage (RAM/Storage) Installed RAM: 2 GB Total Memory: 1920 MB Available Memory: 1221 MB Memory Used: 707 MB (36% of 1.9 GB) Total Internal Storage: 11.00 GB Free Internal storage: 10.11 GB Storage usage: 914 MB (8% of 11 GB) 4. Display and GPU (Display) Display: 1920 x 1080 (Full HD, 16:9) Screen resolution: 1920 x 1080 xdpi / ydpi: 320 / 320 dpi GPU manufacturer: ARM GPU renderer: Mali-450 MP Refresh rate: 60 Hz Default orientation: Landscape OpenGL ES version: 2.0 GPU version: OpenGL ES 2.0 OpenGL ES extensions: (List: GL_EXT_debug_marker, GL_OES_texture_npot, GL_OES_vertex_array_object, GL_OES_compressed_ETC1_RGB8_texture, GL_EXT_compressed_ETC1_RGB8_sub_texture, GL_OES_standard_derivatives, GL_OES_EGL_image, GL_OES_depth24, GL_ARM_rgba8, GL_ARM_mali_shader_binary, GL_OES_depth_texture, GL_OES_packed_depth_stencil, GL_EXT_texture_format_BGRA8888, GL_OES_vertex_half_float, GL_EXT_blend_minmax, GL_OES_EGL_image_external, GL_OES_EGL_sync, GL_OES_rgb8_rgba8, GL_EXT_discards_framebuffer, GL_OES_get_program_binary, GL_ARM_mali_program_binary, GL_EXT_shader_texture_lod) 5. Network and Connections (Network/Bluetooth/USB) Network: WiFi Telephony: None Wi-Fi Status: Enabled SSID: BSSID: 02:00:00:00:00:00 Hidden SSID: No IPv4 Address: 192.168.1.35 IPv6 Address: fe80::5ef3:83b1:27d0:574a Signal Strength: -46 dBm (Excellent) Link Speed: 54 Mbps Frequency: 2427 MHz Gateway: 192.168.1.254 Netmask: 255.255.255.0 DNS1: 192.168.1.254 DHCP Lease Time: 24 hours 5 GHz Band: Supported Wi-Fi Aware: Not Supported Wi-Fi Direct: Supported Bluetooth: Enabled Bluetooth Version: 4+ USB Device - Linux 6.1.118 ehci_hcd EHCI Host Controller: (Serial Number: ff100000.usb, ID: 1D6B-0002, Class: 09/00, Speed: 480 Mbps) USB Device - Linux 6.1.118 xhci_hcd xHCI Host Controller: (Serial Number: xhci-hcd.4.auto, ID: 1D6B-0002, Class: 09/00, Speed: 480 Mbps) USB Device - YICHIP Wireless Device 6. Other Data Audio: HDMI 7.1 Codecs: Widevine L3 (SD only) Wireless Debugging: Enabled IP Address and Port: 192.168.1.35:40729 Wi-Fi pairing code: 642947 IP address and port (for pairing): 192.168.1.35:40035 Device features: (List: android.hardware.audio.output, android.hardware.bluetooth, android.hardware.bluetooth_le, android.hardware.camera, android.hardware.camera.any, android.hardware.camera.external, android.hardware.camera.front, android.hardware.cetherandroid.hdware.mi android.hardware.keystore.app_attest_key, android.hardware.location, android.hardware.location.network)

Thank you @Revellion I just did ``` sudo apt-mark unhold armbian-firmware sudo rm -rf /lib/firmware/qcom/sm8550/ayn/ sudo apt update && sudo apt upgrade ``` and it worked fine

I just ran into the same issue on a FriendlyARM RK3588. Wanted to swap it out with FriendlyWRT to turn it into a router, but now only Armbian SD cards boot. Even after a vendor supported 'factory reset' process via USB. While it may not be intended to be a lock down and just due to poor testing/planning/silo effect, this is really uncool and should either be fixed or a better way to back out than having to manually pull pieces out and DD them over..

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. Armbian v26.5.1 delivers another strong round of improvements across the project, focusing on expanded hardware support, desktop and userland refinements, build framework modernization, and infrastructure enhancements. This release introduces new board images and platform updates, improves Ubuntu 26.04 "Resolute" integration, refines Bianbu desktop support, adds firmware and driver updates including AX210 wireless support, and continues ongoing work to strengthen the build system, CI pipelines, and developer tooling. Numerous kernel, bootloader, and device tree updates further improve stability, compatibility, and performance across a wide range of ARM and x86 platforms, reinforcing Armbian's commitment to providing a reliable and flexible Linux distribution for single-board computers, embedded devices, and edge computing deployments. 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. Release Armbian Quarterly digest · armbian/buildThis quarter’s work centers on three priorities: kernel modernization across SoC families, a redesigned desktop subsystem driven by armbian-config, and substantial expansion of board and platform c…GitHubarmbianNative UFS boot lands on the NanoPi M5Armbian’s next release boots the FriendlyElec NanoPi M5 end-to-end from UFS on a mainline U-Boot, with no proprietary recovery image in the loop. It is the first RK3576 board in the catalogue to reach this state, and the integration pattern paves the way for the others. UFS, the storage classArmbian blogDaniele BriguglioWe rewrote how Armbian installs desktops. Here’s what changedA friendlier, faster, snap-free desktop install in armbian-config If you’ve installed a desktop environment with armbian-config over the last few months, you may have noticed things feel different: there’s a tier you can pick, the browser actually works on every arch, uninstall doesn’t take half your system with it, andArmbian blogIgor PecovnikView the full article

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. Armbian v26.5.1 delivers another strong round of improvements across the project, focusing on expanded hardware support, desktop and userland refinements, build framework modernization, and infrastructure enhancements. This release introduces new board images and platform updates, improves Ubuntu 26.04 "Resolute" integration, refines Bianbu desktop support, adds firmware and driver updates including AX210 wireless support, and continues ongoing work to strengthen the build system, CI pipelines, and developer tooling. Numerous kernel, bootloader, and device tree updates further improve stability, compatibility, and performance across a wide range of ARM and x86 platforms, reinforcing Armbian's commitment to providing a reliable and flexible Linux distribution for single-board computers, embedded devices, and edge computing deployments. 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. Release Armbian Quarterly digest · armbian/buildThis quarter’s work centers on three priorities: kernel modernization across SoC families, a redesigned desktop subsystem driven by armbian-config, and substantial expansion of board and platform c…GitHubarmbianNative UFS boot lands on the NanoPi M5Armbian’s next release boots the FriendlyElec NanoPi M5 end-to-end from UFS on a mainline U-Boot, with no proprietary recovery image in the loop. It is the first RK3576 board in the catalogue to reach this state, and the integration pattern paves the way for the others. UFS, the storage classArmbian blogDaniele BriguglioWe rewrote how Armbian installs desktops. Here’s what changedA friendlier, faster, snap-free desktop install in armbian-config If you’ve installed a desktop environment with armbian-config over the last few months, you may have noticed things feel different: there’s a tier you can pick, the browser actually works on every arch, uninstall doesn’t take half your system with it, andArmbian blogIgor PecovnikView the full article

Finally this board works. But it doesn't boot from eMMC onboard when flashing it. I used both dd on the Armbian image (Trixie), or the armbian-config and official download and flash image into eMMC. The error is: U-Boot SPL 2024.10_armbian-2024.10-Sf919-P0490-Hc6a9-V4f26-Bd0d2-R448a (May 11 2026 - 06:14:06 +0000) DRAM: 4096 MiB Trying to boot from MMC2 MMC Device 1 not found spl: could not find mmc device 1. error: -19 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### It seems into the SPL bin file there's no eMMC activation code.

@Marvin-03 You're probably right—it may be worth checking the FPC connection. A timeout usually only occurs when the PCIe/NVMe board is not being detected. I'm currently using an early MCUZone NVMe 2230 HAT. I recently ordered a new Waveshare AIO HAT as well, so once it arrives I'll be able to do some additional testing.

its not 905 its 805x android 7 i am working on same board contact me i can help

My ROCK5B was ordered as a 'blue one' on Aliexpress a year ago; I got a 'green one' and as with included case the price was > 150 euro, it got stuck at customs for quite some time. It was with blank/empty SPI flash and endless boot-loop. That was already known by me, so I had fixed 12V soldered to a male USB-C connector. Same story for ROCK3A, although that one booted most of the time but then while running al sorts of strange errors and or crashes. So I think you have to assume USB-C PD negotiation is not working with the Armbian images you tested. Only the U-Boot starting at sector 64 does matter, rest (Linux) is don't care. If a stable U-Boot or UEFIv1.1 form SPI-flash or SD-card, you have already a very extensive commandline interface or text menu's in the EDK2. But lock up might simply happen because the PSU does not do 65W, instead max 15 W (only up to 3A) and the 5V might drop way too low, just very short dip that is not measurable without good oscilloscope or so. The Radxa image might have a bootloader variant that does do USB-C PD, although I haven't seen proof anywhere that it correctly handles and does operate the FUSB302, but that might simply be because my ROCK3A and ROCK5B came out of the box with empty SPI and for ROCK5B I have ignored Radxa images anyway after the big troubles with ROCK3A, so do not really know what happens with those. So I have no other advice then use fixed higher voltage, formally it is >= 9V according to Radxa wiki/docs AFAIR, but I remember the powertree design actually better than those quick facts and my conclusion was : forget about 5V, use 12V and it was easy decision for me as I use 12V UPS and 3.5inch HDD that also needs 12V anyway.

Armbian 26.2.1 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - 26.2.0~git2605212123.7b286abe336 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.3 42ae8b818 (https://ryanfortner.github.io/box64-debs/) + wine-proton-11.0-beta1-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-11.0-beta1/wine-proton-11.0-beta1-amd64-wow64.tar.xz) + DXVK-stripped v2.7.1 ~40fps@720p Grand Theft Auto IV - The Complete Edition

@sr4armbian Try X98H.

Hi, I can't find an image for my TV box and I was wondering if anyone has one that I could use on the device. Thanks for your help

Great job I don't have time to replicate this, but I would like to see more photos, screenshots, and what you can do with so many SDRs It's perfect to use an older kernel, if you don't need anything from a newer Linux (for example more stable Wifi, and resistive LCDs with Wayland)... In your writeup, you could have included the dmesg or journalctl messages, just prior to the crash. Sometimes, there's a confict between a new or changed kernel module and the module you want to use, and it causes crashes, or not being able to start Linux. Then you deactivate the module that gives you the problem. Which services were disabled with sudo systemctl mask systemd-networkd-wait-online ? It sounds like you never want to start a network service automatically on boot. I hope that the SoapySDR developers can fix the root issue, so that you don't need to lock a library .SO like that I made a thread showing how to control GPIO with Python gpiod https://forum.armbian.com/topic/33800-orange-pi-zero-3-gpio/#findComment-181191 Instead of using Opi.GPIO, which relies of sysfs (deprecated, and you can't use it in newer Linux)

I had no idea that there's an OpiZ3W Just in case, it is nothing at all like the Orange Pi Zero 3, which has a lot in common with the OpiZ2W. Yeely: what are your first impressions about this board? Are there demos for the NPU? Are the video encoders and decoders working with the Orange Pi Linux OS? Bring up verifiable (open source) examples of AI generated code, making an improved program.

Ok thanks my apologies. Oh thanks, I missed that point. This box should've been ewaste long ago I gotbthe bright idea.of using it as a low power 'digital sign' driver for my wife's store . I started with ohub bookworm server for the board. I couldn't get the boot toothpick to read cards or usb. It wasn't until I flashed CoreELEC to a card and was trying to see if it was a distro issue that I realized the box was trying to go into android recovery with the toothpick not looking for boot drives. I put aml_autoscript from the CoreELEC root folder and zipped it then I used android recovery mode to clear the cache and update from card pointing at the zip file. Even though the final output was that it failed it actually loaded CoreELEC autoscript and when I rebooted it read the bootloader on sdcard. After discovering that little nuance I did the same for the flashed Arabian distro but it didn't seem to catch the bootloader on sdcard. I assumed I wasn't getting the right dtd.img copied so I tried the most likely for the chip and when I.asked ai it thought I needed a legacy version. When I throw the CoreELEC in now it still boots from the card. I made the assumption that the modifications to android boot would work accross distros so it didn't seem strange that CoreELEC might boot even if it was the bookworm autoscript being used by android. Thanks for taking the time to reply even though it's the wrong forum and my apologies I should've thought that through. Looking at the hub forum it didn't seem like there was much in the way of replies happening. Cheers

Hello, After more research it seems that despite the Wikipedia screenshot, M2 Ultra & M2 Berry do not really have the same CPU : M2U uses R40 and M2B uses V40 This is most probably why it does not work. After checking watchdog & sysrq, I almost rebooted with : echo 1 > /proc/sys/kernel/sysrq echo b > /proc/sysrq-trigger but still hung in the end. I was about to throw the Banana PI away, and I finally found this website which provides a (very) raw debian image for the M2 Berry, and it works correcty including reboot. Sharing the link in case it helps other people with M2B : https://sd-card-images.johang.se/boards/banana_pi_m2_berry.html Thanks for your help Regards

Hello Aniket, as i mentioned the armbian is not working because of the different DRAM Voltage setting in uboot. The board was running with original debian version from RADXA https://github.com/radxa-build/radxa-cubie-a5e/releases. If you check the log you see the dram voltage settings and training. For me i'm waiting until a board with 2/4GB which hopefully runs with armbian. Rolf

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Nick's instructions: You need to add this line to the bottom. "+CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y" and change "@@ -0,0 +1,31 @@" to @@ -0,0 +1,32 @@. ./compile.sh choose "Do not change kernel configuration" choose "Show CSC/WIP/EOS/TVB" choose "I understand and agree" choose "X98H" choose "edge" rest is up to you. Your image should be in output/images directory.

There's been a few changes to make etehrnet work on H6 that broek it for H616/H618 seemingly. Your best course of action for now would be to downgrade to 6.12 and lock the `linux-*` from being upgraded.

Just to let you know usb bug is still present in 7.1 rc3 [ 2.596444] usb 4-1: new full-speed USB device number 2 using ohci-platform [ 2.784449] usb 4-1: device descriptor read/64, error -62 [ 3.076447] usb 4-1: device descriptor read/64, error -62 [ 3.356447] usb 4-1: new full-speed USB device number 3 using ohci-platform [ 3.532450] usb 4-1: device descriptor read/64, error -62 [ 3.824440] usb 4-1: device descriptor read/64, error -62 [ 3.928486] usb usb4-port1: attempt power cycle [ 4.140440] usb 4-1: new full-speed USB device number 4 using ohci-platform [ 4.548447] usb 4-1: device not accepting address 4, error -62 [ 4.732456] usb 4-1: new full-speed USB device number 5 using ohci-platform [ 5.140438] usb 4-1: device not accepting address 5, error -62 [ 5.140481] usb usb4-port1: unable to enumerate USB device