Active threads

I can confirm the above `flash-image-DDR4-1g_1cs_5-1200_750` image boots to U-Boot on the ESPRESSObin Ultra. I wasn't able to test past that because U-Boot isn't being built with Standard Boot enabled (which I use): WTMI-devel-18.12.1-a3e1c67 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 1.260V Setting clocks: CPU 1200 MHz, DDR 750 MHz CZ.NIC's Armada 3720 Secure Firmware d6d9646-dirty (Nov 5 2025 09:00:30) Running on ESPRESSObin Ultra NOTICE: Booting Trusted Firmware NOTICE: BL1: v2.12.8(release):95bbf00da NOTICE: BL1: Built : 09:02:55, Nov 5 2025 NOTICE: BL1: Booting BL2 NOTICE: BL2: v2.12.8(release):95bbf00da NOTICE: BL2: Built : 09:02:56, Nov 5 2025 NOTICE: BL1: Booting BL31 NOTICE: BL31: v2.12.8(release):95bbf00da NOTICE: BL31: Built : 09:02:56, Nov 5 2025 serial_mvebu serial@12000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2025.10_armbian-2025.10-Se50b-P3205-H05ce-V9535-Bbf55-R448a (Nov 05 2025 - 09:00:02 +0000) DRAM: 1 GiB Core: 48 devices, 24 uclasses, devicetree: separate WDT: Not starting watchdog@8300 Comphy chip #0: Comphy-0: USB3_HOST0 5 Gbps Comphy-1: PEX0 5 Gbps Comphy-2: SATA0 6 Gbps Target spinup took 0 ms. AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: ncq led only pmp fbss pio slum part sxs PCIe: Link down MMC: sdhci@d0000: 0, sdhci@d8000: 1 Loading Environment from SPIFlash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Globalscale Marvell ESPRESSOBin Board Net: eth0: ethernet@30000 [PRIME] Hit any key to stop autoboot: 0 Flags not supported: enable CONFIG_BOOTSTD_FULL bootflow - Boot flows Usage: bootflow scan - boot first available bootflow If you enable Standard Boot and want me to test again, happy to. Cheers!

Hello! I have a strange behavior at compiling As i knew, fwnode_for_each_available_child_node_scoped was committed to kernel at 2024 year.. Thats my kernel Any ideas?

Hi again, it booted and I get console output using this config: # 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__rock2f_use_mainline_uboot() { [[ "${BRANCH}" == "vendor" ]] && return 0 display_alert "$BOARD" "Mainline U-Boot overrides for $BOARD - $BRANCH" "info" # To reuse ATF code in rockchip64_common, let's change the BOOT_SCENARIO and call prepare_boot_configuration() again # BOOT_SCENARIO="tpl-blob-atf-mainline" # prepare_boot_configuration # declare -g BOOTCONFIG="generic-rk3528_defconfig" declare -g BOOTDELAY=1 declare -g BOOTSOURCE="https://github.com/u-boot/u-boot.git" declare -g BOOTBRANCH="tag:v2026.01-rc4" declare -g BOOTPATCHDIR="v2026.01" 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 declare -g BOOTSCRIPT="boot-rockchip64-ttyS0.cmd:boot.cmd" declare -g SERIALCON="ttyS0" # 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 } function write_uboot_platform_mtd() { flashcp -v -p "$1/u-boot-rockchip-spi.bin" /dev/mtd0 } } I'll try working on it using github. Still I cannot write in the serial console for some reason. There is zero input. So from what I understand, USB won't work with kernel 6.18, right? The wifi won't work as its aic8800-usb, and usb Ethernet either. With no serial input I have no way to communicate with the board. EDIT: I fixed the issue with not being able to conect via serial, it was because of a HAT that was connected. EDIT2: I figured out how to compile kernel 6.19-rc1. Some patches failed, I just removed them for now. I can send you @johlnx the command. EDIT3: Managed to boot 6.19 but it's pretty barebones. No usb, no pci etc. Time is not correct below. Linux rock-2f 6.19.0-rc1-edge-rockchip64 #8 SMP PREEMPT Sun Dec 14 04:05:07 UTC 2025 aarch64 GNU/Linux Now I can wait for your proper implementation.

