Meestor_X

If you'd like to get the LEDs working with armbian, you can run these commands (or one of the other ones if you want different indications): run modprobe ledtrig-netdev to check if it's loading the driver properly. If not, add the file /etc/modules-load.d/ledtrig.conf add just this line: ledtrig-netdev Then, create /etc/tmpfiles.d/leds.conf and add this: w /sys/class/leds/green:lan/trigger - - - - netdev w /sys/class/leds/green:lan/device_name - - - - eth0 w /sys/class/leds/green:lan/link - - - - 1 w /sys/class/leds/green:lan/tx - - - - 1 w /sys/class/leds/green:lan/rx - - - - 1 w /sys/class/leds/green:wan/trigger - - - - netdev w /sys/class/leds/green:wan/device_name - - - - eth1 w /sys/class/leds/green:wan/link - - - - 1 w /sys/class/leds/green:wan/tx - - - - 1 w /sys/class/leds/green:wan/rx - - - - 1 w /sys/class/leds/red:power/trigger - - - - activity Note that "red:power" is actually the "green:sys" LED. I don't see a way to control the red power led (which is fine, the green:sys is what want to control anyway). I also use NetworkManager and set my ethernet names to eth0 and eth1 instead of the default names... Here's all the choices available for "triggers": none usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock disk-activity disk-read disk-write mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 activity default-on panic usbport mmc1 rfkill-any rfkill-none r8169-0-100:00:link r8169-0-100:00:10Mbps r8169-0-100:00:100Mbps r8169-0-100:00:1Gbps stmmac-0:01:link stmmac-0:01:10Mbps stmmac-0:01:100Mbps stmmac-0:01:1Gbps netdev "activity" is also a good one for red:power if you prefer that to "heartbeat"

I see there's an overlay for the R4S called rk3399-dwc3-0-host, but it already seems to be in host mode by default. I can't figure out how to set it to peripheral mode so I can have some usb-gadget love. Anyone figured out a fix?

Testing the latest build: apt update && apt upgrade -y Hit:1 http://deb.debian.org/debian trixie InRelease Get:2 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB] Get:3 http://security.debian.org trixie-security InRelease [43.4 kB] Get:4 https://github.armbian.com/configng stable InRelease [5,467 B] Get:5 http://deb.debian.org/debian trixie-backports InRelease [54.0 kB] Err:2 http://deb.debian.org/debian trixie-updates InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:41Z Verifying signature: Not live until 2026-03-02T13:39:55Z Err:3 http://security.debian.org trixie-security InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T02:15:55Z Verifying signature: Not live until 2026-03-02T02:15:55Z Err:4 https://github.armbian.com/configng stable InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T16:02:28Z Err:5 http://deb.debian.org/debian trixie-backports InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:27Z Verifying signature: Not live until 2026-03-02T13:39:49Z Get:6 http://fi.mirror.armbian.de/beta trixie InRelease [39.4 kB] Err:6 http://fi.mirror.armbian.de/beta trixie InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T08:25:38Z Fetched 190 kB in 1s (143 kB/s) All packages are up to date. Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://deb.debian.org/debian trixie-updates InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:41Z Verifying signature: Not live until 2026-03-02T13:39:55Z Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://security.debian.org trixie-security InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T02:15:55Z Verifying signature: Not live until 2026-03-02T02:15:55Z Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://github.armbian.com/configng stable InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T16:02:28Z Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://deb.debian.org/debian trixie-backports InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:27Z Verifying signature: Not live until 2026-03-02T13:39:49Z Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://fi.mirror.armbian.de/beta trixie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T08:25:38Z Warning: Failed to fetch https://github.armbian.com/configng/dists/stable/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T16:02:28Z Warning: Failed to fetch http://beta.armbian.com/dists/trixie/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T08:25:38Z Warning: Failed to fetch http://deb.debian.org/debian/dists/trixie-updates/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:41Z Verifying signature: Not live until 2026-03-02T13:39:55Z Warning: Failed to fetch http://deb.debian.org/debian/dists/trixie-backports/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:27Z Verifying signature: Not live until 2026-03-02T13:39:49Z Warning: Failed to fetch http://security.debian.org/dists/trixie-security/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T02:15:55Z Verifying signature: Not live until 2026-03-02T02:15:55Z Warning: Some index files failed to download. They have been ignored, or old ones used instead. Summary: Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0 root@radxa-cubie-a5e:~# armbianmonitor -u Collecting info and sending to paste.armbian.com, wait... https://paste.armbian.com/zefutefuzi Please post the URL in the forum where you've been asked for. https://paste.armbian.com/zefutefuzi

