All Activity

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

@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.17 build but I haven’t had time to test it yet. Don’t worry about those wifi errors it will work fine.

kernel update actually works, I'm now on -current mainline kernel (-edge works OK too); trouble is only in .dtb in mainline package # uname -a Linux transpeed-8k618-t 6.12.43-current-sunxi64 #1 SMP Wed Aug 20 16:30:58 UTC 2025 aarch64 GNU/Linux thanks; there are brcmfmac4334-sdio.bin and brcmfmac4334-sdio.rockchip,rk3318-box.txt; I've renamed them to brcmfmac4334-sdio.transpeed,8k618-t.bin and brcmfmac4334-sdio.txt - wifi appears in device list, there are some strange messages in dmesg but I think it'll work ok [23108.014126] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 [23108.023494] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.clm_blob failed with error -2 [23108.214552] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [23108.214581] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [23108.214910] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e

Well, I do think X11 is going to fall behind at some point if it continues to lack support of new things. I don't know the status for gaming on Wayland. I use lutris and wine to play WoW. Which doesn't yet work on these machines. Perhaps with 6.16. I'm an Xmonad user and I wouldn't touch gnome or kde with a ten foot pole. I'll use fvwm2 in a pinch. So far there isn't a "wm" on Wayland that compares to Xmonad, and I wouldn't use hypr land or any thing related to it for politics. Nasty people. Sway is the most promising at the moment, but it is too close to i3 which is too limited. There is no way Xmonad will become a compositor. So something has to happen. Not using 2 screens might be the easiest. I don't need two. But the Nanopi m6 has two. I can just get another without a screen and use this one as a server. Just living in the increasingly limited realm of X11 seems to be the thing to do unless I want to write a compositor. I've thought about adding compositing abilities to emacs. Someone has done a bit of that. Might be politically difficult to get it in. It would also mean writing a new Exwm. I'll just hang on to X because Wayland still doesn't meet my needs, and it has nothing capable of replacing what I have on X.

@emor acid Here's some information on H616/H618 ethernet phy. This is the 100Mbit ethernet built inside the H618 SOC. https://lore.kernel.org/linux-sunxi/20250526002924.2567843-1-james.hilliard1@gmail.com/T/#t In your dmesg log it shows your box is loading a generic phy. It should be loading the Allwinner phy. For example @NiTr0 logs above. Your box might be using a 1000Mbit external ethernet chip. If that's the case your dts settings will be very different. You'll need check if your box supports Gigabit Ethernet and find the Ethernet chip on your board. @NiTr0 Just freeze the kernel updates using armbian-config. My armbian build is unofficial so you can't use the official armbian kernels. I'm using patches created by warpme and my own custom patches. So the kernel update feature will not work. https://www.google.com/search?q=armbian+config+freeze+kernel&oq=armbian+config+freeze+kernel&gs_lcrp=EgZjaHJvbWUyBggAEEUYOdIBCDY4MDJqMGo3qAIAsAIA&sourceid=chrome&ie=UTF-8 For wifi your box is looking for You need find the brcmfmac4334 bin file and rename it to brcmfmac4334-sdio.transpeed,8k618-t.bin. Also, the brcmfmac4334 txt to brcmfmac4334-sdio.txt. I think it's already in /lib/firmware/brcm under a different name.

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

@Nick A here， compile with this patch +&mdio1 { + rmii_phy: ethernet-phy@0 { + compatible = "ethernet-phy-ieee802.3-c22"; + reg = <0>; + }; +}; journalctl.log dmesg.log

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.

Thanks, ok this works but only over SSH. Maybe the other ones did too and the fact my monitor wouldn't turn on for them had me stuck.