All Activity

The kernel seems to be starting but there is no further output from the serial console. Here are some attemps (forst one with FDT commented out, which prevented the kernel from loading, the last ones also, maybe due to SD card corruption). The green light is on and the blue light is pulsing. This is the config it came up with with my guidance: # Rockchip RK3528 quad core 1-4GB SoC WIFI/BT 0-32GB eMMC BOARD_NAME="ROCK 2F" BOARD_VENDOR="radxa" BOARDFAMILY="rk35xx" BOOTCONFIG="rock-2-rk3528_defconfig" BOARD_MAINTAINER="CodeChenL" KERNEL_TARGET="vendor,edge" KERNEL_TEST_TARGET="vendor" FULL_DESKTOP="yes" BOOT_LOGO="desktop" BOOT_FDT_FILE="rockchip/rk3528-rock-2f.dtb" BOOT_SCENARIO="spl-blobs" IMAGE_PARTITION_TABLE="gpt" enable_extension "radxa-aic8800" AIC8800_TYPE="usb" function post_family_config__rock-2f_use_mainline_uboot() { # use mainline uboot for _edge_ [[ "${BRANCH}" == "vendor" ]] && return 0 display_alert "$BOARD" "Mainline U-Boot overrides for $BOARD - $BRANCH" "info" declare -g BOOTCONFIG="generic-rk3528_defconfig" # Use generic RK3528 config since rock-2f specific config doesn't exist yet in mainline declare -g BOOTDELAY=1 declare -g BOOTSOURCE="https://github.com/u-boot/u-boot" declare -g BOOTBRANCH="tag:v2025.10" declare -g BOOTPATCHDIR="v2025.10" declare -g BOOTDIR="u-boot-${BOARD}" declare -g UBOOT_TARGET_MAP="BL31=${RKBIN_DIR}/${BL31_BLOB} ROCKCHIP_TPL=${RKBIN_DIR}/${DDR_BLOB};;u-boot-rockchip.bin" unset uboot_custom_postprocess write_uboot_platform write_uboot_platform_mtd # disable stuff from rockchip64_common; we're using binman here which does all the work already # Just use the binman-provided u-boot-rockchip.bin, which is ready-to-go function write_uboot_platform() { dd "if=$1/u-boot-rockchip.bin" "of=$2" bs=32k seek=1 conv=notrunc status=none } } Here is the log: pastebin Any ideas? I observed that with some boards, the line "BOOT_FDT_FILE=..." is absent altogether. is removing it possibly the way to go?

Hello everyone, I’m trying to flash a firmware on a generic Android TV Box and I’m stuck at a hardware/bootloader compatibility issue. Device technical details: - SoC: Allwinner H618 - Board / PCB: FX-H618-D4_V10 - RAM: 4GB DDR4 - Storage: eMMC (unknown size, likely 32GB) - USB FEL ID: VID_1F3A PID_EFE8 - Original OS: BigdroidOS (Android generic) - Commercial name: Transpeed 8K618-T Current situation: - Device enters FEL mode correctly (VID_1F3A PID_EFE8) - PhoenixSuit detects the device but firmware upgrade hangs at “Beginning Firmware Upgrade” - Tried multiple PCs (Windows 10 and 11), different USB ports and cables - Allwinner FEL driver installed correctly - SD card flashing with PhoenixCard (Startup mode) is ignored, device boots normally to Android - Reset timing variations tested (short press / long press / no reset) Tested firmware: - sbx_transpeed_h618_atv_12_11.img - H618.apollo-p3.T-H618_100M_12_FD650.2023.09.13.1720.img Both firmwares show similar behavior (FEL detected but no successful flash). I believe the issue is bootloader / DDR4 initialization mismatch. I’m specifically looking for: - A firmware confirmed to work with board FX-H618-D4_V10 - Or the original BigdroidOS firmware dump for this board - Or confirmation whether this board requires a specific boot0/boot1 Any help, working firmware, or dump from the same board would be greatly appreciated. Thank you! Allwinner H618, FX-H618, DDR4, PhoenixSuit, FEL, Transpeed

moved

No need to reply in a PM; just run standard Debian tool: sudo tasksel and select what you want and follow the steps.

