Active threads

@c0rnelius I'm missing technical knowledge to help... Digging the Internet I saw similar bluetooth issue for radxa zero 3w with aic8800, resolved using hciattach / hci up, but needing an available /dev/ttyS1 (UART1) we are missing here... Do you know why? Could it be the problem for banana pi m4 zero and if yes could an overlay activate it? Denis

Thank you for the reply ! I see — is there any version of Armbian or another distro that has working HDMI output and graphics drivers ?

Hi, Then the only other difference would be that your device has a pin tied to usb0-vbus. The topwise dts does not have the display nodes included in the cubieboard. Now as you are currently kernel 6.1, it is possible to enable the display via overlays or compile a version of the topwise dts that includes the display nodes. So the internal display does not work under 6.1? Are there any kind of errors or does it not appear to intialise at all? Cubieboard nodes (*Note - Nodes other than hdmi and usb related have been removed): /dts-v1/; #include "sun4i-a10.dtsi" #include "sunxi-common-regulators.dtsi" #include <dt-bindings/gpio/gpio.h> / { model = "Cubietech Cubieboard"; compatible = "cubietech,a10-cubieboard", "allwinner,sun4i-a10"; hdmi-connector { compatible = "hdmi-connector"; type = "a"; port { hdmi_con_in: endpoint { remote-endpoint = <&hdmi_out_con>; }; }; }; }; &de { status = "okay"; }; &hdmi { status = "okay"; }; &hdmi_out { hdmi_out_con: endpoint { remote-endpoint = <&hdmi_con_in>; }; }; &reg_usb1_vbus { status = "okay"; }; &reg_usb2_vbus { status = "okay"; }; &usb_otg { dr_mode = "otg"; status = "okay"; }; &usbphy { usb0_id_det-gpios = <&pio 7 4 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>; /* PH4 */ usb1_vbus-supply = <&reg_usb1_vbus>; usb2_vbus-supply = <&reg_usb2_vbus>; status = "okay"; }; Topwise a721: /dts-v1/; #include "sun4i-a10.dtsi" #include "sunxi-common-regulators.dtsi" #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/input/input.h> #include <dt-bindings/interrupt-controller/irq.h> #include <dt-bindings/pwm/pwm.h> / { model = "Topwise A721"; compatible = "topwise,a721", "allwinner,sun4i-a10"; panel { compatible = "starry,kr070pe2t"; backlight = <&backlight>; power-supply = <&reg_lcd_power>; port { panel_input: endpoint { remote-endpoint = <&tcon0_out_panel>; }; }; }; reg_lcd_power: reg-lcd-power { compatible = "regulator-fixed"; regulator-name = "reg-lcd-power"; gpio = <&pio 7 8 GPIO_ACTIVE_HIGH>; /* PH8 */ enable-active-high; }; }; &de { status = "okay"; }; &reg_usb0_vbus { status = "okay"; }; &reg_usb1_vbus { status = "okay"; }; &reg_usb2_vbus { status = "okay"; }; &tcon0_out { tcon0_out_panel: endpoint@0 { reg = <0>; remote-endpoint = <&panel_input>; }; }; &usb_otg { dr_mode = "otg"; status = "okay"; }; &usb_power_supply { status = "okay"; }; &usbphy { usb0_id_det-gpios = <&pio 7 4 GPIO_ACTIVE_HIGH>; /* PH4 */ usb0_vbus_det-gpios = <&pio 7 5 GPIO_ACTIVE_HIGH>; /* PH5 */ usb0_vbus-supply = <&reg_usb0_vbus>; usb1_vbus-supply = <&reg_usb1_vbus>; usb2_vbus-supply = <&reg_usb2_vbus>; status = "okay"; }; It is possible to build just uboot using the BUILD_ONLY=uboot option. Again here you could face potential issues as newer uboot might not work well with an old kernel. All the best Ryzer

Vontar X3 is the same as hk1-x3 and I used the one from hk1-x3. Here are the pictures because I didn't open mine: https://github.com/ophub/amlogic-s9xxx-armbian/issues/1006

You can build an armbian image with these instructions:https://docs.armbian.com/Developer-Guide_Build-Preparation/ You can configure it: https://docs.armbian.com/ When you have a setup you like, use this to backup as an image: https://forum.armbian.com/topic/29427-shrink-backup-a-tool-for-backing-up-sbcs/ I still suggest only armbian... but please share if you can use buildroot for opiz2w

