All Activity

Yes, or at least there should be less chances to hit some corner case that reduces the compatibility. LibreELEC is using the mainline kernel only for years though, so it is really strange you have issues with both armbian and multitool. I may wonder there is something odd in the device tree, but it would be odd that a misconfiguration in the device tree causes a kernel fault in the DRM code and in particular in the wait for vblank function 🙄

Hi Guys, I just did a new custom Armbian build ./compile.sh BOARD=orangepi5-plus BRANCH=vendor RELEASE=noble KERNEL_ONLY=yes KERNEL_CONFIGURE=no. The image is Armbian-unofficial_25.11.0-trunk_Orangepi5-plus_noble_vendor_6.1.115_cinnamon_desktop and when I installed it on orangepi I see it is not supporting Panfrost/Mail: glxinfo | grep -E "OpenGL renderer|OpenGL version" OpenGL renderer string: llvmpipe (LLVM 20.1.2, 128 bits) OpenGL version string: 4.5 (Compatibility Profile) Mesa 25.0.7-0ubuntu0.24.04.2 but for older image Old_Armbian-unofficial_25.08.0-trunk_Orangepi5-plus_noble_vendor_6.1.115_cinnamon_desktop All was well glxinfo | grep -E "OpenGL renderer|OpenGL version" OpenGL renderer string: Mali-G610 (Panfrost) OpenGL version string: 3.1 Mesa 25.0.7-0ubuntu0.24.04.2 I did need to enable "ARM Mail Display Processor" under Device Drivers -> Graphics support -> ARM devices before I perform custom build. And I did this for both OS version 25.11.0 and 25.08.0. But newer version is not able to use it. Thanks Manish

Delete the cache and output folder. Try again.

I will try to upgrade to tm16xx driver and be back. As for the HDMI, do you mean that Multitool shoud work anyway? THKS

