Active threads

Interesting, didnt realize that.

Thank you for reporting. If current images have troubles, you can try to use previous ones. There is a link on the download pages or you can find them this way. https://forum.armbian.com/topic/52406-helios-64-fails-to-boot-since-upgrading-to-bookworm/#comment-219614 Which works best for your case, you will need to find on your own. We don't store this information / forum search might help. Similar goes with 3rd party images - most are Armbian based and none is in perfect state, things break apart all the time. By providing logs (if possible) someone might give you hints to workaround the problem, without hardly. As I understand from your report - image boots, but USB port doesn't work to enter password? And also network is down, so you can't login remote. I haven't tested HC4 on last builds, but C4 works just fine. In any case, fixing the problem can take some time - Hardkernel never supported our work, so we don't have active maintainer at stand by. It depends on volunteers that read this forum. When they notice and found time to look into this.

As the Armbian project transitions from spring into summer, the final week of May 2025 brought a dense flurry of development activity, delivering improvements across kernel support, bootloader updates, system performance, and user experience enhancements. With over 35 pull requests merged, this week showcased the Armbian community’s continued dedication to modernizing and stabilizing its build framework and board support packages. Performance & Build System Optimizations A notable performance enhancement arrived via #8248, where build engineer @rpardini delivered a major speed-up in Docker extension handling, cutting processing time by over 50%. Complementing this, PR #8249 addressed inefficiencies in rootfs-to-image by avoiding --sparse, significantly improving I/O speeds on various filesystems. Kernel version parsing and custom kernel description functionality also landed with #8152, thanks to @Grippy98, enabling displaying kernel versioning within build branches. Board Support Enhancements & Bootloader Upgrades A slew of boards received attention this week. The NanoPC-T6 series saw a key modernization in #8219 and #8239, switching to mainline Arm Trusted Firmware and bumping U-Boot to v2025.04 final. The Quartz64A board followed suit in #8250, while the Odroid HC4, Khadas VIM3, and Mixtile Blade3 all received U-Boot updates or reverts to improve stability. Legacy and edge kernel support was also improved. Notably, Rockchip64 edge kernel configuration gained CONFIG_NETKIT=y (#8237), and fixes for display mode handling on RK3588 boards were added (#8253). Meanwhile, the Orangepi 5 Ultra switched to a mainline kernel source (#8252), reinforcing Armbian’s ongoing effort to shed legacy components and embrace upstream compatibility. Infrastructure & Usability Improvements Behind the scenes, @igorpecovnik contributed multiple usability tweaks, including a fix for HiDPI detection (#8236) and @rpardini added improved serial console fallback behavior in GRUB (#8247). The GPG key placement was standardized across distros (#8128), simplifying build reproducibility. Device Tree and Service Fixes The smart am40 received a long-needed RTC node and U-Boot bump (#8214), while the Helios4‘s wake-on-LAN service was fixed (#8235), reinforcing Armbian’s commitment to community-requested board maintenance. Wrapping Up This week’s burst of activity highlights the Armbian community’s tireless commitment to refinement and modernization. Whether through performance enhancements, kernel bumps, or quality-of-life fixes, the project continues to evolve rapidly. Users can expect a more responsive, stable, and future-proof experience across a growing roster of supported hardware. Stay tuned for further updates as June unfolds. The post Armbian Development Highlights: End of May 2025 first appeared on Armbian. View the full article

What do you mean by that? Images that are currently available are still from 25.2 ... new will be created soon. But you can anyway update them standard way: apt update + apt upgrade.

I've seen this error before. I think that's some incompatibility from rpi own packages that have some regex checking if its their own kernel or not. Did not get any further though.

code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-install should be able to do that. Though since there is no option to select WHICH version, if there are multiple installed, to write, I suggest to first check with code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } dpkg -l which uboot package/s is/are installed and make sure there is only the one that you want to write.

config is there: https://github.com/armbian/build/blob/main/config/boards/orangepi5-ultra.csc DIY: https://docs.armbian.com/Developer-Guide_Overview/ Go for edge

