Thanks for your insights @eselarm. I was led to believe that the bootloader could not have any impact on this - guess AI is wrong again 😅 Anyhow I am running EDK2-UEFI v1.1 so might try one of the later artifacts

Please read the FAQ and installation instructions linked on the download page. https://www.armbian.com/amlogic-s9xx-tv-box/

thank you for your reply! I reverted to the stock ubuntu for opi5 for now. I will have a new device in my hands in the next days, I will then try this

hi @spaceship we 'need to start working on it', what that means is that if you search around sufficiently, it is likely u-boot (the bootloader) and linux already supported A733. the task is 'system integration' to build that into Armbian. But as with all things, it means work, to spend hours / days figuring out how to do that and to do so and send a pull request for Armbian to include it. The challenges in life is such that most of us (including me) has very little fragmented time / energy to work on it. Perhaps that if more users 'request' it and support Armbian by way of donations, maybe they'd try to put it together and complete this work. The initial integration is one thing, the trouble is that linux keeps moving and linux 7.0 is about to be real. Hence, say you take what is there now integrate it, and no sooner 7.0 is out, you need to keep maintaining it. Hence, for a more sustainable setup, perhaps is for the community to fund Armbian to do so with donations, and efforts from the side. it is good for the community to support this effort both finanically and efforts from the side, this is to ensure that there is no "influence from a controlling (3rd) party" (possibly including a govt) i.e. no conflict of interest, e.g. to try to embed exploits in it for the govt's or 3rd party purpose, as in that the project is truly open source and inspected to prevent such exploits. but for what is worth, what it takes is a 'project' to get from here to integration e.g. in an 'edge' 7.0 kernel. --- off-topic but related, the security situation affecting commonly used commodity devices sold globally is *bad* https://www.kaspersky.com/about/press-releases/kaspersky-discovers-keenadu-a-multifaceted-android-malware-that-can-come-preinstalled-on-new-devices https://securelist.com/keenadu-android-backdoor/118913/ https://www.tomsguide.com/computing/malware-adware/dangerous-new-keenadu-malware-found-pre-installed-on-cheap-android-phones-and-tablets-how-to-stay-safe https://www.forbes.com/sites/daveywinder/2026/02/17/android-backdoor-pre-installed-on-devices---thousands-already-infected/

Hello NickA, fire-hound from discord here ... You do a tremendous service for us all, keep it up buddy! I loaded your recent build from here: https://github.com/NickAlilovic/build/releases and can confirm it works on my A7A. It correctly detected my Pimorony NVME Base lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 8M 0 disk mmcblk0 179:0 0 29.2G 0 disk ├─mmcblk0p1 179:1 0 256M 0 part /boot └─mmcblk0p2 179:2 0 28.6G 0 part /var/lib/containers/storage/overlay /var/log.hdd / zram0 254:0 0 3.9G 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log zram2 254:2 0 0B 0 disk nvme0n1 259:0 0 238.5G 0 disk └─nvme0n1p1 259:1 0 238.5G 0 part /srv/dev-disk-by-uuid-b28b2f5c-ee2e-4ded-959e-22bc63051b1d and: screenfetch _,met$$$$$gg. root@radxa-cubie-a7a ,g$$$$$$$$$$$$$$$P. OS: Debian 13 trixie ,g$$P"" """Y$$.". Kernel: aarch64 Linux 6.6.98-vendor-sun60iw2 ,$$P' `$$$. Uptime: 11h 14m ',$$P ,ggs. `$$b: Packages: 661 `d$$' ,$P"' . $$$ Shell: bash 5.2.37 $$P d$' , $$P Disk: 4.9G / 271G (2%) $$: $$. - ,d$$' CPU: ARM Cortex-A55 Cortex-A76 @ 8x 1.794GHz $$\; Y$b._ _,d$P' RAM: 534MiB / 7928MiB Y$$. `.`"Y$$$$P"' `$$b "-.__ `Y$$ `Y$$. `$$b. `Y$$b. `"Y$b._ `"""" So far so good The issues: 1. The typical Armbian image has a module in the armbian-config and radxa's rsetup where one can set up the two leds conveiently to other than full on and heartbeat for the green and blue gpio leds respectively. I find it to be a nuisance to dig for that manually 2. The Ovralys module in armbian-config is returning an error - when entering DTO001 module (Device Tree Overlays) saying: Invalid overlay_prefix that might require deeper digging into the issue i guess? What works: Open Media Vault registers the NVME nicely as additional storage. I suspect booting off that NVME would work for an updated SPI bootloader i could test that if you want me to? If you need any other info or output I stand at Your disposal 😁