One might think that if this was a perfect world. The reality is that very few people want to spend the time to find and read tutorials/FAQs/documentation. They just come to these forums and expect expert hand holding support for free from people who are volunteering their time. Igor has a lot more important things to be working on to keep Armbian afloat then even responding to posts in these forums. While I don't personally deal with rockchip sbc's, so I can't help you specifically here, as a moderator of these forums, I end up answering the same questions over and over again simply because people expect free support, not a community of people just trying to help. In the spirit of open source the easiest way for someone to contribute to help others is to dig in, learn and then contribute back what they have learned either through these forums, through contributing to the Armbian documentation or through actual code. (I'm mostly writing this, so that Igor doesn't need to take his time to respond, since I want him to be using his time elsewhere)

@伍翠波 Framebuffer console should work now. https://github.com/NickAlilovic/build/releases/tag/Radxa-a7a-v0.4

Need to post some corrections. The board loads and starts uboot directly from an inserted SD, so no need to be extra careful. Also: the upper M.2 is not recognized by stock uboot, so may next step is to compile u-boot to investigate.

@PH Ph there is graphics acceleration but not on chromium. If you can still boot android then you can extract your dts. Not sure what's wrong with PhoenixCard. I rarely use it. That's mostly for Android images.

Interesting. Also because independent from userspace (Bookworm or Trixie) our kernel/firmware package is the very same.

I'll try building the image again today with a new git clone, without changing anything except the userpatchers configuration. If I don't add the module this way, it won't be enabled in the text menu. I'll report back on my progress later.

With modifications to lightdm.conf I got lightdm working with your tutorial, however lightdm and labwc don't seem to use the SPI display. I verified the setup works on an HDMI screen (with a large box of random color artifacts filling the right quarter side, but that's hopefully just because it was a TV I tested with. I don't really care about HDMI). Do i need to specify lightdm / labwc to use the /sys/class/drm/card0-SPI-1? I'm curious if you simply launched LightDM and had it use the SPI display by default, without changing any configurations (as that is what it sounds like you achieved) I'm realizing I don't know enough about how wayland works to even know how to start debugging the issue or getting it to use the tinydrm device or even the legacy framebuffer device it adds for compatibility. Maybe I need to get Raspbian running and copy their configuration files, since Raspbian Trixie runs on wayland. The only difference between your guide and my setup is I am running kernel 6.18, as I can't seem to find how to compile or install kernel 6.13. Available installable kernels are 6.12, 6.14, and 6.18 as of 26.0.2 Armbian Trixie. The steps you outline in the github repo work with some modification, namely I will edit to include the lightdm.conf when I get home, since it requires modification from the original installed version. Further, certain packages are uninstallable, or named differently than in your guide. Here is the one line APT command to install all the packages you list, with the package names fixed. Certain packages don't seem to be required at all - namely freerdp, providing the windows equivalent of VNC, so its not included in this list. There are likely others and I assume you collected these packages to install from multiple guides / forums, so the inconsistencies are understandable. sudo apt install libcairo2-dev libpango1.0-dev libxml2-dev libglib2.0-dev libdisplay-info-dev hwdata libgbm-dev libdisplay-info-dev libseat-dev libinput-dev libpango1.0-dev libpangocairo-1.0-0 libcairo2-dev libglib2.0-dev libpixman-1-dev libxkbcommon-dev liblcms2-dev libxcb-xinput-dev libxcb-errors-dev libxcb-render-util0-dev libxcb-present-dev libxcb-res0-dev libxcb-dri3-dev libxcb-ewmh-dev libxcb-icccm4-dev libxcb-composite0-dev cmake libxml2-dev libliftoff-dev build-essential cmake libwayland-dev wayland-protocols libegl1-mesa-dev libgles2-mesa-dev libdrm-dev libgbm-dev libinput-dev libxkbcommon-dev libudev-dev libpixman-1-dev libsystemd-dev libcap-dev libxcb1-dev libxcb-composite0-dev libxcb-xfixes0-dev libxcb-xinput-dev libxcb-image0-dev libxcb-render-util0-dev libx11-xcb-dev libxcb-icccm4-dev libwinpr3-dev libpng-dev libavutil-dev libavcodec-dev libavformat-dev universal-ctags expat libexpat1 libexpat1-dev seatd foot librsvg2-dev scdoc gettext appmenu-gtk-module-common libaccountsservice-dev gir1.2-accountsservice-1.0 liblightdm-gobject-dev liblightdm-gobject-1-0 libgtk-3-dev gnome-common nasm meson I am running Armbian Trixie, and I did not need to install any packages from trixie-backports or oldstable-backports to get your setup to work properly. EDIT: It actually seemed to be my SPI clock speed was too high for the display. Lowering it to a conservative 16 or 20 MHz gets labwc to work, without having to configure and specify the display to output on.

