Active threads

OK...I think it worked in OrangePi3 LTS 🙂 ...first, clean up the remnants: ................................................................. sudo apt purge v4l2loopback-dkms sudo apt autoremove ............................................................... armbian-config then I had to switch to a different kernel: edge:6.15.4-edge-sunxi64 ....then update the system: apt update / upgrade / reboot ! install from GitHub: v4l2loopback and then: cd ~/v4l2loopback .................................................................... VERSION=$(grep -oP 'PACKAGE_VERSION="\K[^"]+' dkms.conf) sudo cp -r . /usr/src/v4l2loopback-$VERSION sudo dkms add -m v4l2loopback -v $VERSION sudo dkms build -m v4l2loopback -v $VERSION sudo dkms install -m v4l2loopback -v $VERSION dkms status sudo modprobe v4l2loopback ls /dev/video* ................................................................... I guess it's OK now: ................................................................

It doesn't seem to make a difference:

I would open the box make photos of the board with silk prints visible and search similar box in a relevant section of tv boxes on this forum. Name on the plastic box means nothing, silk prints on the board and SoC itself might help.

Hello @Nick A i was busy on school and my cable is delivered, i was able to use adb. Could you show me how to dunp the boot.img? @SteeMan, My box is fake and it is allwinner h313, is in 32 bit mode

None of the images are no longer working for me, no matter which recent image I take, the A5E board just remains stuck with a solid blue light (with some green light flickering). I even tried compiling armbian myself, but that also didn't work. The only image working for me is the 25.02 version from earlier this year. I am using the Radxa A5E v1.2 version with 4gb ram. I also mounted the SD card to a linux machine and looked into /var/log for a boot file or reading the journal but I don't see any logs written. Have somebody stumbled unto a solution or does somebody have advice me how I can get the logs to find the culprit?

Hi! i already tried this without luck. Based on the version ffmpeg showed it installed the right one. I also did uninstall previous ffmpeg and verified its really gone. I still suspect there is something wrong specific for the duo2. Could you please take a look what exact version ffmpeg does show? T.

I can see that after multiples update that the situation for the video acceleration seems to be better in full HD not in 4K, could you help me to understand how? In addition I'd like to add that I'm still getting problems with my Bluetooth keyboard and touch-pad being laggy especially when there is Ethernet traffic ongoing, i don't know if the bus of the Ethernet, the WiFi and Bluetooth card is shared in this SBC. Could you explain me how can i monitor this problem ? to conclude this morning I got a new packages issue, I runned the command "sudo armbianmonitor -u" and i pubblished the results to: https://paste.armbian.com/geyahoxavi

Meanwhile, I upgraded the old rebooting (working) orangepi zero(1)s from U-boot "SPL 2019.04-armbian (Nov 18 2019 - 23:36:05 +0100)" to U-boot "SPL 2024.01-armbian-2024.01-S866c-P6b16-Ha5c2-V367a-Bb703-R448a (Apr 29 2025 - 02:50:09 +0000)" and they also now poweroff on reboot. So the problem is clearly u-boot, and not SD card vendor, kernel (they all run the same "6.12.43-current-sunxi #1 SMP Wed Aug 20 16:30:58 UTC 2025 armv7l") or whatever else. I'll see if I can manage to test U-boot v2025.07... Btw, one thing I noticed with old working boot.cmd/scr was that load_addr was "0x44000000" while it is now "0x45000000" - no idea what significance may have.

One issue with Debian Trixie and encrypted root file systems is that they made some changes. There's an additional package you now need (in addition to cryptsetup-initramfs) prior to updating your initramfs so it will mount an encrypted root: systemd-cryptsetup Despite what this says, I had to install it manually. https://www.debian.org/releases/trixie/release-notes/issues.en.html#encrypted-filesystems-need-systemd-cryptsetup-package

