Active threads

@Ducdanh Nguyen, if you mean usb<->uart converter, virtually anything with cmos/ttl 3.3v. i/o levels (5v. probably is fine too) will work. Based on ch340 or pl2303 or cp2101 or some FTDI chips - all they should work. But don't use usb<->rs232 converters or COM port directly. If you talking about soldering some sort of connector to tv box board, then I can't suggest anything, except some straight separate pin. This test points are just separate pads and they don't suit any of connectors I familiar with. IMO better way is to solder thin flexible wires (preferably in PTFE or silicone insulation) to the board, and then solder any kind of connector to them. You need uart connected only if you wish to interact by it means with tv box. Through uart you can interact with u-boot bootloader, inspect kernel output and have access to shell console with 'su' enabled. But, just to simply boot tv box, you don't need uart.

@ayoub-hs I don't own one of these boxes. I got the patches from warpme's miniarch/minimyth2. Supporting the x96q is a real PITA. https://github.com/warpme/miniarch/issues/102 Comparing the uboot DTS for both x96q lpddr3 and x96q lpddr3 v1.3. I don't see much difference other than wifi. Maybe you'll find something I missed. u-boot: https://github.com/NickAlilovic/build/blob/v20250306/patch/u-boot/u-boot-h616/159-add-x96-q-lpddr3-v1.3-defconfig.patch https://github.com/NickAlilovic/build/blob/v20250306/patch/u-boot/u-boot-h616/150-add-x96-q-lpddr3-defconfig.patch Kernel: https://github.com/NickAlilovic/build/blob/v20250306/patch/kernel/archive/warpme-6.12/0648-arm64-dts-allwinner-h313-add-x96q-lpddr3-TVbox.patch https://github.com/warpme/minimyth2/tree/master/script/bootloaders https://github.com/warpme/minimyth2/tree/master/script/bootloaders/u-boot-aw/files

I guess you need something similar to udev rule for Logitech Fn key: http:// https://github.com/sta-c0000/logitech-keyboard-udev-rules. IMHO it is more reliable and less resource hungry vs software package, but I have not seen alike for a Win key. So it might be necessary to spy on software doing this and develop udev rule for win key. May be someone on the forum having enough experience could help.

DDR Version V1.08 20210520 ln ddrconfig:3 DDR4, 324MHz BW=32 Col=10 Bk=4 BG=4 CS0 Row=16 CS=1 Die BW=8 Size=4096MB wrlvl:clk skew:0x80,0x80

Thanks but THIS is the question Can anyone provide a confirmed working ffmpeg command line for camera capture and hardware encoding? T.

Awesome! Thank you for adding it!

Hi @Hqnicolas I have same issue with booting from SD card for a board (RK3399) . Can you please share the u-boot image or guide to compile for that chip?

@robertoj I use Nick's exact build (specify the branch) with bookworm. My tanix68 unit has a custom Hal and supplicant firmware, which I'm trying to integrate correctly, but LAN works just fine.

I've tried several recent releases back to bookworm, but the minute I turn apt loose to bring it up to date with a new kernel, in the last case 6.12.59, all /dev/sd* stuff disappears. WTH? I've been contributing to this project for several months

I tried on a RPI and it did indeed detect the OLED display. I forced the scan: # Force scan all addresses for i in {0..127}; do sudo i2cget -y 1 $i 2>/dev/null && echo "Device found at: 0x$(printf '%02x' $i)" done and it returned nothing

I've checked performance of my old rk322x-based box (H2O with 1.5G RAM/4G ROM) and compared it with fresh, h618-based. sysbench shows that rk322x is ~20x times slower in CPU (rk322x - 39 events, h618 - 700 events) and 6x times slower in RAM operations (216MB/s vs 1333 MB/s). in threads test rk3222x is just less than 2x times slower (4317 events vs 7563 events). are these values OK? or maybe something is mistuned?

No clue

Can someone confirm that xwayland is working in the other wayland desktops in armbian? I can't make it work in labwc

Hi all, I got my hands on an Odroid XU4 and wanted to use it as a replacement for my RPi 3 for all my amateur radio related stuff. Unfortunately all of the AX25 kernelmodules have been left out of official builds. I have a commit ready to add them back, yet I am not sure what the actual process is to submit a PR. As I understood I need to open an issue first yet I cannot figure out which category this fits in. I attached a patch file for current kernel. Thank You, Geoffrey ax25.patch

Share your DTS. It is the most challenging part of this. We can customize, based on SBC model.

@Gian Luca On Wayland, you can install the "gnome-remote-desktop" package to enable remote. However, I don't recommend it because it has an issue where the audio is lost after a remote session and reboot (which I don't know how to fix).

@nom What do you mean? Armbian Edge with the mainline kernel and PanVk is working properly.

@0jay the work I've done on the firmware is here: https://github.com/bschnei/ebu-bootloader. Looks like MOCHAbin is an Marvell Armada 88F7040. I believe with the correct changes to configuration, you can build firmware with my scripts. There is another user here with ESPRESSObin v7 and v5 devices that may try to build firmware using my scripts as well:

