Active threads

SBC Orange Pi Zero V1 is still a popular SBC and is still sold on the market, among other things, because it has an integrated sound card and for this reason, a lot of hamradio operators still buy this model because it allows you to build very compact mobile hotspots without having to attach a USB sound card protruding outside the housing and that is why it is very popular and still sold despite the fact that versions V2 and V3 have been released, so it is not an SBC that has completely gone down in history.

I haven't tested this... but I see that pins PH1, PI11, PI14 are not connectable in the orange pi zero 3. Only PH3 would be connectable. Is this correct? Is there an overlay to get PWM in PH2? (i read in the post from April 5 that it can be a PWM pin)

The problem was resolved by upgrading. I had been running Armbian_25.5.1_Orangepi5_bookworm_vendor_6.1.115_minimal and everything was was fine except after a reboot, there would be an Oops error. I reimaged the machine with Armbian_25.5.1_Orangepi5_bookworm_current_6.12.28_minimal and the problem has been resoled.

Thank you, I found the manual for initramfs-tools and hooks ... it looks like I can do it

Hello WDR_s, If you upgraded kernel recently, did you have any problem starting X11 (or lightdm, or desktop)? I started with a downloaded arm minimal image with linux 6.12, and my DTS would bring up the panel-mipi-dbi-spi driver correctly in text mode, but X11 can't start. When I have my normal 99-fbdev.conf, I get this: FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument, When I remove 99-fbdev.conf and let X11 setup everything automatically, X11 complains about needing panel-mipi-dbi_dri.so. I restored an old armbian OS backup with linux 6.11, and everything worked normally. You are using a different LCD driver, did you have any problem?

just like to say that the recent images works just well _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v25.8 rolling for Orange Pi Zero3 running Armbian Linux 6.12.35-current-sunxi64 Packages: Debian stable (bookworm) Support: for advanced users (rolling release) IPv4: (LAN) xxx.xxx.xxx.xxx (WAN) yyy.yyy.yyy.yyy IPv6: fd00:xxxx:xxxx::xxxx:xxxx (WAN) xxxx:xxxx::yyyy:yyyy WiFi AP: SSID: (ssid), Performance: Load: 2% Uptime: 3:50 Memory usage: 4% of 3.83G CPU temp: 41°C Usage of /: 3% of 58G RX today: 7 MiB Commands: Configuration : armbian-config Monitoring : htop

Hello Laibsch, I sent an email to Michael two weeks ago, but I didn't get an answer from him. Do you know a way how to reach him ? Bernd

You are right, supporting a board family is a different thing 🙂 The board can have different hardware (nic, wlan, usb .... ) But sorry im was only care about the processor, and if i'm not wrong, the SOC is completely the same (cpu, gpu, apu). Maybe some minor differences (frequencies etc). And so im looked about the kernel / user modules regarding the cpu/gpu not for the complete image 🙂 But looks like the situation is the the same there, for different features( vpu / openGLES / vulkan) you need special kernel / image versions.

Sorry this Post. https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/page/94/#comment-212510

Sadly no. https://github.com/armbian/build/tree/main/config/boards There are (too) many boards in the system, added by random people (this is build system and we accept anything that builds, but we don't maintain those boards as we can't afford associated costs / there are not enough resources), but only supported / .conf are recognized until there is someone willing to maintaining them and fits condition of "supported" board. When we find out that conditions are not met anymore, they are "un-recognized". Support is defined under those rules: https://docs.armbian.com/User-Guide_Board-Support-Rules

root@rock3a:/lan/tmp# ffmpeg -i file1.AV1.mkv -c:v hevc_rkmpp -c:a copy file1.x265.mkv ffmpeg version 5.1.6-0+deb12u1 Copyright (c) 2000-2024 the FFmpeg developers ... Unknown encoder 'hevc_rkmpp' root@rock3a:/lan/tmp# /usr/share/jellyfin-ffmpeg/ffmpeg -i file1.AV1.mkv -c:v hevc_rkmpp -c:a copy file1.x265.mkv ffmpeg version 7.0.2-Jellyfin Copyright (c) 2000-2024 the FFmpeg developers ... [out#0/matroska @ 0xaaaaeff1e660] video:223157KiB audio:6460KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 0.220596% frame=27421 fps=138 q=-0.0 Lsize= 230124KiB time=00:15:21.52 bitrate=2045.7kbits/s speed=4.64x video plays fine You might have power issues, that is my thirst thought, as I had several issues with my rock3a when I used USB-C (so with default PD with 5V). Now 12V in and user on-board DC-DC to do proper feeding. OPi5 does not have this AFAIK from schematics. But is is a wild guess. Many other things can be wrong, like who knows something with iommu (I guess not). I might try same command sometime later on my NanoPi-R6C when I will upgrade Armbian from Bookworm to Testing/Trixie, it also has RK3588S, same as OPi5, but check this, it is just top-of-my-head. I use mainline kernels mostly now, so need to tune grub or so first.