Restarted with vendor kernel, then same actions: [ 580.015977] BTRFS info (device loop0p2): dev_replace from /dev/loop0p2 (devid 1) to /dev/loop1p2 started [ 599.501402] cma: cma_alloc: cma: alloc failed, req-size: 1024 pages, ret: -12 [ 599.502431] kworker/6:4: page allocation failure: order:10, mode:0xcc0(GFP_KERNEL), nodemask=(null),cpuset=/,mems_allowed=0 [ 599.502452] CPU: 6 PID: 239 Comm: kworker/6:4 Tainted: G W 6.1.115-vendor-rk35xx #1 [ 599.502457] Hardware name: FriendlyElec NanoPi R6C/NanoPi R6C, BIOS v1.1 04/09/2025 [ 599.502461] Workqueue: events atomic_pool_work_fn [ 599.502471] Call trace: [ 599.502474] dump_backtrace+0xf0/0x12c [ 599.502480] show_stack+0x20/0x30 [ 599.502484] dump_stack_lvl+0x7c/0xa0 [ 599.502489] dump_stack+0x18/0x34 [ 599.502493] warn_alloc+0xe0/0x17c [ 599.502498] __alloc_pages+0x524/0x854 [ 599.502501] atomic_pool_expand+0x8c/0x268 [ 599.502506] atomic_pool_resize+0x50/0x64 [ 599.502510] atomic_pool_work_fn+0x44/0x54 [ 599.502515] process_one_work+0x1c0/0x274 [ 599.502521] worker_thread+0x1dc/0x274 [ 599.502525] kthread+0xc4/0xd4 [ 599.502529] ret_from_fork+0x10/0x20 [ 599.502534] Mem-Info: [ 599.502537] active_anon:465 inactive_anon:13222 isolated_anon:0 active_file:37602 inactive_file:1830958 isolated_file:0 unevictable:4 dirty:1679 writeback:166667 slab_reclaimable:15924 slab_unreclaimable:27052 mapped:16566 shmem:499 pagetables:621 sec_pagetables:0 bounce:0 kernel_misc_reclaimable:0 free:12582 free_pcp:127 free_cma:0 [ 599.502546] Node 0 active_anon:1860kB inactive_anon:52888kB active_file:150408kB inactive_file:7323832kB unevictable:16kB isolated(anon):0kB isolated(file):0kB mapped:66264kB dirty:6716kB writeback:666668kB shmem:1996kB writeback_tmp:0kB kernel_stack:4416kB pagetables:2484kB sec_pagetables:0kB all_unreclaimable? no [ 599.502554] DMA free:24920kB boost:0kB min:5448kB low:9248kB high:13048kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:956kB inactive_file:3784292kB unevictable:0kB writepending:29608kB present:3929344kB managed:3825428kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB [ 599.502561] lowmem_reserve[]: 0 0 3902 3902 [ 599.502567] Normal free:25408kB boost:0kB min:5712kB low:9696kB high:13680kB reserved_highatomic:2048KB active_anon:1860kB inactive_anon:52888kB active_file:149060kB inactive_file:3539556kB unevictable:16kB writepending:643228kB present:4194304kB managed:3996056kB mlocked:16kB bounce:0kB free_pcp:556kB local_pcp:0kB free_cma:0kB [ 599.502574] lowmem_reserve[]: 0 0 0 0 [ 599.502580] DMA: 97*4kB (UM) 103*8kB (UM) 95*16kB (UME) 101*32kB (UME) 61*64kB (UME) 22*128kB (UME) 7*256kB (U) 7*512kB (UME) 5*1024kB (UME) 1*2048kB (U) 0*4096kB = 25228kB [ 599.502601] Normal: 962*4kB (UME) 377*8kB (UME) 140*16kB (UMEH) 43*32kB (UMEH) 22*64kB (UME) 25*128kB (UME) 17*256kB (UM) 4*512kB (ME) 5*1024kB (UME) 0*2048kB 0*4096kB = 26608kB [ 599.502621] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB [ 599.502624] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=32768kB [ 599.502628] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [ 599.502631] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=64kB [ 599.502634] 1869148 total pagecache pages [ 599.502636] 0 pages in swap cache [ 599.502639] Free swap = 10873596kB [ 599.502641] Total swap = 10873852kB [ 599.502643] 2030912 pages RAM [ 599.502645] 0 pages HighMem/MovableOnly [ 599.502648] 75541 pages reserved [ 599.502650] 2048 pages cma reserved [ 624.681251] BTRFS info (device loop0p2): dev_replace from /dev/loop0p2 (devid 1) to /dev/loop1p2 finished So although it works, a rather strange side effect with CMA makes me feel that the system could be unstable now. I have seen CMA related errors before on RK35xx, but that was with U-Boot, this is with UEFI firmware, where I maybe forgot to change a setting or so. At least HDMI display is blank, serial console and ssh works.

