All Activity

@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.

@leXia "no matter which image I use, it always boots into Android". Maybe it's not booting into FEL mode or it's not reading your SDcard. To enter FEL mode, power off the TV box, insert your SDcard, press and hold a hidden button (often inside the AV port, reachable with a toothpick) while connecting the power cable, release the button after a few seconds. If that doesn't work try another SDcard.

There are no CS1 tracks. This prevents the controller from detecting dual-rank memory, and the absence of A14-A16 tracks prevents the controller from detecting memory larger than 4GB. The memory chips H5ANAG8NAJR‑WMC are most likely 2GB each, but the controller only detects 4GB due to the lack of A14 and A16 tracks.

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!

https://lore.kernel.org/linux-media/Z4e9wNxZjvnytXlL@pengutronix.de/

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?

Hi all, I'm still working on video hwaccel with some progress. Can anyone provide a confirmed working ffmpeg command line for camera capture and hardware encoding? I dont care about the platform, either rockchip or anything else, no matter about kernel or arbiam version. Using v4l2request is the only requirement. I'm using either 7.1.1 with libreelec patches or @Kwiboo's fork. I know there are a bunch of threads here and elswhere in the web but most are outdated, dealing with vaapi or other stuff, but I want to stay on v4l2 which seems to be the future. Thanks! T.

I am not exactly sure what you are trying to do, but maybe the solaar or logiops package can help you achieve your goal.

@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.

In bookworm, trixie or noble?

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

@Nick A hi nick i posted above my problem with x96q pro 2g 16g board , today i also noticed second usb port is not working.

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?

In settings -> keyboard -> view and customize shortcuts -> launchers -> search I am trying to set this to Windows Key + S, it doesn't register the windows key at all as being pressed, so what keyboard do I choose to be able to use the full k400r keyboard inclusive of the windows key. Many thanks Newbie (please be nice, I'm new to Armbian and SBC's)

@Sergey LepeshkinThank you, it all make sense now… but could you suggest a uart connector? And every time i boot, do i have to get the uart connected?

No clue

So how do I totally disable so access once logged in doesn't timeout in 5 minutes putting machine in sleep mode which disables remote access too? At 16 watts, it can run 24/7/365.25 doing its job which is as a backup server. Thanks all.

Weekly community image produced: https://www.armbian.com/odroid-m1s/ If anyone wants to volunteer as maintainer, a full set of images can follow: https://docs.armbian.com/User-Guide_Board-Support-Rules/#standard-support

Quick retest in the container if I also install normal Debian kernel: root@ranc:~# apt install linux-image-arm64 wireguard Installing: linux-image-arm64 wireguard Installing dependencies: linux-image-6.12.48+deb13-arm64 wireguard-tools Suggested packages: firmware-linux-free linux-doc-6.12 debian-kernel-handbook openresolv | resolvconf

But why the Real-Time kernel and not the normal (linux-image-arm64) kernel package? I actually did run it as a systemd-nspawn -bxD <btrfs read-only snapshot> , so Armbian as container and host vanilla Debian. The actual kernel is then 6.12.48+deb13-arm64, but indeed the Armbian userspace (rootfs tree) has a few others/custom kernels installed only, so standard kernel package is missing.

@Ducdanh Nguyen, about uart: just find someone with soldering skills - it's deal of 3 minutes to solder 3 wires. Screenshots: all them taken from one tv box. I've found recovery menu only once - when accidentally flashed update.zip with system and vendor partitions taken from other tv box (also HiSilicon-based). After flashing, something went wrong while starting Android, and box automatically rebooted to recovery.