Active threads

I have took this variable from Here. Actually the first thing I tried to observe is uart logs. But they are very minimalistic like that: U-Boot SPL 2024.01-armbian-2024.01-S866c-P6b16-Ha5c2-V367a-Bb703-R448a (Apr 29 2025 - 02:50:09 +0000) DRAM: 512 MiB Trying to boot from MMC1

Great！ Thanks a lot! I will try it to se if Diablo II can run tonight!

@chris178 I am currently working on a solution. Radxa typically uses rsetup and extlinux.conf to load overlays during boot; however, Armbian uses armbian-config along with boot.cmd and boot.scr. I have decided to use armbian-config to load the overlays instead.

http://blog.armbian.com/content/images/2026/01/githubhighlights-2.webpThis week’s Armbian development saw significant kernel upgrades across multiple platforms, including meson64, rockchip64, and UEFI, with several branches bumped to versions 6.18 and 6.19. Notable hardware support enhancements were introduced, such as SPI controller support for Allwinner A523, new board additions like mixtile-core3588e, and improved compatibility for devices including Radxa and Youyeetoo. The build system received stability and performance improvements, featuring parallel repository generation, refined CI scripts, and fixes for repository management in concurrent environments. Kernel configuration updates enabled additional filesystems and tickless idle for mvebu devices. Several patches addressed hardware initialization, network, and desktop issues, while deprecated packages were removed for a leaner build. Overall, the changelog reflects a strong focus on expanding hardware support, refining build infrastructure, and maintaining kernel currency. add allwinner: a523: Support SPI controllers patch series. by @EvilOlaf in armbian/build#9124allow build on forky host. by @amazingfate in armbian/build#9153CI: add watchdog action script and adjust log cleaning parameter. by @igorpecovnik in armbian/build#9147Fix repository management script for parallel execution. by @igorpecovnik in armbian/build#9163fix: replace comm with grep to support uutils coreutils. by @cantalupo555 in armbian/build#9148kernel configs - enable EROFS as module, ditto overlayfs & F2FS. by @tabrisnet in armbian/build#9135kernel: mvebu: enable tickless idle. by @neheb in armbian/build#9139meson64-6.19: de-bork PCIe, again (missed a patch from 6.18). by @rpardini in armbian/build#9151meson64: bump edge to 6.19; current 6.12 -> 6.18. by @EvilOlaf in armbian/build#9069meson64: bump edge to 6.19; current 6.12 -> 6.18 (nonsquash). by @rpardini in armbian/build#9146Missing variable in board config - address JSON matrix warnings. by @igorpecovnik in armbian/build#9144mixtile-core3588e: add board with vendor and edge branches (Joshua Riek + fixes). by @rpardini in armbian/build#9119Modify radxa-e54c board config to fix leds, network and Gnome desktop init.. by @schwar3kat in armbian/build#9111radxa-cubie-a5e: maint and fixes. by @EvilOlaf in armbian/build#9152Remove libfuse2t64 from package list. by @igorpecovnik in armbian/build#9155Repo tools: add parallel repository generation support. by @igorpecovnik in armbian/build#9150Revert few Rabbit's suggestions that broke repository management. by @igorpecovnik in armbian/build#9156rockchip64-6.18: Enable HDMI1 and audio for HDMI0/1 on CM3588-NAS. by @rpardini in armbian/build#9138rockchip64: add edge kernel support for Youyeetoo YY3588. by @SuperKali in armbian/build#9137rockchip64: fix broken patch in 6.18.3, rewrite everything. by @EvilOlaf in armbian/build#9157uefi-all: bump edge to 6.19 (except loong64); legacy 6.6 -> 6.12; current/cloud 6.12 -> 6.18. by @EvilOlaf in armbian/build#9086uefi-loong64-edge: bump to 6.19. by @amazingfate in armbian/build#9149View the full article

So the workaround is to set cpu freq max to 1 MHz. I still have to use a ghetto cooler 5000 when running a process that maxes out the CPU. Seems Duo running 10C+ at idle with latest kernel and Noble. I can live with that as long as I know. The default is 1.2 MHz max which runs too hot at 1.3V.

Java UIO Java UIO offers robust Java interfaces optimized for Linux Userspace IO, emphasizing high performance. Engineered from scratch, it leverages contemporary kernel APIs, libraries, and cutting-edge code generation methodologies, embodying a state-of-the-art cross-platform solution. Rather than reinventing established paradigms, Java UIO harnesses existing standards, avoiding redundant development commonly observed in other IO libraries. Seamlessly supporting JDK 25 LTS, this framework integrates Project Lombok to streamline code, enhancing readability and conciseness. 🌍 The 32-bit & FFM Reality With Java 25, there is no more support for X86_32, and ARM32 has limited JDKs available. While FFM (Foreign Function & Memory API) is the future, it is not supported on X86_32 or ARM32. For now, JavaUIO moves into the future providing a high-performance path for ARM32, while fully supporting ARM64 and X86_64.

Just to add, Armbian boots upto systemd and then gets stuck at loading some scripts. This image gives some additional information.

I guess the image was built from a pending pull request for testing before merge. Since it has been merged now it should work. Make sure your framework clone is up to date (git pull).

Oh, I understand. Camera, hardware video decoder and hardware video encoder - they all appear now as /dev/videoX devices, because new hardware videocodec accelerator driver (or standalone video decoder and video encoder drivers) became V4L2 kind of driver. Also thanks for the reference link.