It is Allwinner H618, Quad-core ARM Cortex™-A53 processor. I meant which Eth chip is used in your case Bananapi-m4-berry: h618 ==> Eth chip rtl8211f ==> connecting socket Bananapi-m4-zero: h618 ==> Eth chip ???? ==> connecting socket As far as I understand, this is some kind of expansion card for the 26 pin connector. Can you post a diagram of this expansion board here. The brand of the Ethernet chip matters.

Notice, translation by ChatGPT. Hi everyone! I have an MX10 F3 TV stick running Android for a specific purpose, but I believe it could be more efficient with Armbian. I'm testing Nick's image Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11_xfce_desktop.img.xz on a microSD. It works well, except for Wi-Fi and Bluetooth — the chip is AIC8800. I don’t know how to install the patch that has been shared. I also haven’t been able to make it work by installing the firmware and SDIO from https://github.com/geniuskidkanyi/aic8800 @Nick Aif you plan to release future versions, do you intend to include native support for the AIC8800 chip?

sorry for the typo, it is Kernel 6.12.30 that still doesn't support usb

Hello everyone, I'm currently working on a custom firmware project for the Allwinner V851S/V851SS SoC (e.g., dash cam or smart camera). I've reached the stage where I need to modify and re-sign the firmware images (TOC0/TOC1) for use with tools like PhoenixCard. Unfortunately, the tools found on GitHub (e.g., dragonsecboot, pack_tools, boot0, etc.) are often incomplete or fail to build due to missing references (e.g., rsa_sign_main, GetFullPath, etc.). 🔍 I'm looking for a complete and working version of the following tools: dragonsecboot pack boot0 sunxi_tools Full config files such as dragon_toc.cfg, sys_config.fex Working pack_tools with all required source files Full Tina SDK for V851S or V851SS 🎯 My goal is to properly sign and rebuild TOC0/TOC1 and PACKAGE images, and build a customized embedded Linux system. 📤 If anyone has the official SDK or a working toolchain, I’d really appreciate it if you could share it via Google Drive, Mega, Transfer.sh, or any other file host. Thank you in advance to anyone who can help 🙏

Building on our Open Source strengths in AI and data-driven solutions, Collabora's ML team, led by Marcus Edel, Vineet Suryan, & Aaron Boxer, has taken first place in Track 3 of the ICME 2025 Grand Challenge on Video Super-Resolution for Video Conferencing. View the full article