Hi @gyrex, You might want to try without the fstab entry for your root filesystem: UUID=024728b4-7d81-4433-8476-0f98407d1481 / ext4 defaults,noatime,commit=600,errors=remount-ro 0 1 and add the following to your armbianEnv.txt. extraargs=rw The fstab entry for your rootfs is there to remount your rootfs with some options, it is not there to actuall mount it - that's already done by the rootdev/rootfstype in your kernel commandline. or: change the last digit from 1 to 0 in the fstab entry for your rootfs to prohibit fsck during boot. Hopefully that would allow the system to complete it's boot and make room for some live troubleshooting. Thx, Groetjes,

In the final lines of your build log output, it seems that it cant download some ubuntu packages. I dont see linux compilation errors (I only looked at it for 1 minute). Can you try rebuilding with debian?

@paradigman not to be unfair against OVPN but its very slow (high cpu load) and hard to configure/maintain ( i developed the opvn plugin in ddwrt for some years). you will be better off with Wireguard on this box (i bet it can push linespeed of the gig port).

look here https://github.com/hzyitc/armbian-onecloud/releases

Did anyone managed to boot anything other then android on TX6S?

Yes, the rock5b work just fine. I also installed the UEFI into the SPI there (I have 2 Rock 5b) - I might want to give the itx a shot installing the UEFI into the SPI one day. There is something in the UEFI image which does not boot from SD; trying to find any docu about that - I came across one article mentioning some HW hack to change the boot order (probably what you described up there). The 5b and itx are quite different (itx is also 10-20% faster with higher clocks and faster RAM) but otherwise once the UEFI is installed, mine run the same OS. Unfortunately to run ACPI one needs a latest OS (Ubuntu 25 or Fedora Rawhide) - I haven't actually tried the mainline Armbian - I run KDE Plasma and while there was a Neon image somewhere most Armbian prebuilts don't run KDE (everytime I post install that, something else breaks). Anyway, I am happy that everything is working now on all my Rock5 boards.

EDIT: Actually, armbian can't be installed with PhoenixSuit, I didn't know :/ I've already tried several images, 5+, but this error keeping appearing. Also, I would like a bookworm image for Allwinner H3Q44, if someone have one working good, please send it to me. UPDATE: This random img worked.

This fixed the issue with Chromium. I simply created a file /etc/armbian/cromium.conf with the contents you provided and chromium opened perfectly.

The same issue with Kernel 6.12.23, my flashdrive can not be found. Kernel 6.6.75 is still doing its work

Armbian packages get updated now, so now upgrading to 25.8.0-trunk.100, from .87 I did earlier yesterday. Also now running 6.15.0-edge-rockchip64 with EDK2-UEFI v1.1 in SPI. Need setting to DeviceTree as the default (Both = ACPI and DeviceTree) seems to confuse 6.15.0-edge-rockchip64, got only serial console only or stall somewhere in boot process.

Jens J, woah, I didn't know that you can just split bootloader like that! I did that, and so far, it looks good! TV Box boots into u-boot with this SD card, and it has a partition table. Thank you so much! Now I'll try to make an SD card with system on it

@ovacikar Did you manage to get this fully working? What does this kernel bring? I saw recently hw acc is now working, did you manage to get this working? Im asking because this weekend im going to try to get mine all up to date and see if i can get it be a simple media player

Have you tried `/boot/dtb/amlogic/meson-gxm-mini-m8s-pro.dtb` ? What is wifi chip? Is it LTM8830? If so this is QCA9377 clone, and this dtb should be fully working.

