All Activity

In the afternoon, I decided to look at dmesg. There: 25.729785] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 7307264 bytes), total 32768 (slots), used 11243 (slots) [ 25.734888] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1740800 bytes), total 32768 (slots), used 9297 (slots) [ 26.197594] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1150976 bytes), total 32768 (slots), used 10017 (slots) [ 26.875802] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 7307264 bytes), total 32768 (slots), used 11243 (slots) [ 26.884778] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 2097152 bytes), total 32768 (slots), used 11759 (slots) [ 27.976904] swiotlb_tbl_map_single: 1 callbacks suppressed [ 27.976917] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 2940928 bytes), total 32768 (slots), used 9787 (slots) [ 28.798413] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 438272 bytes), total 32768 (slots), used 9819 (slots) [ 30.420185] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 7307264 bytes), total 32768 (slots), used 11735 (slots) [ 30.423002] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1642496 bytes), total 32768 (slots), used 9841 (slots) [ 99.648400] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[30] not 4 pixel aligned [ 99.665159] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[29] not 4 pixel aligned [ 99.681872] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[25] not 4 pixel aligned and there: 911.698942] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[22] not 4 pixel aligned [ 911.715603] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[21] not 4 pixel aligned [ 912.032227] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[21] not 4 pixel aligned [ 912.065671] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[26] not 4 pixel aligned root@orangepi5-plus:/etc/default# dmesg | grep -i "swiotlb" # Nameless -ah Linux orangepi5-plus 6.12.44-current-rockchip64 #1 OUTPUTS SMP, August 28, 14:31:16 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux at 14:00 local time. # cat /boot/armbianEnv.txt verbosity=1 bootlogo=true console=both overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588-orangepi-5-plus.dtb rootdev=UUID=e08e0355-09a7-41ad-a6db-fa17566a7f12 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u How to fix it?

I got my issue resolved with labwc+greetd+nwg-hello See this link https://github.com/nwg-piotr/nwg-hello/issues/43 Please check it and post any corrections if needed

Hi @Nick A, can you please publish the updated git verision with 6.17?

Hello friends, I'm trying to install Armban from sd card or usb disk on a x96 max+ box( s905x3 confirmed, 4gb ram+ 32gb flash, realtek wifi and samsund emmc or nand). but nothing works. tried minimal and CLI but non of them works. I've done this before for another box(s905), but this one is giving me a hard time. Tried almost all dtb files, and renamed u-boot file as per instruction above( didn't patch the dtb file (as I felt it's already done for S905x3 in latest community image I used(Ubuntu 25.04 (Plucky) , Ubuntu 24.04 (Noble)). Tried installing from usb flash drive and sd card to make sure it's not about medium, no success. Some times the device enters into recovery menu( I think the toothpick method works but as it cannot detect a bootable media goes into recovery menu). and most of the times it goes into a loop ( I see boot logo and then restarts) from both usb and sd card. any Idea? someone said, they were able to boot from 24.5 desktop, but I was unable to find the exact same image to download. cheers,

I think this device already have a working linux on SD-card, make a complete documentation of the boot method used by the current ambernic present in the SOC, and how it makes the search for the SD-card your work around will be only inside the rkbin and the u-boot. you will need to match the needs for this rkbin to find armbian, You may need to migrate armbian to mainline uboot or you may need something legacy, only with a debugger connected to the TTL port will it be possible to distinguish link link link I got this folder with some examples: https://github.com/hqnicolas/Rockchip-Library/tree/main/RK356x/rkbin https://github.com/hqnicolas/Rockchip-Library/blob/main/RK356x/rkbin/ABOUT.md also: Ambernic use some custom rkbin and u-boot, please share your research https://github.com/hqnicolas/Rockchip-Library/tree/main/RK356x/u-boot/socfpga https://github.com/hqnicolas/Rockchip-Library/blob/main/RK356x/u-boot/socfpga/rk3568_common.h

@djtecha6 I have faced the same issue. And it's the Armbian 25.8.2 problem, use the Armbian 25.5.1 image indeed.

OK, tried build my own full server image and the same error. It cannot find SSD, but nand-sata-install had no problem copying the file system over from the SD. The fstabs and boot.ini looks fine. I guess no one has tested this for a while. I'm just going to use Jammy version for now since it still works.

You are going to need to connect a USB uart connector to capture the console log of the boot. Without logs it is hard to know what is happening

I see, thanks for the reply @hexdump. In the end I bought this card https://allegro.pl/oferta/karta-pamieci-samsung-evo-plus-microsdxc-128gb-adapter-15833111368 and I'm using it as main disk. I'm pretty disappointed with the write speed (around 20MB/s in my tests) but I guess it could still be fine for lightweight server usage.

AFAIK bookworm is fine with wayland (weston, kde, ...)

RTL8211F try to make an analogy with bananapi-m4-berry node for this chip. arch/arm64/boot/dts/allwinner/sun50i-h618-bananapi-m4-berry.dts

I can confirm that switching to network-manager seems to make the Bookworm image more stable on my hardware. @bobby3605 @bundle @Eatocee can you confirm if one of the two options below work for you as well. Use Debian Trixie image instead of Bookworm. These can be found by scrolling a bit further down on the official download page at https://www.armbian.com/bigtreetech-cb1/ OR switch to NetworkManager sudo apt install network-manager -y Change renderer from networkd to NetworkManager in /etc/netplan/10-dhcp-all-interfaces.yaml --- /etc/netplan/10-dhcp-all-interfaces.yaml.orig 2025-10-12 20:53:08.558759013 +0300 +++ /etc/netplan/10-dhcp-all-interfaces.yaml 2025-10-12 20:53:28.826717724 +0300 @@ -6,7 +6,7 @@ network: version: 2 - renderer: networkd + renderer: NetworkManager ethernets: all-eth-interfaces: match: Thank you!

Thank you. I meant to ask about that PR14690 I would rather stay with trixie and low fps, because it seems easier to solve my other problem: need 100% wayland and 0% X11 due to a LCD driver problem.

From what I understand and can see from the behavior of the stock ROM, the device first checks whether there is a /boot partition on the SD card, and only then does it start Android.

RTL8211F is the interesting label.

moved to tvboxes for now. perhaps anyone has a clue how to get rid of Android before continuing.

I decided to learn something interesting and wanted to build an image for the Anbernic RG353P console. I checked that uboot has DTS files for my model in the main branch and that there is support in the Armbian kernel (vendor) for my hardware. Unfortunately, after building the image and uploading it to the console, nothing happens. The console has dual boot Linux/Android, Linux should boot from the SD card. Unfortunately, the system immediately loads Android and skips my card. I tried various options in board config, but to no avail. Do you have any idea what I might be doing wrong with the configuration? The board configuration is copied from the existing one for nanopi-r3s-lts. I found two things that didn't seem right to me: - by default, rootdev was configured to mmcblk0p1 in the bootscript, I think (I'm not 100% sure) that it should be mmcblk1p1 - no improvement - my DTB file (/boot/dtb/rockchip) is missing from the /boot partition - I manually mounted the partition and uploaded the file, but that didn't help either (I set the permissions etc. the same as for the other DTBs). I am pasting the configuration files. Thank you very much for any help and advice Board config: armbianEnv.txt verbosity=1 bootlogo=false console=both extraargs=cma=256M overlay_prefix=rk35xx fdtfile=rockchip/rk3566-anbernic-rg353p.dtb rootdev=UUID=8f8aa17e-0953-4c6c-b7bf-8cf0ebbf2b14 rootfstype=ext4