Hallo everyone i really want to filn out how to install armbian onto one of 2 devices i have 2 boxes but ill focus only on one for now. The tvox is a Tangka Cpu = RK3228A Storage chip = SKhynix H9TQ64A8GTMC Wifi chip = s9012p Where could i find the compressed file of the .iso sothat i can flash the firmware onto my tvbox and what software/drivers will i need on windows 10 or ubuntu (preferably win10) id really appreciate if you guys can help me out. I dont have a sdcard only a makeshift working male to male usb adaptor.

You have PM, please reply when you have a moment. Thanks

It is Tomb Raider 1~3 remastered Gog version

No, basically any wine/proton (wow64) will work! Btw, that version of the Tomb Raider!

After my last update on my radxa5-ITX, apart from the name changes of the NIC (related?), I remarked that I could not cryptroot-unlock the root partition because of dm_mod apparently missing from initramfs. To give some context, this is how I set things up some while ago and things went pretty smooth until recently. Too bad armbian does not keep the previous kernel (though I get the reason why). Inspecting the boot partition, cat config-6.1.115-vendor-rk35xx | grep DM_CRYPT CONFIG_DM_CRYPT=m the kernel seems to have been compiled with the proper option and lsinitramfs initrd.img-6.1.115-vendor-rk35xx | grep 'usr.*cryptsetup' usr/lib/aarch64-linux-gnu/libcryptsetup.so.12 usr/lib/aarch64-linux-gnu/libcryptsetup.so.12.9.0 usr/lib/cryptsetup usr/lib/cryptsetup/askpass usr/lib/cryptsetup/functions usr/sbin/cryptsetup and initramfs seems properly linked to the relevant libraries so I do not understand why device mapper remains unavailable. At this point, I have no hypothesis except a very unlikely one An unlikely hypothesis Could failure to initialize the device mapper have nothing to do with dm_mod availability but be solely the side effect of Because I always unlocked the root part either from console or from a dropbear session, I understood device mapper init as an anterior step, independent from NIC availability. But is it really the case. What am I missing?

@Igor wrote about upcoming Muse Pi Pro (a SpacemiT K1 board). Orange Pi RV2 features a "Ky X1" SoC which may be a variant of the SpacemiT SoC and at least similar to the already compile-able Banana Pi F3 board. However, Xunlong seems to be serious about the differences, since the published patch sets on github.com/orangepi-xunlong to kernel and u-boot have a GPL-2 copyright notice, stating I expect my RV2 arriving tomorrow. Thus, it would be very appreciated if support for this board pops up in time 😉 Otherwise I may try my luck with adding Armbian support on my own (without expecting success soon). For clarification, I compiled a list of RISC-V64 boards currently available: Banana Pi F3, runs on SpacemiT K1 8-core X60 RISV-V@1.5? (2 TOPS NPU, 2x1 Gbit, M.2@m, mPCIe, eMMC@soldered, SD/TF) Orange Pi RV, runs on StarFive JH 7110 4-core RISC-V@1.5 (1x1 Gbit, M.2@m, SD/TF, SPI-flash) Orange Pi RV2, runs on Ky X1, 8-core RISC-V@1.5, variant of SpacemiT K1? (2 TOPS NPU, 2x1 Gbit, M.2@m2280, M.2@m2230, SD/TF, eMMC@socket, SPI-flash) Muse Pi Pro runs on overclocked SpacemiT K1 8-core X60 RISC-V@1.8 (2 TOPS NPU, 1x1 Gbit, M.2@m, mPCIe, eMMC@soldered, SPI-flash) Best // Sven-Ola

I am trying to use Zink to play TomRaider , while comes out this error: [BOX64] Using emulated /home/xfding/tmp/wine-proton-10.0-3-amd64-wow64/lib/wine/x86_64-unix/winepulse.so [BOX64] Using native(wrapped) libpulse.so.0 [BOX64] Using emulated /home/xfding/tmp/wine-proton-10.0-3-amd64-wow64/lib/wine/x86_64-unix/winealsa.so [BOX64] Using native(wrapped) libasound.so.2 [BOX64] Using native(wrapped) libGL.so.1 WARNING: Some incorrect rendering might occur because the selected Vulkan device (Mali-G610) doesn't support base Zink requirements: feats.features.fillModeNonSolid feats.features.shaderClipDistance [BOX64] 15479|Ask to run at NULL, will segfault wine: Unhandled page fault on execute access to 0000000000000000 at address 0000000000000000 (thread 0024), starting debugger... [BOX64] winedbg detected, not launching it! 0024:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 32 332" (731) Read the Wine Developers Guide on how to set up winedbg or another debugger Is "GE-proton" is a must to OpenEL games？