It sounds like you're in a tough spot with your x88 box, but there are definitely a few things you can try to unbrick it. Check Power Supply: As you mentioned, the power supply might be outputting 13V, which is not ideal. It's crucial to have a stable 5V supply for the device to boot properly. If you can, try using a different power adapter (5V, 2A) and see if that helps stabilize the boot process. Use a Correct Recovery Image: Make sure you're using the correct image for the box. It seems like you were trying to burn the image directly, but if the process was interrupted, it could leave your internal storage in an inconsistent state. Try downloading the official firmware for your box model from the manufacturer's site (if available) or from trusted forums where users with similar devices share their files. Try the USB Burning Tool: Some boxes like this one can be recovered using a tool like the USB Burning Tool (if it's based on Rockchip). You can try flashing the firmware through USB using the tool while the box is in recovery mode. Here’s a general approach: Download and install the USB Burning Tool. Put your box into MaskROM Mode (this usually involves shorting specific pins or pressing a button while plugging the box into your computer via USB). Connect your device to the PC and use the USB Burning Tool to flash the firmware. Serial Console Output: If you're comfortable with it, connecting a serial console to the box can give you a lot of insight into where things are failing. This could help identify whether it's a hardware or software issue. The serial output could give you error messages that could point to a specific issue (e.g., faulty bootloader or file system corruption). SD Card Recovery: If you can't get it to boot from the internal flash, continue using the SD card with a stable Armbian image. If the internal storage is corrupt, you might still be able to boot and recover your box through the SD card by reinstalling the firmware on the internal storage via the system running off the SD card. If you haven't already, you could also try reaching out to the manufacturer or seller for support, as they might be able to help you with the recovery process. But if that’s not an option, digging into the serial console is definitely your best bet. Good luck! Hopefully, you'll be able to get your device back up and running soon.

Good day, respected Balbes150. Please advise an Armbian build for the Roc-rk3588s-pc v1.1, with support for an M.2 NVMe SSD, intended to be used as a "smart home" server. The image will be installed on an SD card. The single-board computer is connected to the home router via Ethernet cable. HDMI is only used temporarily to connect to a TV for initial setup (further configuration will be done via SSH). The board will run Docker containers. Thank you so much in advance!

Hello, Any update of this?

They will provide you new drivers only if you will pay them to do that for you. End users, including this project, can do nothing about - we have negative budget and can only do best-effort work to keep those drivers at least operational with recent kernels: https://github.com/armbian/build/tree/main/patch/misc while bulk of the patches goes directly to the Git of specific driver. What you are hoping exceeds ability of amateur maintainers, those few people that are actually looking into the code and fix bugs that are made by kernel API changes. HW vendor is usually long gone from there - their development capacity is also limited and they are focused into current products. FYI

there are a few caveats that may need a bit of attention It is documented somewhere that if you use channel 0, the driver would automatically select an appropriate channel / frequency. However, it seemed that back then initially while I tested it, that didn't seem to work. (i'm not sure if it may have changed) hence to list the channels one needs to run iw list and you would get a list of channels like such * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (20.0 dBm) * 2472 MHz [13] (20.0 dBm) * 2484 MHz [14] (20.0 dBm) * 5170 MHz [34] (disabled) * 5180 MHz [36] (20.0 dBm) * 5200 MHz [40] (20.0 dBm) * 5220 MHz [44] (20.0 dBm) * 5240 MHz [48] (20.0 dBm) * 5260 MHz [52] (20.0 dBm) (radar detection) * 5280 MHz [56] (20.0 dBm) (radar detection) ... * 5720 MHz [144] (20.0 dBm) (radar detection) * 5745 MHz [149] (20.0 dBm) * 5765 MHz [153] (20.0 dBm) * 5785 MHz [157] (20.0 dBm) * 5805 MHz [161] (20.0 dBm) * 5825 MHz [165] (20.0 dBm) what I normally do is to do a scan and pick an unused / least used channel : iw wlan0 scan pick an appropriate channel and specify it in hostapd.conf. 5ghz channels (hw_mode=a) delivers a max throughput of like 140 Mbps which is fast. https://docs.armbian.com/WifiPerformance/#uwe-5622 accordingly there are some country specific requirements for 5ghz channel selections and one may like review https://en.wikipedia.org/wiki/List_of_WLAN_channels iw reg set etc I did a google search and some of these resources may be useful https://wiki.archlinux.org/title/NetworkManager https://www.baeldung.com/linux/nmcli-wap-sharing-internet in a same way you may need to set the channel if necessary then that this repo is found in a google search which may be useful https://github.com/pi-top/Wi-Fi-Access-Point-and-Station-Mode/tree/master

I'm trying to compile an LED display driver: https://github.com/arthur-liberman/linux_openvfd I follow this description: https://github.com/bk3a12/openvfd_enable_for_tx3_mini However, I can't build anything and the whole process ends with errors: sh ./scripts/modules-check.sh /home/user/INSTALKI/linux_openvfd/driver/modules.order make -f ./scripts/Makefile.modpost make[3]: *** No rules to make an object '/home/user/INSTALKI/linux_openvfd/driver/modules.order', required by '/home/user/INSTALKI/linux_openvfd/driver/Module.symvers'. Stop. make[2]: *** [/usr/src/linux-headers-6.12.33-current-meson64/Makefile:1897: modpost] Error 2 make[1]: *** [Makefile:224: __sub-make] Error 2 make[1]: Leaving the directory '/usr/src/linux-headers-6.12.33-current-meson64' make: *** [Makefile:5: modules] Error 2

