Active threads

OrangePi 4A Bluetooth Mouse Keyboard connectivity issue Solved The solution to the problem when mouse pairs / connects with BT but doesnt work Prebuilt kernel files are available https://github.com/defencedog/orangepi4A/blob/main/Bluetooth%20Mouse%20Not%20Working%20Solved.md

Yes it worked fine on the other Armbian OS. Unfortunately it still doesn't work. android-vontar-x3.dts

While searching the forum and the documentation, I found the list of mirrors. On some of them, it's possible to find an older version of Armbian (23.11.1). I installed that version and it seems the drivers are working — I was able to use HDMI. This is the mirror I used: https://armbian.atomonetworks.com/archive/cubieboard/archive/

Please, I need an img of Armbian compatible with the following: RK3399T and with HDMI. I have tried all versions of Armbian and they do not work. Some do, but the problem is that it does not display an image. I believe it could be the HDMI. The most preferable versions for me are Armbian Noble or Bookworm. The problem also occurs during updates. After updating, the wireless does not work. If there is a version with this fixed, I would be grateful if someone could post a version for me, as up-to-date as possible. My Radxa is a Rock Pi 4Plus v1.73. With a 256GB microSD, I need an img of Armbian that is compatible with wireless and HDMI. If anyone can send me the link, I would be grateful!

True. Also on most computers we have eth0 Not just eth Devices naming is a cosmetic thing from the outside / user perspection, while it has consistency issue from the inside and currently breaks initial (default netplan) configuration. Our job is not to tell user how to configure his network, but that network devices gets up at first boot. Now they do. Job done.

Hi Loeriver, Where is the other end of your USB serial dongle connected to? Can you check there if the dongle had disappeard from the USB bus and re-appeared around the same time? In my "professional" life we have had workstations mysteriously reboot whenever we would power cycle the device hosting the USB to serial device. Even though you say it's not related, if this is still mysterious, best to check under each stone... Groetjes,

From the picture - I can only guess that kernel package was somehow not upgraded properly as kernel image files are missing. Perhaps they were removed by accident or there was some disk / file system troubles involved. @Chris007 Try hints from here: https://docs.armbian.com/User-Guide_Troubleshooting/

This is being worked on https://lore.kernel.org/linux-sunxi/20250526002924.2567843-1-james.hilliard1@gmail.com/T/#t There is a version of this that was ported over from a vendor kernel to Armbian. https://github.com/armbian/build/pull/6617

Okay, then you have to adjust the source to mitigate the issue. Also log excerpts are often useless. My random guess is that uboot is some old outdated version depending on python2 which has been deprecated years ago.

Last month in Nice, active media developers came together for the annual Linux Media Summit to exchange insights and tackle ongoing challenges in the media subsystem. Here’s a brief summary of the key discussions and upcoming areas of focus. View the full article

duplicate

To anyone this may help, removing hc4 related packages and replacing them with c4 packages did the job. Only to discover that, for whatever reason, I actually had an HC4 board and convince myself that it was a C4 ... Anyway, the reverse process also worked as expected and my board is now running 25.051.1 happily, except for the samsung SSD not recognized at boot, and requires to be hot plugged just after the linux kernel starts in order to be seen by the system, as it is described in other threads.

They have a repository on Mega and Baidu. https://wiki.sipeed.com/hardware/en/longan/h618/lpi3h/3_images.html

As far as I know openvfd needs to be re-worked to support 6.12.y and up. EDIT: I stand corrected. I found a working patch at unifreq. It needs to be patched against the source-tree. 0001-drv-auxdisplay-Add-openvfd-driver.patch

@junji. Can you explain me how you proceed to boot this OS image Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11_xfce_desktop.img.xz ?

I have same hardware issue here. Did you fix this problem?

For a few weeks I've been using the latest official release from May 26, 2025, running just fine from my NVME drive. But then I turned it on and at the screen where you get the Amrbian grey/red logo in the middle of the screen and the spinning circle, it went no further. The spinning circle would either stop rotating or disappear after a minute or so. I can SSH into the device. But when I use remote desktop from a Windows PC, the full and functioning desktop is there. It's just not on my TV screen any more. I've done the usual HDMI cable testing and powering off the TV completely, but no change. The fact that the desktop is accessible remotely does indicate that it must be loading in some fashion. Took a log here: https://paste.next.armbian.com/qococumoga

Thank you for letting us know, much appreciated. Have you tried to reach out to Michael Hawkins, the maintainer?

Hello all Is anybody having success with spidev with orange pi zero 3 and Linux 6.12? I want to test my LCD panel's touch, but I need spidev working first