[🔨] Failed to apply 2 patches: ->0801-net-wireless-backport-aic8800-sdio-v2025_0410_gb99ca8b6-mm2(:1) (+90143/-0)[2M, 135A] {aicwf_firmware_array.c, rwnx_main.c, rwnx_msg_tx.c, aicwf_sdio.c, rwnx_platform.c, lmac_msg.h, regdb.c, aic8800dc_compat.c, rwnx_rx.c, rwnx_debugfs.c, rwnx_tx.c, aic_bsp_driver.c, aicsdio.c, aic_priv_cmd.c, rwnx_mod_params.c, rwnx_radar.c, aic_br_ext.c, rwnx_msg_rx.c, rwnx_txq.c, rwnx_events.h, aic_btsdio.c, aic_vendor.c, aic8800_btlpm.c, lpm.c, aicwf_usb.c, aicwf_txrxif.c, rwnx_tdls.c, ipc_shared.h, rwnx_defs.h, aicwf_compat_8800dc.c, rwnx_mu_group.c, aicwf_tcp_ack.c, aic_bsp_driver.h, rwnx_cmds.c, lmac_mac.h, aic_btsdio.h, aicsdio_txrxif.c, aic_bsp_main.c, rwnx_compat.h, rwnx_gki.c, rwnx_txq.h, rwnx_rx.h, hal_desc.h, aic_vendor.h, btsdio.c, rwnx_dini.c, aicwf_txrxif.h, aic8800d80_compat.c, rwnx_strs.c, rwnx_cfgfile.c, rwnx_testmode.c, aicwf_sdio.h, aicsdio_txrxif.h, rwnx_debugfs.h, rwnx_msg_tx.h, rwnx_tx.h, rwnx_v7.c, rwnx_mu_group.h, ipc_host.h, aicwf_compat_8800d80.c, md5.c, rwnx_radar.h, rwnx_platform.h, aicsdio.h, reg_access.h, usb_host.c, sdio_host.c, rwnx_prof.h, rwnx_utils.h, rwnx_cmds.h, rwnx_bfmer.c, rwnx_bfmer.h, aicwf_usb.h, aicwf_rx_prealloc.c, rwnx_wakelock.c, rwnx_pci.c, aicwf_tcp_ack.h, aic_bluetooth_main.c, rfkill.c, rwnx_mod_params.h, aic_br_ext.h, rwnx_gki.h, rwnx_irqs.c, aic_bsp_export.h, rwnx_testmode.h, aicwf_txq_prealloc.c, lmac_types.h, aicwf_debug.h, rwnx_tdls.h, ipc_host.c, md5.h, rwnx_fw_trace.c, rwnx_mesh.h, rwnx_mesh.c, aic8800dc_compat.h, sdio_host.h, usb_host.h, rwnx_utils.c, aic8800_bsp.mod.c, rwnx_cfgfile.h, rwnx_fw_trace.h, aic_priv_cmd.h, rwnx_strs.h, aic8800_fdrv.mod.c, rwnx_main.h, ipc_compat.h, aic8800d80_compat.h, aicwf_rx_prealloc.h, aic8800_btlpm.mod.c, lpm.h, rwnx_wakelock.h, rwnx_dini.h, rwnx_irqs.h, rwnx_v7.h, rwnx_msg_rx.h, rfkill.h, rwnx_pci.h, aicwf_compat_8800d80.h, aicwf_compat_8800dc.h, rwnx_version.h, aicwf_txq_prealloc.h, rwnx_version_gen.h, aicwf_firmware_array.h, Makefile, Kconfig}<-,->0803-net-wireless-backport-aic8800-usb-v2025_0410_gb99ca8b6-mm2(:1) (+75824/-0)[2M, 128A] {rwnx_main.c, rwnx_msg_tx.c, rwnx_platform.c, aicwf_compat_8800dc.c, lmac_msg.h, regdb.c, rwnx_rx.c, rwnx_debugfs.c, rwnx_tx.c, rwnx_mod_params.c, aicwf_usb.c, aic_priv_cmd.c, rwnx_msg_rx.c, rwnx_radar.c, aic_br_ext.c, rwnx_txq.c, aicwf_txrxif.c, aicbluetooth.c, aicwf_sdio.c, rwnx_events.h, aicwf_wext_linux.c, aic_vendor.c, rwnx_defs.h, ipc_shared.h, rwnx_tdls.c, ipc_host.c, aic_compat_8800d80x2.c, aic_compat_8800d80.c, rwnx_mu_group.c, aicwf_tcp_ack.c, rwnx_cmds.c, lmac_mac.h, rwnx_fw_dump.c, ipc_host.h, aic_txrxif.c, aicbluetooth_cmds.c, rwnx_compat.h, rwnx_rx.h, rwnx_txq.h, hal_desc.h, aic_vendor.h, aicbluetooth_cmds.h, aicwf_txrxif.h, reg_ipc_app.h, rwnx_dini.c, rwnx_strs.c, aicwf_usb.h, rwnx_cfgfile.c, rwnx_testmode.c, aic_txrxif.h, rwnx_debugfs.h, rwnx_msg_tx.h, rwnx_tx.h, rwnx_v7.c, rwnx_mu_group.h, rwnx_platform.h, md5.c, reg_access.h, rwnx_radar.h, usb_host.c, sdio_host.c, rwnx_utils.h, rwnx_prof.h, aicwf_rx_prealloc.c, rwnx_cmds.h, rwnx_bfmer.c, rwnx_bfmer.h, aicwf_sdio.h, rwnx_wakelock.c, aicwf_compat_8800d80x2.c, aicwf_compat_8800d80.c, rwnx_pci.c, aicwf_tcp_ack.h, aic_bluetooth_main.c, rwnx_mod_params.h, aic_br_ext.h, rwnx_irqs.c, rwnx_testmode.h, aicwf_compat_8800dc.h, lmac_types.h, aicwf_txq_prealloc.c, rwnx_tdls.h, aic_compat_8800d80.h, aicwf_debug.h, md5.h, rwnx_main.h, rwnx_fw_trace.c, rwnx_mesh.h, aic_compat_8800d80x2.h, usb_host.h, rwnx_mesh.c, sdio_host.h, aic_load_fw.mod.c, rwnx_utils.c, aicbluetooth.h, rwnx_cfgfile.h, rwnx_fw_trace.h, aic_priv_cmd.h, rwnx_strs.h, aicwf_rx_prealloc.h, ipc_compat.h, rwnx_wakelock.h, rwnx_dini.h, rwnx_irqs.h, rwnx_v7.h, rwnx_msg_rx.h, rwnx_gki.c, rwnx_pci.h, aicwf_wext_linux.h, rwnx_gki.h, rwnx_version.h, aicwf_compat_8800d80.h, aicwf_compat_8800d80x2.h, rwnx_version_gen.h, aicwf_txq_prealloc.h, Kconfig, Makefile}<- [🔨] Summary: kernel patching: 272 total patches; 270 applied; 216 with problems; 154 not_mbox; 152 needs_rebase; 1 invalid_utf8; 3 invalid_diff; 2 failed_apply; 1 overwrites

