Active threads

Update: The reason i haven't released the cursor patch is because im working on the GUI. I managed to now use EGLFS with FFMPEG, so it feels right that we modernized the crankshaft-ng GUI to feel more modern and usable.

Hi guys, I have a Espressobin V7_2-1 Model: Marvell Armada 3720 Community Board ESPRESSOBin (eMMC) CPU 1000 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 800 [MHz] DRAM: 1 GiB Would you be so kind as to make the flash-image-DDR4-1g_1cs_5-1000_800.bin?

Bluetooth now working, no compiling required via hciattach. I don't know how much of this is necessary because I generally don't know what I'm doing. But here goes. Apparently hciattach is a legacy app that requires the firmware to be in /etc/firmware so I made a folder and setup a symlink before running the hciattach. <NOT REQUIRED> sudo mkdir -p /etc/firmware <NOT REQUIRED> sudo ln -sf /lib/firmware/aic8800_sdio/*.* /etc/firmware sudo hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep <NOT REQUIRED> sudo hciconfig hci0 up Bluetooth should be available now. You can test it with sudo hcitool -i hci0 scan This will display any devices in the area the bluetooth adapter has detected. I had installed armbian-firmware package so that might also be required but I doubt it. I will flash a new image and start from scratch just to make sure everything I've stated works on a fresh install and then update the thread. Edit: I tested it on a fresh image and the only command required for bluetooth to activate was the hciattach line. I couldn't figure out how to do strikethrough in the code block so I just listed added the "NOT REQUIRED" info. I didn't want to remove them in case it helps someone else. The firmware files I mentioned in a previous post need to copied over and the device powered down before running the hciattach command. The hciattach commands do not persist through a reboot so I need to figure out how to get this to run on startup, hopefully the easy part. Thanks for all the help. Hard to beat that feeling when you spend hours troubleshooting something and it fires up for the first time!

Some context: https://docs.armbian.com/User-Guide_FAQ/#why-things-stop-working The hardest part and expensive for time is keeping functions working while kernel changes, goes up. Image you are referring too is probably a demo image with some ancient kernel that will never be changed. This is usual way to sell hardware. It is made to work, but you will stay at this very old SW stack without any real option to change or fix anything. All functions on 300+ boards, which on top of extreme diversity, have also different revisions, quality issue ... is already not possible to keep up by entire open source community. Armbian is small part focused into SBCs and we do what we can. Work we are doing is never complete, we (nobody) can't solve bugs and especially not near to (expected) real-time. We (or community open source in total) can address a problem within weeks or months fastest as resources are tiny compared to problems that are constantly found in open source code that somebody else made. We have no option to expand the team / project as users don't care about well being of SW developers. We can only try to keep SW stack operational on a best effort principle. Once this job becomes too expensive (<1% of costs share is on users side), we have to step back and declare support as "community". We will continue to build and ship images as they might still work for some use cases and as downstream projects will provide those Armbian images anyway.

A month ago when doing test boots and power measurements, see I discovered that when using the RPL 27W 'Pi5' PSU, the NanoPi-R6C with the indicated bootloader(s) and kernel(s) sticks to 5V. But when using a 45W USB-C PD PSU from a HP laptop or 60W USB-C PD PSU white-label, switch is made I saw on a USB-C PD power measurement device that was also in the chain. More detailed USB-C PD protocol analysis seems to be needed in order to figure out what happens. One could guess 3A is requested at highest possible voltage as with the 45W PSU, I saw 15V. 9V or 12V would also be OK, but the PD handler cannot be 100% sure I think, depends also what is inserted in USB type-A ports on device etc.

does emmc working yet?

armbianmonitor - u result: https://paste.armbian.com/nocetohemu Best regards Rolf

@Nick A Oh yeah, I did change a few things as well for type c. Maybe the drm heap changes are not needed after all. Looking at my changes. husb311 is now under drivers/power/typec, so just enable it. et7304 is not included in the original bsp, radxa team added them later so simply apply this same patch. https://github.com/radxa/allwinner-bsp/commit/156b6578cc173855b41ea311a229403ccbadb17c