@werner Sorry the delay, I was trying to get the TTL adapter. Here is what I get from the TTL in the first boot after flashing Armbian_community_25.8.0-trunk.228_Orangepi5pro_bookworm_vendor_6.1.115_minimal.img DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 ch0 ttot7 LPDDR5, 2400MHz channel[0] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch1 ttot7 channel[1] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch2 ttot7 channel[2] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch3 ttot7 channel[3] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB Manufacturer ID:0xff DQS rds:l0,l0 CH0 RX Vref:27.1%, TX Vref:20.0%,20.0% DQ rds:h3 h4 h2 h1 h5 h2 h2 h1, h1 h3 h3 h5 h1 h3 h2 h2 DQS rds:l0,h1 CH1 RX Vref:27.9%, TX Vref:21.0%,20.0% DQ rds:l0 h1 h2 h3 h6 h2 h3 h6, h4 h2 h2 h2 h2 h1 h4 l0 DQS rds:l0,l0 CH2 RX Vref:26.7%, TX Vref:19.0%,21.0% DQ rds:h3 l0 l0 l0 h4 h1 h7 h3, h2 l0 h1 l0 h2 h4 h1 h1 DQS rds:l0,h1 CH3 RX Vref:27.9%, TX Vref:20.0%,20.0% DQ rds:h5 h3 h7 h4 h2 h2 h4 h4, h4 h3 h4 h2 h3 h1 h3 h1 stride=0x2, ddr_config=0x6 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0x0 0x2400 0x44800 0x89000, rank_mask0 0 x2000 change to F1: 534MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F2: 1320MHz ch0 ttot8 ch1 ttot8 ch2 ttot8 ch3 ttot8 change to F3: 1968MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F0: 2400MHz ch0 ttot7 ch1 ttot7 ch2 ttot7 ch3 ttot7 out U-Boot SPL board init U-Boot SPL 2017.09 (Jun 13 2025 - 02:18:34) unknown raw ID ff ff ff unrecognized JEDEC id bytes: ff, ff, ff Trying to boot from MMC1 Card did not respond to voltage select! spl: mmc init failed with error: -95 Trying to boot from MMC2 Card did not respond to voltage select! spl: mmc init failed with error: -95 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### # Reset the board to bootrom # Not sure if it matters, but I have a EMMC installed and flashed the image to it using the rkdevelop tool. ( The same way I do to flash the firmware from orangepi site ) Just in case, here are the commands I use ./rkdeveloptool db MiniLoaderAll.bin ./rkdeveloptool wl 0 Armbian_community_25.8.0-trunk.228_Orangepi5pro_bookworm_vendor_6.1.115_minimal.img ./rkdeveloptool rd

Hi, I also tried to run this sensor, tried different ports but to no avail. maybe you found a way to solve this problem?

Share the image of your assembly, preferably server-side.

I think I solved it! In the upgraded system there was no package pahole! After I installed the pahole and reinstalled the package linux-headers-6.12.33-current-x86, I got the BTF stuff as described above in the .config file and I can compile modules! Pfff, finally! I checked the Raspberry Pi 4 version, I see no pahole package installed there, and I can compile modules and zfs. I don't see any BTF stuff in the .config there also. So, I don't know what is really going on here, I should install pahole on arm64 systems as well? And should pahole not be included when you upgrade your system to 25.5.1 ?

Thanks a lot for your help, Igor. That did not make the trick, as the available packages are still in the old form (docker.io instead of docker-ce for example. Nonetheless, I now have a working (but old) docker binary, which is enough for my use case. Now, I will try to build a more recent docker binary. The next problem to solve will be to get the NVMe to work. I'm sorry your F3 died.

accordingly H618 do not have mic in hardware https://www.cnx-software.com/2023/07/03/orange-pi-zero-3-allwinner-h618-sbc-ships-with-up-to-4gb-ram/ hence, an option is to use a usb soundcard / dongle https://www.aliexpress.com/w/wholesale-usb-sound-card.html there are also those 'arduinoish' approaches e.g. to use a ADC module board e.g. https://www.ti.com/lit/ds/symlink/ads1110.pdf https://www.aliexpress.com/w/wholesale-ads1110.html https://www.instructables.com/Arduino-and-the-TI-ADS1110-16-bit-ADC/ but that you would need to hack the pin interfaces to use i2c etc. note it seemed ads1110 is a bit too slow for sound. alternatives are like stm32, which has built-in adc that can go to like 1-2.5 Msps, but you would need to hack the spi interface etc. the 'easiest / cheapest' way seemed to be generic 'usb sound cards'

Has a fixed image been posted? Just upgraded to 25.5 from 25.2, so havent tested a new image download yet.

probably best to specify location for any sales offer