Active threads

This method works for me, but I don't change Bluetooth driver's. You can also try command: apt reinstall bluez apt --fix-broken install

When using armbian-config to select an overlay ("DTO001")e.g. for uart2, one is offered the full names w/ overlay prefix, e.g. sun7i-a20-uart2. The system adds this to armbianEnv.txt: overlays=sun7i-a20-uart2 But it has also the line overlay_prefix=sun7i-a20 In the end, uart2 is not activated (no output from /dev/ttyS1) - after changing the overlay line to overlays=uart2, I can read from /dev/ttyS1. System is Armbian 25.2.2 stable (bookeworm), Armbian Linux 6.12.20-current-sunxi.

@Nick A I’m using the MiniArch image that was shared here on the forum. From it, I extracted the DTBs, Image, and other boot files, and replaced them in the Armbian image. I also took the bootloader from the MiniArch image and replaced the one in Armbian. With that, I managed to boot into Armbian, but unfortunately, no network adapters were detected.

Can you compare the device tree between your working system, and from the freshly installed 25.2.3/6.12.22 (write the img in a new microSD) View your device tree with: #(root) dtc -I fs -O dts /sys/firmware/devicetree/base (you need to find out which driver handles the audio, and search for that driver name in the working device tree) Also, check differences in armbianEnv.txt Also, check differences in ".config" in the /boot/ folder (specially anything related to audio) Also check the contents of "dmesg", searching for the audio driver name

Try setting ZRAM_PERCENTAGE=50 where 50 would be half of available memory. Not sure if the builder picks this up. If it doesn't I'd go the customize-image.sh route and use this to modify the /etc/default/armbian-zram-config file just before assembly closure.

Well, folks say it is being worked on - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71025ec7f7767 Decoding works so I was hoping it did progress but may be not.

I have device X10 Plus TV BOX 4/32 same smae Rtv 10x 4/32 How to get file image or build for device It run Allwinner H6 Link product I find fourm but cannot get the file

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

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!

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 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,