Active threads

You could use the Cubie for it. The trunk.100 works you said, so you have a working Linux computer, can be operated via serial cable console.

moved to tvboxes

Post the UART log.

Succes, I lowlevel formatted my SD cart. Now i can install the CLI I think there was something not right The next thing to try is install a desktop image. And fix the overscan issue and then install to the emmc internal memory My internal menory is Sandisk SDINADF4-16G so i am hopefull. But when i brick the system, is it stil possible to boot from a SD card or must i try to flash a version of android first using a USB A to USB a cabble? Sorry I am not allowed to upload Image?

@Werner OK, since I have a few Duos (v1.0 and v1.1) I tried same Jammy with 6.1.63 kernel SD in each and let idle. The 1.1 with copper heatsink runs about 40C, the 1.1 with same aluminum heat sink runs around 45C. The v1.0 runs around 50C. So weird. I'll try latest build, but stress-ng causing thermal shutdowns worries me. I used to run decent loads on these little boards. Good thing is thermal shutdown works or it would burn up the board.

How can I force it to boot from SD though?

As a followup: hardware crypto is damn slow on the Ky / SpacemIt platform, at least for default LUKS block encryption with AES. This probably also affects the Banana Pi F3 image. With default sector-size of 512 byte, HW-AES is 5 times slower than SW-AES, while cryptsetup benchmark reports 5 times faster. Main reason: block size. With sector-size of 4096 LUKS is reasonable fast. Also there is leftover debug (cannot be switched off) and a small bugs in the driver that triggers SW crypto fallback after HW crypto succeeds. Patches: https://github.com/sven-ola/armbian-build/tree/orangepi-rv2/patch/kernel/ky-current Best // Sven-Ola

I do not use chatgpt Most of them are rubbish anwers

Here is ukrainian forum with Android for this box: https://legione.name/upload/?dir=Smart-TV-Box/Q1/ Any chance to find linux for the same box? Android tv box q1 v3.0 Allwinner H313 If someone will find working version, please share

Hello! It seems that there is some issue with the user files FTP server. The multitool image should be acessessible from: https://users.armbian.com/jock/web/rk322x/multitool/ But it is present in: https://users.armbian.com/users.armbian.com/jock/web/rk322x/multitool/

I now actually see after some more reading and checking other SoC's that the CPU's in the A733 must start the kernel at EL2. See also ARM reference doc: 102412_0103_01_en So also 5.x kernel should work if EL2 I think If the A733 has not implemented EL2 and EL3 as could be the case as suggested in ARM reference doc, no KVM. See chapter6: As it is Allwinner, I won't be surprised, but wait and see what Radxa will come up with.

npu is there in both vendor bsp kernel 6.1.y. There is no node exposed afaik. Everthing beyond like libraries to use npu is userspace and out of scope of Armbian. edge 6.18.y also has reverse-engineered npu support with a driver called Rocket.

Good afternoon. I'm trying to stream video to my orange pi zero 2w. I am using Gstreamer and while testing I saw that v4l2slh264dec fails. When using autosink, only a transparent window is shown and when using a specific sink, no window is opened. My intention is to take advantage of the VPU with Gstreamer but that failure has caused me headaches. I tried using MVP and it works fine but it's not what I need. Maybe I will choose other options for what I want to do but first I would like to ask here about the topic- Thank you very much to whoever takes the trouble to read this and thanks in advance to whoever responds ❤️ By.: Google Translate

Developing solutions and sharing by sending PR and/or using customize image script might be the way address those.

Hi, I'm new to this forum but I've been researching this topic for quite some time. I have a Mecool KM1 Deluxe with 4GB of RAM and 64GB of storage, and an Amlogic S905X3 chip. I wanted to install Armbian to use it as a Linux device, but I've tried several versions and it hasn't worked. Someone mentioned on this forum that installing CoreELEC would prevent Armbian from booting. I installed emuelec and it worked perfectly, but I haven't been able to run Armbian. Could this be the reason? Thanks.

I've been using my Helios64 nonstop since i got it in 2020 (and the Helios 4 since 2018). It's been great the whole time; does exactly what I want it to do, and now I've made it my sole Plex server to save power. My only problem is that the internal eMMC is now 100% full (thanks to Plex), and I can't work out how to move the install back to the SDCard (Linux noob...), which is my I'm here. I'm sad these guys had to shut down. This could have been a magnificent project

