Active threads

Do you get sound (HDMI) through your monitor speakers with the official vendor image?

https://fi.mirror.armbian.de/apt/pool/noble-utils/b/base-files/ They are in. Perhaps need some time for repo to get in sync.

Addressing the need for reliable hardware testing for RISC-V adoption, the RISE Project and Collabora added two RISC-V boards to Collabora's LAVA testing lab. View the full article

Building a rolling release is more than just showing that in the MOTD. If you do "sudo apt upgrade" in an OS image you just built, you probably will have zero or one packages to upgrade. If you start with an image built a long time ago, or with packages defined a long time ago, then "sudo apt upgrade" would take a long time.

I have the same debian as you: 5.1.4-xxx-v4l2request, installed over Debian Bookworm, with Linux 6.15 (OS built by myself). When I tried the ffmpeg-7.x.x-v4l2request for Trixie, I could not get hardware acceleration.

Banana Pi M2 Berry – My Advice This board is a pain. It can’t boot from SSD. An SSD can hit ~200 MB/s, but you’ll need a strong 5 V power supply – especially at startup it often needs 3 A or more. If it refuses to boot (happened to me a lot), the cause was almost always a weak PSU. Other issues: the V40 SoC has almost no proper support and was never optimized. That means no real 3D acceleration – if it works at all, it’s unstable. Sound output often doesn’t work, HDMI audio basically never worked for me. Wi-Fi usually works, but only 2.4 GHz and WPA2 max. If you want more, you’ll need a compatible USB stick – but even then you’re limited to ~15 MB/s because it’s just USB 2.0. If you want >100 MB/s, you’ll need to use the LAN port and write to SSD. Forget doing that on the SD card. To be honest, almost nothing that came out after 2020 runs well as an OS on this thing. The official ISOs are here: 👉 https://wiki.banana-pi.org/Banana_Pi_BPI-M2_Berry You can test them if you like – they all run “meh” at best. As I said, 3D acceleration is rare, and when it exists it’s terrible. Another option to test: 👉 https://docs.banana-pi.org/en/BPI-M2_Berry/BananaPi_BPI-M2_Berry For me, the best (and really the only sensible) choice right now: 👉 https://sd-card-images.johang.se/boards/banana_pi_m2_berry.html But it’s pure/light – console only. You have to install everything else yourself. If you’ve ever managed a root server, you know the path: tmux/screen for multi-window SSH, sudo apt install apache2 -y, MariaDB, mail server, SSL certificates (yes, free ones), dynamic DNS, Pi-hole, cronjobs, and so on. Everything works, but you’ll need patience and some hand-holding (AI copilots can help). If you don’t have time for all that: get something better. Realistically, all you can use this board for today is as a shell server. Nothing else works properly. Honestly, even an old smartphone is a thousand times better. That’s why the M2 Berry was already dirt-cheap when I bought it in 2017 (€18 😂💩). Bottom line: The only sensible use is as a shell server. For anything else it’s useless – the drivers are crap, the V40 has almost no support. An old laptop or smartphone will serve you better (and it will run latest linux and 3d accel..) and by the way SPI or something like that can be also used over special boards/esp2066/esp32 and more ... And Banana Pi M2 Berry as an emulator? Forget about it ... PS: To write proper image files on Windows, I use Rufus or PowerISO (on Windows 11, UAC probably needs to be turned off).

No, he's problem is much more simpler. He have JTAG and UART wired on his board, so it's not a problem to do virtually anything with his box. Are you sure? Have you successfully connected adb on PC to this tv box using usb cable?

It is shown on internet how to get maskrom, serIal, and more. Also there is a clue that this box should start with firefly dtb but not stated exactly. Things are different from 1997 now and getting this working without experience is very difficult. With kernel 4.4 you could try with android dtb.

I've a similar issue but on a different board nanopi m4v2. Could you also help me in troubleshooting the problem? In addition to video problems at 4K I'm getting also Bluetooth problems with my keyboard. Feel free to ask for extra info.

Etcher used to be / is broken. https://docs.armbian.com/User-Guide_Getting-Started/#flash-to-sd-card https://docs.armbian.com/User-Guide_Troubleshooting/

Hi @Ed van den Enden, Looks like the on-chip RTC is used for initial time-setting by the kernel in your case. It also seems that the overlay to enable i2c is now loaded correctly! I can help with two options, you can choose which one you want to use: Option 1: Use the `rtc-sync` script with the cronjob and systemd modification. Option 2: Use the user-overlay that will move the I2C "external" RTC to the first slot, naming it `rtc0`. The on-chip RTC will move to the second slot, `rtc1`. Option 1 will need more modifications in your configuration, but will work nonetheless. You can find the script attached here: Put the rtc-sync script in /usr/local/sbin/. Change onwership/permissions: sudo chown root:staff /usr/local/sbin/rtc-sync sudo chmod 0775 /usr/local/sbin/rtc-sync Create the cronjob /etc/cron.d/rtc-sync as follows: #min hr mon day dow run-as command 30 * * * * root /usr/local/sbin/rtc-sync -Ad update Modify ntp service unit file by adding the following to the end of the file (/lib/systemd/system/ntpsec.service OR /lib/systemd/system/ntp.service depending on which ntp package you have installed): # Added to sync wallclock to an external RTC [Service] ExecStartPre=-/usr/local/sbin/rtc-sync -A -d start ExecStopPost=-/usr/local/sbin/rtc-sync -A -d stop Option 2 will require adding the user-overlay file and changing only your armbianEnv.txt. I can only give you the user-overlay i used that works for the orangepi zero, but as this uses the same CPU as your board, it should work. if it does not work, you will always have option 1 as fallback. You can find the user-overlay (rtc1-soc.dts) and the instruction on how to compile and add this to armbianEnv.txt in this topic here: The user-overlay is also included down here: In addition to the user-overlay, you will also need to disable the `fake-hwclock` service, as that tries to emulate a real RTC by reloading the last known wallclock from a file that was created when the system was shutdown/rebooted. Instructions for this also in the same linked topic. Pick your option and try it out. If it all works well, for option 2 you will find that the i2c RTC is named rtc0, for option 1 you will see i2c RTC is still rtc1, but the rtc-sync script, cronjob and systemd modification will use the i2c RTC to set the wallclock (after it's set improperly by rtc0). Feel free to check back in if it still does not work. Groetjes,

Maybe try another power adapter Or add to /boot/armbiEnv.txt extraargs=pcie_aspm=off nvme_core.default_ps_max_latency_us=0 pci=pcie_bus_safe Otherwise you could try an image of Radxa first, if that works then it might be an issue with the dtb

I have two of these cheap Chinese sticks and I was wondering if I could load a better OS onto them I think there's only a USB port

That's why I am here To ask for help I could not find any installable packages I am a novice user

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: ................................................................ But in my opinion the module is not working properly 😞 I'll be more precise, it works OK... but OrangePi3LTS is a weak device and the option/module: v4l2loopback and the ffmpeg program that transmits/splits the image to two programs (motion/ustreamer) causes high CPU usage... but it works OK, so my problem is solved

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?

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.