Active threads

In that case I would strongly recommend purchasing an A1 rated SD card before trying anything else. If you are getting MMC related errors these are definitely related to the SD card rather than RAM. Once you have done this then we can look into DRAM config if need be. Trying to enable the display post build is kinda tricky. If it was just a matter of adding the HDMI display nodes, then yes that is normally possible however the display driver needs a slight patch in order to work. Now if you had kernel headers installed you could try to build the driver however another current problem means that custom loaded modules seem to not load/unload properly. Seeming as you are using the pre-built Cubieboard images, it already has the display nodes in place but not the recent patches to sun4i-drm. Looking again at the build log you provided earlier it looks like something is blocking the download of bookworm distro which is why it is failing. what happens if you trying ping apt.armbian.com? Given that this issue happens with bookworm, I wonder if it will also happen if trying build with Ubuntu Noble instead. I am currently working on formally including the display patches on my latest development branch so please bear with me. Best of luck Ryzer

i need help too.... please

Hello, @sicxnull, Thanks for all your work on the H96X box. I'm trying to install Armbian on my x96q V5.1, your image (Armbian-unofficial_24.11.0-trunk_X96q-v5-1_bookworm_current_6.6.44_mate_desktop.img.xz) works great apart from I'd really like a server instead of desktop. I'm just wanting to use it for a VPN (Tailscale) exit node. Would it be hard to build a server version? I have no Linux experience.

I don't know what else to do... I usually research and learn on the go Search the 88xxau.c in your downloaded linux source. Try to find any link to documentation or github. Search 8812au in the respberry pi forum

Hi! On the Orange Pi 5 plus with the 6.1 image (KDE), with a 4k monitor @ 60FPS and 200% scaling, when opening discord on Chrome it gets incredibly laggy. I'm just curious, is this a limitation with the GPU itself, or is this related to something in the software stack? Thanks!

The actions in the dts for setting the GPIO pin are is based on the boot log line. marlin chip en dummy pull up -- need manually set GPIO You can check the whole discussion here and the reasoning https://chatgpt.com/share/68466d15-e5bc-8013-b200-17ae7f7c89fc However, After your last answer, Chatgpt suggests this is not really the issue, but a delayed initialisation would help. When the bt fails to initialise, try the following: sudo hciattach /dev/ttyS0 any 115200 flow sudo hciconfig hci0 up If this works, you can put this in a service to run at every boot. You can try yourself to continue the above conversation with chatgpt and see if you find the final solution. Then you can post it here.

I have decompiled the dtb file but am unable to incorporate the patch. How do i incorporate the patch or change it? In terms for a newbie please! I should say it is for debian 12 Cinnamon 6.12.

NO_PUBKEY 93D6889F9F0E78D5 while using apt (e.g. apt update) symptom: > apt update ... Err:8 https://github.armbian.com/configng stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 ... W: Failed to fetch https://github.armbian.com/configng/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 observed in Armbian image for Orange pi zero 3 Armbian_community_25.8.0-trunk.90_Orangepizero3_bookworm_current_6.12.30_minimal.img build date May 28, 2025 fix: - run this as root > su - ^ login as root > wget -O - https://apt.armbian.com/armbian.key | gpg --dearmor -o /usr/share/keyrings/armbian.gpg you should find a file /usr/share/keyrings/armbian.gpg about 2 KB in size repeat apt update etc should have resolved the error

NO_PUBKEY 93D6889F9F0E78D5 while using apt (e.g. apt update) symptom: > apt update ... Err:8 https://github.armbian.com/configng stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 ... W: Failed to fetch https://github.armbian.com/configng/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 observed in Armbian image for Orange pi zero 3 Armbian_community_25.8.0-trunk.90_Orangepizero3_bookworm_current_6.12.30_minimal.img build date May 28, 2025 fix: - run this as root > su - ^ login as root > wget -O - https://apt.armbian.com/armbian.key | gpg --dearmor -o /usr/share/keyrings/armbian.gpg you should find a file /usr/share/keyrings/armbian.gpg about 2 KB in size repeat apt update etc should have resolved the error