Hello, Here is a config file that works with linux-6.6.119 config-6.6.119 And a tarball here : https://drive.google.com/file/d/14EHPMT01-geYNflC2lqXNue4ZH25z-lA/view?usp=drive_link with a fresh built kernel. Two small patches are needed : one to activate the wifi/bluetooth card (in dtb file), another to add a delay in mwifiex_sdio.c What works : wifi, eth0 and eth1 cards I can't activate the bluetooth card with btmrvl_sdio (need to be investigate) If someone else can test this (@rolli_44 , @umiddelb ? ). Next : propose a patch to integrate this board in armbian ?

log says: No space left on device So you need to look at that, remove unneeded stuff etc. Also check the output of df Maybe something else is wrong

OrangePi in general is bad support, as also is stated on the image download page. For just driving a relay, so a pin change between high and low, you first need to select which pin from the GPIO header you want to use. You can see what are probably generic GPIO by default from picture here: http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-2W.html In the latest image, I see there is no real support for OrangePi02W, only H5 and A64, not the actual H618 (it seems to use H616, so also that might lead to issues). You can look in file maybe, if you want other then defaults: /boot/dtb/allwinner/overlay/README.sun50i-H5-overlays I have older 32-bit Allwinner things, H3 for example. Analog and SPDIF audio works great there, that is why I bought those mainly. Also GPIO6 I use for driving a switch (via extra resistors and some MOSFET/TRIAC). I did some C-code and got working temp sensor and switch, see lgio code https://abyz.me.uk/lg/download.html But currently for years already in bash script: init: test -f /sys/class/gpio/gpio6/value && echo 6 > /sys/class/gpio/unexport echo 6 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio6/direction chown root:gpio /sys/class/gpio/gpio6/value chmod g+w /sys/class/gpio/gpio6/value on: gpioset gpiochip0 6=1 off: gpioset gpiochip0 6=0 This still works since Armbian Buster, now kernel 6.12. Not tested yet with 6.18

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + wine-10.14-staging-tkg-ntsync-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/10.14) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v1.6.1 ~60fps@720p Noted: . The DX9 version of the game is black-screen. . The DX10 version works. However, it will crash immediately after the tutorial stage because the PanVk driver still lacks the "Geometry Shaders" feature. . By using dgVoodoo2, the DX9 black screen issue was fixed. Devil May Cry 4 (DX9 + dgVoodoo2 + DXVK) Devil May Cry 4 (DX10)

As I said above, there is no usb otg functionality. If you want shell as ordinary user - install any app which allows access to shell (I'm using "Admin hands" in local shell mode) on your tv box. In this mode 'su' refuses to escalate privileges. If you want root access, you should connect using uart (see my messages above). You will get access to u-boot and android console. There you can execute 'su' and it will give you root privileges.

This started happening fairly recently. If my Docker containers are left running for a period of time, this message will start appearing over and over in journalctl: dockerd[1491]: time="2025-12-27T20:55:44.808894213-05:00" level=error msg="Error writing log message" driver=json-file error="error writing log entry: write /var/lib/docker/containers/97e823567c56600b69888e6abf63189c6f586afbf6bcf06fca820eaf4ef46f7d/97e823567c56600b69888e6abf63189c6f586afbf6bcf06fca820eaf4ef46f7d-json.log: no space left on device" message= After a while, these two messages will start repeating (these were taken from a different instance of this happening, so the PID is different): rsyslogd[599]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2504.0 try https://www.rsyslog.com/e/2027 ] rsyslogd[599]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2504.0 try https://www.rsyslog.com/e/2027 ] Looking at btop when this is happening shows that the rsyslog and dockerd processes are using up most of the CPU, along with fail2ban for some reason. The full command for dockerd is: /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock Here are all my docker packages: docker-buildx-plugin/trixie,now 0.30.1-1~debian.13~trixie arm64 [installed] docker-ce-cli/trixie,now 5:29.1.3-1~debian.13~trixie arm64 [installed] docker-ce/trixie,now 5:29.1.3-1~debian.13~trixie arm64 [installed] docker-compose-plugin/trixie,now 5.0.0-1~debian.13~trixie arm64 [installed]

I would check out the boards with Platinum Support. Go to the vendor sites to see if they include or sell a fan for their board. Look for something with a Rockchip RK3576, plenty of RAM, and EMMC or UFS. RK3588 usually needs a fan.

I reread it, but the information is not publicly available. Contact them directly? I haven't tried. Maybe they can help. Thanks for your time. I'll write back later; maybe someone will be interested.

That would be a good start indeed.