Hi. Do you still want to sell your helios64 ?

@dfahren you can configure modprobe like the above to display "boot" without modifying the source code. You could even replace "echo boot" with "display-utils -t whatever" to scroll any text you would like. I really think this is a much better way to do so. It prevents having the driver module to manage content instead of the device. The idea of turning on all led at module probe is to ease diagnostic of module configuration, much like a car console that will turn on all subsystems LEDs when turning the ignition key. Personally, I don't understand why so many people want to display "boot" but it's up to you to customize the display the way you want.

armbian failed fastmirror.pp.ua:80 Do first: curl -s http://apt.armbian.com/mirrors | jq . Do second: vi /etc/apt/sources.list.d/armbian.list change https://apt.armbian.com to any another mirror from step 1 Edit /etc/apt/sources.list.d/armbian.sources and replace the URL https://apt.armbian.com with your preferred mirror. Step 3: rm -rf /var/lib/apt/lists/* apt update --fix-missing && apt upgrade use it! apt autoclean && apt autoremove # after

Today unattended upgrades ran and installed the following: libtasn1-6 linux-dtb-current-odroidxu4 linux-image-current-odroidxu4 linux-u-boot-odroidxu4-current Afterward, the system automatically rebooted and went into a boot loop. I had a backup I was able to copy to the emmc and get back up and running but it is from October 2024 and I am not really sure what to do. coming here to see if anyone else has experienced the same. I tried to run armbianmonitor -U and it had some weird html. I am pretty good with Linux but everything is self taught. thank you in advance for any help Dan

I don't know why it is working but you can edit the armbianEnv.txt and add overlays=ssd-sata then reboot. The OS will recognize the NVME disk