Active threads

Nicely done 👍 I remember dealing with similar problems when I upgraded my desktop to an nvme drive. I transferred the partition to the new drive but the OS would not boot from it due to nvme modules being missing.

An `armbian-plymouth-theme` package must be installed to make it worked in the latest (6.x ???) kernels. Steps: 1. `sudo nano /boot/armbianEnv.txt` and adjust/add following line `bootlogo=true` 2. `sudo apt install armbian-plymouth-theme` 3. sudo reboot 4. Check plymouth or/and armbian-plymouth-theme documentation for more customizations

Both Debian 12 and Debian 13 use Wayland by default for the GNOME desktop environment. However, X11 also remains an available option in the login manager, allowing you to choose between the two. Wayland is a communication protocol that specifies the communication between a display server and its clients. A display server using the Wayland protocol is called a Wayland compositor, because it additionally performs the task of a compositing window manager. The aim of Wayland is replacing the X Window System (Also known as X11, or Xorg) with a modern, secure, and simpler windowing system xrandr is used on top of X.org, that's why it doesn't work on a debian that uses Wayland.

Seeking SKW (SWT6621 / EA6521) SDIO Wi-Fi driver source or Linux 6.x port Hi all, I’m running Nick's Armbian-unofficial_25.05.0-trunk_Tanix-tx6s-axp313_bookworm_edge_6.12.11_server.img.xz on a TV box that originally shipped with Android using kernel 5.15 AIDA64 run on Android gives: System Device Type: TV Manufacturer: Oranth Model: TX68 Brand: ADT-3 Board: exdroid Device: adt3 Hardware: sun50iw9p1 Platform: apollo Product: adt3 Installed RAM: 4 GB Total Memory: 3891 MB Available Memory: 2512 MB Internal Storage Total Space: 54.22 GB Internal Storage Free Space: 52.57 GB Bluetooth Version: 4+ Wi-Fi works perfectly under Android, but not under Armbian — the onboard Wi-Fi chip (connected over SDIO) is a SeekWave SWT6621, also known as SKW or EA6521. From the Android side, I can see the driver is provided in binary form via: /vendor/bin/hw/android.hardware.wifi-service-lazy /vendor/etc/init/init.wlan.common.rc /vendor/etc/firmware/SWT6621*_SDIO.bin and the kernel logs show active skw_scan and skw_dump_survey messages when Android is running. However, when booting Armbian, wlan0 never appears — only eth0 and virtual interfaces. This strongly suggests that the SKW SDIO driver needs to be rebuilt or ported for kernel 6.x. What I’m looking for: Has anyone already ported or rebuilt the SKW (SWT6621 / EA6521) SDIO driver for Linux 6.x / Armbian? If so, could you please share your source, patches, or build instructions? If the work is in progress, I’d be very happy to help or test — I have the Android image and full /vendor contents available for reference. Any leads on SeekWave source releases, OEM SDKs, or community ports would be greatly appreciated. Thanks in advance for any guidance — I’d rather reuse or help finish existing work than start from scratch if someone has already begun tackling this. Best Regards John

Hi @Igor, I was looking at configng repo and I found this issue: https://github.com/armbian/configng/issues/225. I think that's why I could not find a place to create the sway section in the desktop. In the same I found this in not being planned yet to be made, if ever. Should I look at the Armbian build and try there instead?

Hey! So, when i enter the multitool link it says 404 not found... Is there any new link or smth?

Great! That worked. Do I need to do anything else after that?

I can confirm this is still broken as of 10/18/2025 Currently attempting the overwrite armbian uboot with vendor uboot solution The solution did work. The spl loader files can be found here https://dl.radxa.com/rock5/sw/images/loader/rock-5b/release/ All of the files need to be gathered together, or the file paths adjusted when you run the commands. I pulled the rkdeveloptool from git and built it and put everything else the folder with it. ❯ ./rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x350b,LocationID=101 Maskrom ❯ sudo ./rkdeveloptool db rk3588_spl_loader_v1.15.113.bin Downloading bootloader succeeded. ❯ sudo ./rkdeveloptool wl 0 armbian.img Write LBA from file (100%) ❯ sudo ./rkdeveloptool wl 64 idbloader.img Write LBA from file (100%) ❯ sudo ./rkdeveloptool rd Reset Device OK.

I finally installed Postmarket OS (Alpine Linux) using Pmbootstrap., I close this topic. Thanks to all of you for your comments and suggestion.

