Active threads

We support Armbian software but not random software from the internet. RKdevtool is as far as I know a tool from Radxa, not Armbian, either. CPU boxes are cheap and cheap for a reason. Nobody really supports them. We give some very limited community support here. With your current random software this is not the right spot for you. Best of luck to you.

HW (features are determined by kernel used in the image) related issues are shared among all variants, desktop, cli, minimal, Debian or Ubuntu.

Sige5 is community supported and those boards receive automatic generated images only - once per week. Since GitHub introduced additional limitations few months ago, we can't (auto)produce desktop images anymore - only one Debian stable minimal per CSC build target. However, this might change in the future.

Hello, I have an Android M98-Y6 HDMI stick that reportedly has an Allwiner H313 processor with 2GB of RAM and 16GB of storage. When I opened the case, I identified the emcp memory module KMQNW000SM-B316. I don't have access to console mode. I can only access adb commands as root.The RAM type DDR3 seems LPDDR3 ( version ??) I've tried different Armbian images without success. Unfortunately, Secure Boot is enabled. I read this post and test Armbian-20240716-unofficial_24.5.0-trunk_Transpeed-8k618-t_bookworm_edge_6.7.12_xfce_desktop_Secure_Boot.img.tar.xz from Nick, without success I have an Android image named M96-Y6.img. Attached is the "dts" file devicetree.dts device_tree_dump.txt

Never had an issue like that. However we also have mirrors in Asia or RU/UA where politics might interfere with bandwidth. So perhaps you hit one of those? Or you simply hit a mirror which was under heavy load at this time.

Sent a nudge.

@Fredrik thank you for the reply. I wonder what's Gnome doing to initialize the audio that's different from a regular (non-graphical) boot. FWIW I installed also Pipewire/Wireplumber and tried to test the audio through the PW ALSA emulation, but that didn't work either. Just out of curiosity, does speaker-test work from the CLI once booted into Gnome or is it just the sound test in Gnome settings that's working ?

I troubleshooted my problem! So for some reason (I'm not sure if this is for all x88 pro 10's), the SD card needed to be under pressure on it to read Multitool. So, throughout the entire Multitool process, I needed to hold down the SD card with my thumb. I did hurt a bit, but it flashed to the EMMC

I retried that image now but with a different installation method, booting into OOWOW (?) via the Function+Reset button, control via serial debug console. I then wget the image from my local server and dd out to /dev/mmcblock0. Subsequent boot was indeed successful.

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

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.

@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

@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