Active threads

@laibsch https://u-boot.org/

Updating via `apt update && apt upgrade` causes Armbian to fail to boot on the single-board computer. I'm attaching the UART logs in the file `failed_log.txt`. Start-Date: 2025-11-13 04:45:12 Commandline: apt -y upgrade Upgrade: armbian-bsp-cli-nanopct4-current:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), linux-dtb-current-rockchip64:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), linux-image-current-rockchip64:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), linux-u-boot-nanopct4-current:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), armbian-firmware:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469) End-Date: 2025-11-13 04:47:04 out: Starting kernel ... efi_free_pool: illegal free 0x00000000f0f09040 "Synchronous Abort" handler, esr 0x96000004 elr: 00000000002856e4 lr : 00000000002702f0000000f3f9b2f0 x0 : dfb6333a7ba2b4b7 x1 : 00000000f3fba060 x2000000 x5 : dfb6333a7ba2b4b7 x6 : 00000000f0d07000 x7 : 00000000000ef98 x11: 00000000f1f0b5bc x12: 000000000000ef98 x13: 000003f558a4 x17: 00000000d8136251 x18: 00000000f1f22d90 x19: 000000000000001 x23: 00000000f1f303c0 x24: 00000000f3fdcff0 x25: 00000000000000001 x29: 00000000f1f0b470 Code: eb04005f 54000061 5resetting ... To reproduce the issue (~13.11.2025-16.11.2025), simply download and flash the current `Minimal/IOT for Armbian Linux v6.12 [Debian] Debian 12 (Bookworm)` images (`https://www.armbian.com/nanopc-t4/`) and run `apt update & upgrade` on a running system, then reboot. After this, the system, regardless of whether the `SD card` or `EMMC` is used, will enter an infinite boot loop (`out` and file `failed_out.txt`). Thank you. failed_log.txt armbian_release.txt normal_log.txt

@Henrik Larsson Did you end up changing anything or is this with the default configuration? Are you still using kernel 6.12? Have you tried build with a 6.16 edge based image yet?

Any update here? Same broken image is still linked from back in may and no update to these images since then?

Made some progress. after installing Armbian_25.8.1_Odroidxu4_noble_current_6.6.102 to eMMC ran armbian-upgrade Installed xubuntu-desktop or xubuntu-desktop-minimal package reboot now i'm getting the greeter screen. after login, I entered xfce desktop. functions ok could only install firefox via snap. installed firefox via snap ran firefox to view a video on youtube. audio is not working. install pulseaudio reboot system audio still not working when viewing a youtube video any suggestions?

There are no other images available at the moment. Regarding this, there is some initial but incomplete work in progress here: https://github.com/armbian/build/pull/8831 We can’t merge it in its current state, as it still requires a significant amount of additional work and refinement. Unfortunately, this means there isn’t a quick solution right now, so we’ll need to wait until the implementation is completed and validated.

Apparently the key needs to go to `/etc/apt/trusted.gpg.d/armbian.gpg` too...

hello i have updated with wrong firmware throw usb c nothing happens when flashing with USB_Burning_Tool or booting from sd card this box has no recovery button only on off inside earsphone

It looks like knotes has been replaced with Marknotes. Remove knotes and, if you like, install marknotes. It is supposed to import your old knotes data.

The 6.18.0-rc5 kernel doesn't require any patches, just have to been build with DRM_ACCEL_ROCKET.

Hi, I currently have the issue of a non working usb port on my odroidhc4. dmesg output: [ 133.464610] usb usb1-port2: connect-debounce failed The port does not show up when lsusb is entered. uname -a: Linux odroidhc4 6.12.56-current-meson64 #1 SMP PREEMPT Wed Oct 29 13:09:02 UTC 2025 aarch64 GNU/Linux I solved this temporairly a while ago by booting an older kernel (linux-image-6.12.43+deb12-arm64) like mentioned here: Are there any progresses on how to fix this reliably? Because I think still running kernel 6.6.63 is not save. Thanks for your answer in advance, if you need more information I am happy to deliver.

https://drive.google.com/file/d/1vyQGR8kgzhCzmwuXhb8q5j707U9IXFob/view?usp=sharing The file in this shared link is the image file provided by the manufacturer for my Android device. I hope it will be useful, and thank you for your help! I can't compile a custom Armbian image and hope to get help from the community.@Hqnicolas

Just for posterity. fluster-run-odroid-m2-summary

Did you also install the dtb that belongs to that kernel version? You could check if the dtbo is compatible with your dtb with: fdtoverlay -v -i /boot/dtb/current.dtb -o /tmp/test.dtb your-overlay.dtbo It would be better to compile the dts with armbian-add-overlay your-overlay.dts so it will automatically install it to /boot/overlay-user and added to your armbianEnv.txt. In this way it also won't get overwritten when you update the dtb. And of course like Werner said, check the debug serial console, you'll see much more detailed information. And check if the symlinks are correctly linked to your kernel version. ls -l /boot