OK thanks. I am just trying to take a working copy of the NVME installation and create a back-up image file, just as I do with Windows installations, for restore in case of emergency. I had hoped that because I could transfer a live system from SD card to NVME, then I might be able to do something similar the other way. As I said above, all I was getting from the various attempts were errors of either Not a directory, No such file or directory or Is a directory But now that I know that it is not possible this way, I shall boot from a separate installation and hope that things work from there. I am still concerned about the 3 errors that I was continually receiving and would like to get the DD syntax correct, so that I can see what I need to do.

Don't know where to report this as Armbian bug reporting form refused to accept community supported board, but it may not necessarily be board-specific. When logging the first time there is a message: sed: -e expression #1, char 0: no previous regular expression Generating locales: en_US.UTF-8 _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v25.8 rolling for radxa cubie a5e running Armbian Linux 6.14.0-rc1-dev-sun55iw3 Packages: Debian stable (bookworm) Updates: Kernel upgrade enabled and 2 packages available for upgrade Support: for advanced users (rolling release) sed: -e expression #1, char 0: no previous regular expression Performance: Load: 6% Uptime: 17 min Memory usage: 7% of 1.93G CPU temp: 54°C Usage of /: 15% of 6.7G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop The second login does not show this message. Hope this helps

labwc is available in debian trixie: Start with a minimal armbian install Make sure your /dev/fb0 is DRM, not framebuffer $ sudo apt install seatd labwc foot $ labwc -s foot

🤩🤪 super , thanks for the information

hcitool does see something, but bluetoothctl still does not $ hcitool scan Scanning ... 41:BB:00:D0:D3:D8 Baseus Bowie WM02

Sorry I did not provide enough info. I am using Debian bookworm, completely updated as far as I know, and it looks like you might be using Ubuntu. Maybe I needed to use bookworm-backports as you suggested; it looks like a newer version there. I've actually found another way to do what I was trying to do with v4l2loopback and don't need it anymore, but thanks for looking at it. Here is some output that you asked for: _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.5.1 for Renegade running Armbian Linux 6.12.32-current-rockchip64 Packages: Debian stable (bookworm) IPv4: (LAN) 10.0.44.17, 192.168.4.254 (WAN) 107.77.207.5 Performance: Load: 50% Up time: 0 min Memory usage: 13% of 968M CPU temp: 36°C Usage of /: 13% of 30G Commands: Configuration : armbian-config Monitoring : htop Last login: Sat Jul 5 20:21:20 2025 from 10.0.44.1 pburt@gato:~$ cat /etc/debian_version 12.11 pburt@gato:~$ apt-cache policy v4l2loopback-dkms v4l2loopback-dkms: Installed: (none) Candidate: 0.12.7-2 Version table: 0.13.2-1~bpo12+1 100 100 http://deb.debian.org/debian bookworm-backports/main arm64 Packages 100 http://deb.debian.org/debian bookworm-backports/main armhf Packages 0.12.7-2 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 500 http://deb.debian.org/debian bookworm/main armhf Packages pburt@gato:~$ sudo apt install v4l2loopback-dkms [sudo] password for pburt: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: dkms Suggested packages: menu Recommended packages: fakeroot The following NEW packages will be installed: dkms v4l2loopback-dkms 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 86.0 kB of archives. After this operation, 308 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://deb.debian.org/debian bookworm/main arm64 dkms all 3.0.10-8+deb12u1 [48.7 kB] Get:2 http://deb.debian.org/debian bookworm/main arm64 v4l2loopback-dkms all 0.12.7-2 [37.2 kB] Fetched 86.0 kB in 1s (119 kB/s) Selecting previously unselected package dkms. (Reading database ... 71668 files and directories currently installed.) Preparing to unpack .../dkms_3.0.10-8+deb12u1_all.deb ... Unpacking dkms (3.0.10-8+deb12u1) ... Selecting previously unselected package v4l2loopback-dkms. Preparing to unpack .../v4l2loopback-dkms_0.12.7-2_all.deb ... Unpacking v4l2loopback-dkms (0.12.7-2) ... Setting up dkms (3.0.10-8+deb12u1) ... Setting up v4l2loopback-dkms (0.12.7-2) ... Loading new v4l2loopback-0.12.7 DKMS files... Building for 6.12.32-current-rockchip64 Building initial module for 6.12.32-current-rockchip64 Error! Bad return status for module build on kernel: 6.12.32-current-rockchip64 (aarch64) Consult /var/lib/dkms/v4l2loopback/0.12.7/build/make.log for more information. dpkg: error processing package v4l2loopback-dkms (--configure): installed v4l2loopback-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: v4l2loopback-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) pburt@gato:~$ cat /var/lib/dkms/v4l2loopback/0.12.7/build/make.log DKMS make.log for v4l2loopback-0.12.7 for kernel 6.12.32-current-rockchip64 (aarch64) Sun Jul 6 06:20:57 PM CDT 2025 Building v4l2-loopback driver... make -C /lib/modules/6.12.32-current-rockchip64/build M=/var/lib/dkms/v4l2loopback/0.12.7/build modules make[1]: Entering directory '/usr/src/linux-headers-6.12.32-current-rockchip64' CC [M] /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.o /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.c: In function ‘vidioc_querycap’: /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.c:717:9: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration] 717 | strlcpy(cap->driver, "v4l2 loopback", sizeof(cap->driver)); | ^~~~~~~ | strncpy cc1: some warnings being treated as errors make[3]: *** [scripts/Makefile.build:229: /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.o] Error 1 make[2]: *** [/usr/src/linux-headers-6.12.32-current-rockchip64/Makefile:1945: /var/lib/dkms/v4l2loopback/0.12.7/build] Error 2 make[1]: *** [Makefile:224: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-6.12.32-current-rockchip64' make: *** [Makefile:43: v4l2loopback.ko] Error 2 pburt@gato:~$

