Active threads

If you are on a relatively recent kernel, the kernel probably already has support, but the default DTB has it disabled. This is from a bookworm nightly build for a radxa zero 3 ~$ grep rknpu /usr/lib/modules/6.1.115-vendor-rk35xx/modules.builtin kernel/drivers/rknpu/rknpu.ko However, it's disabled in the DTB by default $ cat /sys/firmware/devicetree/base/npu@fde40000/status disabled For the board that I am using, the vendor publises a DTO source that enables it at https://github.com/radxa-pkg/radxa-overlays/blob/main/arch/arm64/boot/dts/rockchip/overlays/rk3568-npu-enable.dts Which works well with armbian-add-overlay. Though you may need to make a similar overlay for your DTB if it is different enough. Note that the NPU in the 3566 and 3568 are interoperable.

Here some troubles are expected ... Can you try manual steps to install docker by follow: https://github.com/armbian/configng/blob/main/tools/modules/software/module_docker.sh#L26-L56 installing packages, adding to group, adding docker bridge. This might reveal more. BTW. My F3 died - waiting for replacement.

Ok, I was able to boot on maskrom mode! I had to cut the bottom shield (it is soldered, but I'm not using lora anymore so I didn't care). Just cut the shield right beneath the eMMC chip, and you'll uncover some pads. Short-circuit the middle big one (clk) in the attached photo with any gnd point, and plug the thing. That made the magic for me.

I am glad you could do it with the orange pi zero 2w, because I also want to use a very small arm board I am having trouble with the red ili9488 red LCD's touch function, and if I keep having no results, I will replace with the waveshare LCD model (I wanted to have 4-inch LCD ) What armbian and linux version did you use? If you go to the latest linux, you may need to modify the DTS a little bit (modifications are in my ili9488 thread). Warning: I use a different driver (parameter "compatible") for DRM graphics, and different drivers might need different DTS lines. Always use a different microSD for experiments, so you don't mess with your working setup Does the orange pi zero 2w just need male pin headers on the 40-pin connector, and then plug the LCD on top?

Hello, first of all, I’d like to thank everyone for the post and your contributions! My problem is simple: I have an H96 Mini 4K Ultra HD, with CPU RK3228A, OS: Android 9.0, RAM: 2.0 GB, and ROM: 16 GB. I installed the ArmBian system on it; but then I decided to reinstall the original ROM. However, during the step sudo rkdeveloptool db rk322x_loader_v1.10.238_256.bin, I mistakenly flashed the original system image instead. Now, the device shows no sign of life — it's not recognized by either Linux or Windows. What should I do?

it seemed that the (minimal/iot) images linked on the boards page , have been updated, I just downloaded Armbian_community_25.8.0-trunk.228_Orangepizero3_bookworm_current_6.12.30_minimal.img.xz for orangepi zero 3. note I only checked debian as that is what i'm using https://www.armbian.com/orange-pi-zero-3/

it seemed that the (minimal/iot) images linked on the boards page , have been updated, I just downloaded Armbian_community_25.8.0-trunk.228_Orangepizero3_bookworm_current_6.12.30_minimal.img.xz for orangepi zero 3. note I only checked debian as that is what i'm using it seemed to be similar for orangepi zero 2 https://www.armbian.com/orange-pi-zero-2/

Hi I have upgraded an existing x86 Armbian system with kernel 6.6.63 and zfs 2.3.2 to the suggested kernel 6.12.32-current-x86, but I cannot get the zfs kernel module loaded after the latest updates to Armbian 25.5.1 noble. I also tried on other kernels, only the old 6.6.63 seems to work. Normally when you select a different kernel in the armbian-config menu, it should automatically compile the zfs modules if it is activated. It just skips it. But you can of course compile it with the provided DKMS system: the build just finishes fine, without any error, also the install, but when you try to load the module: it responds with: dmesg: I have zfs 2.3.2 on kernel 6.12.32-current-bcm2711 running just fine on a Raspberry Pi 4, so I tested what would happen if I just build a small kernel driver module: root@armbian:/usr/src/dummydriver# cat dummydriver.c root@armbian:/usr/src/dummydriver# cat Makefile So when I run this on the Raspberry Pi 4, I can load the module and unload But when I run this on the x86 machine I get the same error: root@armbian:/usr/src/dummydriver# modinfo dummydriver.ko root@armbian:/usr/src/dummydriver# gcc --version I also tried gcc 11.4.0 Here is my armbianmonitor -u: https://paste.armbian.com/orepumazam Any help welcome! Philippe