Ah yes indeed. I meant laibsch. Sorry. I made an autoRevert.sh POC that hooks into the initramfs system. Assuming the partition layout described above the following script will revert to the other partition. It is assumed that if an update happened the updater will place a testBoot1 file inside the new boot directory and reboots. During initrd time the script will check for that file and rename it to testBoot2. If the script already detects a testBoot2 it will change the symlink of /boot to the other partition and reboots. Otherwise it is assumed that once the system is up testBoot2 is deleted from the running system if everything works. The script needs to be placed into /etc/initramfs-tools/scripts/init-premount/ and busybox needs to be installed as the script needs the more sophisticated basic commands. Then rebuild initrd. #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" if ! dpkg -s busybox>/dev/null 2>&1; then >&2 echo "Busybox not installed." exit 1 fi } case $1 in prereqs) prereqs exit 0 ;; esac reboot=0 echo mkdir /run/bootRevert mount /dev/mmcblk0p1 /run/bootRevert if [ -L "/run/bootRevert/boot" ]; then echo "/boot is a symlink. OK." cd /run/bootRevert currentTarget=$(readlink "boot") if [ -f "boot/testBoot2" ]; then echo -n "Reverting " if [ $currentTarget = "bootA" ]; then echo "to bootB." if [ -f "bootB/armbianEnv.txt" ]; then rm boot/testBoot2 ln -snf bootB boot reboot=1 else echo "Aborting revert. bootB seems to be empty." fi fi if [ $currentTarget = "bootB" ]; then echo "to bootA." if [ -f "bootA/armbianEnv.txt" ]; then rm boot/testBoot2 ln -snf bootA boot reboot=1 else echo "Aborting revert. bootA seems to be empty." fi fi else if [ -f "boot/testBoot1" ]; then echo "Going to testboot stage 2." mv boot/testBoot1 boot/testBoot2 else echo "No revert/testboot detected. Booting $currentTarget normally." fi fi fi cd / umount /run/bootRevert if [ $reboot = "1" ]; then sync echo "Rebooting..." reboot -f fi It seems then this concept works. As the script checks if /boot in the boot partition is a symlink and then does nothing if not it can also be placed in an unchanged armbian system without interfering. Perfect for creating new images. Still missing are the management scripts for: - converting an initially downloaded armbian image into an AB boot partition scheme - creating an image/update package from a running and well prepared or updated local armbian installation - a cronable management script to call a more specific download script and for switching partitions and rebooting - the download script that will attach to any distribution system that downloads the new update package places it into the other partition and adjusts machine identity; this download script could also just implement a backup of the running partition to the other partition so that switching back is possible if OTA is done using apt All of these can be done in shell.

Board say Orange Pi 5 V1.2

Hi , I am unable to boot my RK3568 board and cannot get it into MaskROM mode for recovery. The boot process fails with a "Synchronous Abort" in U-Boot SPL during DDR initialization. The device gets stuck in a boot loop. It starts DDR training (`ddrconfig:0`) but fails with a Data Abort exception. Standard methods to enter MaskROM /Loader have not worked. I have attached the full serial log (Boot_log.txt). Any guidance would be greatly appreciated. Thank you. Boot_log.txt

@fabiobassa Not work, I did wrongly or something. The rk322x image didn't have this ap6330 dtb overlay, so I pull it from another armbian image

Are u kidding me? This is freaking awesome Thanks guys, I will be patiently waiting..

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Finally there is a proper tor-browser available for arm64/aarch64: 1. Goto https://nightlies.tbb.torproject.org/nightly-builds/tor-browser-builds/ 2. Navigate into: tbb-nightly.<date>/nightly-linux-aarch64/ 3. Download tor-browser-linux-aarch64-tbb-nightly.<date>.tar.xz 4. Unpack with tar -Jxvf and run tor-browser/start-tor-browser.desktop Yay! (I'm sure you can compile it too from their github page)

Hey, has anyone tried using the BPI-3C1-27? Just wondering about price and if it’s really in stock.

Search my threads with keyword "ili9341". Post a photo of your wiring, a schematic, and what did you try within armbian... in this thread.

This is similar to physical damage to the SD card

Those are standard kernel patches. Do you mean Armbian build system does not support multiple patches in a single file? If so, you can download each of the 14 patches individually and then apply them. Or you can try reformatting the combined patch file as a single patch.

