c0rnelius

@KrzyPac You apply the patch to the kernel source-tree, In this case we will use meson64 as an example. Add the patch to: patch/kernel/archive/meson64-6.12/ Enable in the defconfig: echo "CONFIG_OPENVFD=m" >> config/kernel/linux-meson64-current.config Build a new IMG or KERNEL as one normally would for your unit. general-drv-auxdisplay-Add-openvfd-driver.patch

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

As far as I know openvfd needs to be re-worked to support 6.12.y and up.

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.

@ScoreABSM I don't think that is the reason? No, I haven't solved the Bluetooth issue. I have theories, but I still haven't cracked the nut. You are more than welcome to give it a whirl

@KrzyPac Ur welcome.

@KrzyPac I suspect you just need the DTB correct? Git clone the armbian/build, place the patch in patch/kernel/archive/meson64-6.12/ and build any meson64 board. ./compile.sh KERNEL_GIT=shallow BRANCH=current EXPERT=yes KERNEL_BTF=no kernel BOARD=bananapicm4io The DTS files are one of the first things to be compiled, so once you see them finish, hit CTRL+C to cancel the build and then grab the DTB file from the source dir: cache/sources/linux-kernel-worktree/6.12__meson64__arm64/arch/arm64/boot/dts/amlogic/ That is the easiest way I can think of doing what you want to achieve. Here is an updated PATCH and pr-ecompiled DTB. NOTE: There are different variants of the X96-AIR. I have two. One that uses Qualcomm for wireless and another that is Realtek. Each variant requires a different DTS for it to function properly. This patch is for the Realtek variant. x96-air-gbit-spdif-jack-i2c1-openvfd-jl2xx1-bt-support.patch meson-sm1-x96-air-gbit.dtb

Ah gotcha.

Not sure what you mean by outdated? Gets updated often or when needed; https://github.com/jwrdegoede/rtl8189ES_linux/tree/rtl8189fs

If the u-boot on the unit supports USB Boot, yes. GXL:BL1:9ac50e:bb16dc;FEAT:ADFD318C:0;POC:3;RCY:0;EMMC:800;NAND:81;SD:800;USB:8;LOOP:1;EMMC:800;NAND:81;SD:800;USB:8;LOOP:2;EMMC:800;NAND:81;SD:800;USB:8;LOOP:3;EMMC:0;READ:0;0.0;CHK:0; The above looks like USB Mode. This Mode is for flashing vendor or custom imgs to the unit via USB. This is for recovery.

https://github.com/armbian/build/pull/8191

@ScoreABSM can I see the dmesg?

There are big differences between the two revisions. The biggest one is, one is using Wifi/BT over USB and the other SDIO, which requires the sdio overlay. The reason for BT not working on Armbian, I have yet to figure out. Like I said before, it works on (my personal) a more minimal build; Debian GNU/Linux trixie/sid 6.12.26 #1 Sun May 4 17:50:23 EDT 2025 aarch64 BananaPi BPI-M4-Zero v2 ── DISK Filesystem Size Used Avail Use% Mounted on /dev/mmcblk2p2 29G 2.8G 26G 10% / /dev/mmcblk2p1 466M 74M 363M 17% /boot ── NETWORK Hostname: bananapim4zero Wireless: wlan0 UP 10.0.0.XX Bluetooth: hci0 AC:6A:A3:3B:D9:D6 ── SYSTEM Processor: Cortex-A53 @ 1416MHz 52°C Frequency: 1416MHz Online: 0-3 Governor: performance Memory: 3.8G 199M Entropy: 256 Uptime: 15:13:05 up 4 min, 1 user, load average: 0.01, 0.06, 0. It is hard for me to determine the reasons BT doesn't work, as the patching is very extensive. If it is even the patching? And yes I include the BT node in the overlay; https://github.com/armbian/build/blob/main/patch/kernel/archive/sunxi-6.12/patches.armbian/Add-BananaPi-BPI-M4-Zero-overlays.patch#L267 As for HDMI audio and GPU, the PR I posted a link to corrects this. In future releases and rolling (give it a day) it should now work. Although I think I need to now add my changes to the 6.14.y branch? I'll check.

@ScoreABSM Should fix part of the problem; https://github.com/armbian/build/pull/8191 As for Wifi, it works fine for me. Make sure you have an antenna attached or it may not find anything on the network to connect to. As one user already discovered;

The GPU node needs to be enabled. There has been adjustments made to the patching for 6.12.y and above, but I haven't messed with yet. Basically nodes need to be added for sound. As for Bluetooth. I haven't figured out yet why it doesn't work on Armbian. In my personal builds it works fine. I believe there is some patching or service preventing it from loading. But I can't be sure. I've put a lot of time already into the DTS to get this working on both REVS. To much time in my opinion. Anyone is welcome to do a PR and add and enable the bits if they like. Otherwise peps are just gonna have to wait till I get around to it again.