I had to enter all of this on my Orange Pi 5 Max: https://gist.github.com/default-writer/6ca5f1f05e88c9c51e2e1b09147ad23e

I have been experimenting with trying to get video acceleration working on the A83T. I can see from /proc/device-tree/soc/... that there is already a video-engine node within the current A83T device tree. It appears to be applied as one of the megous patches ARM-dts-sun8i-a83t-Add-cedrus-video-codec-support-to-A83T-untes.patch. Admittedly this is noted as being untested. In my initially created build via the build framework, Cedrus was not present at all among the list of loaded modules. I addressed this by creating an entry in the Cedrus compatibility table for the sun8i-a83t-video engine drv-sun8i-a83t-cedrus-add-variant.patch It now appears to load but complains about being unable to allocated an SRAM: [ 10.046406] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 10.046490] cedrus 1c0e000.video-codec: Failed to probe hardware [ 10.091215] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 10.091339] cedrus 1c0e000.video-codec: Failed to probe hardware [ 10.419296] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 10.419597] cedrus 1c0e000.video-codec: Failed to probe hardware [ 20.193058] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 20.193114] cedrus 1c0e000.video-codec: Failed to probe hardware [ 20.193322] platform 1c0e000.video-codec: deferred probe pending: (reason unknown) Using both sun8i-a23-a33.dtsi and sun8i-h3.dtsi as points of reference, I attempted to make an SRAM allocation under the system controller but this still appears to fail with the same failure messages. I have double checked in the user manual and VE memory should definitely exist at 0x01D0 0000. arm-dts-sun8i-a83t-add-ve-node.patch I would be grateful for any pointers. Thanks Ryzer

Hi all, and thanks for your incredible work I just received an "X98k pro" tvbox (sold as rk3566 4gb/32gb ) from T*** The box arrives already rooted. Outside : blue info lcd display --> Sdcard ; usb2.0/OTG ; usb2.0 ; usb 3.x --> Optical SPDIF, HDMI , hole marked "UPDATE" , power (5v 2A); external antenna female. -> EMPTY SIDE What's Inside the black box SOC : Rockchip RK3566 RAM : 8 Micron Technology (MT) D9QBJ memory chips Wireless : RTL8822cs Ethernet : RTL8211F eMMC : SanDisk China 32G Front lcd display controller : AIP1628 TTL rx tx gnd Device Info HW 5.23 and CPU-z confirm it's a rk3566 4/32, mali g52 Other infos from Device info HW : Device : rockchip X98k PRO ; Platform rk30board Android 11 , Wifi rtl88x2cs, kernel 4.19.232 (ubuntu...) CPU : Rockchip RK3566 BOX DEMO V10 ANDROID Board After installing termux I tried to find this box's dtb, but the only dtb file I found until now is /sys/firmware/fdt (no .dtb extension just "fdt") I don't know if it's the right one. Anyway, I de-compiled it using dtc to "X98k_pro_4g-32g_from_fdt.dts". I'd like to try armbian on this box If u wanna know something else let me know. Update 1)pressing the hole with a pin + power on takes to Android recovery (see photo) seems I can just boot froom sd from there ... 2) Trying to make Rockchip Driverassistant (modified 4.2 or 4.5) work to connect the box to a PC via usb2.0/otg. But nothing. 3) after trying to start with generic armbian for arm64 and then Station M2 (both just gave blank screen), I had a first success with a miniarch image (20240715-6.17.1-board-rk3566.x96_x6), hdmi and usb keyboard works, but ethernet is not working. Lets see what comes next. X98k_pro_4g-32g_from_fdt.dts

root@rk3318-box:~/tm16xx-display# make module make EXTRA_CFLAGS="-DCONFIG_TM16XX -DCONFIG_TM16XX_KEYPAD -DCONFIG_TM16XX_I2C -DCONFIG_TM16XX_SPI" -C /lib/modules/6.16.4-edge-rockchip64/build M=/root/tm16xx-display modules make[1]: Entering directory '/usr/src/linux-headers-6.16.4-edge-rockchip64' make[2]: Entering directory '/root/tm16xx-display' CC [M] line-display.o /tmp/cc8iv0mf.s: Assembler messages: /tmp/cc8iv0mf.s:8: Error: junk at end of line, first unrecognized character is `L' /tmp/cc8iv0mf.s:9: Error: junk at end of line, first unrecognized character is `L' /tmp/cc8iv0mf.s:10: Error: junk at end of line, first unrecognized character is `L' /tmp/cc8iv0mf.s:11: Error: junk at end of line, first unrecognized character is `L' make[4]: *** [/usr/src/linux-headers-6.16.4-edge-rockchip64/scripts/Makefile.build:290: line-display.o] Error 1 make[3]: *** [/usr/src/linux-headers-6.16.4-edge-rockchip64/Makefile:2003: .] Error 2 make[2]: *** [/usr/src/linux-headers-6.16.4-edge-rockchip64/Makefile:248: __sub-make] Error 2 make[2]: Leaving directory '/root/tm16xx-display' make[1]: *** [Makefile:248: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-6.16.4-edge-rockchip64' make: *** [Makefile:46: module] Error 2 fresh install, box T9 rk3328

