All Activity

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.

@Jean-Francois Lessard sorry for making you confused. Device tree source for tm16xx driver that I convert from a working openvfd.conf is below /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 = < 7 GPIO_ACTIVE_HIGH>; mosi-gpios = < 2 GPIO_ACTIVE_HIGH>; cs-gpios = < 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0>; spi-3wire; spi-lsb-first; spi-max-frequency = <500000>; digits { #address-cells = <1>; #size-cells = <0>; 01 02 03 04 }; leds { #address-cells = <2>; #size-cells = <0>; led@{GRID0},0 { reg = <{GRID0} 0>; function = "apps"; }; led@{GRID1},1 { reg = <{GRID1} 1>; function = "setup"; }; led@{GRID2},2 { reg = <{GRID2} 2>; function = LED_FUNCTION_USB; }; led@{GRID3},3 { reg = <{GRID3} 3>; function = LED_FUNCTION_SD; }; led@{GRID4},4 { reg = <{GRID4} 4>; function = "colon"; }; led@{GRID5},5 { reg = <{GRID5} 5>; function = "hdmi"; }; led@{GRID6},6 { reg = <{GRID6} 6>; function = "video"; }; }; }; }; }; The convert script I downloaded from this commit https://github.com/jefflessard/tm16xx-display/blob/a93b257ed4c73780fcdefbb1f1dd189599cf6ecc/vfdconf-convert Can you please help get it to work? Thanks!

@Nick A based on chatgpt with website research, it depends on with box meaning that mine still have a h313, its cortex a53. 64 bit, then what is it? (I can give you more proof that mine is allwinner h313)

Everything you wish for here is achievable with pure U-Boot technology. A long time ago, I tried to practice how to realize this here in the forum, but my lesson from it was: You can't teach old dogs new tricks, and Armbian users want to celebrate their cargo cult and hope that it will magically fulfill their wishes.

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

@Ducdanh Nguyen without a axp chip I’m pretty sure you don’t have a h313. You’re going to have research your box on your own. Sorry but I’m too busy.

What guidance are you trying to follow?

To anyone interested, I am seeking help to test the latest tm16xx changes for the (hopefully) final upstreaming submittal. You will find in-tree patches here: https://github.com/torvalds/linux/compare/master...jefflessard:linux:tm16xx, just suffix with ".patch" to get all patches in a single download. You will find out-of-tree version, device-specific dtso and latest display-service in the https://github.com/jefflessard/tm16xx-display/tree/v4-feedback branch. Thanks to all of you for you help so far!

Flashing under Linux you will have many options to do it and check some problems on partitions etc. Normally, I use the Balena Etcher and dd by console.

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.

I'd read rumors that uBoot has the ability for a multi-boot menu, but I was never able to get any video out of it to my DVI monitor to explore that too deeply. What I ended up doing was installing this UEFI port, and booting from it (instead of uBoot): https://github.com/edk2-porting/edk2-rk3588 The image takes up just over 8MB, but the built image is only 6MB in size. So you need to use dd to zero out a space first. The difference is where it stores the configuration. It can be flashed onto a microSD card or once you're confident in it, onto the SPI-NOR. I've done both. There are a few other versions of it for other hardware (other than rk3588). https://github.com/orgs/edk2-porting/repositories?type=all&q=edk2 That will boot UEFI and into grub very easily, and I do use grub to select which OS to boot into. I have one grub partition, and multiple installed OS partitions. The edk2 port is highly configurable, and recognizes hardware, including the network. Not sure if it's usable for remote access or not in its current build, but I think it can, at least, boot off the network. You can also configure a standard layout/path for your devicerees and overlays, where it will load them, but I haven't tested that out yet. If you don't override in the edk2 configuration or in grub, it will use the Vendor or Edge kernel's devicetrees (built in), or ACPI (also built in). Btw, I built it last night with a tiny change I made to the Orangepi5-plus edge devicetree to re-enable the ES8388 audio, and tested it out in Trisquel 12 with its kernel (with the devicetree from edk2) - it worked! The great thing is - their git clone and build process puts ALL the source files on your computer, so you don't need the internet to build, and you can know that any changes you make in the source code won't be "updated" overwritten by the build process. I've found with Grub, the update-grub utility will not find and add devicetrees, so you have to do that manually or hack in (which is what I've done). But again, apparently the edk2 port would make that unnecessary. So to add to the resources already mentioned, the edk2 port is open-source - they did it. Btw, I have also read that uBoot can boot grub directly, but I think you have to supply it with the address to load it into. Without knowing what I'm doing (when I first got my SBC), I didn't want to touch that.

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

Although writing the USB using Linux produced a good GPT the efi partition (FAT32) is unmountable and hence I cannot change anything. I tried gparted to fix it but the checkdisk failed. Hence I cannot follow the original guidance I had found. Where am I going wrong? thank again for any help

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.

Well using Linux to write the USB appears to have fixed the problems. Damn Windows Thank you for the pointers, much appreciated.

Hi all, I'm trying to use a DHT11 temperature and humidity sensor with my Armbian-based Orange Pi. I grabbed this DHT11 module. It’s cheap and seemed ideal for simple readings. The wiring matches the usual 3.3 V setup (VCC, data, GND), and I'm using the Adafruit_DHT Python library with the right pin number. Here’s my problem: Readings work perfectly right after reboot. tempo is consistent and logical. After a few minutes, the humidity values hang (stuck at 0 %), and temperature readings start to spike randomly or freeze. Resetting the board or restarting the Python script often fixes it temporarily. I've double-checked wiring (no loose connections), shielded against shorts, and even tried using a 10 k pull-up resistor on the data line. but the issue persists. Questions: Could this be a timing issue with how the Armbian kernel handles the GPIO? Any known quirks with DHT11 + Armbian or Orange Pi boards? Would using a level shifter or adding a small capacitor help stabilize the data line? Would love to hear from anyone who’s successfully run DHT11 sensors on Armbian or suggestions on how to dig into what's causing the freeze-up. Thanks for any help! —Jordan

nice, thank you for your feedback

We have a long wish to implement OTA solution into the build framework. The problem is - like always - time / not enough man power to run another (sub)project. Instead of reinventing the wheel - better is to follow / use (learning from) experts made frameworks: https://rauc.io/ as a base perhaps also this https://github.com/silitics/rugix/issues/82 and https://qbee.io/docs/index.html - all as extensions. If we can join resources, to do it right, its easier. But its still timely and complex due to the nature of what Armbian is dealing with.

I will soon be in the situation of having an offsite Helios4 installation at my non-techie father's place on another continent. I want to prepare for being able to do remote updates and if possible even some Armbian image testing. For that, I need a robust, bullet-proof and fully remote mechanism. The most I should assume to be able to ask my father is to unplug and replug the machine to powercycle. I hope you guys don't mind me joining your conversation to discuss my options. In the past, I had a setup on X86 with grub that I would like to hopefully replicate now in function with the Helios 4. There was a very minimal (read-only?) OS in a partition (network with DHCP, sshd) that would be the default boot target. The machine would always boot into this after a power cycle. From there, I issued a grub-reboot command to reboot into my desired OS. If I screwed the main system up somehow, I was always able to go back into the minimal system. How would I go about doing that in the Armbian world? From your discussion, it seems to be about tweaking armbianEnv.txt. But how can I do that in a way that has a bullet-proof option the system falls back to after a power cycle but also allows me to tweak it in a way that survives a warm reboot? I do like btrfs a lot and believe it should play a role here. I read @eselarm mentioning btrfs support in u-boot. How can I verify which u-boot is installed on my machine and whether it supports btrfs or not? Edit: https://embear.ch/posts/sw-update-concepts/ https://rauc.io/ https://mender.io/ https://bootlin.com/pub/conferences/2022/elce/opdenacker-implementing-A-B-system-updates-with-u-boot/opdenacker-implementing-A-B-system-updates-with-u-boot.pdf

There are various recent reports of windows corrupting the partition table.

If I remember correctly, recently there was a similar thread on the forum re GPT corruption under windows. Not sure, but there might be some useful info. Alternatively, flashing under Linux might be an option.

Hi, I am returning to Armbian after quite a few years. I was trying to follow guidance from nexbox-a95x-armbian and after a search found the debian & Ubunt images (https://www.armbian.com/uefi-arm64/) which I downloaded and wrote to a USB using Rufus (also balenaEtcher). I then tries to look at the FAT32 partition contents but the GPT was corrupt - tried many windows tools and Linux.I "repaired" the GPT using Linux tools but then the FAT32 filesystem was corrupt. What am I doing wrong? any help much appreciated

Thanks for the reply @laibsch . I looked for alternative solutions and it seems to be possible to only disable certain parts of PAM instead of the whole thing. Specifically it seems like the armbian dynamic MOTD is the biggest part of the problem. I opened /etc/pam.d/sshd , and commented out these lines to disable the motd: session optional pam_motd.so motd=/run/motd.dynamic session optional pam_motd.so noupdate And rebooted. This drastically improved the speed, from 5 seconds to around 2-3 seconds on first login and 1 second on subsequent logins. Still pretty bad though, what is there that needs to take one whole second or more to do to open a simple shell connection?