All Activity

does orange pi zero2W support the headsets with built in microphone or not? I do not see any MICINN in the 24 pin connector?

Here are some:https://github.com/armbian/community/releases/

I have the same problem, and for me it seems unrelated to kernel revisions. I have a whole bunch of Orange Pi Zeros, all running the same kernel and all with the same updated packages. However, the ones that run from old SD cards and have been updated from earlier releases, they reboot fine, while those that running from relatively recently flashed SD cards struggle and halt instead of reboot. Since this is super annoying, I wish to find out what's causing this, so I will do some diffing between the systems to see if I can find the culprit.

Hi all, which image should i choose for a LuckFox core3566 ? Thanks

Most likely USB OTG unless there are any USB related errors in the kernel log. In the case of OTG, there should be auto detection via the ID pin which sets the device role but I have never known this to work. Fortunately it is possible to set the mode manually to host in the device tree. I tend to use the following device tree overlay: /dts-v1/; /plugin/; /{ compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20"; fragment@0{ target = <&usb_otg>; __overlay__{ dr_mode = "host"; }; }; }; just connect via serial or ssh, once logged in use nano and paste in the text above. Save it as something like sun4i-usb-host.dts. Then run armbian-add-overlay sun4i-usb-host.dts. This automatically compiles the overlay and places it /boot/dtb/overlay-user/ The RAM may just need fine tuning slightly. As far as I know it is not possible to adjust the RAM frequency in uboot once compiled, only check clock rate via sudo cat /sys/kernel/debug/clk/pll-ddr/clk_rate. I might have to try that on my pcDuino2, I didn't think the A10 would be powerful enough to run Octoprint. All the best Ryzer

Bumps dtschema from 2025.2 to 2025.6.1. Commits 18ac2d8 validator: Fix ordering issue with properties referencing another property 4dbacd6 tests: Add test for DTSchema.check_schema_refs() 2c5f057 schema: Rework instantiating DTSchema.validator 19c88b9 schemas: gpio-nexus-node: Fix schema $ref paths fb770c7 schema: Fix a false positive unevaluatedProperties/additionalProperties check b7f612c schemas: reset: Add '#reset-cells' into schema 7e3ef3e schemas: reset: Add descriptions from original text binding 53a2132 meta-schemas: nodes: Allow if-then-else directly in patternProperties objects 9d1305d schemas: PCI: Add standard PCIe WAKE# signal 49451a5 schemas: root-node: Add 'all-in-one' chassis-type Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Bumps oras from 0.2.33 to 0.2.37. Release notes Sourced from oras's releases. Oras Python v0.2.37 What's Changed Use correct credsStore/credHelpers binary by @rasmusfaber in oras-project/oras-py#212 Full Changelog: https://github.com/oras-project/oras-py/compare/0.2.36...0.2.37 Oras Python v0.2.36 What's Changed Fix authentication priority: AWS-native -> docker login -> credHelpers -> credsStore by @rasmusfaber in oras-project/oras-py#211 Full Changelog: https://github.com/oras-project/oras-py/compare/0.2.35...0.2.36 Oras Python v0.2.35 What's Changed fix: auth via ECR to be an extra by @tarilabs in oras-project/oras-py#208 Full Changelog: https://github.com/oras-project/oras-py/compare/0.2.34...0.2.35 Oras Python v0.2.34 What's Changed [tributors] contributors/update-2025-05-31 by @github-actions in oras-project/oras-py#203 Add support for Docker credsStore and credHelpers by @rasmusfaber in oras-project/oras-py#206 [tributors] contributors/update-2025-06-08 by @github-actions in oras-project/oras-py#207 Ecr auth support by @rasmusfaber in oras-project/oras-py#205 New Contributors @rasmusfaber made their first contribution in oras-project/oras-py#206 Full Changelog: https://github.com/oras-project/oras-py/compare/0.2.33...0.2.34 Changelog Sourced from oras's changelog. CHANGELOG This is a manually generated log to track changes to the repository for each release. Each section should include general headers such as Implemented enhancements and Merged pull requests. Critical items to know are: renamed commands deprecated / removed commands changed defaults backward incompatible changes (recipe file format? image file format?) migration guidance (how to convert images?) changed behaviour (recipe sections work differently) The versions coincide with releases on pip. Only major versions will be released as tags on Github. 0.0.x (0.0.x) Use the correct credsStore/credHelpers binary (0.2.37) Properly prioritize auth methods (0.2.36) fix 'authentication with ECR' to be an extra as intended (0.2.35) Add support for authentication with ECR registries (0.2.34) Add support for Docker credsStore and credHelpers fix 'get_manifest()' method with adding 'load_configs()' calling (0.2.33) fix 'Provider' method signature to allow custom CA-Bundles (0.2.32) initialize headers variable in do_request (0.2.31) Make reproducible targz without mimetype (0.2.30) don't include Content-Length header in upload_manifest (0.2.29) propagate the tls_verify parameter to auth backends (0.2.28) don't add an Authorization header is there is no token (0.2.27), closes issue 182 check for blob existence before uploading (0.2.26) fix get_tags for ECR when limit is None, closes issue 173 fix empty token for anon tokens to work, closes issue 167 retry on 500 (0.2.25) align provider config_path type annotations (0.2.24) add missing prefix property to auth backend (0.2.23) allow for filepaths to include : (0.2.22) release request (0.2.21) add missing basic auth data for request token function in token auth backend (0.2.2) re-enable chunked upload (0.2.1) refactor of auth to be provided by backend modules (0.2.0) bugfix maintain requests's verify valorization for all invocations, augment basic auth header to existing headers Allow generating a Subject from a pre-existing Manifest (0.1.30) add option to not refresh headers during the pushing flow, useful for push with basic auth (0.1.29) enable additionalProperties in schema validation (0.1.28) Introduce the option to not refresh headers when fetching manifests when pulling artifacts (0.1.27) To make it available for more OCI registries, the value of config used when manifest_config is not specified in client.push() has been changed from a pure empty string to {} (0.1.26) refactor tests using fixtures and rework pre-commit configuration (0.1.25) eliminate the additional subdirectory creation while pulling an image to a custom output directory (0.1.24) updating the exclude string in the pyproject.toml file to match the data type black expects patch fix for pulling artifacts by digest (0.1.23) patch fix to reject cookies as this could trigger registries into handling the lib as a web client ... (truncated) Commits 5d3c15d Use correct credsStore/credHelpers binary (#212) 385f138 Fix authentication priority: AWS-native -> docker login -> credHelpers -> cre... d296ffd fix: auth via ECR to be an extra (#208) 1d448f2 Ecr auth support (#205) dad7734 Automated deployment to update contributors 2025-06-08 (#207) 2a421e2 Add support for Docker credsStore and credHelpers (#206) b63ede0 Merge pull request #203 from oras-project/contributors/update-2025-05-31 6886229 Automated deployment to update contributors 2025-05-31 See full diff in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Bumps tj-actions/changed-files from 4140eb99d2cced9bfd78375c2088371853262f79 to d52d20fa3f981cb852b861fd8f55308b5fe29637. Changelog Sourced from tj-actions/changed-files's changelog. Changelog 46.0.5 - (2025-04-09) ⚙️ Miscellaneous Tasks deps: Bump yaml from 2.7.0 to 2.7.1 (#2520) (ed68ef8) - (dependabot[bot]) deps-dev: Bump typescript from 5.8.2 to 5.8.3 (#2516) (a7bc14b) - (dependabot[bot]) deps-dev: Bump @types/node from 22.13.11 to 22.14.0 (#2517) (3d751f6) - (dependabot[bot]) deps-dev: Bump eslint-plugin-prettier from 5.2.3 to 5.2.6 (#2519) (e2fda4e) - (dependabot[bot]) deps-dev: Bump ts-jest from 29.2.6 to 29.3.1 (#2518) (0bed1b1) - (dependabot[bot]) deps: Bump github/codeql-action from 3.28.12 to 3.28.15 (#2530) (6802458) - (dependabot[bot]) deps: Bump tj-actions/branch-names from 8.0.1 to 8.1.0 (#2521) (cf2e39e) - (dependabot[bot]) deps: Bump tj-actions/verify-changed-files from 20.0.1 to 20.0.4 (#2523) (6abeaa5) - (dependabot[bot]) ⬆️ Upgrades Upgraded to v46.0.4 (#2511) Co-authored-by: github-actions[bot] (6f67ee9) - (github-actions[bot]) 46.0.4 - (2025-04-03) 🐛 Bug Fixes Bug modified_keys and changed_key outputs not set when no changes detected (#2509) (6cb76d0) - (Tonye Jack) 📚 Documentation Update readme (#2508) (b74df86) - (Tonye Jack) ⬆️ Upgrades Upgraded to v46.0.3 (#2506) Co-authored-by: github-actions[bot] Co-authored-by: Tonye Jack jtonye@ymail.com (27ae6b3) - (github-actions[bot]) 46.0.3 - (2025-03-23) 🔄 Update Updated README.md (#2501) Co-authored-by: github-actions[bot] (41e0de5) - (github-actions[bot]) Updated README.md (#2499) Co-authored-by: github-actions[bot] (9457878) - (github-actions[bot]) 📚 Documentation ... (truncated) Commits d52d20f chore(deps-dev): bump @types/node from 22.15.26 to 24.0.1 (#2587) f1c0eb9 chore(deps-dev): bump eslint-plugin-prettier from 5.4.0 to 5.4.1 (#2578) 944a0f7 chore(deps-dev): bump eslint-plugin-jest from 28.13.0 to 28.13.3 (#2585) 3dbc1e1 Updated README.md (#2592) 7a7221b chore(deps): bump github/codeql-action from 3.28.18 to 3.29.0 (#2588) c260d49 feat: add any_added to outputs (#2567) b1ccff8 Updated README.md (#2591) a892f50 docs: update link to glob patterns (#2590) 5ca5422 chore(deps-dev): bump ts-jest from 29.3.4 to 29.4.0 (#2589) See full diff in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

If you are on a relatively recent kernel, the kernel probably already has support, but the default DTB has it disabled. This is from a bookworm nightly build for a radxa zero 3 ~$ grep rknpu /usr/lib/modules/6.1.115-vendor-rk35xx/modules.builtin kernel/drivers/rknpu/rknpu.ko However, it's disabled in the DTB by default $ cat /sys/firmware/devicetree/base/npu@fde40000/status disabled For the board that I am using, the vendor publises a DTO source that enables it at https://github.com/radxa-pkg/radxa-overlays/blob/main/arch/arm64/boot/dts/rockchip/overlays/rk3568-npu-enable.dts Which works well with armbian-add-overlay. Though you may need to make a similar overlay for your DTB if it is different enough. Note that the NPU in the 3566 and 3568 are interoperable.

Here some troubles are expected ... Can you try manual steps to install docker by follow: https://github.com/armbian/configng/blob/main/tools/modules/software/module_docker.sh#L26-L56 installing packages, adding to group, adding docker bridge. This might reveal more. BTW. My F3 died - waiting for replacement.

Ok, I was able to boot on maskrom mode! I had to cut the bottom shield (it is soldered, but I'm not using lora anymore so I didn't care). Just cut the shield right beneath the eMMC chip, and you'll uncover some pads. Short-circuit the middle big one (clk) in the attached photo with any gnd point, and plug the thing. That made the magic for me.

I am glad you could do it with the orange pi zero 2w, because I also want to use a very small arm board I am having trouble with the red ili9488 red LCD's touch function, and if I keep having no results, I will replace with the waveshare LCD model (I wanted to have 4-inch LCD ) What armbian and linux version did you use? If you go to the latest linux, you may need to modify the DTS a little bit (modifications are in my ili9488 thread). Warning: I use a different driver (parameter "compatible") for DRM graphics, and different drivers might need different DTS lines. Always use a different microSD for experiments, so you don't mess with your working setup Does the orange pi zero 2w just need male pin headers on the 40-pin connector, and then plug the LCD on top?

Thank you so much for sharing me the thread, i finally make the screen true color follow dts of user wdr_s Here is my dts file The thing i change compare with dts in https://github.com/dev-null2019/orangepizero2w35tft : 1. spi-max-frequency from 48000000 to 16000000 (I think it due to speed of spi on the board) 2. And in init, i change both value of 0x1000036 0x48 I test on Debian Bookworm, Armbian it work ok Note that, with this device tree, i got reversed touch screen (up to down work ok, but left to right is reversed) so i need to change the calib matrix Here is the content of /usr/share/X11/xorg.conf.d/80-calibration.conf Once again, Thank you very much. I stuck in this problem 3 days, and try so many device tree, and try full supported os from orange pi but it not work, until follow your thread.

Hello, first of all, I’d like to thank everyone for the post and your contributions! My problem is simple: I have an H96 Mini 4K Ultra HD, with CPU RK3228A, OS: Android 9.0, RAM: 2.0 GB, and ROM: 16 GB. I installed the ArmBian system on it; but then I decided to reinstall the original ROM. However, during the step sudo rkdeveloptool db rk322x_loader_v1.10.238_256.bin, I mistakenly flashed the original system image instead. Now, the device shows no sign of life — it's not recognized by either Linux or Windows. What should I do?

I tried to install docker via armbian-config --CON02 on Trixie but I got quite a lot of errors during the installation. Here is the board information if it ever can help: https://paste.armbian.com/xozimixeqi . Thanks.

Description There is a drawback to configuring audio routing using asound.state. Although you can specify the device of the axg-sound card via commands to output sound to either HDMI or the internal speaker, in a desktop environment, there is only one analog output (defaulting to HDMI). This is because the device actually has only one sound card. By using ALSA UCM to manage sound instances and audio routing, you can freely choose between HDMI or the built-in speaker output in a desktop environment. This is because PipeWire/WirePlumber will parse ALSA UCM and create sinks. How Has This Been Tested? build image boot form usb drive test sound in CLI and DE Checklist: [x] 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 View the full article

Hello everyone, I'm working on repurposing an MX9 5G TV Box (RK3229) for educational use and I'm looking for a lightweight Armbian image that already includes a working desktop environment (XFCE or similar) with GPU acceleration enabled (Mali drivers, no llvmpipe). I’ve tried minimal builds and installed XFCE manually, but I’m still getting software rendering (llvmpipe) instead of hardware acceleration. I'd really appreciate it if anyone could recommend a tested image (preferably based on Bookworm or Bullseye) that: Boots successfully on the MX9 5G (RK3229) Has Mali GPU acceleration enabled by default Includes or supports installing a lightweight DE (XFCE preferred) Bonus if it includes support for video playback or has a browser that runs decently. Thanks in advance for any suggestions or links!

it seemed that the (minimal/iot) images linked on the boards page , have been updated, I just downloaded Armbian_community_25.8.0-trunk.228_Orangepizero3_bookworm_current_6.12.30_minimal.img.xz for orangepi zero 3. note I only checked debian as that is what i'm using https://www.armbian.com/orange-pi-zero-3/

it seemed that the (minimal/iot) images linked on the boards page , have been updated, I just downloaded Armbian_community_25.8.0-trunk.228_Orangepizero3_bookworm_current_6.12.30_minimal.img.xz for orangepi zero 3. note I only checked debian as that is what i'm using it seemed to be similar for orangepi zero 2 https://www.armbian.com/orange-pi-zero-2/

Description Add initial support for board Luckfox Nova W. Luckfox Nova W is recently produced board on SoC Rockchip RK3308B: 4 x Cortex-A35 CPU, 512 RAM, 8 GB eMMC. It also has Ethernet, WIFI & BT, USB-A and USB-C ports, soldered microphone. Product page: https://www.luckfox.com/Luckfox-Nova?ci=646 But beware: it is very fresh board, has almost no documentation and only buildroot SDK with kernel 5.10 is available from vendor. Documentation I decided to create separate directory for vendor kernel patches. This kernel must be the same as rk35xx-vendor-6.1, but this SoC is not RK35XX. Used U-Boot is mainline. Instead of DKMS AIC8800 driver I enabled the one from kernel sources, because I needed to apply patches to it. And image builds faster than with DKMS. UART4 is used for serial console and by proprietary firmware blobs. How Has This Been Tested? [ ] eMMC does not work in mainline kernel, current and edge [x] Boot Noble 24.04 with vendor kernel rk6.1 [x] USB host and peripheral is working [x] WIFI is working [x] SPI May have quirks, though spidev-test appears to be working [ ] SPI1-M1 MISO is not receiving data [x] SPI2 is working Checklist: Please delete options that are not relevant. [x] 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

Hi I have upgraded an existing x86 Armbian system with kernel 6.6.63 and zfs 2.3.2 to the suggested kernel 6.12.32-current-x86, but I cannot get the zfs kernel module loaded after the latest updates to Armbian 25.5.1 noble. I also tried on other kernels, only the old 6.6.63 seems to work. Normally when you select a different kernel in the armbian-config menu, it should automatically compile the zfs modules if it is activated. It just skips it. But you can of course compile it with the provided DKMS system: the build just finishes fine, without any error, also the install, but when you try to load the module: it responds with: dmesg: I have zfs 2.3.2 on kernel 6.12.32-current-bcm2711 running just fine on a Raspberry Pi 4, so I tested what would happen if I just build a small kernel driver module: root@armbian:/usr/src/dummydriver# cat dummydriver.c root@armbian:/usr/src/dummydriver# cat Makefile So when I run this on the Raspberry Pi 4, I can load the module and unload But when I run this on the x86 machine I get the same error: root@armbian:/usr/src/dummydriver# modinfo dummydriver.ko root@armbian:/usr/src/dummydriver# gcc --version I also tried gcc 11.4.0 Here is my armbianmonitor -u: https://paste.armbian.com/orepumazam Any help welcome! Philippe

i answered in your thread.

https://forum.armbian.com/topic/46824-orange-pi-zero-3-ili9486-tft-lcd/ user wdr_s had success with that same lcd. Try it with linux 6.1 (check the success case) If you have a file named orangeEnv.txt... you arent using armbian yet! Make sure to use armbian-add-overlay In the ili9341 or ili9488 there's someone trying with orange pi zero 2w, which is very close to zero 3

About wrong color i think the driver cause it. Driver for render image in this kernel sunxi is ili9486drmtft. I get right color in raspberry pi 4 but raspberry pi 4 use fb_ili9486. On this orangepi zero 2 w, i try 3 different OS but still get same wrong color after adding dts for ili9486 1. Orangepi OS Kernel 6.1 2. Armbian OS Kernel 6.1 3. Debian Bookworm 12 Kernel 6.1 All using ili9486drmtft and get wrong color I also try to change bgr value in dts, but it only create change in .../spi@1.0.../bgr not the color on screen I try to get source code https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-6.1-sun50iw9 to change the bgr field in driver, but i can't insmod the module i build. It say invalid symbol I see someone comment that after kenel 5.4 in repo sunxi remove fbtft_device, so we can't add the fb_ili9486 . The Offical OS supported by Orangepi has Kernel 5.4 Debian, i use it, but after add overlays and reboot, it seem wrong setup, ethernet not working, and i don't know why.

Hello @robertoj I think i have the same problem with @RimYT above about wrong color with ili9486, i'm using screen MPI3501 which is clone screen of waveshare tft35 I apply the same device tree and guide in https://github.com/dev-null2019/orangepizero2w35tft. The screen work but i wrong color, it seem revered Red. —> blue Green —> red Blue. —> green I also write detail in here I know my problem not totally related to your topic, but can you suggest me what i should to check more