It's more than a year later - but the update to the distro-agnostic.sh to copy resolv.conf also fixed my native build as well. DNS for the apt/image build process was failing before I did that.

Hi, just to give a maybe final feedback on this topic: Although it is not a really satisfying solution, I decided to switch off the sysrq functionality by setting kernel.sysrq=0 in /etc/sysctl.conf. This was 1 month ago and there were no sysrq events in my logs since then. So for now this is a "good enough" solution for me. Thank you all for your support, I learned again a lot ...

@blackc Exact the original U-boot DRAM settings from your boot.bin or an update. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/23/#findComment-218660 If you are still having issues ask the sunxi guys on IRC. https://oftc.catirclogs.org/linux-sunxi/2025-11-14

Armbian Bookworm 25.8.1. (minimal) Odroid XU4 with 32GB eMMc After lots of searching and trying 2017 Hardkernel solutions and github etc - And this forum suggestions - I could never get get it to boot. I think this is partly because things have changed since 2016/17. I did not have my eMMc on an usb adapter. Just installed, brand new (untouched from China) eMMc and a imaage install on MicroSD of Armbian. The method I believed should work was "armbian-install". But, it had errors while using mkpartimage. I put debug statements in the script and found the particular instance of invoking mkpartimage. Actually the issue is; 2 files are missing from /boot folder. Current SD installation image of Armbian minimal only creates one fdisk (MBR) partition on which /boot is a folder. I tried for ages to create a separate /boot partition. Maybe, since I have now succeeded with an eMMc install, I might try doing a separate root and boot. The 2 missing files are armbianEnv.txt and boot.cmd If one "touch"es armbianEnv.txt then - if it doesn't exist it will be created - if it does then no harm done. If one copies boot.ini to boot.cmd then these two things will satisfy armbian-install. Amrbian-install correctly changes the R/O of mmcblkXboot1 (where X is emmc device number) write the boot stuff and markit back R/O. It also ensures that armbianEnv.txt has got correct entries in it. In summary Install eMMc and Micro SD in XU4 Ensure SD/eMMc switch set to SD and boot armbian from SD Login as root or use sudo touch /boot/armbianEnv.txt cp /boot/boot.ini /boot/boot.cmd armbian-install choose the install and boot from eMMc option shutdown change switch to boot armbian from eMMc boot

Hi @djurny Just to inform you that, after cleaning out some mess I made, your overlay and armbianEnv.txt update to make the external RTC ds3231 to work, did the job. For my SBC's I use the Banana Pi M2 Zero and v25.5 rolling for Banana Pi M2 Zero running Armbian Linux 6.6.75-current-sunxi My application needs to work in the field as an Access Point with an RTC, the right date and time is important info in the diagnostics of my applications. A remark on the mentioned Armbian release: For using the GPIO pins of the SBC, python3-libgpiod works great. I use USB camera's (V4L2 camera). After any update or upgrade, my USB camera's won't work anymore. Not really a problem for me, because I'm happy as it works right now, no updates or upgrades needed. Thanks again for your great help. Met vriendelijke groet, Ed

https://github.com/armbian/build/blob/main/config/boards/retroidpocket-rp5.csc https://github.com/armbian/build/blob/main/config/boards/retroidpocket-rpmini.csc You can build images on your own. https://docs.armbian.com/User-Guide_Board-Support-Rules/#community-maintained

Choose install/update bootloader on spi flash option on armbian-install. Some uart logs could be useful if you have usb-ttl converter stuff

Hello all, I have a/m model with 2GiB RAM / 16GiB eMMC- Wifi: XR819 (XRadio XR819). I've download and install a .img file Armbian_community_25.11.0-trunk.437_Tanix-tx6_trixie_current_6.12.47_minimal.img.xz I want to have a server version CLI, but I don't know where to find that. My problem is that the WIFI is not availible after the boot in ARMbian. Is there any solutions for make it availible? Thank you in advance.

moved

@Sergey Lepeshkinok

I did not detect the fancontrol issue sooner as I had not tested the trixie image. Indeed PrivateDevices=no should be set because helios64 and helios4 points fancontrol tu /dev symlinks prepared via udevs rules to sysfs files. I don't know if I can get rid of these udev rules, ie if I have persistend access to the proper sysfs directories for thermal and hwmon required by fancontrol on helios64. I also question why only 3 boards uses fancontrol in armbian. I had a thermal policy patch for the dts, it has the added bonus that it works when the kernel start and until it stops thus no uneeded high fan speed before fancontrol start and after it stops. But I am still wondering why kobol team chossed fancontrol and thus what are the pros and cons of fancontrol vs dts thermal policy. https://github.com/armbian/build/pull/8928 PR to set PrivateDevices=no when one upgrades armbian-bsp-cli-helios64-current or edge is in the pipe.