Hi again, one quick question -- I previously made the mistake of running apt upgrade of the system packages and had installed armbian-configNG over the included armbian-config, so I basically nuked the SD card and reinstalled the image to roll back to the old config. This likely has been covered, but is there a way to reinstall armbian-config or is this a known issue and "DON'T UPGRADE" ? Cheers!

It's a progress! This or similar problem was seen / reported on H3 too.

Here is a more vanilla build of the kernel. patrick@bananapim4zero:~$ ls /dev/ttyS* /dev/ttyS0 /dev/ttyS3 /dev/ttyS5 /dev/ttyS7 /dev/ttyS2 /dev/ttyS4 /dev/ttyS6 patrick@bananapim4zero:~$ sudo rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 unblocked unblocked 1 wlan phy0 unblocked unblocked patrick@bananapim4zero:~$ bluetoothctl hci0 new_settings: powered bondable ssp br/edr le secure-conn Agent registered [CHG] Controller AC:6A:A3:3B:D9:D6 Pairable: yes [bluetoothctl]> exit patrick@bananapim4zero:~$ uname -a Linux bananapim4zero 6.12.32 #1 SMP Sat Jun 7 17:23:51 EDT 2025 aarch64 GNU/Linux patrick@bananapim4zero:~$ dmesg | grep brcm [ 9.007064] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 9.007614] usbcore: registered new interface driver brcmfmac [ 9.303238] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 9.303576] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Aug 29 2023 01:47:08 version 7.45.265 (28bca26 CY) FWID 01-b677b91b [ 9.430799] Bluetooth: hci0: BCM4345C0 'brcm/BCM4345C0.sinovoip,bpi-m4-zero.hcd' Patch As you can see the Bluetooth works fine. If I add these two patches it breaks bluetooth on this kernel build. drv-rtc-sun6i-support-RTCs-without-external-LOSCs.patch drv-rtc-sun6i-Add-Allwinner-H616-support.patch I'm still investigating in my spare time, but I'm not 100% on anything. Could be I need to take another approach to the bluetooth node in Armbian? So this is where am at. If anyone has any thoughts I'm all ears.

I consider the btrfs issue 'solved', from past experience I know sometimes explicit balancing is needed for certain blockdevice level or lowlevel operations, like conversion of profiles, for example single into raid1, there must be enough unallocated space so new 1GB chunks can be created, especially on the originating device as it is all fundamentally copy-on-write so at least extra/double space for 1 system, meta, data chunk shall be available and I simply forgot to check/realize that. Further enhancements to Btrfs that this is done automatically somehow means likely that I first need to browse the kernel mailing list and see what people like David Sterba are doing nowadays. The CMA issue I suspect maybe it is related to power supply. Because of testing, I needed to take the NanoPi-R6C to another room where i used a 65W 'white-label branded' USB-C PD PSU that I got delivered with a refurbished laptop. That PSU has once shown under-voltage on an RPi4, so I expect too much ripple (when 5V). Besides the CMA issue, lateron also sudden hard reset of the NanoPi-R6C when I was doing networked backup, was 2x ethernet + HDMI + NVMe + eMMC active and that could mean >3A when only 5V. When I also took my RPI5 27W USB-C PD PSU to that room and used that, no strange issues anymore, so running fine at least with EDK2-UEFI and Armbian kernel 6.15.2-edge-rockchip64 and Bookworm or Tumbleweed userspace (and KDE Wayland). I have never seen PD working on the NanoPi-R6C and the powering circuit looks a lot like ROCK3A w.r.t. staged DC-DC conversion. And I use Armbian mainline based U-Boot or EDK2-UEFI, not the original FriendlyWrt installation with some 2017 based U-Boot. Also for that original one, I doubt that it does USB-C PD to request 9V or higher. I assume not, looking at: https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R6C#PD_Power_Adapters_We_Tested https://wiki.friendlyelec.com/wiki/index.php/Template:PDPowerWeTested There is also nothing about USB-C PD under https://www.friendlyelec.com/Forum/viewforum.php?f=81 so I assume: Great HW but SW/OS support is abandoned and DIY. That also means, same as for ROCK3A and ROCK5B, solder some 12V wire to a male USB-C connector and use that in order to be sure power won't drop too much when e.g. some USB3 HDD/SSD is inserted. Or limit cables to only RPI5 PSU and WAN/1GB ethernet (and still Samsung 970 NVMe, that works OK, even when 800% CPUload). Or check/see if PD handling is available in denx.de/mainline U-Boot.

Yes exactly

New topic created: