Active threads

Hello Jock, Can you confirm that you use the patch in mpv PR1460, or something else?

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).

@NiTr0 I guess transferring the dtb to official armbian kernel 6.12.43 will work. Most of warpme’s collection of patches are already in the official armbian build. There might be some differences. the reason I use warpme patches is because he’s usually quick at porting his patches to the latest kernel versions. I made a 6.18 build but I haven’t had time to test it yet. Don’t worry about those wifi errors it will work fine.

This bug is not showing again with Trixie, and the repository labwc 0.8.3 (same), same orange pi zero 3, same HDMI monitor.

First resize framebuffer to a convenient one and then start x11vnc xrandr --fb 1920x1080 -d :0 x11vnc -display :0

One suggestion I can give you is to try a fresh image from https://github.com/armbian/community/releases. Make a backup of the eMMC and clean it up (multitool can do both things), then try to boot from sdcard with the new image. Newer images come with u-boot v2025.10-rc5 and a "fix" to reset the VOP before entering the kernel. Some people on the other thread reported that disabling u-boot HDMI made the HDMI work once in Linux. With kernel 6.17 this issue hit my box and I could arrange a fix, perhaps this fix will address your problem too (for reference: https://github.com/armbian/build/pull/8674/files#diff-70c2c867b6e2024080868c0d5c3230d58be2d2c4b88a24291b0469c7d2229629)

I've never been able to wake up my Orange PI 5 Plus from suspend. It just goes into oblivion - requiring a hard restart. The keyboard and mouse don't wake it up. Tapping the power button doesn't wake it up. I've tried it on Armbian as well as pure Debian Trixie. Apparently something is off in the design of the SBC. But also hibernation doesn't work (again in Armbian and in pure Trixie). Using a 32 GB (32 * 1024^3) swap for a "32 GB" (actually around 31 GB) RAM device, and setting RESUME to the swap partition, the hibernation option appears. But when used, it just goes into oblivion (like suspend). I left it alone like that once for about 20 minutes, it was still in limbo. and when I (have to) hard restart it, the previous supposedly-hibernated state is gone. Given that the SBC is capable of doing a power shutdown from the OS (i.e. after dumping allocated RAM to the swap), there is no legitimate reason for hibernation to not work. But it doesn't.

Just to help anyone else that ran into this. I was able to get up and running by Armbian_25.8.2_Orangepi5_noble_current_6.12.49_minimal (1).img.xz then on boot I found the IP address on my network and SSH'd to it. Once on I used armbian-config to go and fetch the edge kernel 6.16.4-edge-rockchip64 Display is now working, but the older USB for the keyboard doesn't work. Only the USB 3.0 does.

Hello everyone, is there a solution to install Armbian on it? Thanks to all the experts.

I compiled kernel on debian vm which I just brought up via Vagrant but I guess that maybe I assigned not enough vCPUs to this vm (just 1). Yes, you're right, real kernel package is much smaller as around 103M vagrant@test-debian12:~/build/output/debs$ ls -lh linux-image-current-meson_25.11.0-trunk_armhf__6.12.51-Sa915-D8343-P0029-C8d22H47a6-HK01ba-Va132-B14f4-R448a.deb -rw-rw-r-- 1 vagrant root 103M Oct 9 17:43 linux-image-current-meson_25.11.0-trunk_armhf__6.12.51-Sa915-D8343-P0029-C8d22H47a6-HK01ba-Va132-B14f4-R448a.deb I think I will go with using this new Armbian disk Image (this 1.3 GB file ;-)) so it will be easier to get this working. I have copy of my old drive so I don't have to worry about loosing any data . To be honest, I very occasionally compiling something from sources not even mention of cross-compiling kernel even if I use Linux on daily basis (work and home). I really appreciate your time in helping me with this and I think this information is very valuable as many people are still using the Odroid C1 board. Many Thanks !!!

@Meestor_X Please check the following: on a running device. It seems that we have a more reliable way to determine the block device SD or eMMC

Use them as command line switches, like code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh BUILD_MINIMAL=yes FULL_DESKTOP=no ... Used by CI only which kernel to do automatic build tests.

To keep the forum updated: I closed my PR to downgrade all NanoPC-T6 boards to use HS200 mode, since there are other folks who do have the NanoPC-T6 and can successfully use HS400 mode. @SuperKali opened up a PR to downgrade all NanoPC-T6 boards to use HS400 mode without enhanced strobe as "This should maintains the same ~400MB/s throughput while eliminating I/O errors under load.". I tried applying the patch on my board, but unfortunately still hit I/O errors. @SuperKali had suggested on my original PR to try reducing the eMMC frequency from the default 200000000 to 150000000. I created an overlay for this... and it worked! I'm going to prepare a PR tomorrow to add that overlay as a kernel overlay, so that others who are experiencing this issue can opt-in to it without needing to find this thread and copy the overlay file.

@JohnTheCoolingFan I tested a Debian Trixie image from the website ( Armbian_25.8.1_Bigtreetech-cb1_trixie_current_6.12.35_minimal.img.xz ) and it seems to be stable even with the default configuration that uses systemd-networkd.

