Active threads

the guide has a warning: Note: If you have previously run other distributions on the box such as coreelec the below installation will not work. You will need to restore the original android firmware before attempting the install. coreelec changes the boot environment in ways that are incompatible with these Armbian builds. I have run coreelec but only ever from an SD card, I don't think the firmware has ever been changed as if I remove the SD card it boots into the original android system. Is this likely to be true or am I again missing something.

HP Pavilion8 core processor, 32Gig RAM laptop. I wanted to limit information to limit time for digging into it, but here they are: log-build-322ed1c8-a4db-4873-85ac-be8e6a87fbd6.log.ans summary-build-322ed1c8-a4db-4873-85ac-be8e6a87fbd6.md

dig through the github actions, how the images are compiled is public information ;-)

probably time for the serial console my suspicion tells me that it will be hard to get proper logs otherwise my suspicion is that some umounts does not come back. <- try to unmount everything you can before the reboot and see if that helps.

This is great. Apparently mine didnt persist after reboot either, yours seems to be permanent and working even better. Thanks!

I have looked at a lot of other 4 and 8 PIN cables and considered using multiple single SATA power connector to double connectors but I have reservations because the harness cable included with the Helios64 has those capacitors. I am not certain what their purpose is and I am concerned if I do some sort of unique solution I will damage the motherboard. Also this was being used as an offsite NAS for a production environment backup data and so stablity is essential. I've asked this question in multiple places, I am at the point that I am just going to have to order a new NAS unit that doesn't use custom cables.

spendist is the maintainer of the Nanopi Neo. Maybe he has something to say. Did you try another kernel? Another OS?

Awesome! Please do elaborate. Please do elaborate. What is the cargo cult practiced here at Armbian? I'm old, but I'm still interested to learn, so please do teach me.

A google search indicates that the MXQ Pro 4K 5G often uses a RK3229 quad-core CPU

@dale it seems like vfd-convert has not worked well. Perhaps because of some mix between script version and the template files version. Whatsoever, I've looked closer at the patch link you previously posted, this is the older pre-review dt-bindings syntax. You should be go to start with something like: /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = <&gpio 7 GPIO_ACTIVE_HIGH>; mosi-gpios = <&gpio 2 GPIO_ACTIVE_HIGH>; cs-gpios = <&gpio 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0x0>; spi-3wire; spi-lsb-first; spi-rx-delay-us = <1>; spi-max-frequency = <500000>; titanmec,digits = [00 01 02 03]; titanmec,segment-mapping = [03 01 02 06 04 05 00]; #address-cells = <2>; #size-cells = <0>; led@4,0 { reg = <4 0>; function = LED_FUNCTION_ALARM; }; led@4,1 { reg = <4 1>; function = LED_FUNCTION_USB; }; led@4,2 { reg = <4 2>; function = "play"; }; led@4,3 { reg = <4 3>; function = "pause"; }; led@4,4 { reg = <4 4>; function = "colon"; }; led@4,5 { reg = <4 5>; function = LED_FUNCTION_LAN; }; led@4,6 { reg = <4 6>; function = LED_FUNCTION_WLAN; }; }; }; }; Note that I haven't tested it, just made it from some copy-paste. If it doesn't work, even partially, you would most likely need to replace &gpio with the right reference to the gpio controller wired to the display.

Hello, I am new to arm board, I had this android tv stick called S moon mx10 5G, it have rk322x cpu, 2GB Ram, and ap6330 wifi chip. I tried armbian on this device but wifi chip was not detected, I tried using "rockchip-rk3318-box-wlan-ap6330.dtbo" as user_overlays, but still not working, could anyone tell me how to make this wifi chip working on rk322x armbian?. I attached some files for information: dmesg.txt s_moon_mx10_5g.dts

Hey Guys, I know this post is old but I have some questions. I was following @Jaybyrd's instructions and I have a question pertaining to the Plugin USB-C to the power on the device "I am assuming that is on The OPi5 device." Am I supposed to plug in something else? Because it says to open a terminal "what terminal? On what device?" Thank you for your time, Michael

I wouldn't be so categorical - I have rock pi 4b, which never saw android or any os other than armbian, which has same thing- two boot devices on emmc. Since it doesn't bother me, I didn't investigate further.

If the card still mounts, try running fsck first. If it’s clean but won’t boot, you can copy fresh /boot files from the same Armbian release. Otherwise, reinstalling to a new SD and restoring your data may be the safer route.

