Search the Community

Hi everyone, I'm struggling to get gpio_keys working. I'm trying to use the overlay, which I have attached below, but after reboot there is no event node listed in "/dev/input/". (There is only one node named mice.) Inspecting dmesg, I found the following error messages: [ 1.529891] sun50i-h616-pinctrl 300b000.pinctrl: pin PC8 already requested by gpio-keys-user; cannot claim for 300b000.pinctrl:72 [ 1.529917] gpio-keys gpio-keys-user: failed to get gpio: -22 [ 1.529926] gpio-keys: probe of gpio-keys-user failed with error -22 Inspecting the dts file of my board (orange pi zero 2), I found that PC5,PC6 and PC8 are already listed as mmc2-pins, but mmc2 is disabled, so I don't think that this is the issue. However, I have no idea what else might be wrong. Any help? Attachements: custom-keys.dts Overlay: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&pio>; __overlay__ { custom-buttons: custom-buttons { pins = "PC5","PC6","PC8"; function = "gpio_in"; bias-pull-up; }; }; }; fragment@1 { target-path = "/"; __overlay__ { gpio-keys-user { compatible = "gpio-keys"; pinctrl-names = "default"; pinctrl-0 = <&custom-buttons>; play_button { label = "GPIO Key 1"; linux,code = <25>; gpios = <&pio 0 69 1>; }; vol_up_button { label = "GPIO Key 2"; linux,code = <22>; gpios = <&pio 0 70 1>; }; vol_down_button { label = "GPIO Key 3"; linux,code = <32>; gpios = <&pio 0 72 1>; }; }; }; }; };

Hey folks, I have a really weird issue where any time I try to `cat` any of the cpufreq files or use any of the cpufreq commands, it just hangs indefinitely. I've made sure that everything is up to date, reinstalled cpufreq, and because I have 2 of the same board, have confirmed that it's an issue with both of my Zero 2s. I also ran `strace` on one of the cpufreq commands and found that it's getting hung on a write step: openat(AT_FDCWD, "/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor", O_WRONLY) = 3 write(3, "ondemand", 8 Other than this, the device has been doing just fine. Any advice on this is welcome! OrangePi Zero2 Armbian (24.11.1) aarch64 6.6.62-current-sunxi64 (also attempted on the latest edge version of the kernel)