this is my external ethernet chip

yes, The box is 1000Mbit external ethernet chip, But I don't know how to set the dts to support this 1000Mbit external ethernet chip.

is there gpu acceleration support/drivers for s905w? if yes, where can i obtain that?

I compiled mpv 0.40.0 and the commits from this PR. Results are mixed and situation is messier than before, so if you need hardware acceleration, it is better to go gstreamer or revert to debian bookworm for now.

The armbian edge image for the FriendlyElec CM3588-NAS is currently on kernel 6.17 but has no HDMI audio despite it having been added in 6.15 (I think). This is simply because it has not been enabled in the device tree for this board. You can enable it with this user overlay: /dts-v1/; /plugin/; / { fragment@0 { target-path = "/hdmi0-sound"; __overlay__ { status = "okay"; }; }; fragment@1 { target-path = "/hdmi1-sound"; __overlay__ { status = "okay"; }; }; };

Hello Jock, Can you confirm that you use the patch in mpv PR1460, or something else? --vo=gpu or -vo=gpu-next? I installed mesa-vulkan-drivers today, with some difference in the mpv log, but same performance I also get: [vo/gpu-next/libplacebo] Found no suitable device, giving up. [vo/gpu-next/libplacebo] Failed initializing vulkan device and ... Does it matter? If I want to test the latest libplacebo route (with git clone https://code.videolan.org/videolan/libplacebo.git...) do I need to uninstall libplacebo and libplacebo-dev?

Hello everyone, I followed the configuration steps for the st7735s LCD driver, and here are the details of my setup and observations so far: Configuration Files and Commands /boot/overlay-user/st7735s-fb5.dts Command used: armbian-add-overlay /boot/overlay-user/st7735s-fb5.dts dmesg Output Filtered dmesg output related to framebuffer or SPI: Observations Based on dmesg, the driver and display appear to be detected. Relevant messages are logged during updates. The command fbi works correctly, and running cat /dev/fb0 reveals some data. However, the display remains bright white, and nothing is visible on the screen. I attempted to test various initialization sequences (the commented-out sections in the overlay file) but without success. Next Steps Before writing this post, I wanted to conduct more testing, particularly with the LCD initialization parameters, but I'm unsure how to proceed further in debugging this issue. I'd appreciate any advice or suggestions to resolve the display issue! Thanks in advance for your help.

When I switched to trixie lxde was not yet available, therefore I have been working with lxqt (x11) for almost a year now. With your message I realised there is lxde for trixie. Since the mirroring problem I found myself looking for a wayland "windowmanager" a few weeks ago. Installing labwc and the sid-package "lxqt-wayland-session" you can use lxqt with wayland. I have been using lxqt/wayland for a few days now. Some functions are missing (I do miss the oxygen mouse cursors in wayland). Can't say much about stability yet. So YMMV. If you lookup lxqt/wayland on github you'll find it is a recent development, somewhere between alpha and beta stage. However if your strict on kde, lxqt might not be for you since it is qt-based (althought the looks of lxde are mostly similar).