symptom: > apt update ... Err:8 https://github.armbian.com/configng stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 ... W: Failed to fetch https://github.armbian.com/configng/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 observed in Armbian image for Orange pi zero 3 Armbian_community_25.8.0-trunk.90_Orangepizero3_bookworm_current_6.12.30_minimal.img build date May 28, 2025 fix: - run this as root > su - ^ login as root > wget -O - https://apt.armbian.com/armbian.key | gpg --dearmor -o /usr/share/keyrings/armbian.gpg you should find a file /usr/share/keyrings/armbian.gpg about 2 KB in size repeat apt update etc should have resolved the error

So I understand that no one will help me because I am not a programmer.

At this point anything like thoughts, clues and things you heard about would be helpful because I don't find any solutions online too

https://source.android.com/

Armbian Development Highlights: June 2–9, 2025 This week’s Armbian updates focused on kernel improvements, bootloader modernization, and several core enhancements to the build infrastructure. Key work spanned platforms like Rockchip, Sunxi, and Odroid, emphasizing kernel stability and broader compatibility across boards. Kernel Upgrades Several boards received kernel updates: Rockchip 32-bit edge kernel bumped to 6.15 in PR #8262 by paolosabatino. SpacemiT platforms updated to 6.6.93 in PR #8274 by pyavitz. Odroid XU4 kernel upgraded to 6.6.93 via PR #8277 by belegdol. Patches also landed to adapt Wi-Fi drivers to 6.15-era changes, including fixes for xradio and uwe5622 on Sunxi, contributed by The-going: sunxi: xradio – Switch from del_timer_sync to timer_delete_sync uwe5622: Fix timer API changes for 6.15 Bootloader and U-Boot Work Improvements were made to bootloader support: Tinkerboard 2 now uses U-Boot v2025.04 (PR #8268 by hyx0329). RK3328 boards gained setexpr support in U-Boot v2022.04/07 (PR #8260 by djurny). Build System Changes Several build system enhancements landed this cycle: PR #8276 by Ayush1325 prevented unintentional conversion of built-in kernel drivers to modules. A new helper function chroot_sdcard_custom_with_apt_logic was introduced in PR #8245 by rpardini, streamlining SD card build logic. PR #8279 by igorpecovnik removed obsolete Trixie package references. Networking Improvements PR #8259 and commit cdf71df by djurny expanded DHCP configuration in netplan to automatically include interfaces matching lan* and wan*, simplifying initial setup across devices. Miscellaneous Signing key backward compatibility was preserved in PR #8282 and commit aa5526a by igorpecovnik. Commit 0f43036 reworked prepare-host.sh after review. Contributors This Week Ayush1325 The-going djurny igorpecovnik pyavitz belegdol hyx0329 rpardini paolosabatino The post Armbian Weekly Updates first appeared on Armbian. View the full article

Hi there! We have some good news, a guy from the 4pda forums figured out how to make the missing SD slot work. I've replicated that on my M9s box a few days ago and it works like a charm. You can see original post in Russian here. So, basically, this TV box uses the same reference design for that circuitry as Armsom Sige5 and other boards. You can check the diagrams for Sige5 to get an idea. You need two capacitors (10uF and 100nF, on the power line) on the SD slot side (two smaller pads) and a LPW5202ADB5F chip and some resistors and caps on the other side. LPW5202ADB5F is a power switch chip with current limiter, can be bought on Aliexpress for like $5-6 for 20 pcs, also need these components: 1x 10k resistor - controls current limiter (this value is for 0.7A according to data sheet, lower values for higher current, or 3.6k = 2A), 2x 10uF caps on power input/output lines 1x 100k - pull down resistor on the 'enable' contact 1x 2k - limiting resistor from the CPU to the 'enable' line 6x 22 Ohm resistors for the data lines between CPU and SD card slot In theory, it's possible to put a zero-ohm resistor between in and out instead of that switch chip, in that case SD slot will be powered all the time and won't have a current limiter.

Do you have idea with chip S928X-K in device Ugoos SK1 ? if you have Rom please share for me thank you so much

A little typo in the commands: patch -b sun50i-h6-orangepi-3-lts.dtso opi3lts-dtb.patch Should be: patch -b sun50i-h6-orangepi-3-lts.dts opi3lts-dtb.patch it should be .dts and not .dtso, its'n not an overlay. Sorry if that confused anyone.