To build for other devices, you need to figure out the correct configuration and adjust these values accordingly: https://github.com/bschnei/ebu-bootloader/blob/main/Makefile#L15-L19 Reference for configuration options is here: https://trustedfirmware-a.readthedocs.io/en/latest/plat/marvell/armada/build.html So for V7 you probably want DDR_TOPOLOGY of 5 or 6 depending on RAM size; for V5 a value of 2. You'll have to look up your defconfig in u-boot. It's probably this one: https://github.com/u-boot/u-boot/blob/master/configs/mvebu_espressobin-88f3720_defconfig but note that I have added an ultra variant here: https://github.com/u-boot/u-boot/blob/master/configs/mvebu_espressobin_ultra-88f3720_defconfig which has settings required to provide HWRNG to the kernel at boot. So you may way want to start with the default if it is known to work and experiment with your own configuration file. You know how to test an image without flashing it to SPINOR, right? I have a guide at my repo above. Regarding Armbian and device support in general, there is another thread here where I had some back and forth a while back:

I am having the same issue on Nanopi Neo Air and uname -r 6.12.51-current-sunxi I can't find a solution. I can also as @mue473 mentioned see that prebuild kernel modules: readelf -r netlink_diag.ko | grep cleanup 00000000 00003402 R_ARM_ABS32 00000001 cleanup_module 000002d4 00003402 R_ARM_ABS32 00000001 cleanup_module while my own has readelf -r testm.ko | grep cleanup 00000000 00004902 R_ARM_ABS32 00000001 cleanup_module 000002c4 00004902 R_ARM_ABS32 00000001 cleanup_module I have no idea though if this matters at all. Does anyone know?

Hi all, I just installed Armbian Linux v6.12 with OpenMediaVault (build date 2025/09/23) on a Odroid HC4. When I try to use apt update I get these errors Get:1 file:/var/cache/openmediavault/archives InRelease Ign:1 file:/var/cache/openmediavault/archives InRelease Get:2 file:/var/cache/openmediavault/archives Release Ign:2 file:/var/cache/openmediavault/archives Release Get:3 file:/var/cache/openmediavault/archives Packages Err:3 file:/var/cache/openmediavault/archives Packages Method gave a blank filename Get:3 file:/var/cache/openmediavault/archives Packages Err:3 file:/var/cache/openmediavault/archives Packages Method gave a blank filename Get:3 file:/var/cache/openmediavault/archives Packages Err:3 file:/var/cache/openmediavault/archives Packages Method gave a blank filename Get:3 file:/var/cache/openmediavault/archives Packages Err:3 file:/var/cache/openmediavault/archives Packages Method gave a blank filename Get:3 file:/var/cache/openmediavault/archives Packages Err:3 file:/var/cache/openmediavault/archives Packages Method gave a blank filename Get:3 file:/var/cache/openmediavault/archives Packages Err:3 file:/var/cache/openmediavault/archives Packages Method gave a blank filename Get:3 file:/var/cache/openmediavault/archives Packages Is this expected and related to Armbian setup or should I ask on OMV forum?

I think I messed something up in the system, maybe with the repositories, but I get this message when updating... apt update Stary:1 http://deb.debian.org/debian bookworm InRelease Stary:2 http://security.debian.org bookworm-security InRelease Stary:3 https://download.docker.com/linux/debian bookworm InRelease Stary:4 http://deb.debian.org/debian bookworm-updates InRelease Stary:5 http://deb.debian.org/debian bookworm-backports InRelease Stary:6 https://dtcooper.github.io/raspotify raspotify InRelease Stary:7 https://github.armbian.com/configng stable InRelease Stary:8 http://armbian.lv.auroradev.org/beta bookworm InRelease Czytanie list pakietów... Gotowe Budowanie drzewa zależności... Gotowe Odczyt informacji o stanie... Gotowe 1 package can be upgraded. Run 'apt list --upgradable' to see it. root@orangepi3-lts:~# apt list --upgradable Listing... Gotowe armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49] N: There is 1 additional version. Please use the '-a' switch to see it root@orangepi3-lts:~# apt list --upgradable -a Listing... Gotowe armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49] armbian-bsp-cli-orangepi3-lts-current/now 25.8.0-trunk.49 arm64 [installed,upgradable to: 25.11.0-trunk.401] maybe someone has already dealt with this message and error?

Armbian Version: 6.12.56-current-rockchip64 TV Box: I have same board that is mentioned at this post. Issue: using the .dts mentioned in the above link I am able to see the clock with blinking separator. However I am not seeing the disk activity or LAN connections icon. If I am using devicetree changed to rk1188-box-led-conf-5, I can see the disk blinking icon and LAN connection, however the clock is not visible. Is there anyway I can get the clock as well the icons? Can you share the steps or the post that has the solution to this?

When I first flashed your latest image, the USB2 port did not work, only the blue port works. I then applied this overlay and after rebooting it now works. USB3 speed is still not functional. rk3528-x88pro13-usb2ndhost.dts rk3528-x88pro13-usb2ndhost.dtbo

This is a reply to treii28's post from 2023: To enable i2c on PH4 and PH5 pins, one would have to have to following lines in /boot/armbianEnv.txt files: Reboot and see the new devices with: Scan for all the connected i2c devices: All relevant (and some extra) overlays can be seen with the following command: To see the configuration one could disassemble the dtb binary file and search it's contents for i2c3-ph Whenever making changes it would be the best to connect a serial monitor to the physical serial pins (3 separate pins labeled with UART and GND, RX, TX) to see kernel output at boot (115200 baud rate). The kernel log would have a line for loading the dtbo (or maybe an error for missing file: For easier reference there are included lsmod output, kernel config and dts files from an armbian and the opiz version for "original" debian image (distributed by a sketchy Google drive link, it runs an unnecessary service with weird software repositories enabled by default). lsmod-armbian lsmod-opiz kernel-armbian.config kernel-opiz.config opz3-armbian.dts opiz3-opiz.dts