Active threads

If Allwinner does not provide C-source code (kernel, libs, ffmpeg, etc) for recent Linux, I consider it as is; no encoding on Allwinner SoCs. I have several H3 boards, I also dreamed that I once maybe could use that for HEVC->H264 transcoding (low power 24/7 multiple TV channels) but it is not happening. I spent a lot of time to get it working on Pi4 and that breaks at various distro updates or just kernel updates. But RPL then hacks/fixes it in their custom ffmpeg, but it is only Pi4 and also limited, Pi5 has no HW encoding so even they as biggest SBC company give up on it I would say. Rockchip and Intel have fairly easy out-of-the-box solutions, but both not V4L2m2m.

Which image are you using? Axp313? https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_Tanix-tx6s-axp313_bookworm_edge_6.12.11.img.xz

@Aleqssandro Farias your miniarch image says it’s using Tanix TX6s (axp313). Try the armbian version. https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_Tanix-tx6s-axp313_bookworm_edge_6.12.11.img.xz

Hello, we have tried wifi and it is working fine https://www.armbian.com/armsom-sige5/

AFAIR someone on this forum also experienced booting issue with orange pi board though 4 not 5 with quite similar symptoms. May be worth contacting that person for his results so far - might give some hints on what's going on and whether it's a manufacturing fault

Hm if an image works but self-made won't either means something has been messed up which I doubt since it fails at uboot level. Or a change in the code broke it in the mean time. Also interesting that kernel building fails when RKNPU is a module rather than built-in. I guess that goes to poor implementation on Rockchip's side. Which exact pre-built image did you test that works well? This is quite old. We had a few version bumps in the mean time. More recent vendor kernels should already contain 0.9.8 What you could also try is to integrated the most recent patch series for mainline npu driver into edge kernel: https://patchwork.kernel.org/project/linux-rockchip/cover/20250519-6-10-rocket-v4-0-d6dff6b4c0ae@tomeuvizoso.net/

Yes, DB9 won't work. But if, as eselarm mentions, a proper chip is on board already a simple usb-a to usb-c or c-to-c cable should do. Check dmesg when connection to see what pops up.

These things can happen, yes. Sometimes old vendor-style uboot cannot process a modern mainline kernel and vice versa. Glad to hear it worked well this time.

and I must say that not only your passion, but also your dedication and commitment are truly inspiring for the whole community! One just cannot thank you guys for everything you have done! @fabiobassa @jock @ilmich Since @jock provided the experimental image on May 12th, i've been playing non-stop with this device, doing numerous flashing attempts and testing things out, just for fun... I must have spent 30+ hours on this ever since, mostly trying to compile things myself to run in the box, playing with the different overlays to test what works and what doesn't and learning about Tee, trust, op-tee,... You know those kids that when get their toys, they tear it apart instead? well... same feeling... the discovery passion thing... I'm preparing a report on my findings for my specific "MXQ-EP-2-V1.0" MoBo model, specially around on the working overlays, perhaps I can post it in the weekend.... And responding to my own question earlier about armbian minimal, in the armbian-config tool from the experimental image, there is an option to disable desktop... it gives you a system with only 25 tasks running and lower RAM usage than a DietPi. Now I begin to become interested on (re)assembling ROM images... I've been trying to replace some internet roms with the Trust Partitions and u-boot from the ROM I know it works... No successful test yet, but not sure if I'm repacking them correctly... Anyway, I'm learning a lot and that's great thanks to this community!

Incbot, hi I have this problem too. Use rk3318-config command to set device tree overlay (on the second step push space then enter) and then don't touch device tree overlay in armbian-config. After reboot use command hciconfig -a, if it have some message on screen - Bluetooth working

Thank you, I tried. But this is not my level, it is too difficult for me. I'll probably wait for your next release.

I believe I have the same issue with an unbootable Rock64 after the kernel update from 6.6.x to 6.12.x.

Good day, I've installed ARMBIAN to my old TV box. It's running fine as I ussually use it headles with a ssh connection to it. BUT NOW I've attached it to the hdmi TV and I want to remotely use that HDMI screen w/o local keyboard and mouse. I don't know how to do that. Please give me a help?

Yeah, I noticed it was not rebuilt on the next calls to compile.sh. Might not solve the problem for CI/CD environments, but for development it should work. Thanks!