The base device tree for the Renegade (roc-rk3328-cc) already includes a PWM2 device but armbian does not include the .dtbo to enable it. Thus, it is also unavailable through armbian-config. The Libre builds of Debian support it, but not armbian. I have copied the overlay from the Libre build of Debian for Renegade and it applies correctly on after I manually add it to the overlay directory: /boot/dtb-6.12.32-current-rockchip64/rockchip/overlay/rockchip-rk3328-pwm2.dtbo Note that as of today armbian-config is having a general issue with loading overlays via armbianEnv.txt. This can be bypassed by avoiding using armbian-config for overlays and editing armbianEnv.txt directly and adding the overlay name to the overlays= line minus the "rockchip-" prefix. FWIW - here's the overlay source: =========================== /dts-v1/; / { compatible = "libretech,roc-rk3328-cc\0rockchip,rk3328"; fragment@0 { target = <0xffffffff>; __overlay__ { status = "okay"; }; }; __fixups__ { pwm2 = "/fragment@0:target:0"; }; };

That's completely understandable. Given how long the A10 and A20 have been around, I wouldn't expect recent kernels to be thoroughly tested on them. Even from my perspective HDMI is more of a nice-to-have rather than a priority. I realize I might be an exception in this, but I prefer trying to fix issues myself rather than relying on someone else to do it. The only real barrier is my own lack of knowledge. That said, I believe I’ve firmly gotten to grips with device trees now. I acknowledge that I still have some way to go before I can confidently dig into driver development myself. I really appreciate the effort from you and others in making the build system so easy to use. Thanks to that, I’m able to apply my own fixes where needed with relatively minimal technical knowledge of the intricacies of Linux. I actually noticed the change today while browsing kernel.org. Exactly what I had in mind.

Did you make any progress with this? Also looking to build something with I2S.

Welcome! This question is a bit off topic here as general Armbian updates are not part of HA extension. As this is community supported hardware, stable BSP upgrades - where OS version is stored - might not be generated, while kernel and everything else is getting upgrades. tl;dr; Don't worry about this. For board related topics proceed here https://forum.armbian.com/forum/173-allwinner-sunxi/

Hey if it’s still available I will pay the shipments

@Igor Just tried with the latest image on https://dl.armbian.com/rock-5b-plus/Noble_vendor_gnome. This 100% works as I had tested, so either @armbuilder has a broken flash storage or had an error while writing to the storage medium. Gnome Desktop is working too

Thank you. I also can confirm this issue on Armbian 25.5.1 Bookworm, and that the suggest workaround works. For those interested, here is a more detailed explanation of what @Lars Christian Nygård said. Create a backup of original DTB. sudo cp /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts-orig.dts Decompile the DTB for the Orange Pi 3 LTS. sudo dtc -I dtb -O dts -o /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dtb Modify the decompiled DTS file according with your favorite editor, e.g. nano or vim. sudo nano /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts Navigate to the "spi@5011000" section and modify it. Set "status" to "okay" and add the "spidev@0" section. spi@5011000 { compatible = "allwinner,sun50i-h6-spi\0allwinner,sun8i-h3-spi"; reg = <0x5011000 0x1000>; interrupts = <0x00 0x0b 0x04>; clocks = <0x06 0x53 0x06 0x51>; clock-names = "ahb\0mod"; dmas = <0x2e 0x17 0x2e 0x17>; dma-names = "rx\0tx"; pinctrl-names = "default"; pinctrl-0 = <0x31 0x32>; resets = <0x06 0x20>; status = "okay"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0x78>; spidev@0 { compatible = "armbian,spi-dev"; reg = <0x00>; spi-max-frequency = <0xf4240>; }; }; Save and compile the modified DTS file. sudo dtc -I dts -O dtb /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts -o /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dtb Remove any previously configured overlay for SPI using "armbian-config" or editing the "/boot/armbianEnv.txt" file directly. No further modifications are needed to load our new recompiled DTB, since we directly modified the base DTB. Reboot when done.

Just plugged a M.2 M key to E key adapter with an Intel AX200 iwlwifi (installed the firmware) booted up and Wifi 6 is going without using a USB port. My project is one step closer!!! Just have to get that last USB-C port working.