I faced a similar Ethernet throughput issue on Armbian under high latency. One thing that helped was using a USB Ethernet dongle instead of the onboard NIC. To simulate latency, you can use the tc command: sudo tc qdisc add dev eth0 root netem delay 200ms sudo tc qdisc del dev eth0 root For more solutions, check out this.

Hi and thanks! Tested now but no luck. Compiled edge 6.15.4 Linux nanopiduo2 6.15.4-edge-sunxi #1 SMP Fri Jun 27 10:13:43 UTC 2025 armv7l GNU/Linux now i get Device creation failed: -14. [h264 @ 0x11f9b40] No device available for decoder: device type drm needed for codec h264. Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> wrapped_avframe (native)) Device setup failed for decoder on input stream #0:0 : Bad address [AVIOContext @ 0x11ac030] Statistics: 498846 bytes read, 0 seeks command as follows: ffmpeg -v trace -re -hwaccel drm -i Big_Buck_Bunny_720_10s_10MB.mp4 -f null - also tried fbdev output but same result. ffmpeg version is still ffmpeg -v ffmpeg version 5.1.7-0+deb12u1 Copyright (c) 2000-2025 the FFmpeg developers built with gcc 12 (Debian 12.2.0-14+deb12u1) configuration: --prefix=/usr --extra-version=0+deb12u1 --toolchain=hardened --libdir=/usr/lib/arm-linux-gnueabihf --incdir=/usr/include/arm-linux-gnueabihf --arch=arm --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared libavutil 57. 28.100 / 57. 28.100 libavcodec 59. 37.100 / 59. 37.100 libavformat 59. 27.100 / 59. 27.100 libavdevice 59. 7.100 / 59. 7.100 libavfilter 8. 44.100 / 8. 44.100 libswscale 6. 7.100 / 6. 7.100 libswresample 4. 7.100 / 4. 7.100 libpostproc 56. 6.100 / 56. 6.100 Unfortunately there are countless forks of ffmpeg. I used the one from here https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/ As of now I haven't found anything about a current kernel and ffmpeg working on any H3, only stuff back in 2019 and/or kernel 4.x 🙂 I also tried several extraargs=cma=### up to 256M but all same error. I really woud love to get some more tech background on "how stuff works" which may help me troubleshoot. => Can we enable debug output from the cedrus driver? How? => Can we enable debug output from thev4l2 layer? How? => Which libraries are involved, eg. v4l2request, other v4l2* which may need additional install/update? => Do in need v4l2-util / v4l2-ctl to configure some stuff? If yes, what exactly? (Remember, Its currently for file playback. I know about for cam capture) => Could the v4l2loopback help? => Can anybody confirm it really works on H3 maybe on an OrangePi board? If yes I can pull the Opi device tree and compare for possible differences. T.

I think Thunderbird, Firefox and other programs should configure firewall as well, of course without any information about that.

I have a ssh connection with my TV BOX (it is a AMLOGIC with S912), in my etc/ssh/sshd_config I have "UsePAM yes" and without any delay for connection, and probably it was not the problem of your delay in the start connection. In addition, I installed a vnc service to work remotely using the graphical interface. Either ssh and vnc Viewer (xtightvncviewer in my Debian Desktop) run pretty well. Please, check your basic network services, as well, fix the IP in the TV BOX. In my case I did some adjusts such: cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.15.22 netmask 255.255.255.0 gateway 192.168.15.1 dns-nameservers 8.8.8.8 1.1.1.1 There are some network services that can be impling in your delay by ssh (it is robust, old and fast application of Linux) I hope to help you too.

Hi everyone, i manage to extract the .dtb file from the recovery partition of the rk3528-X88pro13-android. This is the board number : X88PRO 13-D4-V1.1 (2023-04-12). Maybe it will be useful to someone 😉 rk3528-x88pro13-android.dtb

Overlay was renamed at some point to just uart5 `/boot/dtb/allwinner/overlay/sun50i-h616-uart5.dtbo` (without `ph5`), so `overlays=uart5` works and is available at /dev/ttyS1

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

nice, thank you for your feedback

hi, I am unable to boot Armbian on Gamebox G11 Pro. I am able to boot CoreElec and Emuelec easily via sd card. I have tried every tip and trick to boot it, lot of Armbian versions and forks. Can you suggest a suitable armbian dtb file for the same. The most reliable method to boot it.

Great to see continued development for RK3318/RK3328 boards, Armbian support really helps unlock their full potential for lightweight Linux projects.

@usual user The USB and Ethernet ports are exposed, but how would that work exactly? I don't know how to make the software boot from USB or Ethernet and even if I did I don't know what to boot into that can write an image file to the emmc chip. I can find no info on this on radxa or armbian sources.