All Activity

Hello! It seems that there is some issue with the user files FTP server. The multitool image should be acessessible from: https://users.armbian.com/jock/web/rk322x/multitool/ But it is present in: https://users.armbian.com/users.armbian.com/jock/web/rk322x/multitool/

I now actually see after some more reading and checking other SoC's that the CPU's in the A733 must start the kernel at EL2. See also ARM reference doc: 102412_0103_01_en So also 5.x kernel should work if EL2 I think If the A733 has not implemented EL2 and EL3 as could be the case as suggested in ARM reference doc, no KVM. See chapter6: As it is Allwinner, I won't be surprised, but wait and see what Radxa will come up with.

Hm I briefly remember there was an optional overlay to raise voltage to 1.3 volts..but I don't know why it should be now standard. Did not do any investigation though

npu is there in both vendor bsp kernel 6.1.y. There is no node exposed afaik. Everthing beyond like libraries to use npu is userspace and out of scope of Armbian. edge 6.18.y also has reverse-engineered npu support with a driver called Rocket.

But.... i can run from IOT img WTF

That isn't some you can do in armbian-config. This is Linux, use search to find how others have solved this.

after configuring the image from the sd card and installing the system on ssd m2 via armbiab-install, the board stopped shutting down. I tried to change bootloader, img, and EF through rkdeveloptool, but nothing helps. PS EF doesn't work, does anyone know what to do?