Will comment on the new thread, since the initial question of driving SPI displays with tinyDRM has been answered. Although, I'm starting to wonder if the kungfupancake modifications are inadequate for my display, since I still cannot get a full plymouth boot log to display (it seems to "run off the screen" a little at some point then just stop). Maybe its overflowing some buffer or the display is mis-sized or something and the screen is attempting to display physically off the screen? I don't really know. I might need to peruse LCDwiki to find other init commands. Edit: Actually it seems to be the SPI speed. A conservative 16 or 20 MHZ gets the display working, with significantly unusable screen tearing any higher than that. I have a direct jumper connection but my jumper cables are pretty long (about 20 cm) and some are crossed over, which might mean there is some interference. Will try shortening, since the low 16 or 20 MHz speed has very low FPS rates. Do you know if the ili9488 is capable of reduced color mode, since i believe it only works on 666? Or maybe I need to enable DMA? Edit 2: The ili9488 data sheet indicates it can use 16, 18, and 24 bit color modes, however attempting to use 16 bit (565 on the format line) results in a white screen. Looks like it is over DPI or DSI only, not SPI.

Update: I was right, it is an allwinner system U-Boot 2014.07 (Aug 28 2020 - 08:44:29) Allwinner Technology Mali: ERR: /home/work/share/akrd6/custom_relese/H3_ANDROID7.0_BOX_SDK_V1.0_20190702_eng/lichee/linux-4.4/modules/gpu/mali-utgard/kernel_mode/driver/src/devicedrv/mali/linux/mali_platform.c These where the smoking guns that caught my eye, i will likely install Armbian in this anyhow.