I'm not sure it's related to your issue, but on some pi's I've seen Ethernet bandwidth issues accumulating over uptime. It was related to only to a part of specific hardware models, so suspect might be related to either hardware or kernel/driver version/implementation. After some tests I've found that the issue affects only per TCP connection downlink bandwidth - UDP does not have limits, as well as uplink TCP, multiple downlink TCP connections bandwidth stacks linearly. The worst bw case I've seen is ~2Mbps per TCP conn. Reboot fixes the issue for a random time (briefly from a few hours to a few months). Sometimes(?) the issue disappears on its own. So far I've not found a fault-proof fix except a reboot, but changing tcp congestion algo is worth to try: # sysctl net.ipv4.tcp_available_congestion_control net.ipv4.tcp_available_congestion_control = reno bic cubic westwood highspeed hybla htcp vegas nv veno scalable lp yeah illinois bbr # sysctl net.ipv4.tcp_congestion_control net.ipv4.tcp_congestion_control = cubic # sysctl net.ipv4.tcp_congestion_control=bbr net.ipv4.tcp_congestion_control = bbr For tests you may use iperf3 varying -C/-P/-R/..., e.g.: # iperf3 -4 -f m -P 1 -i 0 -t 5 -c IPERF3_SRV_IP --bind LAN_IP -R -b 100M -u # Single connection DL UDP up to 100Mbps for 5 sec # iperf3 -4 -f m -P 1 -i 0 -c IPERF3_SRV_IP --bind LAN_IP -R -C bbr # Single TCP conn DL using BBR as a congestion algo ... # iperf3 -4 -f m -P 50 -i 0 -c IPERF3_SRV_IP --bind LAN_IP -R # 50 TCP conns DL

this board appears to have effervesced from your repo in this commit, just a few weeks ago. is it maintained elsewhere?

Hello, is BPI-6202/6204 supported? It should have A40I CPU, like the M2 Ultra (which is actually supported)

./compile.sh BOARD=orangepizero3 BRANCH=current RELEASE=trixie BUILD_MINIMAL=yes KERNEL_CONFIGURE=no https://docs.armbian.com/Developer-Guide_Build-Preparation/ replace BRANCH with edge if you prefer more recent kernel. replace RELEASE with noble if you prefer Ubuntu flavour. remove BUILD_MINIMAL=yes to get the choice to build a standard cli image instead of minimal/iot.

The Trixie-based XFCE image seems to work fine too, so only the Noble-based images seem to be broken.

Collabora and MediaTek are advancing upstream Linux support for the latest Genio IoT boards and Chromebook Plus laptops, enabling full hardware functionality, improved security, and broader access to the open source community. View the full article

No it is not.

I've learned that I can pass BRANCH=vendor and I can confirm that everything works with the vendor 6.1.x kernel. I'd rather not be stuck with this old version but just wanted to confirm that it works with my setup.

Has anybody tried compiling mpv-0.35 + PR14690 within Trixie and ffmpeg 7.x.x? If anyone is curious... mpv-0.37 fails in the compilation step in ad-spdif.c due to an incompatible pointer But mpv-0.38 (without patches) compiles successfully

take note that these functions are done by other repos with specificity using the name Armbian, as an example ophub is (ab)using the name Armbian without permission and they do not contribute to the core development process. Rather they trick users into thinking they get support here and therefore (ab)using our resources. everyone in the community has this as the main feature of a TV box

@Amaliacan you please share the devfmc and armbian image version names/link that you have used to make the box booting? Is sound, wired and wireless networks working for you in this approach? I have a x96 x4 box with S905x4 chipset 4/64 GB model. I am trying to load Armbian. So far Devfmc version boots, network is also working. I am unable to boot into Armbian of any version.

@Tomi Skies It could be your gpio settings. You need to extract your original android dts. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/4/#comment-187672