Okay, so I ran a little experiment to verify that it's not about mocp but rather something about the file or file system: $ cp -a /mnt/music/_INCOMING/Malukah\ -\ The\ Dragonborn\ Comes\ \(2017\)/01\ -\ Awake.flac 01.flac Segmentation fault The resulting file contains 9175040 Bytes instead of the expected 9593429, so is truncated. Consequently I also see the corresponding dmesg output parrots what I showed before. So it's about exfat, it appears. Prior to the upgrade did I move the file over to an ext4 partition as well (as I guessed it would be impossible with the 6.12.30-current-sunxi kernel). Copying that around, including _to_ the USB key doesn't seem to cause any issues. I'll see if I am able to figure out how to get the clusters of that particular file. Perhaps it becomes reproducible elsewhere with a (trimmed down) disk image? 2025-07-06_dmesg.txt

This would be very very hard. Would likely take years and would likely never achieve full functionality. If you have access to the source code for the firmware that comes on the device you would have a chance.

Right, judging by only one instance in the topwise a721 dts: [ 3.446799] sun4i-drm display-engine: No panel or bridge found... RGB output disabled I am inclined to think that is configuring the panel. This can be validated by checking ls /sys/devices/platform/display-engine/drm/card0 or looking for simple-panel in lsmod. I suspect it may be a pin-muxing issue where the pins are not being set. now what these are set depends on the lcd panel type which could be LVDS or a parallel panel. I believe it should be LVDS but just wanted to confirm. Now the A10's pin controller section within the dtsi does not map out as many function compared A20 dtsi, so within the topwise a721 dts under the pio node the display pins need to be declared and their function stated. Secondly attach the pin control handle to tcon0. For example: &pio { lvds0_pins: lvds0-pins@0 { pins = "PD0", "PD1", "PD2", "PD3", "PD4", "PD5", "PD6", "PD7", "PD8", "PD9"; function = "lvds0" }; }; &tcon0 { pinctrl-names = "default"; pinctrl-0 = <&lvds0_pins>; };

I can do that but it does not provide any useful information on the subject in my opinion. Is there a way to downgrade to 25.8.0-trunk.313? According to this post, it might be useful to set the kernel option nvme_core.default_ps_max_latency_us resp. the DT overlay parameter pciex1_gen=3. How can the kernel (cmdline) option be set in Armbian? Regarding the DT overlay parameter pciex1_gen, should I follow this part of the documentation?

The issue appears to be two things. These two patches and the current defconfig(s) being used. drv-rtc-sun6i-support-RTCs-without-external-LOSCs.patch drv-rtc-sun6i-Add-Allwinner-H616-support.patch When I disable those patches and use my own defconfig everything works as it should. https://paste.armbian.com/tixixocubu The hard part here would be figuring out exactly what in the defconfig(s) are either breaking things or missing. Also if I disable those patches, what does it break on other units? I'm under the impression these patches were rejects from the original h616 bring up in mainline. But I could be wrong?

If you need hdmi support use vendor or edge kernel. 6.12 was released with a bare minimum of support for rk3588 so nonworking hdmi is kind a expected.

I added a patch that activates the gpu. https://lore.kernel.org/linux-sunxi/20250706025625.2707073-1-iuncuim@gmail.com A ready to install kernel is available for manjaro. But it's worth realizing that without output it will be useless at the moment.

I've gone round in circles with this one and it seems that there might not be a solution, so will set it up again on the NVME drive. Thanks for all the help offered.