moved

Set var environments as below: export MESA_LOADER_DRIVER_OVERRIDE=zink export GALLIUM_DRIVER=zink export LIBGL_KOPPER_DRI2=true

How do you use Zink?

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + GE-Proton (https://github.com/GloriousEggroll/proton-ge-custom) + Zink (openGL) >=60fps@1080p Tomb Raider Remastered IV - V - VI

I just got a mystery box from Ameridroid that contained a ODROID-GO-Ultra. Hardkernel has an old Ubuntu 20.04 image. Does Armibian support this device?

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + GE-Proton (https://github.com/GloriousEggroll/proton-ge-custom) + Zink (openGL) >=60fps@1080p Tomb Raider Remastered I - II - III

With the help of Claude I generated a config with both. Compiling now. Hopefully it boots this time. If it does, I may then do a PR.

Actually, hope is not all lost. The image downloaded for the 4c from Armbian. Has the sources set to beta. So, I changed them and was able to install armbian-config. Although it isn't officially supported on the version I'm using. It does the job. Disabled kernel and firmware updating. Also, add Radxa's Bookworm repo. Ran a upgrade and all is well. Should last me a few years. Until the day I decide I want to throw a bunch of my time at an other SBC.

@John Taylor I finally had some time to test this today and it is working fine for me. I built a fresh image on an ubuntu laptop, copied the image to a SD card, it mounted fine on ubuntu, where I edited the extlinux.conf file and then used the SD card to boot on an amlogic based TV box. You mention etcher as your sd card tool. Etcher in recent versions (recent being the last two years or so) is known to have problems. It is no longer recommended for use with Armbian images. I have noticed that in particular if Etcher is burning a compressed image it doesn't work for me. But I have had some success if the image is uncompressed first. But others have reported that it fails in general.

First of all, thank you to @Hqnicolas and all the members for this great effort. Just bought an H96 rk3566, having this hardware configuration: BOARD LABEL: HCY-RK3566-1X32-V20 2023-01-13 SOC RK3566 PMIC RK809-5 LAN RTL8211F DISPLAY FD6551 WIFI AIC8800D40 eMMC H26M74002HMR - SK Hynix eMMC 5.1 NAND Flash 64Gb. It seems to be a mix of the other versions described in this topic, although very close to the one of @WINEDS (thanks for the hints). Everything seems to work so far. Installed using rockchip dev tools, as advised. here its: _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v26.2 rolling for h96-tvbox-3566 running Armbian Linux 6.12.61-current-rockchip64 Packages: Debian stable (trixie) Support: for advanced users (rolling release) IPv4: (LAN) 192.168.111.228, 192.168.111.91 (WAN) xxxxxxxxxxx Containers: big-bear-photoprism-db Performance: Load: 8% Uptime: 46 minutes Memory usage: 6% of 7.50G CPU temp: 38°C Usage of /: 31% of 57G To enable Bluetooth I have used this small overlay in /boot/overlay-user/ (which enables SPDIF as well): /dts-v1/; /plugin/; /* &{/serial@fe650000} */ &uart1 { status = "okay"; dma-names = "tx\0rx"; bluetooth { status = "disabled"; }; }; &spdif { clock-names = "mclk\0hclk"; status="okay"; }; The followings are the drivers used for wifi-bluetooth wget https://github.com/radxa-pkg/aic8800/releases/download/4.0%2Bgit20250410.b99ca8b6-3/aic8800-firmware_4.0+git20250410.b99ca8b6-3_all.deb wget https://github.com/radxa-pkg/aic8800/releases/download/4.0%2Bgit20250410.b99ca8b6-3/aic8800-sdio-dkms_4.0+git20250410.b99ca8b6-3_all.deb dpkg -i aic8800-firmware_4.0+git20250410.b99ca8b6-3_all.deb dpkg -i aic8800-sdio-dkms_4.0+git20250410.b99ca8b6-3_all.deb Service to enable bluetooth : [Unit] Description=Bluetooth HCI Attach (AIC8800) After=systemd-modules-load.service Requires=systemd-modules-load.service After=dev-ttyS1.device Requires=dev-ttyS1.device [Service] Type=oneshot # Load AIC module ExecStartPre=/sbin/modprobe aic8800_btlpm_sdio # Just a small delay ExecStartPre=/bin/sleep 2 # Attach HCI ExecStart=/usr/bin/hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep To re-enable display in Linux 6.12 another small overlay is required: (the display itself it is not scrolling and available at: /sys/class/leds/display/value ) /dts-v1/; /plugin/; &{/i2c-aux-display} { compatible = "i2c-gpio"; #address-cells = <0x01>; #size-cells = <0x00>; display@24 { compatible = "fdhisi,fd6551"; reg = <0x24>; #address-cells = <0x01>; #size-cells = <0x00>; tm16xx,digits = [04 03 02 01]; tm16xx,segment-mapping = [00 01 02 03 04 05 06]; led@0,0 { reg = <0x00 0x00>; function = "alarm"; }; led@0,1 { reg = <0x00 0x01>; function = "usb"; linux,default-trigger = "usb-host"; }; led@0,2 { reg = <0x00 0x02>; function = "pause"; linux,default-trigger = "mmc2"; }; led@0,3 { reg = <0x00 0x03>; function = "play"; linux,default-trigger = "mmc0"; }; led@0,4 { reg = <0x00 0x04>; function = "colon"; }; led@0,5 { reg = <0x00 0x05>; function = "lan"; linux,default-trigger = "stmmac-0:00:link"; }; led@0,6 { reg = <0x00 0x06>; function = "wlan"; linux,default-trigger = "mmc1"; }; digits { status = "disabled"; }; leds { status = "disabled"; }; }; }; rk3566-bt-fix.dtso rk3566-led-fix.dtso

My solution is to compile the image like this: ./compile.sh INSTALL_HEADERS=yes Then scp the driver on the machine, and execute echo "obj-m += panel-mtf0397swi.o" > Makefile make -C /lib/modules/`uname -r`/build M=$PWD cp panel-mtf0397swi.ko /lib/modules/$(uname -r)/kernel/drivers/gpu/drm/panel/ depmod -a

Hi @eselarm, thanks for the detailed response. I've checked my boot.cmd and boot.scr is ancient ( from Aug 2023 ). I'm going to try to set the variables beforehand, as I see in the output they are blank ( devtype, devnum, prefix ). When I succeed I guess the next step will be to set these variables in U-Boot, but nowadays there's no gpt partition table in SPI with the uboot_env, so I guess will need to figure it out later ( via env or find the boot.scr in the NVMe ), first I want to try to boot from NVMe manually. Thanks again

Hello everyone,does anyone have working armbian for rockchip 3228a with lpddr3 for x96q V20?

Easy is what standard Debian (12 and 13) does: NetworkManager and openresolv/resolvconf , even for complex setup of VLANs and bridges, Virtual Machines. Canonical/Ubuntu have invented netplan.io, so they manage NM and systemd-networkd with a yaml script. Easy for them as large organization for business customers. Might not for you as image downloader, as it introduces extra yaml while .nmconnection files are easy to copy between hosts. Also, systemd-resolved might be used, which is actually a sort of local DNS server. It should enable high performance I guess, by default caching enabled, but is that applicable for a simple ARM SBC connected to an ISP router, I don't know. I know is needs extra work for me. So you need to dig into that. Or not use Ubuntu at all. I anyway do not use images, only for testing for others, not to use them myself. It is simply using apt for (dist-)upgrades and so I use standard Debian upgrade method to get from Bookworm to Trixie and keep my KDE as I use that mostly. Also switching kernel, just via apt removals/installs and/or bootmanager. If you get stuck, use sudo nmtui to set an extra network profile connection with fixed IP, known DNS maybe. Done that many times to get things running although not permanent good solution.