The ffmpeg conversation in https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847 suddenly stopped 2 weeks ago. Does it seem like there's a big obstacle suddenly, or just a well deserved engineer vacation going on?

Thank you for testing my instructions I was on vacation, and I didn't remember to check this until now Which LCD are you using? Which kernel driver are you using for it? All the questions in your post depend on the LCD model and the driver you used. (I am using panel-mipi-dbi, which I know that it has lost its ability to display X11 graphics since a few months ago) Can you 100% say that you don't have X11? You don't need to use the same kernel version I use. The newer version you have is preferable 🆗 I am glad you can use the Trixie labwc. Personally, I am using Bookworm in the meantime, since its the only way I know to get H264 hardware acceleration. With Trixie's labwc, do you ever get desktop crashes when you log out?

I updated my patches to the new style (using series.conf) and that took some time. They are back online, as are some new images. I post more updates at the opi discord btw. As far as I know, neither network, spi flash or pcie are working currently.

Current way of installing is as written on the download pages. It was verified with latest v24.11.2 image.

when send command poweroff or reboot alywas display client_loop: send disconnect: Broken pipe instead in on ArmBian Debian 12: Connection to 192.168.1.12 closed by remote host. Connection to 192.168.1.12 closed. but maybe on Debian 13 now is different message after reboot or poweroff

@Ducdanh Nguyen, virtually every adapter will work. I'm using DFRobot multiplexer v.1.0 (FT232R-based): https://wiki.dfrobot.com/Multi_USB_RS232_RS485_TTL_Converter__SKU_TEL0070_

I found a way to install 25.04 onto emmc with no problems afterwards. Updates and upgrades just fine now. https://pastebin.com/DzNYtmQa

Okay we're randomly poking at things. Please provide the following for every image you test. dmesg | grep -iE "stmmac|sun8i|dwmac|emac|phy|mdio|motorcomm|yt8531" dmesg | grep -i "registered.*phy\|phy.*connect" ls -l /sys/bus/mdio_bus/devices/ cat /sys/bus/mdio_bus/*/phy_id 2>/dev/null find /sys/class/net -name "end0" -o -name "eth0" | head -1 | xargs -I {} cat {}/phys_switch_id 2>/dev/null ls /sys/firmware/devicetree/base/soc/ethernet*/mdio/ and the output of armbianmonitor -u (if network doesn't work use -U instead to print to stdout) The following one adds phy-io-supply = <&reg_gmac_3v3>; to the emac, just in case... https://testing.armbian.de/Armbian-unofficial_26.02.0-trunk_Orangepi3-lts_trixie_current_6.12.63_minimal_phy-io-supply.img.xz

duplicate https://forum.armbian.com/topic/57200-orange-pi-zero-2w-repeatedly-asks-for-wi-fi-password/?do=findComment&comment=231167

https://github.com/twdragon/FFmpeg/tree/cedrus264 may produce green line artefact at the frame bottom on 1080p resolution. In the https://github.com/agustinov/FFmpeg-Cedrus/tree/4.4-cedrus this artefact is fixed.

if you are not seeing option to enable in armbian-config you can try: sudo apt install xfce4 xfce4-terminal lightdm -y or sudo apt install xfce4-goodies -y

i was installed armbian on hg680fj with schipset amlogic s905x2, replace dtb with spesific hg680fj and change xtlinux config, after that starting boot, but looping on armbian screen. please help ehat shoud i do.

I found a post on this forum and tried it, but it didn't appear to have any effect. I might have just run it wrong. I believe they were also dealing with a different source having this problem.

Hello everyone, I am using an Orange Pi Zero 2W with a graphical user interface (GUI). I downloaded and installed the official Orange Pi Zero 2W image. Unfortunately, I keep running into a Wi-Fi connection issue. After booting, the system repeatedly asks me to enter my Wi-Fi password. If I don’t enter it, I have no internet connection. What’s interesting is: If I disable and re-enable Wi-Fi in the network manager, it automatically reconnects to the known network without asking for the password again. Alternatively, a system reboot also restores the Wi-Fi connection automatically. I have already seen online that this seems to be a known issue, but I haven’t found a proper or permanent solution so far. Has anyone experienced similar behavior or knows how to configure Wi-Fi so that it connects reliably and permanently without repeatedly asking for the password? Thanks in advance!

Please report here https://github.com/armbian/imager/issues

Thank you to everyone who spent time reading my post, and contributing to it. Having had some free days I decided to give it another try and experimented my helios64 with some of the newer images, none of which worked perfectly (my main requirement is OMV plus its miniDLNA, and couldn't get this installed on noble or trixie, although they were booting and working just fine), eventually running now some bookworm from eMMC and while it seems stable there are some performance issues* (need to re-read that bookworm issues thread again as I did not try all the fixes yet, including the dtb one). *By performance issues I mean some apparently slow reading/writing to eMMC, and network performance on 2.5gb, which I know were thoroughly discusses on that thread, just need to spend more time on trying them out I guess. I'm still a newbie into all this stuff and I was reading a lot again before the new tests. Would anyone be able to recommend some version of an archived bookworm image that I should start from? My device is connected to the router via the 1gb interface, and I have a second cable going directly to my desktop via the 2.5gb interface that lands into a 2.5gb USB-c network card. I don’t have the 2.5gb hardware fix done as when I installed it years ago it was working fine on buster with this layout and my router is 1gb only anyway. In any case, I still have the SD card with the prior setup untouched, so can revert back to it, was just thinking it makes more sense to try something new. Happy new year all of you!