I don't think I forgot anything. I was just curious about the conditions for the current version, since these sentences are relative generic and don't list issues, before I layout the details that I noticed. I flashed the image to a SanDisk Ultra, A1, Class 10 sdcard. System booted fine, but was relative slow which seemed to be related to constant sdcard speed switching issues. The following was constantly going on in the logs. [Wed Dec 3 13:30:34 2025] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [Wed Dec 3 13:30:34 2025] mmc_host mmc1: Bus speed (slot 0) = 198000000Hz (slot req 200000000Hz, actual 198000000HZ div = 0) [Wed Dec 3 13:30:34 2025] dwmmc_rockchip 2a310000.mmc: Successfully tuned phase to 235 The workaround for this was changing power control from auto to on. Messages stopped after executing the following. cat /sys/devices/platform/soc/2a310000.mmc/power/control auto echo on > /sys/devices/platform/soc/2a310000.mmc/power/control cat /sys/devices/platform/soc/2a310000.mmc/power/control on My permanent workaround was this, to avoid manual intervention after a reboot. # /usr/local/sbin/fix‑sd‑pm.sh #!/bin/sh # Disable runtime PM for SD controller (fixes repeated re-init) echo on > /sys/devices/platform/soc/2a310000.mmc/power/control # /etc/systemd/system/fix-sd-pm.service [Unit] Description=Disable runtime‑PM for SD controller After=multi-user.target [Service] Type=oneshot ExecStart=/usr/local/sbin/fix‑sd‑pm.sh RemainAfterExit=yes [Install] WantedBy=multi-user.target # Enable chmod +x /usr/local/sbin/fix‑sd‑pm.sh systemctl daemon-reload systemctl enable --now fix-sd-pm.service systemctl status fix-sd-pm.service Without the workaround the mmc1 switched between 2 states. root@nanopir76s ~# cat /sys/class/mmc_host/mmc1/mmc1:*/name SD128 root@nanopir76s ~# grep . /sys/kernel/debug/mmc1/ios clock: 400000 Hz vdd: 21 (3.3 ~ 3.4 V) bus mode: 2 (push-pull) chip select: 0 (don't care) power mode: 2 (on) bus width: 0 (1 bits) timing spec: 0 (legacy) signal voltage: 0 (3.30 V) driver type: 0 (driver type B) # OR clock: 200000000 Hz actual clock: 198000000 Hz vdd: 21 (3.3 ~ 3.4 V) bus mode: 2 (push-pull) chip select: 0 (don't care) power mode: 2 (on) bus width: 2 (4 bits) timing spec: 6 (sd uhs SDR104) signal voltage: 1 (1.80 V) driver type: 0 (driver type B) With the workaround it always showed this and system felt also snappy. root@nanopir76s ~# cat /sys/class/mmc_host/mmc1/mmc1:*/name SD128 root@nanopir76s ~# grep . /sys/kernel/debug/mmc1/ios clock: 200000000 Hz actual clock: 198000000 Hz vdd: 21 (3.3 ~ 3.4 V) bus mode: 2 (push-pull) chip select: 0 (don't care) power mode: 2 (on) bus width: 2 (4 bits) timing spec: 6 (sd uhs SDR104) signal voltage: 1 (1.80 V) driver type: 0 (driver type B) root@nanopir76s ~# --- EMMC was visible under Linux. But the emmc problem I noticed is related to u-boot. When I flashed the image to emmc and started from sdcard nothing at all happened. If I boot from sdcard and interrupt the u-boot prompt, the emmc card was not really visible. or accessible. I do not have the full serial output anymore when the Armbian image was flashed to emmc. => mmc list mmc@2a310000: 0 (SD) mmc@2a320000: 2 => # switching to emmc gives this => mmc dev 2 Card did not respond to voltage select! : -110 mmc_init: -95, time 22 => To debug this better, I build my own u-boot and image based on Armbians dts and defconfig. Here is what it looks like when booted from emmc with no sdcard inserted. U-Boot SPL 2026.01-msc-1 (Dec 02 2025 - 23:42:14 +0100) Trying to boot from MMC1 Card did not respond to voltage select! : -110 mmc_init: -95, time 21 spl: mmc init failed with error: -95 Error: -95 SPL: Unsupported Boot Device! SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### I created a patch for the dts, which modifies the sdmmc and sdhci nodes in the dts file. The patch is in my u-boot repo. https://github.com/mschirrmeister/PKGBUILDs/blob/f02af83ae5e0180ae1fd50706624dee348b820d7/core/uboot-rk3576-nanopi-r76s/arm64-dts-rockchip-rk3576-nanopi-r76s-fix-sdmmc-sdhci-coexistence.patch I added also the following Kconfig options to the u-boot defconfig. CONFIG_MMC_SDHCI=y CONFIG_MMC_SDHCI_ROCKCHIP=y CONFIG_MMC_HS200_SUPPORT=y CONFIG_MMC_HS400_SUPPORT=y CONFIG_MMC_HS400_ES_SUPPORT=y Here is the raw patch data. From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001 From: Marco Schirrmeister <mschirrmeister@gmail.com> Date: Sat, 6 Dec 2025 23:56:46 +0100 Subject: [PATCH] arm64: dts: rockchip: rk3576-nanopi-r76s: fix sdmmc/sdhci coexistence The NanoPi R76S (RK3576) features both a DW‑MMC controller for the microSD socket (sdmmc) and an Arasan SDHCI controller for the on‑board eMMC (sdhci). When both were enabled, the shared I/O voltage rail caused initialisation conflicts: the eMMC required 1.8 V signalling while the SD card logic expected 3.3 V. This patch aligns the DTS and U‑Boot configuration so that both storage controllers operate correctly: - Enable CONFIG_MMC_SDHCI and CONFIG_MMC_SDHCI_ROCKCHIP in U‑Boot. - Add explicit `vmmc-supply` and `vqmmc-supply` properties to the eMMC (sdhci) node. - Add `no-1-8-v;` to the SDMMC node to keep the µSD socket fixed at 3.3 V. With these adjustments the board can access both the microSD and eMMC devices simultaneously, and U‑Boot can boot directly from either medium. Signed-off-by: Marco Schirrmeister <mschirrmeister@gmail.com> --- diff --git a/dts/upstream/src/arm64/rockchip/rk3576-nanopi-r76s.dts b/dts/upstream/src/arm64/rockchip/rk3576-nanopi-r76s.dts index 11111111111..22222222222 100644 +++ a/dts/upstream/src/arm64/rockchip/rk3576-nanopi-r76s.dts 2025-12-06 23:33:40.013947291 +0100 +++ b/dts/upstream/src/arm64/rockchip/rk3576-nanopi-r76s.dts 2025-12-06 23:56:46.961392491 +0100 @@ -772,6 +772,7 @@ status = "okay"; }; +/* eMMC on the Arasan/SDHCI host */ &sdhci { bus-width = <8>; full-pwr-cycle-in-suspend; @@ -781,9 +782,13 @@ no-sdio; no-sd; non-removable; + /* add the supply rails for completeness */ + vmmc-supply = <&vcc_3v3_s3>; /* main VCC rail */ + vqmmc-supply = <&vcc_1v8_s3>; /* I/O rail */ status = "okay"; }; +/* µSD socket on the DW‑MMC host */ &sdmmc { max-frequency = <200000000>; no-sdio; @@ -795,6 +800,8 @@ sd-uhs-sdr104; vmmc-supply = <&vcc_3v3_s3>; vqmmc-supply = <&vccio_sd_s0>; + /* keep this host at 3.3 V so it works when eMMC uses 1.8 V */ + no-1-8-v; pinctrl-names = "default"; status = "okay"; }; With this patch and config changes u-boot detects emmc fine and I can boot from either emmc or sdcard. If this changes are good or bad, I have absolutely no idea.

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + FEX-Emu 2510 + hangover-10.18 (https://github.com/AndreRH/hangover/releases/tag/hangover-10.18) + Dxvk 1.10.3 (stripped) 30~60fps@720p (mixed settings) Tomb Raider (2013) Definitive Edition

OK good that is works now. I did not really read all history. I have a build running now (mainline/edge), but I will again need to dig into overlay/dts, hopefully I understand it now a bit better.

suggested solution is to move to kernel 6.18

https://github.com/armbian/build/pull/9094

What kernel version are you using?

I just registered here to say thanks to @bAL, your solution works on my Odroid HC4. I was bashing my head against the wall because I couldn't find what was constantly changing the fan PWM value even after disabling the fancontrol service. Now I finally have full control over the fan PWM (and thus the noise levels). Thanks again! So yeah, this issue is still relevant in 2025. `lsb_release -a` output for the interested: Distributor ID: Debian Description: Armbian 25.11.2 trixie Release: 13 Codename: trixie

Odd. Should more look like this. Also the first time I hear there is an issue like this. Perhaps retry now since your group is no longer validation but members. https://x.na4.eu/KOTu3/PACoFIsE81.jpg

Try the X11 windowing manager or the Wayland compositor without lightdm (or another display manager).

@JuanEsf sunxi-edge is now on 6.18. You can add your patches for t527 there.

Hello, i have a screen thats bigger than what I could see (frame). on a raspberry, i change the config with overlay adjustment. But i dont know how to do this for the banana pi.. Someone Here could redirect me the rijgt pad where to fix it?

Hi @tmb Helios64 and Armbian are still very relevant in 2025! Thanks to this amazing community! I used mine with OpenMediaVault until a couple of MOSFETs failed and some drives stopped to spin up. Unfortunately, the original components were quite cheap. Even though I found better replacements, I didn’t want to pay for micro-soldering services, which can be pricey compared to the parts themselves (just a few euros). Instead, I built my own NAS using an Intel N100. It’s now a low-power device running a dozen Docker containers, using Home Assistant image as base. I’m totally in unsupported territory, but it works great! With this setup, OpenMediaVault can go into sleep mode when needed, and so far, it’s been working really well for me.

If you learn yourself a strategy not to wipe existing installation, but dist-upgrade it and also have a flexible backup and restore for yourself, you don't need lists or so as the same set of software keeps being there. I clone installations from 1 computer to the other, so do not use new images. With tasksel you can remove and add Desktop Environments, sudo systemctl set-default <target> to changes from GUI to CLI and vice-versa. Make sure you have a serial console cable working (for CLI and no HDMI/kbd/mouse connected). But you can use 'sudo apt list --installed' on Debian systems. Cloning on x86 is easy, for ARM, you need change bootloader and kernel and some other packages. Until also all ARM computers come with UEFI bootloader/firmware. https://www.debian.org/releases/trixie/release-notes/upgrading.en.html#preparing-apt-sources-files https://digint.ch/btrbk/doc/readme.html https://btrfs.readthedocs.io/en/latest/Send-receive.html