Active threads

The three holes could be access to a serial console if necessary. Ground Transmit Receive. If you want to try this, baudrate is most likely 115200 like all Allwinner SoCs.

I think the easiest would be to get/build an image with mesa-vpu extension enabled. Unfortunately there is no automated way to do the stuff this extension does while building, in a live system. In general there are two ways to get hw acceleration: panthor or proprietary mali blobs. Former is from my feels better for general desktop usage and latter for hw encoding/decoding. Both cannot co-exist, no idea why. Latter needs vendor kernel branch. This would give you a Noble Gnome desktop image with Panthor driver enabled: ./compile.sh BOARD=youyeetoo-r1-v3 BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers desktop_tools internet multimedia' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base ENABLE_EXTENSIONS=mesa-vpu KERNEL_CONFIGURE=no RELEASE=noble Feel free to test: https://testing.armbian.de/Armbian-unofficial_25.11.0-trunk_Youyeetoo-r1-v3_noble_vendor_6.1.115_gnome_desktop.img.xz

edge = 6.16.y vendor = 6.1.115 Which kernel do you actually use? Also isn't panthor the backported gpu driver for rk35xx?

So besides Armbian a more recent image from khadas themselves also fails to boot?

Yes, this is quite common that feature xy has been implemented but the device trees don't get necessary updates. Often this is fixed by inheritance but sometimes adjustments on board level are necessary. Feel free to compare and send a PR to fix this until edge is bumped to 6.17 or even 6.18-rc1

the current filogic kernel has no info [in github] for where it was forked from, and trying to apply incremental patches from kernel.org I found it contains pieces of 6.14 in an ostensibly 6.12 branch. @chainsx might you be able to divulge where you forked it from?

PR Has been merged. I rebuilt on commit 1cf20837d27a3c09d93395f075cc305c81b4663f and things look good. Build instructions remain the same as my last post on this /_\ _ _ _ __ | |__(_)__ _ _ _ ___ _ _ _ _ ___ / _|/ _(_)__(_)__ _| | / _ \| '_| ' \| '_ \ / _` | ' \___| || | ' \/ _ \ _| _| / _| / _` | | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \_,_|_||_\___/_| |_| |_\__|_\__,_|_| v25.11 rolling for Odroid C1 running Armbian Linux 6.12.49-current-meson Packages: Debian stable (trixie) Support: DIY (custom image) IPv4: (LAN) 192.168.1.95, 10.8.0.1, 10.10.0.1 (WAN) ww.xx.yy.zz IPv6: 0000:1111:2222:3333:444:555:6666:7777 Performance: Load: 2% Uptime: 23:36 Memory usage: 8% of 986M CPU temp: 49°C Usage of /: 15% of 6.9G

Has anyone here configured armbian with a Wayland desktop, and completely free of X11? How did you do it? I have compiled labwc and it works great with my orange pi zero 3, with bookworm or trixie... but I can't figure out how to configure a wayland greeter. I need to do this because my LCD driver can't work with X11 (panel-mipi-dbi-spi).

@ebin-dev could you perhaps update your post 1 and post your latest instructions and upload the files there? That would make it much easier to find the stable files.

Hello everyone, I need help. I have an HK1MAX device with an RK3318 chipset. I need a firmware that can be installed using the loader, as my device is stuck with a red WiFi light (model number: HK6334Q).

@pochopsp - you can buy two tv-boxes of the same type at once from the same seller and they might have different hardware internally still - that is the reason why it is not prossible to provide really good images for tv boxes: the hardware is simply too random and often also low quality

I would put boot and system on the eMMC. Then it will run with or without the SSD, which I would reserve for data. Things like VMs and containers that get a lot of writes can go on the SSD and be symbolically linked to their system folders.

@Luckyisnotcoolest try the x96q images here. https://github.com/NickAlilovic/build/releases/tag/20250306

@emor acid could be your gpio settings for mmc0. Try the x98h image. If that doesn’t work you need to extract your android dts or use the one from the working Ubuntu.

The kernel 6.17 release benefits from improvements in the graphics subsystem, hardware enablement, and more! See where Collabora's kernel team contributed to this release. View the full article

leave a link for other users like @John Taylor to continue your work, also @fedes_gl could give a hand

I know an expert in rk3528, his name is @fensoft we are depending on him finding a weekend to dedicate to the community https://github.com/ilyakurdyukov/rk3528-tvbox he will help us by taking this repository and including it in armbian with a wonderful pull request I would like to buy this board and join the fun that you have, but my country has literally started an embargo on all TV boxes

Hi, I tested with the version 25.11.0-trunk.129 and the second network port worked with this. https://paste.armbian.com/hasewoloti

This is internal development for our boards, unfortunately, there is no public repository for our kernel. The code is borrowed from reverse-engineered POCs h264 + * Based on https://github.com/jemk/cedrus + * Copyright (c) 2014-2015 Jens Kuske <jenskuske@gmail.com> jpeg + * Based on https://gitorious.org/recedro/jepoc + * Copyright (c) 2014 Manuel Braga <mul.braga@gmail.com>

Fix: run armbian-install, then selected “Install/Update the bootloader on SD card (/dev/mmcblk0)”

Describe what you did before to make it work. Show the DTS, the wiring you connected and the linux version that worked. If you used spidev before, I don't have experience in that. I only have experience with these drivers: panel-mipi-dbi-spi, ili9431 and adafrui-xy... The threads I showed you require you to stop using spidev, since the Linux kernel will communicate directly to the LCD, without a user program. Using both will just make them interfere with each other. If the LCD remains white and doesn't even flicker, and you made it work in an older kernel, then keep that wiring. If the /dev/fb0 exists, it means that linux has taken one SPI output port for display, but you need to make sure that: * and SPI parameters in the DTS are correct, * the gpio to handle the command/data, reset parameters are pointing to valid orange pi pins which are not used by anything else * the high/low polarity of those gpio * the wiring is correct, * the initialization bytes are correct

Ok, I foud some time to make additional tests. Here is what I found. It fully boots with 'x96q-lpddr3' SD card image if you swap dtb to one of the two: h618-linganpi-3h h618-orngepi2w However in both cases internal Ethernet does not work. I can use USB to ETH converter. Do you see any way to make internal ETH working in this board? In original Android dmesg there is a message about gmac: [ 28.389711] sunxi-gmac gmac1 eth0: eth0: Type(6) PHY ID 00441400 at 0 IRQ poll (gmac1-0:00) Does it sound like a solution?

quoting JPL: Did you see any announcement by the github's owner, about what we can expect from her/his source code? Looking at the content of the file, it seems like we need to download the code from: https://github.com/philipl/mpv#branch=v4l2request or https://github.com/philipl/mpv/tree/v4l2request And include this build-time configuration -Dv4l2request='enabled' I have posted instructions to build MPV on Sept 26 in this thread

The easiest way to do this is through a chroot (or perhaps systemd-nspawn) but how practical this is will be dependent on your end goals. I do this all the time.

moved