Active threads

Check here https://github.com/armbian/community/releases/tag/25.5.0-trunk.256 or on a mirror with archive https://docs.armbian.com/Mirrors/#current-mirrors for what you are looking for. We're aware that some links are broken for yet to be determined reason.

I think using the ubuntu keyserver is good as well but that this is a 'small' issue, it is easy to miss a small thing in a project this huge consider the number of boards, kernels, and distributions (including the different releases). if this little thing breaks, we can fix in our installed os using these methods.

moved

this soldering is visionally not very attractive 😛 , but at lest the result is what counts 👍

We don't deal with Android. Better check xda developers forums.

Description As per title How Has This Been Tested? [ ] hasn't Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description This is a draft/wip for adding https proxy caching. This is especially designed for machines hosting lots of github runners to reduce their bandwidth usage by sacrificing disk space. http caching has been merged already and only needed minor changes. Caching https however is way more complicated. Encryption needs to be broken and rewrapped and then obviously downloads will fail due to cert issues. Classic MITM. So a new certificate authority (CA) needs to be put in place to allow these "fake" certs. Why is this even necessary? Well one major part is downloads from upstream apt repositories. The other major part is downloading 3rd party repositories and artifacts from OCI/ORAS/whatever the correct name for that system is. They do not allow plain http downloads but redirect to https. So in order to cache these encryption must be broken on the fly. On custom runs this works already with the mentioned extension. However when the build framework is used within a GH Actions Runner environment it would need to detect this and enable the extension automatically. No clue how to do that or overall if it is worth diving even deeper into this topic. Therefore this RFC to collect feedback. Also lots of fail-safe checks are missing. Sometimes I had to mix run_host_command_logged and chroot_sdcard since pipes don't work using latter. Documentation summary for feature / change Yes, this would need documentation. How Has This Been Tested? [x] custom builds with ENABLE_EXTENSION [ ] Test B Checklist: [no idea] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description as per title How Has This Been Tested? [x] build [ ] nope, no hw on hand right now Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Okay I will try that patch and the build switch that you mentioned. About the RAM: It is SKHynix 966.3MB(989480kB) https://linux-sunxi.org/File:A088_Board_Front_3.jpg I then tried an archived image for the cubieboard and so far no errors and runs quite stable: https://armbian.atomonetworks.com/archive/cubieboard/archive/ Is this a kernel issue then? Maybe I should compile with an older kernel. The stable one is 6.1.63 Thanks a lot for your continued support, Shivam

Hi, Tried this Opi5-Plus with kernel-6.15.2-edge-rockchip64 but mpv doesn't seems to have vpu hardware acceleration Does this repository works on RK3588 - Orange Pi 5 Plus Debian Trixie with mainline kernel 6.15.2-edge-rockchip64?

I think @amazingfate made a custom Chromium package at some point that included optimizations for rk35xx but no clue about its status. Might be even included in mesa-vpu extension? Firefox probably won't work since that would need adjustments as well and I think messing with browsers is a pita already. topics merged as duplicates.

I don't know. I don't have this board nor is the Armbian team aware of its state since it is community supported. This looks like some upstream (Debian to say) uboot package which certainly does not support this board. IIRC u-boot versions for rk3588, depending on family are something like 2017.09 or 2024.01 (both vendor cases) and 2025.01 or .04 for current/edge.

Same problem here, but enabling the audio codec on armbian-config was not sucessfull on this version: v25.5.1 for Orange Pi Zero running Armbian Linux 6.12.30-current-sunxi Any solution?

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

Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines Contribute View the full article

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

Description Fix Raspberry Pi 5 DSI functionality. Context: A display connected to the DSI connector of Raspberry Pi 5 does not work. Dmesg reveals the following information: [ 13.283052] mipi-dsi 1f00118000.dsi.0: deferred probe pending: mipi-dsi: supplier 2.reg_bridge not ready [ 13.283060] platform 1.panel_disp: deferred probe pending: platform: wait for supplier /axi/pcie@120000/rp1/i2c@88000/reg_display@45 The problem could be traced back to a missing I2C Driver. See: https://forum.armbian.com/topic/50963-dsi-display-does-not-work-on-raspberry-pi-5/ Documentation summary for feature / change Add module to kernel configuration: CONFIG_I2C_DESIGNWARE_CORE How Has This Been Tested? Local build of armbian bookworm minimal and test if DSI display works [OK] kernel linux-bcm2711-current [fail] kernel linux-bcm2711-edge [fail] kernel linux-bcm2711-legacy Both edge and legacy images failed to build, but the failure seems unrelated to the change. Checklist: Please delete options that are not relevant. [not applicable] My code follows the style guidelines of this project [OK] I have performed a self-review of my own code [not applicable] I have commented my code, particularly in hard-to-understand areas [OK] My changes generate no new warnings [not applicable] Any dependent changes have been merged and published in downstream modules View the full article

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

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

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