i answered in your thread.

So yes, HDMI does work on the archived image. Interestingly, USB does not work. I tried to connect a keyboard and a mouse but that did not work. So, on the HDMI terminal I successfully reach the login screen but can't go past that. But through ssh/serial I can work on the system. I tried memtester and it does show some issues with the memory, but overall, this archived image has worked without issues. I was able to use octoprint_deploy to install Octoprint, but again since USB does not work couldn't connect the printer itself. To replace the dts file easily I need input devices to work, I will try and see if I can do that over serial. And the next thing to try is to compile using an edge kernel and report back. Thanks, Shivam

If you are talking about lag with discord webpage, vpu accel won't help because there is no video played in discord. You can check chromium's gpu status at chrome://gpu, see if the gpu driver is working. My ppa only packages chromium for noble, ubuntu 25.04 is not supported. While chromium in my ppa only add patches to let chromium use vpu when playing videos, this should not help improving discord webpage performance.

Hi, Great work thanks! Why no 25.05 for banana pi M4 zero? Perhaps are you waiting for some additional work on missing bluetooth support for rev2? @c0rnelius ? Denis

@KrzyPac Ur welcome.

I can not get sound out of AnalogCodec LinOutL/R pins either.

Actually its the opposite so it must have been something else. Etcher is known to be broken for bigger images (desktops). There is some bug in the .xz decompression method used by Etcher. I am using only USB imager for at least a year and haven't run into any problems. At least not on this level.

moved

yes I can confirm

Thanks - I'm worried my main issue was with the overlay loading issue I mentioned. I did try 6.15 but prob need to retry with the hack with overlay-user. But man... it is SO incredibly simple to switch the kernels.

See for more details but without using the overlay-user folder - I was not able to get the pwm to work on a fresh download.

https://paste.armbian.com/cawuyeyice

Armbian 24.5 works normally, but this issue occurs in versions 24.8, 25.5 and 25.8 [ 0.872698] dwhdmi-rockchip ff940000.hdmi: supply avdd-0v9 not found, using dummy regulator [ 0.872852] dwhdmi-rockchip ff940000.hdmi: supply avdd-1v8 not found, using dummy regulator [ 2.361552] dwhdmi-rockchip ff940000.hdmi: supply avdd-0v9 not found, using dummy regulator [ 2.361723] dwhdmi-rockchip ff940000.hdmi: supply avdd-1v8 not found, using dummy regulator [ 2.361912] dwhdmi-rockchip ff940000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY) [ 2.363007] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffff80008120fe60) [ 22.444508] hdmi-audio-codec hdmi-audio-codec.8.auto: Only one simultaneous stream supported! [ 22.444524] hdmi-audio-codec hdmi-audio-codec.8.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 0.871390] rockchip-drm display-subsystem: bound ff8f0000.vop (ops 0xffff80008120b5e8) [ 0.872604] rockchip-drm display-subsystem: bound ff900000.vop (ops 0xffff80008120b5e8) [ 2.360057] rockchip-drm display-subsystem: bound ff8f0000.vop (ops 0xffff80008120b5e8) [ 2.361397] rockchip-drm display-subsystem: bound ff900000.vop (ops 0xffff80008120b5e8) [ 2.363007] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffff80008120fe60) [ 2.364674] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0 [ 2.510919] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device

I just did some new experiments, trying to get touch working in ili9488 LCD v2.1 Increasing or decreasing the SPI MHz in both the LCD and touch section of the DTS DONT WORK... I couldn't get touch working Next is to use a software defined SPI with spi-gpio (based on my experience in my ili9341 thread) does anybody know a Python soft spi program which can talk to ads7846/xpt2046?

And could you tell me how to add a patch to my .dtb or .dts file. I installed linux-headers but I don't know what to do next with the patch posted above by c0rnelius.

So I was able to reproduce the issue when trying to boot via NVMe after using armbian-config to switch from emmc. Using rkdeveloptool to flash the SPI with https://dl.radxa.com/rock5/sw/images/loader/rock-5b+/release/rock-5b+-spi-image-8ea7ee4-20240730.img (short guide in the spoiler) I was able to boot into the NVMe. Looking into fixing the broken SPI installation

Check here https://github.com/armbian/community/releases/tag/25.5.0-trunk.256 or on a mirror with archive https://docs.armbian.com/Mirrors/#current-mirrors for what you are looking for. We're aware that some links are broken for yet to be determined reason.