good morning/evening lads can anyone help me on unbricking this? already tried sd card with multitool , no boot with or without sd card(blue and red light are steady and doesn't get bright , no display). looks like its an emmc chip (i brick it on image burning process ) images of the board: https://ibb.co/rRGxJfZ1 https://ibb.co/3524sZCQ https://ibb.co/yBBNYmbG

Hello, I am currently working on a project involving local LLM inference on Rockchip SoCs using the rknn-llm framework. I have two specific questions regarding Armbian support for the NPU: 1. NanoPi M5 (RK3576): FriendlyElec recently released the NanoPi M5 based on the RK3576. If I use the Armbian image for this board, will I be able to run LLM models using the NPU? I am considering purchasing this board for LLM testing and would like to know if the driver support is already there. 2. NanoPC-T6 (RK3588): I have a NanoPC-T6 running Armbian, but I cannot find the /dev/rknpu device node. I have tested this with both 6.1.115-vendor-rk35xx and 6.12.58-current-rockchip64 kernels, but the NPU device is not appearing. Is there a specific overlay or a manual configuration step needed to enable NPU support on these kernels? tried adding tags npu and nanopi m5, but there was no such option. I am happy to provide any additional information, logs (such as `armbianmonitor -u`), or command outputs if needed to help diagnose the issue. Thank you in advance for your help and guidance! Best regards, A.H.

Good afternoon. I'm trying to stream video to my orange pi zero 2w. I am using Gstreamer and while testing I saw that v4l2slh264dec fails. When using autosink, only a transparent window is shown and when using a specific sink, no window is opened. My intention is to take advantage of the VPU with Gstreamer but that failure has caused me headaches. I tried using MVP and it works fine but it's not what I need. Maybe I will choose other options for what I want to do but first I would like to ask here about the topic- Thank you very much to whoever takes the trouble to read this and thanks in advance to whoever responds ❤️ By.: Google Translate

Even 6.1 kernel has voltage set at 1.3. I'm going to do a kernel patch and set it the same way as 5.x kernel was set.

Hello SteeMan I can start armbian-config but i cannot find where to change the display and install a desktop It als displays the current is plucky is not supported or not listed Thanks

I'd recommend you ssh into the box, then you can configure to your needs.

Progress I installed a command line image Armbian_community_26.2.0-trunk.130_Aml-s9xx-box_noble_current_6.12.63.img.xz This image let me boot to a promt asking me to set a root pw make a user and pw Then it gives me a Prompt can use raspbian-config to make a wifi connection But i have a overscan the prompt so i must type the first letters blind I also miss the first letters of the answer I cannot run xrandr to correct this problem xrandr reports cant open display after the command xrandr --listmonitors Also how can i install and run a desktop on this system Thanks in advance for a anser

Developing solutions and sharing by sending PR and/or using customize image script might be the way address those.

Have you also looked at the clocks? I have several NanoPi-NEO's (since around 2021 I think), H3 SoC, never had any overheating issues. I actually did some measurements recently and surprisingly low power, I had expected more. Clock stays at 480 mostly. I see the Duo2 is H3, Duo I don't see on FriendlyElec's site. But quite different HW/board. Only thing I could think of maybe is that I removed ( apt purge --autoremove) cpufrequtils after in-place upgrade from Bookworm to Trixie. Have not looked at it any further, it just is not in my vanilla Debian Bookworm -> Trixie, so just blind purge I thought. Still all fine, also with 6.18 kernel: # uname -a Linux raspi2 6.18.2-edge-sunxi #1 SMP Thu Dec 18 13:03:43 UTC 2025 armv7l GNU/Linux # cat /sys/class/regulator/regulator.?/microvolts 3000000 3300000 5000000 1100000 # cat /sys/class/thermal/thermal_zone0/temp 27116

I suppose this is a genuine problem if someone like me ships the hardware with user not competent to handle uart but would like to switch from default wifi config e.g. Wifi Name: Abc Password: Pqr with dynamic ip. To static IP 192.168.1.123 with destination wifi router with wifi name: Def and password: Xyz. In this case I would like to provide simple SOP to start hotspot on the phone and access putty on phone to switch to new wifi.

Thank you very much for that!

Hi, I'm new to this forum but I've been researching this topic for quite some time. I have a Mecool KM1 Deluxe with 4GB of RAM and 64GB of storage, and an Amlogic S905X3 chip. I wanted to install Armbian to use it as a Linux device, but I've tried several versions and it hasn't worked. Someone mentioned on this forum that installing CoreELEC would prevent Armbian from booting. I installed emuelec and it worked perfectly, but I haven't been able to run Armbian. Could this be the reason? Thanks.

thank you for adding information about big.LITTLE seems that will be the next issue when we need to work virtualization on A7A/A7Z but for now, we seems facing the problem during the boot process CPU in the wrong exception levels(model) so the virtualization is not support in any situation(my guess) also Nick thought it's about u-boot issue and used the official binary image so we might need to wait for official update or we need to work by ourself

May boot from new / known-to-work Armbian on SD-card and use command: sudo lsblk and/or sudo lsblk -f to see what is what. mmcblk numbers have swapped sometime in the past years, so indeed even if you know enough about Linux, mixing numbers might be a disater because you would overwrite the runnig installation. That might also be a reason why tooling might refuse or not list as there is a risk of having it wrong. But you should clean-up the 100% full filesystem. It will take time figuring out what should be deleted, but so does going to the toilet as well. It has to be done, cannot assume there is endless space.

Radxa staff actually does not answer the original question w.r.t. Allwinner A733 HW virtualization, it is just that kernel config has it. But I see from releases 'bullseye', that does not look good at all. In theory, that means 5.10 kernel, and oldoldstable libvirtd/KVM/QEMU etc. As this SoC is bigLITTLE, (Cortex-A76 Cortex-A55), starting a qemu-system-aarch64 process will pick some of those cores randomly, assuming you have more than 1 vCore (smp option > 1) . Kernel older than 6.8 or so does not support moving between an A76 and an A55. That is the same for Rockchips (RK3588). It took me quite a while before I discovered that this is known behavior. So on for example on vendor rk35xx 6.1.115, I pin vCPUs, can be done in virt-manager GUI xml config or cmdline via taskset. As easy test, use -smp 1, then it should work. mainline kernel CPU numbers are such that simplest/lowest CPU's get lowest number. That might be the other way around on 6.1 or older downstream/vendor/BSP kernels. On an RK3588, a 2-core VM with 2x A76 and 512MiB is done by: taskset --cpu-list 6-7 qemu-system-aarch64 -M virt -cpu host -enable-kvm -m 512 -smp 2 \ -bios u-boot.bin \ -drive if=none,file=armbian.img,format=raw,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -netdev bridge,id=hn1 -device virtio-net,netdev=hn1 \ -nographic Same should work on A733

@Linlunson same, I want to run pxvirt on it but now I can only play some container with docker without virtualization funny thing even old raspberry pi can use kvm feature but this "new" allwinner chip can't this out-of-the-box support this besic feature I think I was also deceived by radxa's staff in some way https://forum.radxa.com/t/a7a-harware-virtualization/29745 anyway I also test on Nick's image, but mean the offical image from radxa https://github.com/radxa-build/radxa-a733/releases and it also not work(still stuck on EL1) so I think maybe Nick is do everything he can do issue might on bootloader I asked about the cpu exception levels on discord channel sometime radxa's staff will answer in there too or maybe someone knows about this we just needs standby...

Hi all, I am unable to login to OMV on my Helios64. A bit of sleuthing indicates that this is because the / fs is at 100% capacity. At first, I figured I'll just transfer the system install from the 8GB SD Card I started with to the 16GB internal eMMC. Turns out past unfnknblvbl already did that, and now I need to go the other way. The documentation on the old Kobol site isn't entirely accurate about how to do this. My SDCard is /dev/mmcblk1 and even though it's formatted ext4, it simply doesn't show in armbian-config. In fact, the only device that shows in the Install menu is /dev/md127, which is the RAID array itself. I'd rather not be booting from that for obvious reasons. Assuming that I'm a bit of a Linux noob (I know just enough to be dangerous), is anyone able to tell me what am I doing wrong? Thanks! 😃

Thank you Wolfypotal for the update, The recent days I was also test the official image, Nick A's 0.4, but no good luck for the kvm, which actrally the big reason I purchase this cute small soc. I even upgrade the broad to have 8GB ram and 256 UFS, to use the kvm qemu...