Hey, @xiaobao80! Sadly not - but on the upside I was able to build and use the latest kernel. Also want to update and say that I did manage to use the NPU and the VPU successfully with Immich AI facial recognition and Jellyfin transcoding respectively.

Hello @mvpwar Download image Unzip

Finally someone has the question I wanted to ask right now.. Thank you for the solution you found. I will try it sir..

Makes sense, thanks for pointing that out. I had similar issues and I’ll check which package holds it on my setup and try replacing it. Hopefully that clears it up.. Thank you..

Further testing shows that Armbian 25.2.x through the current version all run the arecord -c 2 -r 192000 -f S32_LE test.wav without error, PROVIDED the 6.12.12 kernel is used. But, any kernel version after 6.12.12 fails. Now I've just got to find out what broke in 6.12.13 🙂

You can find this information on the Rock Pi S PoE Hat Wiki, but you need to write some GPIO values to enable the headphone jack. # echo 15 > /sys/class/gpio/export # echo out > /sys/class/gpio/gpio15/direction # echo 1 > /sys/class/gpio/gpio15/value To persist this across reboots you can create a `systemd-tmpfile` at `/etc/tmpfiles.d/enable-audio-jack.conf` with the following contents. w /sys/class/gpio/export - - - - 15 w /sys/class/gpio/gpio15/direction - - - - out w /sys/class/gpio/gpio15/value - - - - 1

I just updated one of my Armbian installs, including the 6.12.22 kernel, and it's still working normally. $ uname -a Linux snapclient-master-bedroom 6.12.22-current-rockchip64 #1 SMP PREEMPT Mon Apr 7 08:08:37 UTC 2025 aarch64 GNU/Linux $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: analog [analog], device 0: ff320000.i2s-rk3308-hifi ff560000.codec-0 [ff320000.i2s-rk3308-hifi ff560000.codec-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: pcm5102a [pcm5102a], device 0: ff300000.i2s-pcm5102a-hifi pcm5102a-hifi-0 [ff300000.i2s-pcm5102a-hifi pcm5102a-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0

I also have some oom issues when doing an aptitude upgrade in my opizero w/256 MiB ram. Guess even more on a 128MiB board like yours. Best to add a swap file to make sure upgrades go without issue. Grt,

I'm building a multi-zone music streaming setup built around an SBCs running Snapcast/MPD and this MA12070P board (AliExpress link). From the pinout diagrams it looks like the board is the same as the Merus Audio Amp Hat just with a built in USB-C PD supply (why I want to use this board). If it's a clone then it looks like support is in Raspberry Pi OS, but I want to use the Radxa Zero 3W since I can get it at a similar price point with better specs. This is my first embedded project since ~2019 so a bit out of my depth when it comes to device tree overlays. How would I write a DTO to enable audio output to this device?

After installing official Armbian_25.2.1_Orangepi5-plus_bookworm_vendor_6.1.99_xfce_desktop.img to sdcard, then to nvme all is fine, until, I do an apt update & upgrade, after that point chromium fails to run. I explored the logs to see it a failure to load chromium.conf from /etc/chromium.d/chromium.config (failed symbolic link to /etc/armbian/chromium.config). Is there a known workaround besides utilization of firefox?

Finally got around to debug this: Previously I had the system on an nvme drive and the bootloader on spi After reinstalling the system and bootloader both on mmc flash, I eventually ran into the very same issue. According to the logs, the boot bails with the following error: Log1: When I remove the nvme drive, the boot process works just fine for some reason: (boot log after nvme removal) Log2: When I reinstall the nvme, the boot fails again. However, booting from sd-card (using recovery button) and reflashing the bootloader to the mmc fixes the issue as well with the same result as removing the nvme drive had, resulting in the same log2 as above. I had fixed the issue before by reflashing the bootloader to spi but just like yesterday, it eventually stopped booting again until I reflashed the boot loader. There isn't anything particular happening before this occurs, though the last few times it was always after the system had run for some time. After cutting power (without shutdown) and booting it again, the issue would appear. (The device is always cut from power instead of shutting it down, but there was never an error on any drive due to that). The issue also did not show when the device was just turned of (without power) for a day or two. It seems to trigger quite randomly. I already tried to erase the spi flash to avoid any old entries messing up the boot order but without effect. Any clue what I could try next?