In short, I'm trying to build a FULLY-PREEMPT-REALTIME system to run on my Orange Pi Zero 2W. I used this post as a reference, and got quite far. But, I'm stuck on something that I believe I undestand, but don't know how to resolve. I don't believe this is a probleme specific to my board though. What I've done so far with success is both install and run a pre-built Armbian Image on this board, as well as build my own image and run it. Both work perfectly. Now, I'm attempting to apply the RT patch and build a fresh image (or even just a Kernel) to get the FULL REALTIME kernel support working. However, the build system fails after the kernel is built sucesfully, as it is unable to find the resulting kernel image generated. I belive the issue is simply that when the RT .patch is applied and configured to the kernel, it builds a kernel file with an alterered filename. Instead of 6.6.65-current-sunxi64 It creates 6.6.65-rt47-current-sunxi64 As a result, the build process for the kernel stage fails as it's unable to find the file it is expecting to find. Here is what I have done, and what outputs I am finding. As stated, It was a success with A locally built clean Armbian ./compile.sh BOARD=orangepizero2w BRANCH=current RELEASE=bookworm BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=no AUFS=no KERNELBRANCH='tag:v6.6.65' System booted up and ran as normal. $ uname -a inux orangepizero2w 6.6.65-current-sunxi64 #2 SMP Wed Dec 11 15:13:43 UTC 2024 aarch64 GNU/Linux I then attempted to apply the PREEMPT_RT kernel patch. download and gunzip https://cdn.kernel.org/pub/linux/kernel/projects/rt/6.6/patch-6.6.65-rt47.patch.gz into the directory userpatches/kernel/archive/sunxi-6.6 Then a kernel-configure step Worth noting that I do see this patch file applied in the output of the following command. ./compile.sh BOARD=orangepizero2w BRANCH=current RELEASE=bookworm KERNELBRANCH='tag:v6.6.65' kernel-config Where I proceeded to enable the full REALTIME kernel (4th option). General setup -> Preemption Mode -> Fully Preemptible Kernel (Real-Time) Finally followed with a compile command. ./compile.sh BOARD=orangepizero2w BRANCH=current RELEASE=bookworm BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=no AUFS=no KERNELBRANCH='tag:v6.6.65' The part of the build output that I beleive is relevant is this. It shows the failure, and what I believe is an indication of why it fails. It appears that the build script it is not aware of needing to find the file name that has the rt47 portion. 🐳|🔨] INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h616-i2c1-pi.dtbo [🐳|🔨] INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h616-i2c2-pi.dtbo [🐳|🔨] INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h616-gpu.dtbo [🐳|🔨] INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-a64-fixup.scr [🐳|🔨] INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h5-fixup.scr [🐳|🔨] INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h6-fixup.scr [🐳|🔨] INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h616-fixup.scr [🐳|🔨] INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/README.sun50i-a64-overlays [🐳|🔨] INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/README.sun50i-h5-overlays [🐳|🔨] make[1]: Nothing to be done for 'install'. [🐳|🔨] make: Nothing to be done for 'install'. [🐳|🌱] Kernel built in [ 95 seconds - 6.6.65-sunxi64 ] [🐳|🌱] Packaging kernel [ sunxi64 linux-sunxi64-current ] [🐳|🌱] Kernel .deb package version [ 6.6.65-S943e-Dfa7d-P3e46-Caa1fH5c21-HK01ba-Vc222-B59f0-R448a ] [🐳|🌱] Packaging linux-image [ sunxi64 linux-sunxi64-current ] [🐳|🔨] [ 26M] /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/image/boot [🐳|🔨] ├── [215K] config-6.6.65-rt47-current-sunxi64 [🐳|🔨] ├── [3.4M] System.map-6.6.65-rt47-current-sunxi64 [🐳|🔨] └── [ 22M] vmlinuz-6.6.65-rt47-current-sunxi64 [🐳|🔨] [🐳|🔨] 26M used in 0 directories, 3 files [🐳|🌱] Kernel-built image filetype [ vmlinuz-6.6.65-current-sunxi64: cannot open `/armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/image/boot/vmlinuz-6.6.65-current-sunxi64' (No such file or directory) ] [🐳|🔨] ls: cannot access '/armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/image/boot/vmlinuz-6.6.65-current-sunxi64': No such file or directory [🐳|🔨] /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/image/boot: [🐳|🔨] total 26220 [🐳|🔨] drwxrwxr-x 2 root root 100 Dec 30 17:08 . [🐳|🔨] drwxrwxr-x 3 root root 60 Dec 30 17:07 .. [🐳|🔨] -rw-rw-r-- 1 root root 220621 Dec 30 17:08 config-6.6.65-rt47-current-sunxi64 [🐳|🔨] -rw-rw-r-- 1 root root 3564498 Dec 30 17:08 System.map-6.6.65-rt47-current-sunxi64 [🐳|🔨] -rw-rw-r-- 1 root root 23056392 Dec 30 17:08 vmlinuz-6.6.65-rt47-current-sunxi64 [🐳|💥] Error 2 occurred in main shell [ at /armbian/lib/functions/logging/runners.sh:211 run_host_command_logged_raw() --> lib/functions/logging/runners.sh:211 run_host_command_logged() --> lib/functions/logging/runners.sh:193 kernel_package_callback_linux_image() --> lib/functions/compilation/kernel-debs.sh:221 create_kernel_deb() --> lib/functions/compilation/kernel-debs.sh:131 prepare_kernel_packaging_debs() --> lib/functions/compilation/kernel-debs.sh:72 kernel_package() --> lib/functions/compilation/kernel.sh:248 do_with_hooks() --> lib/functions/general/extensions.sh:567 do_with_logging() --> lib/functions/logging/section-logging.sh:81 kernel_prepare_build_and_package() --> lib/functions/compilation/kernel.sh:171 compile_kernel() --> lib/functions/compilation/kernel.sh:100 artifact_kernel_build_from_sources() --> lib/functions/artifacts/artifact-kernel.sh:240 artifact_build_from_sources() --> lib/functions/artifacts/artifacts-obtain.sh:34 obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:280 build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:392 main_default_build_packages() --> lib/functions/main/build-packages.sh:106 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:31 do_with_default_build() --> lib/functions/main/default-build.sh:42 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> compile.sh:50 ] [🐳|💥] Cleaning up [ please wait for cleanups to finish ] [🐳|🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0.log.ans ] [🐳|🌿] Share log manually (or SHARE_LOG=yes): [ curl --data-binary @output/logs/log-build-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0.log.ans https://paste.armbian.com/log ] [💥] -------------Docker run failed after 152s-------------------------- [ 🐳 failed ] [🌱] Cleaning up [ please wait for cleanups to finish ] ~/devel/personal/Armbian/build │ main !1 Thanks for any help with this. I hope I've provided enough information to make sense of what I'm attempting to do.

This is my DTS file for OrangePi Zero2, opened UART5 for attach a GPS module on GPIO. Tried to add 1wire, PPS and SPI , but can't work. maybe help someone. sun50i-h616-orangepi-zero2.dts

First off, I would like to give the crew at Armbian a huge heartfelt thanks for all the awesome work you do under sometimes trying conditions. I would like to present Archian, the bastard child of Armbian & Arch. Why … well, the project I am working on needed current versions of phosh & plasma-mobile and the versions on jammy/bookworm were quite old. The OPi supplied image was quite flaky so I had to find a way to mash these together. And this is the result. It does need to be run as root ! The script has 3 arguments: init - downloads the armbian image file, arch rootfs and arch packages. You need to then write the image to an SD-CARD install - this installs arch over the armbian image on the SD-Card finish - run this option on a booted image as root It has limited/no error checking so run this at your own risk. A wise/cautious person would run the install commands manually as it could really mess up your host system if it goes badly. It could be easily modified to work with different boards but OPi Zero 2W is what I have. Don't forget to edit the script before running it so that ‘things’ point to where you want them. The root password is root. You will need an external screen & keyboard to use it as networking wont work until it is fully installed. Have a play and let me know any issues. archian.sh

Everything come from a try to create a docker compose project. Armbian 24.8.4 bookworm on OrangePI zero 2 - Network forwarding doesn't work: ``` version: '3.6' services: db: image: mariadb:10.3 environment: MYSQL_ROOT_PASSWORD: secret phpmyadmin: image: phpmyadmin restart: always ports: - 8080:80 environment: - PMA_HOSTS=db ``` => FROM test-db-1 => test-db-1 3306 ``` docker exec -ti test-db-1 bash -c 'timeout 0.5 echo -n 2>/dev/null < /dev/tcp/test-db-1/3306 && echo "open" || echo "closed"' ----------- open ----------- ``` => FROM test-phpmyadmin-1 => test-db-1 3306 ``` docker exec -ti test-phpmyadmin-1 bash -c 'timeout 0.5 echo -n 2>/dev/null < /dev/tcp/test-db-1/3306 && echo "open" || echo "closed"' ----------- closed ----------- ``` lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Armbian 24.8.4 bookworm Release: 12 Codename: bookworm uname -a Linux xxxxxx-pre 6.6.44-current-sunxi64 #1 SMP Sat Aug 3 06:54:42 UTC 2024 aarch64 GNU/Linux ``` OrangePI Zero v2 Network forwarding doesn't work ### How to reproduce? ``` ip -4 addr show scope global 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 inet 192.168.1.135/24 metric 100 brd 192.168.1.255 scope global dynamic end0 valid_lft 587718sec preferred_lft 587718sec cat /proc/sys/net/ipv4/ip_forward 1 iptables -A PREROUTING -t nat -i lo -p udp --dport 2222 -j DNAT --to 127.0.0.1:22 iptables -A PREROUTING -t nat -i lo -p tcp --dport 2222 -j DNAT --to 127.0.0.1:22 iptables -A FORWARD -p tcp -d 127.0.0.1 --dport 2222 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT iptables -A FORWARD -m limit --limit 3/minute --limit-burst 3 -j LOG --log-prefix "IPT FORWARD packet" iptables -A POSTROUTING -t nat -j MASQUERADE -o lo iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -A INPUT -j ACCEPT iptables -A OUTPUT -j ACCEPT iptables -A FORWARD -j ACCEPT ``` ssh -l root -p 22 localhost => OK ssh -l root -p 2222 localhost => KO ``` iptables -A INPUT -j ACCEPT iptables -A OUTPUT -j ACCEPT iptables -A FORWARD -j ACCEPT iptables -A PREROUTING -t nat -i end0 -p udp --dport 2222 -j DNAT --to 192.168.1.135:22 iptables -A PREROUTING -t nat -i end0 -p tcp --dport 2222 -j DNAT --to 192.168.1.135:22 iptables -A FORWARD -p tcp -d 192.168.1.135 --dport 2222 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT iptables -A FORWARD -m limit --limit 3/minute --limit-burst 3 -j LOG --log-prefix "IPT FORWARD packet" iptables -A POSTROUTING -t nat -j MASQUERADE -o end0 iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT ``` ssh -l root -p 22 192.168.1.135 => OK ssh -l root -p 2222 192.168.1.135 => KO ### Branch main (main development branch) ### On which host OS are you running the build script and observing this problem? Ubuntu 24.04 Noble ### Are you building on Windows WSL2? - [ ] Yes, my Ubuntu/Debian/OtherOS is running on WSL2 ### Relevant log URL _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct

Hello, Hopefully a maintainer is reading- is there a plan to build/release 24.8 for Orange Pi Zero 2? Thanks!

I've tinkering with this board, and trying to boot from spl, but the boot halts after reading the temperature sensors, which does not happen when booting from the sd card. After booting from the sd card I read the sensor that causes the problem # cat /sys/devices/virtual/thermal/thermal_zone0/temp 51740 I found in a forum some kernel patches to mitigate this: https://forum.manjaro.org/t/support-for-orangepi-zero2-h616-ddr3-zero3-and-zero-2w-h618-lpddr4/154679 Why does it fail when booting from spl, and not when booting from the sd? Here is the system info: # cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=orangepizero2 BOARD_NAME="Orange Pi Zero2" BOARDFAMILY=sun50iw9 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=89476e86f LINUXFAMILY=sunxi64 ARCH=arm64 BOOT_SOC= IMAGE_TYPE=stable BOARD_TYPE=wip INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image KERNEL_TARGET=current,edge KERNEL_TEST_TARGET=current FORCE_BOOTSCRIPT_UPDATE=yes FORCE_UBOOT_UPDATE= OVERLAYDIR="/boot/dtb/allwinner/overlay" VENDOR="Armbian" VENDORDOCS="https://docs.armbian.com" VENDORURL="https://www.armbian.com/" VENDORSUPPORT="https://forum.armbian.com" EDIT: I am booting the same install in both cases from the sd card, but from the spl I do it manually since I have to take the sd card out to get into the spl VENDORBUGS="https://www.armbian.com/bugs" BOOTSCRIPT_FORCE_UPDATE="yes" BOOTSCRIPT_DST="boot.cmd" VERSION=24.8.4 REVISION=24.8.4 BRANCH=current # uname -r 6.6.36-current-sunxi64

Hi, I have managed to install u-boot on the spl flash, and it properly runs and detects everything, but i've run into a bit of an issue, while loading the kernel, it gets stuck. To create the usb drive I just cloned the partition of the sd card (not the whole card, just the ext4 partition), I don't know if that can be the issue. here is the full log: https://pastebin.com/jPEkMnYq Any ideas?

I'm using image Armbian_23.8.3_Orangepizero2_bookworm_current_6.1.53 I'm building a DTS overlay for a SPI Touchscreen and every pin I try to use is showing this error: [ 1.441808] sun50i-h616-pinctrl 300b000.pinctrl: pin PC11 already requested by 5011000.spi; cannot claim for 300b000.pinctrl:75 [ 1.441817] sun50i-h616-pinctrl 300b000.pinctrl: pin-75 (300b000.pinctrl:75) status -22 [ 1.441829] sun6i-spi 5011000.spi: cannot register SPI master I'm trying to configure my touchscreen dts to use the SPI1.0 & SPI1.1. However, the pins exposed on the headers are all allocated for device use under 300b000.pinctrl. How do you allocate header pins for another use? I need 5 pins + SPI1 for the touchscreen to work. My dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { spi1_cs1: spi1_cs1 { pins = "PC11"; function = "gpio_out"; output-high; }; opiz_display_pins: opiz_display_pins { pins = "PC9", "PC6", "PC5"; function = "gpio_out"; }; ads7846_pins: ads7846_pins { pins = "PH6"; function = "irq"; }; }; }; fragment@1 { target = <&spi1>; __overlay__ { #address-cells = <1>; #size-cells = <0>; status = "okay"; pinctrl-1 = <&spi1_cs1>; pinctrl-names = "default", "default"; cs-gpios= <0>, <&pio 2 11 0>; /* PH9 PC11 */ opizdisplay: opiz-display@0 { reg = <0>; /* Chip Select 0 */ compatible = "ilitek,ili9341"; spi-max-frequency = <16000000>; status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&opiz_display_pins>; rotate = <90>; bgr = <0>; fps = <10>; buswidth = <8>; dc-gpios = <&pio 2 6 0>; /* PC6 */ reset-gpios = <&pio 2 9 1 >; /* PC9 */ led-gpios=<&pio 2 5 0>; /* PC5 */ debug=<0>; }; ads7846: ads7846@1 { reg = <1>; /* Chip Select 1 */ compatible = "ti,ads7846"; spi-max-frequency = <500000>; status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&ads7846_pins>; interrupt-parent = <&pio>; interrupts = <7 6 2>; /* PH6 IRQ_TYPE_EDGE_FALLING */ pendown-gpio = <&pio 7 6 0>; /* PH6 */ /* driver defaults, optional */ ti,x-min = /bits/ 16 <0>; ti,y-min = /bits/ 16 <0>; ti,x-max = /bits/ 16 <0x0FFF>; ti,y-max = /bits/ 16 <0x0FFF>; ti,pressure-min = /bits/ 16 <0>; ti,pressure-max = /bits/ 16 <0xFFFF>; ti,x-plate-ohms = /bits/ 16 <400>; }; }; }; };

I built an image for the `orangepi-z-2w` via `./compile.sh build BOARD=orangepizero2w BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm`. The wifi connects (shows as active), however, I am unable to get on the internet (pinging results in `network is unreachable`, also can't ping the device itself). Am I building wrong? Thanks! Some notes: - I've been using `Armbian_24.2.6_Orangepizero2w_bookworm_current_6.6.28.img.xz` in the past (downloaded from armbian.com), and the wifi works just fine.

Hi, I really apologise if the information is out there and I just haven't found it. I was looking to buy a board for a small embedded GUI application and this one seems to fit the bill. I would like to use Wi-Fi, Bluetooth and HDMI. Is there a list of what is working or not working on each build/version? (This is probably a more general question to Armbian for any device) The only thing I could find is this: But it's not that recent. On the download page: https://www.armbian.com/orange-pi-zero-2/ under specifications it does list, Bluetooth and Wi-Fi but I'm not sure if this means its now working? I also saw some forum posts talk about old builds, where can they be found, all I can see is this (linked on the download page): https://fi.mirror.armbian.de/archive/orangepizero2/archive/ and it only has 1 version. One last question, if Wi-Fi or Bluetooth don't work, does that only mean onboard Wi-Fi and Bluetooth and that a dongle would work? Thanks!

@ag123, @c0rnelius, and anyone else that has interest in sound on these devices. I have been able to put together a patch that enables audio for H161/H618 devices. So far only audio on HDMI works. Analog audio is still generating an error on startup. The patches were taken from a git repository by warpme: https://github.com/warpme/minimyth2/tree/master/script/kernel/linux-6.6/files , and probably came from the Zunlong SDK. A lot of the code was written by Allwinner. @pixdrift generated a version of the patches for Armbian and I continued to work on them. I have a git repository if anyone would like to test, particularly on boards other than orangpizero3, on which I have tested. repository: https://github.com/stephengraf/armbian_build_sg.git There is another repository mentioned in the Armbian Forum: https://github.com/NickAlilovic/build If anyone has interest and skills to debug the analog audio, the dmesg errors are: [ 7.125509] ahub_dam-snd-soc-dummy-dai: substream ahub_dam-snd-soc-dummy-dai has no playback, no capture [ 7.125539] sunxi-snd-mach soc:ahub_dam_mach: ASoC: can't create pcm ahub_dam-snd-soc-dummy-dai :-22 [ 7.125780] sunxi-snd-mach: probe of soc:ahub_dam_mach failed with error -22

Hello, I've been using OPiZ2 for about 2 years as Pi-hole in gravity-sync with another one (Orange Pi 3 LTS running Open Media Vault with no problem). Today I found out it was dead, no connection and just a blank screen. It must have happened in the past few days, because I checked it on sunday and it was up and running. I'm almost sure I was using it with Armbian_22.11.0-trunk_Orangepizero2_sid_edge_6.0.6. i have extracted the sd card and checked it on Windows with Diskinternals reader and Minitool Partition Wizard, no problem found. The most recent files and folders have been modified on 2024-07-12, eleven days ago, much prior to my checking, so there is no info about the last hours/days. When I first installed Armbian, I used a version that would brick the OpiZ2 with apt upgrade, but a long time has passed and I don't remember if that issue was fixed. Now, can I somehow resuscitate this install? If not, can I clone/recover at least the pi-hole/unbound/gravitysinc settings? And what version of Armbian should I use? I've downloaded Armbian_24.5.3_Orangepizero2_bookworm_current_6.6.31_minimal, but I came here to ask before doing something.

Hi all, has anyone ever tried to use an atomic firmware upgrade system like rauc or swupdate? https://rauc.readthedocs.io/en/latest/ https://sbabic.github.io/swupdate/swupdate.html I am playing with rauc, in order to do that I have to customize the partitioning of the SD/eMMC: - root1 (4GB) - root2 (4GB) - data (8GB, or remaining space) Can someone suggest how to customize partitioning in such way? I played around setting USE_HOOK_FOR_PARTITION=yes, and hooking the create_partition_table but had no luck. Any hint? Thanks in advance! Andrea

I got my 320x240 ILI9341 touchscreen to work with the image from the OrangePI site: Armbian_23.5.2_Orangepizero2_bookworm_legacy_4.9.318_minimal The display is one I bought from Amazon Hosyond 2.8 Inches TFT LCD Touch Screen Shield Display Module 320x240 SPI Serial ILI9341 with Touch Pen Compatible with Arduino R3/Mega2560 Development Board This document was very helpful getting the display set up on the OPZero 2: https://tienda.tettsa.gt/wp-content/uploads/2022/08/OrangePi_Zero2_H616_User-manual_v3.7.pdf I still don't have the touch part working. If anyone has success getting 2 selects working with SPI1 on OPZero2 and touch working, let me know. The basic steps to getting the SPI LCD to work are: 1) wire up the display to the OPZero2 2.8 Inch TFT SPI 240x320 => OPZero2 1 - VCC => (1) 3.3v 2 - GND => (6) Gnd 3 - CS => (24) Spi1 CS 4 - RESET => (7) GPIO 6 5 - DC => (11) GPIO 1 6 - SDI (MOSI) => (19) Spi1 MOSI 7 - SCLK => (23) Spi1 CLK 8 - LED => (13) GPIO 0 9 - SDO (MISO) => (21) Spi1 MISO 10 - T_CLK 11 - T_CS 12 - T_DIN 13 - T_DO 14 - T_IRQ 2) Install Armbian_23.5.2_Orangepizero2_bookworm_legacy_4.9.318_minimal - must be legacy kernel to work 4.9 is OK 3) sudo apt install fbi kbd armbian-config 4) sudo armbian-config set up desktop now to make the LCD work and start on boot 5) sudo nano /boot/armbianEnv.txt overlays=spi-spidev param_spidev_spi_bus=1 param_spidev_spi_cs=1 extraargs=fbcon=map:1 6) sudo nano /etc/modules-load.d/fbtft.conf fbtft fbtft_device 7) sudo nano etc/modprobe.d/fbtft.conf options fbtft_device custom name=fb_ili9341 gpios=dc:70,reset:73,led:69 speed=16000000 busnum=1 cs=1 bgr=1 txtbuflen-32768 fps=10 rotate=90 😎 sudo dpkg-reconfigure console-setup select UTF-8 select Guess optimal character set select terminus select 6/12 9) sudo nano /usr/share/X11/xorg.conf.d/99-fbdev.conf Section "Device" Identifier "myfb" Driver "fbdev" Option "fbdev" "/dev/fb1" EndSection Now when it boots it should boot to the SPI LCD Display

My friend, when he next inserted the microSD card into the Orange Pi Zero 2 slot, the microSD slot fell off the board 😞 It is not possible to solder it because some of the tracks on the board have become detached so Is it possible to run the ArmBian system on OZPi v2 with a copy of the microSD system on a USB Pendrive? I am looking for a method to run OZIPI v2 without microSD on the system via USB disk

When I tried using a c++ library called sfml which tried opening a window and it gave me an error and after trying every solution on the internet I gave up. And after trying other Debian images I noticed all of them don't have a desktop environment pre installed. So does Debian have graphics at all?

Hi, does anyone have experience with video playback? is playing 1080p in anyway possible? Which image would you recommend for Orange Pi Zero 2 H616 1GB? Is a desktop x11 mandatory?

Hello, I am new to Armbian and Linux in general. I am using an OrangePi Zero 2 (H616) board and need to enable the hardware UART. To do this, I tried using the simplest method I could find: running the command armbian-config -> System -> Hardware. However, in the section where I should find options for peripherals to enable, I found nothing. I have tried installing different versions of Armbian, but nothing changed: - Armbian_24.5.1_Orangepizero2_jammy_current_6.6.31.img - Armbian_24.2.1_Orangepizero2_bookworm_current_6.6.16.img - Armbian_23.8.3_Orangepizero2_bookworm_current_6.1.53.img - Armbian_24.5.1_Orangepizero2_noble_current_6.6.31.img I also tried installing the system on different SD cards, but nothing changed. Please tell me, what am I doing wrong? Thank you.

Hi guys, its the first time im gonna post here so bear with me, i am a recent user of orange pi zero 3, one with 4GB RAM and i have been able to run the latest community release on it, things work besides audio thru hdmi, but i have noticed that the video encoding and decoding is not working, albeit 3d acceleration works thru panfrost and Mesa. I have been digging this topic and i wanted to share what i found and maybe validate if im right or perhaps i am not getting this well. 1. Video encoding and decoding in G31-MP2 is something separated from what Mesa and panfrost would do, so even if those work i cant get video acceleration with h.264 etc. 2. It is possible because the android 12 TV version from the manufacturer can do it in a very easy way, but as far as i understood this is because it is using some kind of closed source driver, that the SoC manufacturer provided (that almost all the boards made with the allwinner H616/H618 would run, so it isnt like orange pi dedicated developers to create the android being offered but it is a stock stuff that Allwinner has available for whoever buys their chips) 3. There are efforts to reverse engineer this properly called CEDRUS but there is kind of a lack of information about them since 2019, it is supposedly present in the kernel, but as many others have said and tried for some reason is not working with H616//h618. Anyone knows if it is still being developed? In conclusion the state of things with hardware decoding and encoding of video in ARM is like a wasteland, at least for linux, these chips, ARM chips we get are mostly developed for android TV boxes or TVs or tablets, but they do not develop for linux, that maybe transferring the necessary code to make it work could be trivial, but with thin resources and doing the bare minimum and being closed source the SoC manufacturer has no interest in creating this support and it is left to open source volunteers to find a way. Which means that support for the H616/H618 might come several years into the future perhaps never. Am I interpreting reality right?, i had some hopes to create something like a jellyfin box with accelerated hardware coding and decoding but nothing might be possible, there is maybe some hope, i read somewhere in the LibreELEC forums that someone made it possible to run it with video decoding (if i am not mistaken) with no audio, so perhaps someone found a way?, thanks in advance.

Using Orange Pi zero 2 Debian bookworm minimal 24.5.1 image , I have disabled Network manager and enabled ifupdown service with static IP configuration. Linux orangepizero2 6.6.31-current-sunxi64 #1 SMP Fri May 17 10:02:40 UTC 2024 aarch64 GNU/Linux Trying to restrict ssh to listen on IP assigned to end0 only, but it is ignoring the ListenAddress 192.168.8.1:22 directive. It listens on all interfaces, which I do not want. sudo service ssh status ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Active: active (running) since Thu 2024-05-30 16:10:42 UTC; 22s ago TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1362 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Main PID: 1363 (sshd) Tasks: 1 (limit: 932) Memory: 1.3M CPU: 231ms CGroup: /system.slice/ssh.service └─1363 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups" May 30 16:10:41 orangepizero2 systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... May 30 16:10:42 orangepizero2 sshd[1363]: debug3: already daemonized May 30 16:10:42 orangepizero2 sshd[1363]: debug3: oom_adjust_setup May 30 16:10:42 orangepizero2 systemd[1]: Started ssh.service - OpenBSD Secure Shell server. May 30 16:10:42 orangepizero2 sshd[1363]: debug1: Set /proc/self/oom_score_adj from 0 to -1000 May 30 16:10:42 orangepizero2 sshd[1363]: debug2: fd 3 setting O_NONBLOCK May 30 16:10:42 orangepizero2 sshd[1363]: Server listening on :: port 22.

Hi. I would like to know if someone can help me. I was successfully able to compile armbian 6.6.30 with all of @Stephen Graf patches for my orangepi zero 3 having Full Audio working even on HDMI. see below for reference. Now I have a 2nd project. It runs the h616 with 2GB DDR3 RAM with AXP313. Can someone help me with a patch for the AXP313 on h616. Or alternatively, could my h618 orangepi zero 3 setup work if I patch it to run with DDR3? If so where can I find such a patch. Thanks in advance.

Hello everyone Now I have finished compiling armbian once and want to check and change the device tree of uboot, but I don't know where to download it, only see the kernel source code in cache/source, so I want to ask

Hello, I hope someone might help me on this. Is anyone here using the ENC28J60 Ethernet port on an Orange Pi Zero 2W or Orange Pi Zero 3? If so, can you please share the file .dts (or .dtbo) that is working for you? I've generated a .dtbo using the file in https://github.com/armbian/sunxi-DT-overlays/blob/master/examples/spi-enc28j60.dts, with: dtc -I dts -O dtb -o /boot/overlay-user/spi-enc28j60.dtbo spi-enc28j60.dts but still it doesn't work. It says "chip not found". I'm using the same cable pinout as in my Raspberry Pi Zero 2W and it works successfully, but not in the Orange Pi Zero 2W. Any idea?