[🔨] Failed to apply 2 patches: ->0801-net-wireless-backport-aic8800-sdio-v2025_0410_gb99ca8b6-mm2(:1) (+90143/-0)[2M, 135A] {aicwf_firmware_array.c, rwnx_main.c, rwnx_msg_tx.c, aicwf_sdio.c, rwnx_platform.c, lmac_msg.h, regdb.c, aic8800dc_compat.c, rwnx_rx.c, rwnx_debugfs.c, rwnx_tx.c, aic_bsp_driver.c, aicsdio.c, aic_priv_cmd.c, rwnx_mod_params.c, rwnx_radar.c, aic_br_ext.c, rwnx_msg_rx.c, rwnx_txq.c, rwnx_events.h, aic_btsdio.c, aic_vendor.c, aic8800_btlpm.c, lpm.c, aicwf_usb.c, aicwf_txrxif.c, rwnx_tdls.c, ipc_shared.h, rwnx_defs.h, aicwf_compat_8800dc.c, rwnx_mu_group.c, aicwf_tcp_ack.c, aic_bsp_driver.h, rwnx_cmds.c, lmac_mac.h, aic_btsdio.h, aicsdio_txrxif.c, aic_bsp_main.c, rwnx_compat.h, rwnx_gki.c, rwnx_txq.h, rwnx_rx.h, hal_desc.h, aic_vendor.h, btsdio.c, rwnx_dini.c, aicwf_txrxif.h, aic8800d80_compat.c, rwnx_strs.c, rwnx_cfgfile.c, rwnx_testmode.c, aicwf_sdio.h, aicsdio_txrxif.h, rwnx_debugfs.h, rwnx_msg_tx.h, rwnx_tx.h, rwnx_v7.c, rwnx_mu_group.h, ipc_host.h, aicwf_compat_8800d80.c, md5.c, rwnx_radar.h, rwnx_platform.h, aicsdio.h, reg_access.h, usb_host.c, sdio_host.c, rwnx_prof.h, rwnx_utils.h, rwnx_cmds.h, rwnx_bfmer.c, rwnx_bfmer.h, aicwf_usb.h, aicwf_rx_prealloc.c, rwnx_wakelock.c, rwnx_pci.c, aicwf_tcp_ack.h, aic_bluetooth_main.c, rfkill.c, rwnx_mod_params.h, aic_br_ext.h, rwnx_gki.h, rwnx_irqs.c, aic_bsp_export.h, rwnx_testmode.h, aicwf_txq_prealloc.c, lmac_types.h, aicwf_debug.h, rwnx_tdls.h, ipc_host.c, md5.h, rwnx_fw_trace.c, rwnx_mesh.h, rwnx_mesh.c, aic8800dc_compat.h, sdio_host.h, usb_host.h, rwnx_utils.c, aic8800_bsp.mod.c, rwnx_cfgfile.h, rwnx_fw_trace.h, aic_priv_cmd.h, rwnx_strs.h, aic8800_fdrv.mod.c, rwnx_main.h, ipc_compat.h, aic8800d80_compat.h, aicwf_rx_prealloc.h, aic8800_btlpm.mod.c, lpm.h, rwnx_wakelock.h, rwnx_dini.h, rwnx_irqs.h, rwnx_v7.h, rwnx_msg_rx.h, rfkill.h, rwnx_pci.h, aicwf_compat_8800d80.h, aicwf_compat_8800dc.h, rwnx_version.h, aicwf_txq_prealloc.h, rwnx_version_gen.h, aicwf_firmware_array.h, Makefile, Kconfig}<-,->0803-net-wireless-backport-aic8800-usb-v2025_0410_gb99ca8b6-mm2(:1) (+75824/-0)[2M, 128A] {rwnx_main.c, rwnx_msg_tx.c, rwnx_platform.c, aicwf_compat_8800dc.c, lmac_msg.h, regdb.c, rwnx_rx.c, rwnx_debugfs.c, rwnx_tx.c, rwnx_mod_params.c, aicwf_usb.c, aic_priv_cmd.c, rwnx_msg_rx.c, rwnx_radar.c, aic_br_ext.c, rwnx_txq.c, aicwf_txrxif.c, aicbluetooth.c, aicwf_sdio.c, rwnx_events.h, aicwf_wext_linux.c, aic_vendor.c, rwnx_defs.h, ipc_shared.h, rwnx_tdls.c, ipc_host.c, aic_compat_8800d80x2.c, aic_compat_8800d80.c, rwnx_mu_group.c, aicwf_tcp_ack.c, rwnx_cmds.c, lmac_mac.h, rwnx_fw_dump.c, ipc_host.h, aic_txrxif.c, aicbluetooth_cmds.c, rwnx_compat.h, rwnx_rx.h, rwnx_txq.h, hal_desc.h, aic_vendor.h, aicbluetooth_cmds.h, aicwf_txrxif.h, reg_ipc_app.h, rwnx_dini.c, rwnx_strs.c, aicwf_usb.h, rwnx_cfgfile.c, rwnx_testmode.c, aic_txrxif.h, rwnx_debugfs.h, rwnx_msg_tx.h, rwnx_tx.h, rwnx_v7.c, rwnx_mu_group.h, rwnx_platform.h, md5.c, reg_access.h, rwnx_radar.h, usb_host.c, sdio_host.c, rwnx_utils.h, rwnx_prof.h, aicwf_rx_prealloc.c, rwnx_cmds.h, rwnx_bfmer.c, rwnx_bfmer.h, aicwf_sdio.h, rwnx_wakelock.c, aicwf_compat_8800d80x2.c, aicwf_compat_8800d80.c, rwnx_pci.c, aicwf_tcp_ack.h, aic_bluetooth_main.c, rwnx_mod_params.h, aic_br_ext.h, rwnx_irqs.c, rwnx_testmode.h, aicwf_compat_8800dc.h, lmac_types.h, aicwf_txq_prealloc.c, rwnx_tdls.h, aic_compat_8800d80.h, aicwf_debug.h, md5.h, rwnx_main.h, rwnx_fw_trace.c, rwnx_mesh.h, aic_compat_8800d80x2.h, usb_host.h, rwnx_mesh.c, sdio_host.h, aic_load_fw.mod.c, rwnx_utils.c, aicbluetooth.h, rwnx_cfgfile.h, rwnx_fw_trace.h, aic_priv_cmd.h, rwnx_strs.h, aicwf_rx_prealloc.h, ipc_compat.h, rwnx_wakelock.h, rwnx_dini.h, rwnx_irqs.h, rwnx_v7.h, rwnx_msg_rx.h, rwnx_gki.c, rwnx_pci.h, aicwf_wext_linux.h, rwnx_gki.h, rwnx_version.h, aicwf_compat_8800d80.h, aicwf_compat_8800d80x2.h, rwnx_version_gen.h, aicwf_txq_prealloc.h, Kconfig, Makefile}<- [🔨] Summary: kernel patching: 272 total patches; 270 applied; 216 with problems; 154 not_mbox; 152 needs_rebase; 1 invalid_utf8; 3 invalid_diff; 2 failed_apply; 1 overwrites