Hi, I wanted to report an issue with the currently available Armbian images for the PocketBeagle 2 (all of them from what I can tell), that stops them from booting up. I attempted to go through the bug reporting form, but it seems to only point you to the forum, so here I am. I couldn't find a location to post about the PocketBeagle 2 board specifically, so I am putting this under the Beagle Y board (they have the same maintainer listed). Please move this to the right place (or maybe create it if it doesn't exist?) or tell me how I should do this myself. The issue is in the file "/boot/extlinux/extlinux.conf", where a ".dts" file is being referenced from the directory "/boot/dtb/ti/", which contains only ".dtb" files. U-Boot fails to find the device tree file and fails to boot. Changing the file extension of the device tree in "extlinux.conf" to ".dtb" fixes the boot up issue and everything else seems to be working fine. If this is not the right place to be reporting this issue, please direct me to the correct place, so this can be brought to the attention of the appropriate maintainer. It should be a quick fix, but the images currently available to download are likely unusable for inexperienced users. Many Thanks, Paul

With new python based build system there is error compiling headers while installing headers deb. Im not sure is it because of new build system or the problem is in 6.1.15 kernel branch. My compile command was: ./compile.sh BOARD=orangepione BRANCH=current BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=yes KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,img SKIP_EXTERNAL_TOOLCHAINS=no BUILD_KSRC=no PRIVATE_CCACHE=yes RELEASE=bionic ARTIFACT_IGNORE_CACHE=yes BUILD_KSRC=yes KERNEL_GIT=full While installing i got: igor@honeypot:~/trash/debs$ ls -1 armbian-config_23.05.0-trunk_all.deb armbian-firmware_1-SA56ad-Bf566_all.deb linux-dtb-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb linux-headers-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb linux-image-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb linux-u-boot-orangepione-current_2022.07-Se092-P12e0-Be261_armhf.deb igor@honeypot:~/trash/debs$ sudo dpkg -i * [sudo] password for igor: (Reading database ... 107907 files and directories currently installed.) Preparing to unpack armbian-config_23.05.0-trunk_all.deb ... Unpacking armbian-config (23.05.0-trunk) over (23.02.0-82) ... dpkg: warning: downgrading armbian-firmware from 23.02.0-82 to 1-SA56ad-Bf566 Preparing to unpack armbian-firmware_1-SA56ad-Bf566_all.deb ... Unpacking armbian-firmware (1-SA56ad-Bf566) over (23.02.0-82) ... dpkg: warning: downgrading linux-dtb-current-sunxi from 23.02.0-82 to 6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8 Preparing to unpack linux-dtb-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb ... Armbian 'linux-dtb-current-sunxi' for '6.1.15-sunxi': 'preinst' starting. + rm -rf /boot/dtb + rm -rf /boot/dtb-6.1.15-sunxi + set +x Armbian 'linux-dtb-current-sunxi' for '6.1.15-sunxi': 'preinst' finishing. Unpacking linux-dtb-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) over (23.02.0-82) ... dpkg: warning: downgrading linux-headers-current-sunxi from 23.02.0-82 to 6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8 Preparing to unpack linux-headers-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb ... Armbian 'linux-headers-current-sunxi' for '6.1.15-sunxi': 'preinst' starting. + [[ -d /usr/src/linux-headers-6.1.15-sunxi ]] + set +x Armbian 'linux-headers-current-sunxi' for '6.1.15-sunxi': 'preinst' finishing. Unpacking linux-headers-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) over (23.02.0-82) ... dpkg: warning: downgrading linux-image-current-sunxi from 23.02.0-82 to 6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8 Preparing to unpack linux-image-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb ... Armbian 'linux-image-current-sunxi' for '6.1.15-sunxi': 'preinst' starting. + export 'DEB_MAINT_PARAMS=upgrade 23.02.0-82 6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8' + DEB_MAINT_PARAMS='upgrade 23.02.0-82 6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8' + export INITRD=Yes + INITRD=Yes + test -d /etc/kernel/preinst.d + run-parts --arg=6.1.15-sunxi --arg=/boot/vmlinuz-6.1.15-sunxi /etc/kernel/preinst.d update-initramfs: Deleting /boot/initrd.img-5.15.93-sunxi Removing obsolete file uInitrd-5.15.93-sunxi + mountpoint -q /boot + set +x Armbian 'linux-image-current-sunxi' for '6.1.15-sunxi': 'preinst' finishing. Unpacking linux-image-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) over (23.02.0-82) ... Preparing to unpack linux-u-boot-orangepione-current_2022.07-Se092-P12e0-Be261_armhf.deb ... Unpacking linux-u-boot-orangepione-current (2022.07-Se092-P12e0-Be261) over (23.02.0-82) ... Setting up armbian-config (23.05.0-trunk) ... Setting up armbian-firmware (1-SA56ad-Bf566) ... Setting up linux-dtb-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) ... Armbian 'linux-dtb-current-sunxi' for '6.1.15-sunxi': 'postinst' starting. + cd /boot + ln -sfT dtb-6.1.15-sunxi dtb + set +x Armbian 'linux-dtb-current-sunxi' for '6.1.15-sunxi': 'postinst' finishing. Setting up linux-headers-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) ... Armbian 'linux-headers-current-sunxi' for '6.1.15-sunxi': 'postinst' starting. + cd /usr/src/linux-headers-6.1.15-sunxi ++ grep -c processor /proc/cpuinfo + NCPU=4 + echo 'Compiling kernel-headers tools (6.1.15-sunxi) using 4 CPUs - please wait ...' Compiling kernel-headers tools (6.1.15-sunxi) using 4 CPUs - please wait ... + yes '' + make ARCH=arm oldconfig HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/confdata.o HOSTCC scripts/kconfig/expr.o LEX scripts/kconfig/lexer.lex.c YACC scripts/kconfig/parser.tab.[ch] HOSTCC scripts/kconfig/lexer.lex.o HOSTCC scripts/kconfig/menu.o HOSTCC scripts/kconfig/parser.tab.o HOSTCC scripts/kconfig/preprocess.o HOSTCC scripts/kconfig/symbol.o HOSTCC scripts/kconfig/util.o HOSTLD scripts/kconfig/conf # # configuration written to .config # + make ARCH=arm -j4 scripts SYNC include/config/auto.conf.cmd HOSTCC scripts/dtc/dtc.o HOSTCC scripts/dtc/flattree.o HOSTCC scripts/dtc/fstree.o HOSTCC scripts/dtc/data.o HOSTCC scripts/dtc/livetree.o HOSTCC scripts/dtc/treesource.o HOSTCC scripts/dtc/srcpos.o HOSTCC scripts/dtc/checks.o HOSTCC scripts/dtc/util.o LEX scripts/dtc/dtc-lexer.lex.c YACC scripts/dtc/dtc-parser.tab.[ch] HOSTCC scripts/dtc/libfdt/fdt.o HOSTCC scripts/dtc/libfdt/fdt_ro.o HOSTCC scripts/dtc/libfdt/fdt_wip.o HOSTCC scripts/dtc/libfdt/fdt_sw.o HOSTCC scripts/dtc/libfdt/fdt_rw.o HOSTCC scripts/dtc/libfdt/fdt_strerror.o HOSTCC scripts/dtc/libfdt/fdt_empty_tree.o HOSTCC scripts/dtc/libfdt/fdt_addresses.o HOSTCC scripts/dtc/libfdt/fdt_overlay.o HOSTCC scripts/dtc/fdtoverlay.o HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTCC scripts/dtc/dtc-parser.tab.o HOSTLD scripts/dtc/fdtoverlay HOSTLD scripts/dtc/dtc HOSTCC scripts/bin2c HOSTCC scripts/kallsyms HOSTCC scripts/recordmcount HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp HOSTCC scripts/sorttable HOSTCC scripts/asn1_compiler HOSTCC scripts/insert-sys-cert + make ARCH=arm -j4 M=scripts/mod/ CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig CC scripts/mod/devicetable-offsets.s UPD scripts/mod/devicetable-offsets.h MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost MODPOST scripts/mod/Module.symvers + make ARCH=arm -j4 tools/objtool DESCEND objtool HOSTCC /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/fixdep.o HOSTLD /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/fixdep-in.o LINK /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/fixdep CC /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/weak.o CC /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/check.o MKDIR /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/arch/arm/ LD /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/arch/arm/objtool-in.o CC /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/special.o CC /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/exec-cmd.o check.c:11:10: fatal error: arch/elf.h: No such file or directory 11 | #include <arch/elf.h> | ^~~~~~~~~~~~ compilation terminated. make[3]: *** [/usr/src/linux-headers-6.1.15-sunxi/tools/build/Makefile.build:97: /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/check.o] Error 1 make[3]: *** Waiting for unfinished jobs.... special.c:14:10: fatal error: arch/special.h: No such file or directory 14 | #include <arch/special.h> | ^~~~~~~~~~~~~~~~ compilation terminated. CC /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/help.o make[3]: *** [/usr/src/linux-headers-6.1.15-sunxi/tools/build/Makefile.build:97: /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/special.o] Error 1 CC /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/pager.o make[2]: *** [Makefile:54: /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/objtool-in.o] Error 2 make[2]: *** Waiting for unfinished jobs.... CC /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/parse-options.o CC /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/run-command.o CC /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/sigchain.o CC /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/subcmd-config.o LD /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/libsubcmd-in.o AR /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/libsubcmd.a make[1]: *** [Makefile:73: objtool] Error 2 make: *** [Makefile:1437: tools/objtool] Error 2 dpkg: error processing package linux-headers-current-sunxi (--install): installed linux-headers-current-sunxi package post-installation script subprocess returned error exit status 2 Setting up linux-image-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) ... Armbian 'linux-image-current-sunxi' for '6.1.15-sunxi': 'postinst' starting. + export 'DEB_MAINT_PARAMS=configure 23.02.0-82' + DEB_MAINT_PARAMS='configure 23.02.0-82' + export INITRD=Yes + INITRD=Yes + test -d /etc/kernel/postinst.d + run-parts --arg=6.1.15-sunxi --arg=/boot/vmlinuz-6.1.15-sunxi /etc/kernel/postinst.d update-initramfs: Generating /boot/initrd.img-6.1.15-sunxi update-initramfs: Converting to u-boot format + echo 'Armbian: update last-installed kernel symlink to '\''zImage'\''...' Armbian: update last-installed kernel symlink to 'zImage'... + ln -sfv vmlinuz-6.1.15-sunxi /boot/zImage '/boot/zImage' -> 'vmlinuz-6.1.15-sunxi' + touch /boot/.next + set +x Armbian 'linux-image-current-sunxi' for '6.1.15-sunxi': 'postinst' finishing. Setting up linux-u-boot-orangepione-current (2022.07-Se092-P12e0-Be261) ... Errors were encountered while processing: linux-headers-current-sunxi

