All Activity

Also interested in this. Was able to install using `sudo ./sunxi-fel -p spiflash-write 0 u-boot-sunxi-with-spl.bin`, where the u-boot image came from the Armbian I downloaded (scp'd it off). That makes use of a patch submitted to the sunxi-tools repo (https://github.com/linux-sunxi/sunxi-tools/pull/232), which does actually work. It is quite happy to boot the image from SD card, and runs even when there is no SD card installed, which is great! However, I don't see any SPI or mtdblock messages in dmesg, and naturally, none exist in /dev/. Am I missing something? Or is SPI not enabled currently for some reason?

Native Steam Client For ARM Linux https://interfacinglinux.com/community/sbcsoftware/native-steam-client-for-arm-linux/

Upstream support for rk3588 is still wip. For desktop usage I suggest to either try "edge" which may have the feature you want already merged in or try "vendor" kernel which is based on Rockchip BSP.

@DaBo Thanks for sharing this. Are you able to run Armbian on this? Is LAN, HDMI, etc working fine on this?

Hello, good evening. I'll check again tomorrow; I don't remember which version of Armbian I have installed, but the microphone works without any problems in Armbian. I simply installed the Armbian version and didn't have to modify anything.

The problem (Armbian on U9-H requires physical button after power loss) The discovery process (MCU at I2C bus 0, address 0x15, register 0x11) The fix: i2cset -y 0 0x15 0x11 0x00 The systemd service for persistence That 0x01 = button required, 0x00 = auto power on Note it likely applies to the Minix NEO U1 as well since it uses the same MCU

From your logs: Healthy: 6.12.32-current-meson64 Unhealthy: 6.18.15-current-meson64 Certainly sounds like something changed/broke in a major kernel update? For the near term, I would grab a copy of the 6.12 kernel and keep a copy. The apt tool should have saved a copy in /var/cache/apt/archives, so you should be able to pull a copy from the good system, and use "sudo dpkg -i" to downgrade the other two boards for the time being. If the working node has been upgraded, it's fan will probably stop working as intended after a power cycle. In parallel, the next thing to do is to take a look at the .dtb files for both kernels (amlogic/meson-sm1-odroid-hc4.dtb), and see what's changed. If I have a free evening, I'll take a peek. As @Igor as the board maintainer, you can also file a bug at https://github.com/armbian/build/issues, but could be a bit to get addressed.

I ran Geekbench on the A7S with all the clocks at maximum. Here are the results: https://browser.geekbench.com/v5/cpu/24253556 https://browser.geekbench.com/v6/cpu/17727869 And your script gives me: ╔══════════════════════════════════════════════════╗ ║ CPU Performance Benchmark Tool v1.0 ║ ║ Single · Multi-Core · Big/LITTLE Benchmark ║ ║ Auto-detects heterogeneous cores ║ ╚══════════════════════════════════════════════════╝ ════════════════════════════════════════════════════════════ System Info ════════════════════════════════════════════════════════════ OS: Linux 6.6.98-vendor-sun60iw2 (aarch64) Processor: aarch64 Logical cores: 8 Core topology: 8 cores [homogeneous / unprobed] Python: 3.13.5 (CPython) Test time: 2026-04-21 00:46:32 Single-core 5s/test | Per-core 3rounds x 3s | 8 dimensions ════════════════════════════════════════════════════════════ Single Core Benchmark (Fastest Core) ════════════════════════════════════════════════════════════ [1/8] Integer (Prime Sieve) ... 4637 iters / 5.00s (927.39 ops/s) [2/8] Float (Matrix Mul) ... 7 iters / 5.12s (1.37 ops/s) [3/8] Float (FFT) ... 3 iters / 7.05s (0.43 ops/s) [4/8] Hash (SHA-256) ... 114 iters / 5.02s (22.70 ops/s) [5/8] Memory Sort ... 4 iters / 6.56s (0.61 ops/s) [6/8] Recursion (Fibonacci) ... 1 iters / 11.63s (0.09 ops/s) [7/8] Math (Pi) ... 1852 iters / 5.00s (370.35 ops/s) [8/8] Compress (zlib) ... 25 iters / 5.14s (4.86 ops/s) ════════════════════════════════════════════════════════════ Per-Core Power Probe (8 logical cores) ════════════════════════════════════════════════════════════ System reports no heterogeneous topology, probing empirically 3 rounds x 3s/round, warmup 0.5s, pinned mode, 8 workers Probing Integer (3 rounds): Round 1/3 ... max 923.9 min 277.1 ratio 3.33x pinned Round 2/3 ... max 922.6 min 275.2 ratio 3.35x pinned Round 3/3 ... max 921.8 min 273.9 ratio 3.37x pinned Median results (3 rounds): Core 6: 922.63 ops/s [████████████████████] 100.0% Core 7: 916.12 ops/s [███████████████████░] 99.3% Core 4: 276.21 ops/s [█████░░░░░░░░░░░░░░░] 29.9% Core 1: 276.10 ops/s [█████░░░░░░░░░░░░░░░] 29.9% Core 3: 276.04 ops/s [█████░░░░░░░░░░░░░░░] 29.9% Core 5: 275.76 ops/s [█████░░░░░░░░░░░░░░░] 29.9% Core 2: 275.56 ops/s [█████░░░░░░░░░░░░░░░] 29.9% Core 0: 275.17 ops/s [█████░░░░░░░░░░░░░░░] 29.8% -> Heterogeneity detected: 2 big cores (avg 919.4 ops/s) + 6 little cores (avg 275.8 ops/s) ratio 3.33x Probing Float (3 rounds): Round 1/3 ... max 370.4 min 95.4 ratio 3.88x pinned Round 2/3 ... max 371.1 min 95.4 ratio 3.89x pinned Round 3/3 ... max 369.5 min 95.3 ratio 3.88x pinned Median results (3 rounds): Core 6: 370.39 ops/s [████████████████████] 100.0% Core 7: 369.28 ops/s [███████████████████░] 99.7% Core 5: 95.59 ops/s [█████░░░░░░░░░░░░░░░] 25.8% Core 4: 95.51 ops/s [█████░░░░░░░░░░░░░░░] 25.8% Core 1: 95.46 ops/s [█████░░░░░░░░░░░░░░░] 25.8% Core 3: 95.46 ops/s [█████░░░░░░░░░░░░░░░] 25.8% Core 2: 95.45 ops/s [█████░░░░░░░░░░░░░░░] 25.8% Core 0: 95.36 ops/s [█████░░░░░░░░░░░░░░░] 25.7% -> Heterogeneity detected: 2 big cores (avg 369.8 ops/s) + 6 little cores (avg 95.5 ops/s) ratio 3.87x Multi-benchmark cross-validation agrees: 2 big + 6 little System didn't report heterogeneous, but probe found 2 big + 6 little (ratio 3.58x) ════════════════════════════════════════════════════════════ Big/Little Independent Benchmark (2 big + 6 little) ════════════════════════════════════════════════════════════ Three phases: big(2 threads) / little(6 threads) / mixed(8 threads) [1/8] Integer (Prime Sieve) Big ( 2 threads): iters 3637 | throughput 1818.20 ops/s | per-core min/avg/max: 907.88/909.10/910.33 Little ( 6 threads): iters 5881 | throughput 2939.47 ops/s | per-core min/avg/max: 275.72/489.91/924.17 Mixed ( 8 threads): iters 6989 | throughput 3492.59 ops/s | per-core min/avg/max: 275.81/436.57/919.04 Speedup: big 1.97x little 3.18x mixed 3.78x Efficiency: big 98.4% little 53.0% mixed 47.3% Big per-core min/avg/max: 907.88/909.10/910.33 ops/s Little per-core min/avg/max: 275.72/489.91/924.17 ops/s Mixed per-core min/avg/max: 275.81/436.57/919.04 ops/s [2/8] Float (Matrix Mul) Big ( 2 threads): iters 4 | throughput 1.14 ops/s | per-core min/avg/max: 0.57/0.57/0.57 Little ( 6 threads): iters 8 | throughput 1.95 ops/s | per-core min/avg/max: 0.23/0.32/0.51 Mixed ( 8 threads): iters 8 | throughput 2.59 ops/s | per-core min/avg/max: 0.24/0.32/0.48 Speedup: big 1.48x little 2.54x mixed 3.37x Efficiency: big 74.2% little 42.3% mixed 42.1% Big per-core min/avg/max: 0.57/0.57/0.57 ops/s Little per-core min/avg/max: 0.23/0.32/0.51 ops/s Mixed per-core min/avg/max: 0.24/0.32/0.48 ops/s [3/8] Float (FFT) Big ( 2 threads): iters 2 | throughput 0.74 ops/s | per-core min/avg/max: 0.37/0.37/0.37 Little ( 6 threads): iters 6 | throughput 1.51 ops/s | per-core min/avg/max: 0.18/0.25/0.36 Mixed ( 8 threads): iters 8 | throughput 1.79 ops/s | per-core min/avg/max: 0.16/0.22/0.35 Speedup: big 1.93x little 3.93x mixed 4.65x Efficiency: big 96.3% little 65.4% mixed 58.1% Big per-core min/avg/max: 0.37/0.37/0.37 ops/s Little per-core min/avg/max: 0.18/0.25/0.36 ops/s Mixed per-core min/avg/max: 0.16/0.22/0.35 ops/s [4/8] Hash (SHA-256) Big ( 2 threads): iters 90 | throughput 44.91 ops/s | per-core min/avg/max: 22.44/22.45/22.47 Little ( 6 threads): iters 192 | throughput 93.90 ops/s | per-core min/avg/max: 12.15/15.65/22.60 Mixed ( 8 threads): iters 241 | throughput 117.73 ops/s | per-core min/avg/max: 12.10/14.72/22.54 Speedup: big 1.98x little 4.14x mixed 5.19x Efficiency: big 99.0% little 69.0% mixed 64.9% Big per-core min/avg/max: 22.44/22.45/22.47 ops/s Little per-core min/avg/max: 12.15/15.65/22.60 ops/s Mixed per-core min/avg/max: 12.10/14.72/22.54 ops/s [5/8] Memory Sort Big ( 2 threads): iters 4 | throughput 1.06 ops/s | per-core min/avg/max: 0.53/0.53/0.53 Little ( 6 threads): iters 6 | throughput 2.01 ops/s | per-core min/avg/max: 0.23/0.33/0.49 Mixed ( 8 threads): iters 8 | throughput 2.28 ops/s | per-core min/avg/max: 0.19/0.29/0.47 Speedup: big 1.78x little 3.37x mixed 3.83x Efficiency: big 89.1% little 56.2% mixed 47.9% Big per-core min/avg/max: 0.53/0.53/0.53 ops/s Little per-core min/avg/max: 0.23/0.33/0.49 ops/s Mixed per-core min/avg/max: 0.19/0.29/0.47 ops/s [6/8] Recursion (Fibonacci) Big ( 2 threads): iters 2 | throughput 0.17 ops/s | per-core min/avg/max: 0.08/0.08/0.09 Little ( 6 threads): iters 6 | throughput 0.36 ops/s | per-core min/avg/max: 0.04/0.06/0.08 Mixed ( 8 threads): iters 8 | throughput 0.43 ops/s | per-core min/avg/max: 0.04/0.05/0.08 Speedup: big 2.00x little 4.20x mixed 5.07x Efficiency: big 100.0% little 70.1% mixed 63.4% Big per-core min/avg/max: 0.08/0.08/0.09 ops/s Little per-core min/avg/max: 0.04/0.06/0.08 ops/s Mixed per-core min/avg/max: 0.04/0.05/0.08 ops/s [7/8] Math (Pi) Big ( 2 threads): iters 1492 | throughput 745.39 ops/s | per-core min/avg/max: 370.74/372.70/374.65 Little ( 6 threads): iters 2263 | throughput 1130.50 ops/s | per-core min/avg/max: 94.95/188.42/375.07 Mixed ( 8 threads): iters 2642 | throughput 1319.41 ops/s | per-core min/avg/max: 95.16/164.93/374.73 Speedup: big 2.03x little 3.07x mixed 3.58x Efficiency: big 101.3% little 51.2% mixed 44.8% Big per-core min/avg/max: 370.74/372.70/374.65 ops/s Little per-core min/avg/max: 94.95/188.42/375.07 ops/s Mixed per-core min/avg/max: 95.16/164.93/374.73 ops/s [8/8] Compress (zlib) Big ( 2 threads): iters 20 | throughput 9.51 ops/s | per-core min/avg/max: 4.73/4.75/4.78 Little ( 6 threads): iters 40 | throughput 18.53 ops/s | per-core min/avg/max: 2.21/3.09/4.78 Mixed ( 8 threads): iters 50 | throughput 22.02 ops/s | per-core min/avg/max: 2.09/2.75/4.62 Speedup: big 1.96x little 3.81x mixed 4.53x Efficiency: big 97.8% little 63.5% mixed 56.6% Big per-core min/avg/max: 4.73/4.75/4.78 ops/s Little per-core min/avg/max: 2.21/3.09/4.78 ops/s Mixed per-core min/avg/max: 2.09/2.75/4.62 ops/s ════════════════════════════════════════════════════════════ Score Report (Heterogeneous: 2 big + 6 little) ════════════════════════════════════════════════════════════ Test Single Big Little Mixed Big eff Little eff ──────────────────────────────────────────────────────────────────────────────── Integer (Prime Sieve) 11592 22728 36743 43657 98.4% 53.0% Float (Matrix Mul) 2733 2282 3899 5183 74.2% 42.3% Float (FFT) 142 247 503 596 96.3% 65.4% Hash (SHA-256) 1514 2994 6260 7849 99.0% 69.0% Memory Sort 203 354 670 761 89.1% 56.2% Recursion (Fibonacci) 29 57 119 144 100.0% 70.1% Math (Pi) 1852 3727 5652 6597 101.3% 51.2% Compress (zlib) 972 1901 3705 4405 97.8% 63.5% ──────────────────────────────────────────────────────────────────────────────── Single geomean.................... 719 Big group geomean................. 1236 Little group geomean.............. 2289 Mixed geomean..................... 2760 ════════════════════════════════════════════════════════════ Big/Little Power Comparison ════════════════════════════════════════════════════════════ Big/Little power ratio (from per-core probe): 3.58x Big avg ops/s: 1.99 Little avg ops/s: 0.56 Power composition: Big (2 cores): [████████████████░░░░░░░░░░░░░░] 54.4% 54.4% Little (6 cores): [█████████████░░░░░░░░░░░░░░░░░] 45.6% 45.6% Equivalent big cores: 3.7 (little cores converted to big power) ══════════════════════════════════════════════════ Single score: 719 (fastest core) Big group score: 1236 (big cores only) Little group score: 2289 (little cores only) Mixed score: 2760 (big+little mixed) Mixed / Single: 3.84x ══════════════════════════════════════════════════ Benchmark complete!

@BacchusIX Odroid H4 Plus

@Sponzo that image also doesnt work for me, did you have to unlock to bootloader or something else in dev settings?

@Alexander Polko Do you still have stock firmware in eMMC? You should get some output from the serial uart if you have the stock firmware, otherwise your serial is not working correctly. Also, boot from sdcard only works via u-boot from stock firmware on this board, for the reason I stated above.

Collabora is headed to Stuttgart for XR Expo 2026! Visit us in Hall 2, booth 2C22, to experience the latest around Monado and ElectricMaple, and catch our 2 talks! View the full article

I also tried different U-Boot SPL variants, but I was unable to get Armbian to boot. However, I noticed something interesting — on my MikroTik router I saw a DHCP lease that was issued to a client identified as "uboot", though I only noticed this after the fact and missed the chance to investigate further.

Hi @jock, thank you very much for your detailed explanation and for pointing me to the multitool project! I successfully built the multitool image for rk3528 and wrote it to the SD card, but unfortunately the box does not boot from it — it stuck every time. I also tried connecting via UART (FT232 adapter, 1500000 baud, 8N1) but I only get garbage/noise in the terminal — no readable output at all, even right after powering on the device.

@Nick A Thanks for taking my advice.😄 This is the test program of mine. You can play around with it if you have time. cpu_benchmark.py.zip

@qq20739111 thanks I'll remove the patch and compile a new image.

Hi. I booted the image, ran the gpu script provided earlier and did a reboot. uart gets stuck at (from my memory) "running premount script". I connected monitor over hdmi, but it's just a mouse on black screen. I could switch to different tty. WiFi module doesn't seem to work either: the armbian script doesn't show on option to connect to a wifi hotspot. I noticed this in update logs: ``` Armbian 'linux-image-current-spacemit' for '6.18.21-current-spacemit': 'prerm' starting. dkms: removing: bcmdhd-spacemit-sdio 101.10.591.84.37-4 (6.18.21-current-spacemit) (riscv64) Module bcmdhd-spacemit-sdio-101.10.591.84.37-4 for kernel 6.18.21-current-spacemit (riscv64). Before uninstall, this module version was ACTIVE on this kernel. bcmdhd.ko.xz: - Uninstallation - Deleting from: /lib/modules/6.18.21-current-spacemit/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. dhd_static_buf.ko.xz: - Uninstallation - Deleting from: /lib/modules/6.18.21-current-spacemit/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod...... Deleting module bcmdhd-spacemit-sdio-101.10.591.84.37-4 completely from the DKMS tree. Armbian 'linux-image-current-spacemit' for '6.18.21-current-spacemit': 'prerm' finishing. Armbian 'linux-image-current-spacemit' for '6.18.22-current-spacemit': 'preinst' starting. Armbian 'linux-image-current-spacemit' for '6.18.22-current-spacemit': 'preinst' finishing. ``` Which IIUC means that wifi module was uninstalled. Also there is this: ``` gdm.service is not active, cannot reload. invoke-rc.d: initscript gdm3, action "reload" failed. Synchronizing state of lightdm.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable lightdm The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. OK. ```

@Nick A As shown in the figure, I tested your newly released patched image on this fanless DIY heatsink dev board using a CPU benchmark tool, and the CPU performance is indeed heavily throttled! With v0.6.1, I scored 2571, with average core temps around 75°C. However, with v0.6.4, the all-core score dropped to just 985, with temps hovering around 60°C. This is even significantly lower than the official system image (1700+). I would really prefer a version without these patches; otherwise, the board's potential is being wasted. After all, sustained operation below 90°C is perfectly safe for this CPU. The official release limits CPU performance to prevent high-temp instability and reduce support tickets, but your image doesn't need to impose these restrictions.

Good afternoon. I extracted the DTS. What is the next step? Thanks in advance extracted_dt.dts

@Kauã Fonseca There are SSH commands in my GitHub repository. Just SSH into your TV box and execute them one by one. sudo apt-get update sudo apt-get install -y build-essential linux-headers-$(uname -r) git git clone https://github.com/cdhigh/armbian_sv6256p.git cd armbian_sv6256p chmod +x ./parser-conf.sh make ARCH=arm64 KSRC=/lib/modules/$(uname -r)/build ls -lh ssv6x5x.ko sudo cp ./ssv6x5x-wifi.cfg /lib/firmware/ sudo cp ./ssv6x5x-sw.bin /lib/firmware/ sudo cp ./ssv6x5x.ko /lib/modules/$(uname -r)/kernel/drivers/net/wireless/ sudo depmod -a sudo modprobe ssv6x5x ip link show nmtui

Hi Ive just installed the latest version of Armbian (Ubuntu Noble+KDE) and everything works fine except it looks like it is not detecting my TV resolution correctly. I can choose 1920x1080@120hz but if I try yo go to 4K I can only select 24Hz I attach armbian monitor logs url, modetest and kscreendoctor My cable is HDMI 2.1 Any help would be appreciated modetest -c trying to open device '/dev/dri/card1'... is not a KMS device trying to open device '/dev/dri/card0'... done opened device `RockChip Soc DRM` on driver `rockchip` (version 1.0.0 at 0) Connectors: id encoder status name size (mm) modes encoders 83 82 connected HDMI-A-1 1880x1060 35 82 modes: index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot #0 4096x2160 24.00 4096 5116 5204 5500 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #1 4096x2160 23.98 4096 5116 5204 5500 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver #2 3840x2160 30.00 3840 4016 4104 4400 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #3 3840x2160 29.97 3840 4016 4104 4400 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver #4 3840x2160 25.00 3840 4896 4984 5280 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #5 3840x2160 24.00 3840 5116 5204 5500 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #6 3840x2160 23.98 3840 5116 5204 5500 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver #7 1920x1080 120.00 1920 2008 2052 2200 1080 1084 1089 1125 297000 flags: phsync, pvsync; type: driver #8 1920x1080 119.88 1920 2008 2052 2200 1080 1084 1089 1125 296703 flags: phsync, pvsync; type: driver #9 1920x1080 100.00 1920 2448 2492 2640 1080 1084 1089 1125 297000 flags: phsync, pvsync; type: driver #10 1920x1080 60.00 1920 2008 2052 2200 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver #11 1920x1080 59.94 1920 2008 2052 2200 1080 1084 1089 1125 148352 flags: phsync, pvsync; type: driver #12 1920x1080 50.00 1920 2448 2492 2640 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver #13 1920x1080 30.00 1920 2008 2052 2200 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver #14 1920x1080 29.97 1920 2008 2052 2200 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver #15 1920x1080 24.00 1920 2558 2602 2750 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver #16 1920x1080 23.98 1920 2558 2602 2750 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver #17 1680x1050 59.88 1680 1728 1760 1840 1050 1053 1059 1080 119000 flags: phsync, nvsync; type: driver #18 1600x900 60.00 1600 1624 1704 1800 900 901 904 1000 108000 flags: phsync, pvsync; type: driver #19 1280x1024 60.02 1280 1328 1440 1688 1024 1025 1028 1066 108000 flags: phsync, pvsync; type: driver #20 1152x864 75.00 1152 1216 1344 1600 864 865 868 900 108000 flags: phsync, pvsync; type: driver #21 1280x720 60.00 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver #22 1280x720 59.94 1280 1390 1430 1650 720 725 730 750 74176 flags: phsync, pvsync; type: driver #23 1280x720 50.00 1280 1720 1760 1980 720 725 730 750 74250 flags: phsync, pvsync; type: driver #24 1280x720 30.00 1280 3040 3080 3300 720 725 730 750 74250 flags: phsync, pvsync; type: driver #25 1280x720 29.97 1280 3040 3080 3300 720 725 730 750 74176 flags: phsync, pvsync; type: driver #26 1280x720 24.00 1280 3040 3080 3300 720 725 730 750 59400 flags: phsync, pvsync; type: driver #27 1280x720 23.98 1280 3040 3080 3300 720 725 730 750 59341 flags: phsync, pvsync; type: driver #28 1024x768 60.00 1024 1048 1184 1344 768 771 777 806 65000 flags: nhsync, nvsync; type: driver #29 800x600 60.32 800 840 968 1056 600 601 605 628 40000 flags: phsync, pvsync; type: driver #30 720x576 50.00 720 732 796 864 576 581 586 625 27000 flags: nhsync, nvsync; type: driver #31 720x480 60.00 720 736 798 858 480 489 495 525 27027 flags: nhsync, nvsync; type: driver #32 720x480 59.94 720 736 798 858 480 489 495 525 27000 flags: nhsync, nvsync; type: driver #33 640x480 60.00 640 656 752 800 480 490 492 525 25200 flags: nhsync, nvsync; type: driver #34 640x480 59.94 640 656 752 800 480 490 492 525 25175 flags: nhsync, nvsync; type: driver props: 1 EDID: flags: immutable blob blobs: value: 00ffffffffffff004dd9057901010101 011e010380bc6a780a0dc9a057479827 12484c2108008180a9c0714fb3000101 01010101010108e80030f2705a80b058 8a005a227400001e023a801871382d40 582c45005a227400001e000000fc0053 4f4e5920545620202a33300a000000fd 0017790e883c000a20202020202001bf 020367f05861605d5e5f621f10140513 0420223c3e1203110265663f402f0d7f 071507503d07bc570601670403830f00 006e030c004000b8442b008001020304 67d85dc401788003eb0146d000480382 88627697e200cbe305df01e40f030030 e6060d018aac10011d007251d01e206e 2855005a227400001e000000000000a3 2 DPMS: flags: enum enums: On=0 Standby=1 Suspend=2 Off=3 value: 0 5 link-status: flags: enum enums: Good=0 Bad=1 value: 0 6 non-desktop: flags: immutable range values: 0 1 value: 0 4 TILE: flags: immutable blob blobs: value: 84 max bpc: flags: range values: 8 8 value: 8 kscreen-doctor -o Output: 1 HDMI-A-1 ea40cb77-73bf-4175-8970-22f84927f147 enabled connected priority 1 HDMI replication source:0 Modes: 1:4096x2160@24.00*! 2:4096x2160@23.98 3:3840x2160@30.00 4:3840x2160@29.97 5:3840x2160@25.00 6:3840x2160@24.00 7:3840x2160@23.98 8:1920x1080@120.00 9:1920x1080@119.88 10:1920x1080@100.00 11:1920x1080@60.00 12:1920x1080@60.00 13:1920x1080@59.94 14:1920x1080@50.00 15:1920x1080@30.00 16:1920x1080@29.97 17:1920x1080@24.00 18:1920x1080@23.98 19:1680x1050@59.88 20:1600x900@60.00 21:1280x1024@60.02 22:1152x864@75.00 23:1280x720@60.00 24:1280x720@60.00 25:1280x720@59.94 26:1280x720@50.00 27:1280x720@30.00 28:1280x720@29.97 29:1280x720@24.00 30:1280x720@23.98 31:1024x768@60.00 32:800x600@60.32 33:720x576@50.00 34:720x576@50.00 35:720x480@60.00 36:720x480@60.00 37:720x480@59.94 38:720x480@59.94 39:640x480@60.00 40:640x480@59.94 Custom modes: None Geometry: 0,0 1821x960 Scale: 2.25 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none Color profile source: sRGB Color power preference: prefer efficiency and performance Brightness control: supported, set to 100% and dimming to 100% Color resolution: automatic (10), range: [8; 8] bits per color Allow EDR: unsupported Sharpness control: unsupported Automatic brightness: unsupported Thank you

If someone is eager to add sway - we have a new cleaner way to add and maintain (unit tests, AI auto maintain) new desktop: https://docs.armbian.com/Developer-Guide_Desktops/

I see. I actually tried to educate myself to see if I could help out, that is why I extracted the code in the first place. I would love to be able to help, but it seems outside of my capabilities. But I'll keep reading trying to learn, and maybe some day I will be able to make a pr rather than just a post on the forum. Thank you AGAIN for ALL you do!!

Which kernel, debian, mesa and sway versions are running normally when you run a stock Armbian? Which new versions have you observed working together? (even if it's not ARM). If they are too different, they may not work together due to library functions expecting other parameters. You can try it with Ubuntu Noble, which has newer packages than Debian Trixie (build Armbian by yourself).

https://actions.armbian.com/?repo=armbian.github.io Here anyone can monitor ... but the real problem is capacity to fix problems. Not knowning them. We have too many problems on the to do list It is not O.K., but also not a critical problem. This script is making a cache for this package which is needed in critical operations. Where it can't fail. This is why this was made in 1st place. We can't rely on upstream infrastructure.