For some reason I have to delete some packages to install others... Both related an unrelated to this guide. Trying to install packages from step 3C gives an error and can't get this dependency: libelf1. And if I install that package alone, it removes many others, including some from step 2B. Then, if I install again the packages from 2B, it will remove a few from 3C. I'm using Armbian Bookworm Minimal on my Orange Pi 5 Pro, with just a handful of extra packages (including gnome-session, gnome-terminal and firefox-esr).

Hmm. That came across as a bit passive-aggressive, but alright — the question really was poorly phrased and in the wrong place. My intention was to find people from here who had already taken the test... because if documentation were enough, online forums wouldn’t exist 8^)

> ... straightforward and smooth. Same in 25.8.2

@nick a Thanks will check it out

@John Taylor I found the driver source code for your wifi but it's for an older android/linux kernel. I asked info@lb-link.com for the linux/android driver. They sent me SWT6621S_H25.34.7.1_F25.34.6.1.rar

@emor acid The error above says you are missing node or label "reg_gmac_3v3". Add this just below "reg_vcc5v" in in your dts. https://github.com/The-going/linux-sf/blob/aa1ea7ec81c99dbc42f6d2ea4244ab4f54d0f3ee/arch/arm64/boot/dts/allwinner/sun50i-h618-bananapi-m4-berry.dts#L101-L108 reg_gmac_3v3: gmac-3v3 { compatible = "regulator-fixed"; regulator-name = "gmac-3v3"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-on; vin-supply = <&reg_vcc5v>; };

@Unrealchex try the x98h image. Or you’ll need to take the wifi node from x98h and add it to your dts. Not sure why your build stops in the middle of the kernel patches without any errors. Are you sure that's the full log?