Hi everyone, I’m working on a custom Armbian build for an RK3588-based board (cm3588-nas) and trying to completely disable the Rockchip crypto driver (rk_crypto2), since it's negatively impacting LUKS (AES-XTS) performance. Despite several attempts, the module continues to register algorithms in /proc/crypto after boot: driver : rk2-sm3 module : rk_crypto2 driver : rk2-sha512 module : rk_crypto2 driver : xts-aes-rk2 module : rk_crypto2 ... ------------------------------------------------------------ What I’ve Tried ------------------------------------------------------------ 1. Kernel Config Override - Added CONFIG_CRYPTO_DEV_ROCKCHIP=n and CONFIG_CRYPTO_DEV_ROCKCHIP2=n to: userpatches/linux-rockchip-rk3588-edge.config - Verified .config has it set to n after build. - Used CLEAN_LEVEL="make,debs,oldcache" in the build command. 2. Blacklisting & Deletion in customize-image.sh echo "blacklist rk_crypto" > /etc/modprobe.d/blacklist-rk_crypto.conf rm -f /lib/modules/*/kernel/drivers/crypto/rockchip/rk_crypto.ko* 3. Post-Boot Verification - lsmod | grep rk_crypto → empty - modinfo rk_crypto → module not found - /proc/crypto still shows rk2-* drivers tied to rk_crypto2 4. Manual Source Removal - Commented out this line in drivers/crypto/rockchip/Makefile: # obj-$(CONFIG_CRYPTO_DEV_ROCKCHIP) += rk_crypto.o - Also removed or disabled its Kconfig entry. ------------------------------------------------------------ System Details ------------------------------------------------------------ Board : cm3588-nas (RK3588) Kernel : rockchip-rk3588 edge (Linux 6.8.x) Builder : Official Armbian compile.sh ------------------------------------------------------------ Goal ------------------------------------------------------------ I want to fully disable the Rockchip crypto engine (rk_crypto2): - It should not load, not build, and not register anything in /proc/crypto. - LUKS should fall back to software crypto (cryptd, aesni, or default fallback). ------------------------------------------------------------ Any help is appreciated. I’d love to hear from anyone who’s successfully disabled rk_crypto2 entirely or has ideas for where the registration is coming from even when the module appears removed. Thanks!

Hi @Vodalex, Write down the MAC address of the interface you want to use to wake up the Helios4. ip link show You would need to put the Helios4 in suspend, by either: sudo pm-suspend or: echo 'suspend' | sudo tee /sys/power/state To wake it up, from another system, make sure that wakeonlan is installed. Then: wakeonlan ${HARDWARE_ADDRESS} That should be it. Groetjes,

Did anyone managed to get Linux working on TX6S?

Next week Collabora will be covering a lot of ground, attending 3 separate events in 3 different time zones: ISC High Performance, Augmented World Expo, and InfoComm! Catch up with us at one of these events. View the full article

This is what AI tells: Role of BL30 The BL30 component serves as the firmware for the Amlogic Secure Co-Processor (SCP). Its primary responsibilities include managing system-level operations such as Dynamic Voltage and Frequency Scaling (DVFS) and handling suspend/resume functionalities. These tasks are crucial for optimizing power consumption and ensuring efficient thermal management within the system. lists.denx.de In addition to BL30, there is a closely related component called BL301. BL301 acts as a board-specific firmware "plug-in" that provides customized parameters for DVFS and suspend/resume operations, tailored to the specific hardware configuration of the board. lists.denx.de Integration into the Boot Process The typical boot sequence in Amlogic devices follows this order: BL2 → BL30 → BL31 → BL33. Each stage is responsible for initializing specific aspects of the system, with BL30 focusing on power management and system control tasks. If any stage fails, the boot process may attempt to fall back to an alternative boot medium, although this behavior can vary depending on the specific SoC and its configuration. 7Ji’s Blog+1lists.denx.de+1 Understanding the role of BL30 is essential for developers and system integrators working with Amlogic platforms, especially when customizing firmware or troubleshooting boot-related issues. All Amlogic SoCs boards needs this. AFAIK here we don't have open source alternative. Only from the owner of this file after you sign certain papers https://www.amlogic.com/#Company/Contact/index.html This is complex operation and possible where / when there is a big enough interest and when more people join in this common interest and are willing to sacrifice months of their precious private time. https://github.com/crust-firmware/crust Here is an example of similar feature for some other SoC (allwinner). It works, but it's also not feature complete and probably never will. Many of those SoCs are already commercially obsolete, similar for the one you are asking.