While attempting, using AI, to see if there were DTS changes that could help this (spoiler: there aren't), it came up with some DTB changes that it claims need to be made for the board's stability. Maybe someone who understands these things can see if they got it right? Also, does the new allwinner update for armbian help/fix any of the cubie's USB/Power issues? https://github.com/armbian/build/pull/9381 a5e-armbian-DTS.patch

Hi Brent; YES! I did figure it out, finally. The issue is that almost all information on the web is for the older pipewire and wireplumber which works completely differently than the new versions. Bookworm used the "old way" and Trixie uses these new versions for which there isn't much info. Compounding the issue is that most information is regarding desktop versions of Linux, not headless like I run. So, when you use bluetooth on linux, wireplumber auto-creates profiles and pw nodes. Or at least it's supposed to. It wasn't creating these profiles because I was missing a conf file which is only needed when your NOT running on desktop, AFAICT. Add this file: /etc/wireplumber/wireplumber.conf.d/50-bluez-no-seat.conf wireplumber.profiles = { main = { monitor.bluez.seat-monitoring = disabled } } If you do that, all of sudden, bluetooth "just works". Took forever to find that stupid little piece of information.

Ok, in case anyone's got any ideas about how to fix this, I'm happy to help if I can, but kernel repairs are a bit out of my league... It seems to reboot for different reasons - when it doesn't like something connected to the USB port, when doing a lot of disk I/O, etc. Here's a couple of the error logs from the terminal: INFO: task sgdisk:1567 blocked for more than 120 seconds. Tainted: G O 6.18.10-edge-sunxi64 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:sgdisk state:D stack:0 pid:1567 tgid:1567 ppid:1566 task_flags:0x400000 flags:0x00000018 Call trace: __switch_to+0xcc/0x180 (T) __schedule+0x348/0xaf8 schedule+0x38/0x110 io_schedule+0x40/0x60 folio_wait_bit_common+0x15c/0x390 folio_wait_bit+0x1c/0x30 folio_wait_writeback+0x4c/0xb8 __filemap_fdatawait_range+0x70/0xb0 filemap_fdatawait_keep_errors+0x24/0x58 sync_bdevs+0xb4/0x1a8 ksys_sync+0x64/0x98 __arm64_sys_sync+0x14/0x28 invoke_syscall.constprop.0+0x54/0xe8 do_el0_svc+0x44/0xc8 el0_svc+0x38/0x140 el0t_64_sync_handler+0x98/0xe0 el0t_64_sync+0x170/0x178 Kernel panic - not syncing: hung_task: blocked tasks CPU: 6 UID: 0 PID: 61 Comm: khungtaskd Tainted: G O 6.18.10-edge-sunxi64 #1 PREEMPT Tainted: [O]=OOT_MODULE Hardware name: Radxa Cubie A5E (DT) Call trace: show_stack+0x1c/0x30 (C) dump_stack_lvl+0x30/0x80 dump_stack+0x14/0x20 vpanic+0x2d4/0x308 panic+0x50/0x58 watchdog+0x278/0x718 kthread+0x134/0x1f8 ret_from_fork+0x10/0x20 SMP: stopping secondary CPUs Kernel Offset: disabled CPU features: 0x080000,00008000,48006281,0400701b Memory Limit: none ---[ end Kernel panic - not syncing: hung_task: blocked tasks ]--- INFO: task systemd-udevd:285 blocked for more than 120 seconds. Tainted: G O 6.18.10-edge-sunxi64 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:systemd-udevd state:D stack:0 pid:285 tgid:285 ppid:1 task_flags:0x400100 flags:0x00000809 Call trace: __switch_to+0xcc/0x180 (T) __schedule+0x348/0xaf8 schedule+0x38/0x110 io_schedule+0x40/0x60 folio_wait_bit_common+0x15c/0x390 folio_wait_bit+0x1c/0x30 folio_wait_writeback+0x4c/0xb8 __filemap_fdatawait_range+0x70/0xb0 filemap_write_and_wait_range+0x90/0xc0 sync_blockdev+0x24/0x40 bdev_disk_changed+0x64/0x5c8 blkdev_get_whole+0xa4/0xf8 bdev_open+0x278/0x3b0 bdev_file_open_by_dev+0xdc/0x148 disk_scan_partitions+0x6c/0x150 blkdev_ioctl+0x664/0xfc0 __arm64_sys_ioctl+0x470/0xaa0 invoke_syscall.constprop.0+0x54/0xe8 do_el0_svc+0xa4/0xc8 el0_svc+0x38/0x140 el0t_64_sync_handler+0x98/0xe0 el0t_64_sync+0x170/0x178 INFO: task sgdisk:1465 blocked for more than 120 seconds. Tainted: G O 6.18.10-edge-sunxi64 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:sgdisk state:D stack:0 pid:1465 tgid:1465 ppid:1464 task_flags:0x400000 flags:0x00000008 Call trace: __switch_to+0xcc/0x180 (T) __schedule+0x348/0xaf8 schedule+0x38/0x110 io_schedule+0x40/0x60 folio_wait_bit_common+0x15c/0x390 folio_wait_bit+0x1c/0x30 folio_wait_writeback+0x4c/0xb8 __filemap_fdatawait_range+0x70/0xb0 filemap_write_and_wait_range+0x90/0xc0 bdev_release+0x19c/0x1b0 blkdev_release+0x18/0x30 __fput+0xd0/0x2e8 fput_close_sync+0x44/0x108 __arm64_sys_close+0x3c/0x88 invoke_syscall.constprop.0+0x54/0xe8 do_el0_svc+0x44/0xc8 el0_svc+0x38/0x140 el0t_64_sync_handler+0x98/0xe0 el0t_64_sync+0x170/0x178 Kernel panic - not syncing: hung_task: blocked tasks CPU: 1 UID: 0 PID: 61 Comm: khungtaskd Tainted: G O 6.18.10-edge-sunxi64 #1 PREEMPT Tainted: [O]=OOT_MODULE Hardware name: Radxa Cubie A5E (DT) Call trace: show_stack+0x1c/0x30 (C) dump_stack_lvl+0x30/0x80 dump_stack+0x14/0x20 vpanic+0x2d4/0x308 panic+0x50/0x58 watchdog+0x278/0x718 kthread+0x134/0x1f8 ret_from_fork+0x10/0x20 SMP: stopping secondary CPUs Kernel Offset: disabled CPU features: 0x080000,00008000,48006281,0400701b Memory Limit: none ---[ end Kernel panic - not syncing: hung_task: blocked tasks ]---

I've gotten it working. I'll detail the steps soon, but it's not difficult. I just want to confirm that running it this way I can boot from sd/usb/nvme/eMMC/Network, and see if changing the boot order works.

Not excited AT ALL about Allwinner, but there are few (actually none that I've found?) choices for low-priced, "higher performance" SBCs with WiFi 6, BT 5.4, USB3, GB Ethernet, PoE and a small size and factory case. I'll take anything rockchip in a heartbeat I much prefer their chips. My go-to has been the RockPI-S, but it's low performance CPU, WiFi 4, BT 4, 100M Ethernet, USB2, and getting pretty old. AFAIK, there's nothing out there that checks all the boxes, sadly.

I seem to remember at one point thinking that U-Boot could be installed into the SPI on the a5e and then I could choose the boot order. Is that possible or did I just dream it? If it is, how do I install U-Boot into the SPI? Is there one specifically for the a5e?

Just tested trunk 244, (Armbian_community_26.2.0-trunk.244_Radxa-cubie-a5e_trixie_edge_6.18.5_minimal.img.xz) and it doesn't have this reboot issue. However, trunk 244 doesn't support the PCIe, USB3 or WiFi/BT so something must have changed when those devices started to be supported recently. I take that back, it does still have the rebooting issue. I'll keep digging.

Lol. Maybe for YOU!! 😉 So I can post my questions about it here, then? Appreciate the help.

The e25 that I have has SD, eMMC and NVME storage options. It has an MTD/SPI as well. Pretty sure it's similar to the Cubie a5e where you can set the boot order in the SPI, however I just chatGPT'd the shit out of that one to get it sorted. I'd prefer to do it the "approved/armbian" way... Again, I assume having U-Boot in the SPI is the appropriate way to do things so I can boot from any of these devices (and perhaps even external USB?). I'd like to understand how to do that if someone knows?

I assume I should be using the MTD/SPI for u-boot on this device? If so, how do I update it and choose the boot order? armbian-install complains "No SPI image found." if I select "Install/Update the bootloader on MTD Flash"

I'm having trouble understanding armbian-install, is this a good place to discuss? Basically, I'd like to understand the menu options better. Probably because it's a generic tool for all devices, the selections aren't clear (to me at least), depending on what device I'm working with. For the most part, all I ever need to do is to copy the working SD image to the eMMC or NVME. Any armbian-install gurus lurking?

This would be amazing. I don't suppose anything came of this? I'm not sure if armbian-install is still actively maintained, but I'm not having any luck using it with several boards I have now.