Using Armbian_25.8.1_Odroidxu4_noble_current_6.6.102.img I can boot off SD. Then when I run nand-sata-install it sharts and comes up with initramfs prompt. I'll try to fix it there next time, but I'm just using a 3.5" SATA laptop disk with USB controller. .oading, please wait.. .tarting systemd-udevd version 255.4-1ubuntu0.11 .begin: Loading essential drivers ... done. .begin: Running /scripts/init-premount ... done. .begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. .begin: Running /scripts/local-premount ... done. .begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. done. Save up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay=(did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=546a0798-29c9-4f3c-beea-1563d848abd0 does not exist. Dropping to a shell! BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3.1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) _

http://armbian.lv.auroradev.org/beta bookworm/main armhf armbian-bsp-cli-bananapim2ultra-current armhf 25.11.0-trunk.302 [434 kB] http://armbian.lv.auroradev.org/beta bookworm/main armhf armbian-firmware all 25.11.0-trunk.302 [100 MB] http://armbian.lv.auroradev.org/beta bookworm/main armhf linux-dtb-current-sunxi armhf 25.11.0-trunk.302 [211 kB] http://armbian.lv.auroradev.org/beta bookworm/main armhf linux-image-current-sunxi armhf 25.11.0-trunk.302 [41.8 MB] http://armbian.lv.auroradev.org/beta bookworm/main armhf linux-u-boot-bananapim2ultra-current armhf 25.11.0-trunk.302 [271 kB] after update fastfetch: Armbian 25.11.0-trunk.297 bookworm armv7l

Thank you very much. You are my superman.

For this 16xx displays we need to ask @Jean-Francois Lessard he was in contact with this drivers for a while. these 16xx displays will be included in the mainline 6.18 drivers as tm16xx_i2c make sure to adjust your device according to this repository to benefit from the update https://github.com/jefflessard/tm16xx-display

Read this entire topic, It's all there, just read it

oh how cool, send a shout out: https://forum.slitaz.org/ Let me read this https://doc.slitaz.org/en:start and I will give you the answer The answer is Yes https://arm.slitaz.org/

Hi, for 2 day i am searching for set a bootlogo on the screen while loading klipper but all i get is the linux text that fly by. I set bootlogo= true in armbianEnv.txt does not help i can't find any other option. There should also be Splash can find any decent information about that either So is it possible to show a logo at booting klipper, if yes is it also possible to change it to custom logo or video because it would be nicer to show a logo or video then al these linux lines And i am not a professional programmer so easy language if possible

Any news on this subject ? Official Ubuntu is too limited .... I'm thinking to change to armbian my server ..... To install it, does it need a full recompilation ? or is there an img ? where can I find the DTB file for M2 ?

@Hqnicolas I'm a bit late because I have overlooked your request for testing. Now I can confirm that the AuxDisplay works correctly with my H96_tvbox_3566 (with AIC 8800 wlan chip). Thank you for your effort.

Hardware: OrangePI-5-Plus (rk3588), with "32 GB" of RAM Operating System: Debian Trixie (pure, except EFI boot and Armbian edge kernel) Root File System: Ext4 (encrypted) Desktop: KDE Plasma 6.3.6 (wayland, GDM3), KDE Frameworks version: 6.13.0, QT version: 6.8.2 EFI Source: https://github.com/edk2-porting/edk2-rk3588 The boot messages, after a few starts (spaced apart) of the low-memory-monitor.service, say there's a failure to start it. After booting is complete, here's a screenshot of the output of: systemctl status low-memory-monitor.service This error didn't show up until I installed a number of packages. I tracked down the offending package from the Trixie repository: Package: xfsprogs Version: 6.13.0-2+b1 Size: 4774 kB Description: A set of commands to use the XFS filesystem, including mkfs.xfs Once this package was removed, the error vanished, and a repeat of the above Status command reported low-memory-monitor-service as active and okay. I also found that, while the error occurred with the Armbian edge 6.16.4 kernel, it did NOT occur with the Debian 6.16.3 kernel. Kernel With The Error (kernel source: Armbian trixie) --------------------- Package: linux-image-edge-rockchip64 (Armbian Linux edge kernel image 6.16.4-edge-rockchip64) Version: 25.8.1 Size: 282 MB Kernel Without The Error (kernel source: Debian trixie-backports) ------------------------ Package: linux-image-6.16.3+deb13-arm64-unsigned (Linux 6.16 for 64-bit ARMv8 machines) Version: 6.16.3-1~bpo13+1 Size: 210 MB I also briefly tried regressing the Armbian edge kernel from 25.8.1 (6.16.4) to the previously available version of 25.5.2, which was 6.16.0-rc3 (I think). The error occurred with that kernel as well. An Effect of This Bug (Possibly) When this error was showing up, I was once using the internet (firefox-esr package version 140.3.1esr-1~deb13u1) for a while, when after closing it, I discovered that my desktop background image had changed on its own. I could not change it back, no matter what I did (in the KDE settings gui). I could change it to something else, but whenever I changed it back, the altered image returned instead of what it should have been. But once I rebooted, the background was back to normal. While this one experience (very much an outlier) may not be conclusive, it is indicative of a possible memory leak.