Thank you a lot, my Dragon Q6A now has audio

Hey just checking in. I haven't forgotten about this yet, I want to make sure everything is repeatable and possible to do on multiple versions of armbian before I write a guide and confuse a lot of people. Noticing that mpv doesn't work, I tried to do what jock suggested to Harleyyyu and update to a newer kernel version. So far... no luck. Seems like the problem boils down to having to write u-boot.bin to the eMCP before burning the actual OS onto it. I'll write again if anything goes.

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

@robertoj the problem is not ffmpeg, which already is works totally fine on debian Trixie (and backwards), the problem is within mpv that changed in v0.4.0 carried by debian Trixie, and at the moment I don't have enough motivation to carry on a custom mpv package for Debian Trixie. You may try with debian forky by the way, but it is a moving target as long as it is still in development.

@jock Thank you for your reply. Unfortunately, I can't do it I tried to short it, but it doesn't load from the SD card. I shorted it with a piece of wire. When I do it with USB connected, I see the device is in Maskrom. Here the console output from rkdeveloptool using: root@lensky-lp:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 10c4:8105 Silicon Labs USB OPTICAL MOUSE Bus 001 Device 005: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD Camera Bus 001 Device 006: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 008: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge Mini Keyboard] Bus 001 Device 009: ID 2207:320c Fuzhou Rockchip Electronics Company RK3328 in Mask ROM mode Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub root@lensky-lp:~# rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=104 Maskrom root@lensky-lp:~# rkdeveloptool td Test Device failed! root@lensky-lp:~# rkdeveloptool ---------------------Tool Usage --------------------- Help: -h or --help Version: -v or --version ListDevice: ld DownloadBoot: db <Loader> UpgradeLoader: ul <Loader> ReadLBA: rl <BeginSec> <SectorLen> <File> WriteLBA: wl <BeginSec> <File> WriteLBA: wlx <PartitionName> <File> WriteGPT: gpt <gpt partition table> WriteParameter: prm <parameter> PrintPartition: ppt EraseFlash: ef TestDevice: td ResetDevice: rd [subcode] ChangeStorage: cs [storage: 1=EMMC, 2=SD, 9=SPINOR] ReadFlashID: rid ReadFlashInfo: rfi ReadChipInfo: rci ReadCapability: rcb PackBootLoader: pack UnpackBootLoader: unpack <boot loader> TagSPL: tagspl <tag> <U-Boot SPL> ------------------------------------------------------- root@lensky-lp:~# rkdeveloptool rid Reading flash ID failed! root@lensky-lp:~# rkdeveloptool cs 2 AMO: ERR_DEVICE_WRITE_FAILED Change Storage failed! root@lensky-lp:~# rkdeveloptool ppt Read GPT failed! Read parameter failed! Not found any partition table! root@lensky-lp:~# rkdeveloptool db /home/lensky/Downloads/For\ RK3328\ devices/RK3328MiniLoaderAll_V2.50.bin Downloading bootloader succeeded. root@lensky-lp:~# rkdeveloptool ppt **********Partition Info(parameter)********** NO LBA Name 00 00002000 uboot 01 00004000 trust 02 00008000 misc 03 0000A000 baseparamer 04 0000A800 resource 05 00012000 kernel 06 00022000 boot 07 00032000 recovery 08 00042000 backup 09 00062000 cache 10 000A2000 metadata 11 000AA000 kpanic 12 000AC000 system 13 003AC000 userdata As you see after boot it looks like the flash is empty. I can't ready any info and there no partitions. But after download bootloader command I see partiosions and can read flash info and chip info. After reboot all is disappear again. This is my board: This is my eMMC chip: I have found YouTube video how to short the clock pin for my board. On the opposite side, I need to short these pins: When I insert the SD card and boot the device, it just lights the red led and nothing more. Is something I do wrong?

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 652da4fbc (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + DXVK-stripped v1.6.1 30~60fps@720p (low settings, high texture, no AA) box64 environment variables: Black Mesa

diy image and you get it immediately

Decided to see how far the LLM have come along and give this another crack. Gemini 3 Flash seems to have got me a few steps forward. It had me add zswap and build a swap file while adjusting some of the U-Boot variables. /boot/armbianEnv.txt additions/changes fdt_addr_r=0x42000000 ramdisk_addr_r=0x42800000 fdt_high=0xffffffff initrd_high=0xffffffff extraargs=zswap.enabled=0 swiotlb=1024 I had to expand the filesystem to use more of the SD card then added a 512M swapfile sudo fallocate -l 512M /mnt/pinecube/swapfile sudo chmod 600 /mnt/pinecube/swapfile sudo mkswap /mnt/pinecube/swapfile It took a solid 5 or so minutes but I got booted. It's very slow but at least I got this far! Just leaving this here for anyone else that may stumble along.

That isn't what you use for amlogic tv boxes. Follow the instructions linked from the download page: https://www.armbian.com/amlogic-s9xx-tv-box

THANK YOU so much for this effort. I no longer regret buying an OrangePi RV2!

On the 25.11.1 Noble release, using the 6.12 kernel, there is no package to install the linux-headers for installed kernel. Is there some place to get them so that it is possible to install a kernel module for the provided ubuntu-rockchip kernel?

Rpi support for whatever of their devices is mainly on the level of RaspberryPi OS. We use their kernels sources as base, add some additional things and release timing is different - not much difference. If they added new device, it should just work. If anyone wants to improve support or fix WiFi -> https://github.com/armbian/build/pulls

http://blog.armbian.com/content/images/2026/01/coverleter.pngWelcome to the latest Armbian Newsletter: your source for the latest developments, community highlights, and behind-the-scenes updates from the world of open-source ARM and RISC-V computing. http://blog.armbian.com/content/images/2026/01/image-2.pngJoin Armbian at embedded world 2026. Meet us in Hall 3, Booth 3-556 (Seeed Studio), where we’ll be showcasing the Armbian build framework and how it powers reliable, production-ready Linux for ARM devices. FriendlyElec’s NanoPC T6 Plus: The flagship edge computing powerhouse and media stationThe NanoPC T6 Plus, powered by the performance-optimized Armbian OS, is your ticket to a truly professional, high-speed edge computing experience. This industrial-grade device is built around the flagship Octa-core Rockchip RK3588 SoC and now features a massive upgrade to LPDDR5 RAM (up to 32GB), giving it the muscle tohttp://blog.armbian.com/content/images/icon/favicon-40.icoArmbian blogMecid Urgancihttp://blog.armbian.com/content/images/thumbnail/T6-Plus-01.pngSponsored Github HighlightsThis week’s Armbian development saw a wide range of updates focused on automation, hardware support, and workflow improvements. Key highlights include the introduction of automatic YAML target generation, expanded support for Hetzner ARM64 runners, and enhancements to the redirector update workflow with cache mirror support. Several board-specific fixes andhttp://blog.armbian.com/content/images/icon/favicon-36.icoArmbian blogMichael Robinsonhttp://blog.armbian.com/content/images/thumbnail/githubhighlights-2-2.webpForget third-party utilities: meet Armbian ImagerArmbian Imager eliminates the guesswork from flashing SBC images. Real-time board detection, persistent caching, and built-in safety make installation fast, simple, and risk-freehttp://blog.armbian.com/content/images/icon/favicon-37.icoArmbian blogDaniele Brigugliohttp://blog.armbian.com/content/images/thumbnail/introducing-armbian-imager.pngArmbian 2025: by the numbersOpen hardware is growing faster than ever and breaking in new ways. 2025 has been a productive year for the Armbian project. As the Single Board Computer ecosystem continues to fragment and expand, Armbian has consolidated its position as the universal glue holding the open-source hardware world together. Our missionhttp://blog.armbian.com/content/images/icon/favicon-39.icoArmbian blogMichael Robinsonhttp://blog.armbian.com/content/images/thumbnail/New_review1.pngView the full article

Thanks Igor. Just for reference, I also tried Armbian_community_26.2.0-trunk.332_Odroidhc4_forky_current_6.18.7_minimal.img apt update apt upgrade apt install linux-headers-current-meson64 apt install zfsutils-linux zfs-initramfs zfs-dkms zfs-zed Everything went fine and seams to working OK. Chris

Hi! This is my first message here, congrats to the community for building this I would also like to corroborate that the current Balena Etcher, in Windows at least, is not writing the image correctly to the SD card. The Armbian imager did it well for me. I just booted an unused A95X (S905X) "Mini Kitty" with Armbian, but I don't think I will spend too much time with it, I already got a lot of mini PCs for servers and it's too slow for a terminal 😅 What do you recommend me to do with this little box? Thanks!