Dear Community, I currently want to reduce the transmission power of the NanoPi Neo Air. This means that I simply want to be able to set the Wifi transmission power in 10% steps, for example. What I have already tried: Instructions according to Wiki: OpenWrt image is not flashed. No access via browser. But it doesn't matter: max. transmission power is used in AP mode. Setting as in the Wiki image "TransmitPower:auto" probably does not apply here anyway. Network Manager TUI via "sudo nmtui" has no such settings. Adjust the NVRAM files in "/lib/firmware/brcm" or "/lib/firmware/ap6212" step by step. All changes are saved in the txt file but not written to the host driver. The tests do not recognise any changes. No matter how I adjust the values. (Many different attempts) Firmware patch ("brcmfmac43430a1-sdio.bin") with HxD: The place where "Maxp2ga0" is set is found & edited in binary file. --> 07 60 3F 60 6D 61 78 70 32 67 61 30 = `?`maxp2ga0 Bytes for maxp2ga0: 07 60Bytes for maxp2ga1: 3F 60 3F 60 → 0x603F or 0x3F60 → similar, typically 0x60 = 96 → 20 dBm (Both antenna values have been set) Unfortunately, this change is not loaded into the host driver on the chip either... Continue working on existing "locked" firmware with Seemoo Lab? (unlikely) Throttling Tx-Power via command "sudo iw dev wlan0 set txpower fixed 1500" Change is displayed under "iwconfig wlan0", but it is either overwritten directly or not taken into account at all. No change is noticeable in the tests, no matter how low the value is set. Other firmware & NVRAM tested: Wifi does not start at all (IP rebount reconnect try xx) or the W-Lan is not visible. Maybe you can start here again and find a working firmware that is not "locked"? Which software to use? I test with Putty via the wifi connection. I use the following command: for i in $(seq 1 30); do iw dev wlan0 station dump | awk '/signal/ {print $2}'; sleep 1; done \ | awk '{x[NR]=$1; s+=$1} END{ if (NR>0) {mean=s/NR; for(i=1;i<=NR;i++) v+=(x[i]-mean)^2; sd=sqrt(v/NR); print 'N="NR, "mean="mean, "sd="sd} }' This measures the connection strength in dBm every second, 30 times, and only outputs the mean value. I always have the same 3 measurement positions with the exact same antenna alignment. (In a corridor: 3m, 12m, 25m) Interesting stuff: sudo iw phy phy0 info dmesg | tail -n 50 | grep -i brcmfmac File paths: /lib/firmware/brcm & /lib/firmware/AP6212 CC code (country) is not set by default: "sudo iw reg get" & "sudo iw reg set DE" Are there any other approaches or have I overlooked something? Thank you very much for your help!

Thanks, very helpful. Maybe someone will be able to bring some light on how second partition could appear (uboot update script transition bug?), while being not a part of Armbian's functionality.

This doesn't exactly answer your question, but it may meet your need better... I experimented around with different fans & heatsink configurations. Using an official Debian image from Orange PI 5 Plus, I found that the PWM controlled fan changed speed pretty abruptly, and only at high temperatures. Their adjustment algorithm didn't apply any decent smoothing at all. It was very noisy, and the constant changes whenever I did anything made it very distracting. I ended up purchasing a 3rd party fan with two single-pin leads that I could connect to the GPIO's 3.3v (or 5v). And I have it mounted on a Geekworm case (N508 - made for the Orange PI 5 Plus), with a short heatsink over the ICs. That case had actually come with a fan that had a single 2-pin connector, so it was only good for 5v and about 5 months before it died. From the GPIO, the 5v is on all the time the computer is receiving power, but the 3.3v is only on while the computer is on. If you "shut down" the computer, the 3.3v shuts down along with it. When I first tried the new fan on 5v, it wasn't too bad, but I could hear it. If I ran it off the 3.3v (which I do all the time now), it's virtually silent. When I run something that maxes out the CPU for a long time, with this fan on 3.3v running (and the short heatsink in place), the SoC temperatures stabilize around 50 degrees, and I've never seen them exceed the mid-50s with this setup. That is way lower than that official PWM fan did with that pseudo-heatsink it's mounted on, under the same CPU load. And I never have to worry about the fan quitting if some software PWM control malfunctions. Here's that new fan I bought (it came in a pack of 4): https://www.amazon.com/dp/B08R1CXGCJ?ref=ppx_yo2ov_dt_b_fed_asin_title If you have an N508 or similar type of case, the fan mounts to the top of the case. I checked, and Geekworm is apparently no longer selling that case? But back when I was looking into all this, I had found another very similar case sold by a different company (after I'd already purchased the N508) - I don't remember its name. But the fan it came with came with two single-pin connectors like the fan I eventually ended up staying with.

Or simply add whatever packages you desire with apt.

mihanson@armbi400:~$ sudo poweroff Broadcast message from root@armbi400 on pts/0 (Thu 2025-09-04 07:29:16 PDT): The system will power off now! mihanson@armbi400:~$ [41893.451514] reboot: Power down [41893.454658] ------------[ cut here ]------------ [41893.459337] Voluntary context switch within RCU read-side critical section! [41893.459354] WARNING: CPU: 0 PID: 1 at kernel/rcu/tree_plugin.h:331 rcu_note_context_switch+0x4e0/0x530 [41893.475859] Modules linked in: sg rfcomm cmac aes_arm64 algif_hash algif_skcipher af_alg bnep zram zsmalloc binfmt_misc hci_uart btbcm bluetooth ecdh_generic ecc bcm2835_codec(C) bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) v4l2_mem2mem vc_sm_cma(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_bcm2835(C) videodev snd_pcm videobuf2_common snd_timer mc raspberrypi_hwmon snd raspberrypi_gpiomem i2c_dev drm drm_panel_orientation_quirks backlight fuse bonding ipv6 brcmfmac_wcc brcmfmac cfg80211 rfkill brcmutil uio_pdrv_genirq uio nvmem_rmem [41893.527454] CPU: 0 UID: 0 PID: 1 Comm: systemd-shutdow Tainted: G C 6.12.44-current-bcm2711 #1 [41893.537603] Tainted: [C]=CRAP [41893.540606] Hardware name: Raspberry Pi 400 Rev 1.0 (DT) [41893.545989] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [41893.553048] pc : rcu_note_context_switch+0x4e0/0x530 [41893.558080] lr : rcu_note_context_switch+0x4e0/0x530 [41893.563112] sp : ffff80008002b770 [41893.566466] x29: ffff80008002b770 x28: ffff2262c6ffb3c0 x27: ffff2262c0c5f8c0 [41893.573707] x26: ffff2262c0260000 x25: ffffcc22d85831f4 x24: 0000000000000000 [41893.580947] x23: 0000000000000000 x22: ffff2262c0260000 x21: ffffcc22d98b3070 [41893.588187] x20: 0000000000000000 x19: ffff22637b779fc0 x18: 0000000000000006 [41893.595426] x17: ffffcc22d97fb000 x16: 00000000a53a0512 x15: ffff80008002b0d0 [41893.602666] x14: 0000000000000000 x13: 216e6f6974636573 x12: 206c616369746972 [41893.609905] x11: 6320656469732d64 x10: ffffcc22d96d7a28 x9 : ffffcc22d7724ed8 [41893.617145] x8 : 00000000ffffefff x7 : ffffcc22d96d3960 x6 : 00000000000002b3 [41893.624384] x5 : 00000000000002b4 x4 : 40000000fffff2b3 x3 : 0000000000000000 [41893.631623] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff2262c0260000 [41893.638863] Call trace: [41893.641336] rcu_note_context_switch+0x4e0/0x530 [41893.646016] __schedule+0xb4/0xe70 [41893.649463] schedule+0x3c/0x148 [41893.652733] schedule_timeout+0x98/0x1a0 [41893.656709] wait_for_completion_timeout+0x80/0x160 [41893.661653] mbox_send_message+0xf8/0x140 [41893.665716] rpi_firmware_property_list+0x104/0x298 [41893.670662] rpi_firmware_property+0x78/0xc8 [41893.674988] rpi_exp_gpio_get_polarity+0x68/0x100 [41893.679760] rpi_exp_gpio_dir_out+0x6c/0x120 [41893.684089] gpiod_direction_output_raw_commit+0x6c/0x348 [41893.689562] gpiod_direction_output+0xa8/0x1b8 [41893.694065] gpio_poweroff_do_poweroff+0x2c/0xd0 [41893.698747] sys_off_notify+0x48/0x80 [41893.702458] notifier_call_chain+0x80/0x140 [41893.706699] atomic_notifier_call_chain+0x44/0x70 [41893.711468] do_kernel_power_off+0x5c/0x80 [41893.715618] machine_power_off+0x40/0x58 [41893.719594] kernel_power_off+0x88/0x98 [41893.723479] __do_sys_reboot+0x1e0/0x240 [41893.727452] __arm64_sys_reboot+0x2c/0x40 [41893.731514] invoke_syscall+0x50/0x120 [41893.735314] el0_svc_common.constprop.0+0x48/0xf0 [41893.740083] do_el0_svc+0x24/0x38 [41893.743441] el0_svc+0x38/0x120 [41893.746622] el0t_64_sync_handler+0x120/0x130 [41893.751037] el0t_64_sync+0x190/0x198 [41893.754745] ---[ end trace 0000000000000000 ]--- 25.8.1 Trixie Armbian image and EXT4 FS. Does not happen on reboot, just poweroff. The below also produce the same result. $ sudo shutdown -H now $ sudo systemctl poweroff mihanson@armbi400:~$ armbianmonitor -u Collecting info and sending to paste.armbian.com, wait... Failed grabbing info (pipe 3 result 22) and sending to server paste.armbian.com. Collecting info and sending to paste.next.armbian.com, wait... https://paste.next.armbian.com/oxawoposil Please post the URL in the forum where you've been asked for.