Very weird HDMI is not functional in both armbian and multitool: they use very different kernels. Multitool uses the 4.19 vendor kernel, which should be supposed to provide "best" compatibility. The dmesg error is highly related to the missing HDMI, but in a way I can't recognize. About the VFD driver, I guess you're using OpenVFD driver. Latest kernels (both 6.12 and >= 6.16) come with tm16xx driver which is by far much much better and candidate to be upstreamed in the mainline kernel. Here is the github project reference; the driver is already compiled in the kernel, but you may need to edit a device tree overlay by yourself to let it work with your board. To try some debugging, the complete dmesg output and the original device tree of the stock android firmware would be very useful.

Ecco una risposta adeguata per il forum in inglese, considerando il tuo aggiornamento: Hello everyone, I’ve reviewed all the connections carefully using the reference manual to ensure everything is correctly wired. Unfortunately, while the display powers on and stays brightly lit, I still don’t see any output on the screen. Here are a few thoughts and tests I’ve tried: Initialization Problem? I’m unsure if the issue is related to the initialization sequence. I don’t know how to create one tailored to this display. Perhaps this could be due to the fact that it’s an ST7735S, while the driver is designed for the ST7735R? Could this be causing incompatibility issues with the current driver? GPIO Changes: I’ve also experimented with changing the GPIO configurations, specifically: dc-gpios = <&pio 2 6 1>; /* changed the 1 to 0 */ r eset-gpios = <&pio 2 9 1>; /* changed the 1 to 0 */ However, this had no effect. Kernel Compatibility: When I use a kernel version 5.x, the display works correctly. But with the current configuration and the newer kernel, I can’t seem to get it to work. This might be a kernel-level issue, or perhaps something changed in how the driver is initialized. Temporary Workaround: I’ve ordered another display to rule out any potential hardware issues, but it will take a while to arrive. At this point, I’m unsure of how to proceed. If anyone has advice on adapting the driver for ST7735S or creating a compatible initialization sequence, I’d greatly appreciate it. Thanks in advance for your help!

Still not clear why HDMI not working, However VFD display based n FD650 is working. Attached the vfd.conf file for openvfd: clock , USB, ETH,WIFI and COLON working. vfd.conf

Some manufactures change the wifi and lan controllers to keep prices down on new BOM of materials: @WINEDS got experience with thos problems https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/page/16/#comment-210825 https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/#findComment-217289 https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/#findComment-216154

Please share your .desktop file... with sensitive information redacted.

@MartinB Official DXVK won't work, because it requires some Vulkan extension/features that Mali drivers don't have. So, I build the stripped versions that remove most of the requirements. You can download it here https://github.com/khanh-it/dxvk/actions https://github.com/pythonlover02/DXVK-Sarek/actions Just extract it into the game's folder and allow dlls overrides in wine.

Hello. Sorry to be late. I succeed, I find the image to be installed. I think it was debian-12.11.0-arm64-netinst.iso.

Hi @Nick A Please help me. I have H96 MAX H313 and Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11 work well, but no wifi I tried several times to compile with your instuctions, but every time during compilation I get a lot of warnings and eventually a compilation error. What I was doing: I don't understand all this very well, but I see that there is a way to solve the problem. If it's not too much trouble, may I ask you to describe step by step what I should do? I would be very grateful. I attach a log file and a photo of my board. build logs.md

@khanhdtp Excellent What does DXVK-stripped mean, and where did you get it / how did you prepare it? Is it just the normal DXVK v2.7.1 from the github? Cheers.

hi, Compilation error, I also decompiled the dts available for Android for reference output.dts @Nick A

it works OK on stock kernel, but there's some strange things with network/routing. I use static IP with static default route, and often when I run wget or apt install I've got 'network unreachable'; ping 8.8.8.8 -i 0.1 (or other IP not from internal subnet; for ex., external IP of router) - may ping OK without any losses for a seconds and then loss packets for seconds or even tens of seconds, or may report 'ping: Do you want to ping broadcast? Then -b. If not, check your local firewall rules' and exit. IPs from internal subnet are pinged OK. but when I tried to add static route for some external IP via default gateway - it starts to work OK, and works OK even when route is removed. does anybody noticed such strange things?

A known issue with the Odroid XU4, HC1, and HC2 is that it (uboot?) does not properly park the hard disk heads before/during shutdown or power cycle/off. So, the disk drive is forced to emergency hard retract the heads when power is shutdown/cycled. This is of course a violent action for the HDD and should be avoided. Use this odroid.shutdown script and install into /lib/systemd/system-shutdown/. https://wiki.odroid.com/odroid-xu4/troubleshooting/shutdown_script Recommend adding to armbian for XU4 distros.