All Activity

You need to install rkdeveloptool on your PC. Connect the board to your PC using a USB-C to USB-A cable. Before powering the board, press and hold the mask button, then plug in the power cable. Once this is done, your PC should detect the device, and you can verify it with: rkdeveloptool ld You can follow this guide: https://docs.armbian.com/User-Guide_Getting-Started/#rockchip

Please specify which OS and kernel version. By the way, I recommend building EDGE yourself.

moved Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

I don't see anything above about your boot-loader being updated. i.e. u-boot or grub. If you're using u-boot, was your uInitrd in your /boot directory updated? The initrd-image needs to be converted to its u-boot format of uinitrd. Instructions for how to do that are located at the bottom of your boot.cmd file (using the mkimage command from the u-boot-tools package). Though that may be a generic example that you'll have to update for your system. Also if you have an armbianEnv.txt (or an equivalent) in your /boot directory, be sure it's up to date for your current kernel's devicetree file location and name. If that doesn't solve it read on.... I keep seeing everywhere that kernel 6.12 is broken. Not sure if that applies to all systems. I use the edge kernel (6.16) in my OrangePI-5-Plus. I've found that to work much better than Vendor (6.1). To chroot in from an another identical system. This works on Debian Trixie. I'm not sure about other OS's. Note: I don't know much about this, I recently found this from searching and used it myself. I found it works great to install new packages and also to run update-initramfs. mount -t proc proc /mnt/proc mount -t sysfs sysfs /mnt/sys mount -t devtmpfs devtmpfs /mnt/dev mount --bind /dev/pts /mnt/dev/pts # If you need for the chrooted system to be able to access the internet, the link at its: (/etc/resolv.conf) must be valid, so add this as well: mount --bind /run/systemd /mnt/run/systemd Then chroot in (I'm not sure if the /bin/bash) is necessary - or if you're using something else than bash, put that there instead?) chroot /mnt /bin/bash [Do what you need to do in there] i.e. install a different kernel, and be sure update-initramfs has been run or run it yourself, and the u-boot (or grub) is updated. Whenever you're installing a new kernel, it's a good idea to leave the old one there. Once you get it working, it might then be a good idea to remove any non-functioning kernels (like that 6.12), and leave any functioning kernels in. Then to back get out of chroot and return undo the above mounts: # Exit chroot exit # This line is only necessary if you mounted it to use the internet while chrooted: umount /mnt/run/systemd # Unmount the rest umount /mnt/dev/pts umount /mnt/dev umount /mnt/sys umount /mnt/proc umount /mnt

@Ian Coelho Success! I got it working by tweaking the eMMC parameters in the dtb file. Generally I changed the `<max-frequency>` to 50M. I've attached my version if you want to give it a shot, but make sure you have a backup ROM handy. my.dtb

Thanks for this info, just wanted to share that the image for the "Linux v6.1 vendor IOT image for the 5 "Max" model" you linked to also worked for me on my Orange Pi 5 Ultra with no modifications needed. I haven't tested wifi or any use cases besides some simmple stuff over ssh so far, I did get a warning on first boot that it's a developer version of Armbian and shouldn't be used for production, but I suppose that's the case for all "community" builds? I also found this gist with steps to build Armbian from scratch for the 5 Ultra, but I haven't tried this yet. In case anyone else is looking for related info this PR also is also relevant: https://github.com/armbian/build/pull/8252 I still regret not buying a better supported board like the 5 Max board instead but hopefully better support will come for the 5 Ultra with time.

Upon reading the content of RPi5 about 6.12 from this and this , I was under the impression that it's okay to upgrade the Armbian 24.11 based NextCloudPi to a 6.12 kernel. Well, I was wrong and the RPi5 current stuck in the RPi Logo on a black page. Net address seems to be 0.0.0.0. I could really use some advice on how to restore this, perhaps some `chroot` method from another Linux machine to get the right kernel package and intramfs. Here are the steps that got me to the current situation. Maybe a hint on how to restore? 1. Mark `raspi-firmware`, like what was recommended in 1st post. sudo apt-mark hold raspi-firmware [sudo] password for pi: raspi-firmware set on hold. 2. Remove the old bsp for RPi5b specific package? pi@nextcloudpi:~$ sudo dpkg --remove --force-all libraspberrypi0 armbian-bsp-cli-rpi5b-current dpkg: warning: ignoring request to remove libraspberrypi0 which isn't installed (Reading database ... 50983 files and directories currently installed.) Removing armbian-bsp-cli-rpi5b-current (24.11.1) ... Armbian 'armbian-bsp-cli-rpi5b-current' for '1-PC980a-V32ae-H032a-B6e44-R7697': 'postrm' starting. Armbian 'armbian-bsp-cli-rpi5b-current' for '1-PC980a-V32ae-H032a-B6e44-R7697': 'postrm' finishing. Processing triggers for initramfs-tools (0.142+deb12u3) ... update-initramfs: Generating /boot/initrd.img-6.6.63-current-bcm2712 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152 3. Install the newer RPI4b bsp package, which guessing from the 2nd post, including everything from 3b to 5b. pi@nextcloudpi:~$ sudo apt install armbian-bsp-cli-rpi4b-current Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: armbian-bsp-cli-rpi4b-current 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 1,515 kB of archives. After this operation, 5,411 kB of additional disk space will be used. Get:1 https://mirrors.ustc.edu.cn/armbian bookworm/main arm64 armbian-bsp-cli-rpi4b-current arm64 25.8.1 [1,515 kB] Fetched 1,515 kB in 2s (1,008 kB/s) Selecting previously unselected package armbian-bsp-cli-rpi4b-current. (Reading database ... 50867 files and directories currently installed.) Preparing to unpack .../armbian-bsp-cli-rpi4b-current_25.8.1_arm64.deb ... Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'preinst' starting. Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'preinst' finishing. Unpacking armbian-bsp-cli-rpi4b-current (25.8.1) ... Setting up armbian-bsp-cli-rpi4b-current (25.8.1) ... Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'postinst' starting. Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'postinst' finishing. Processing triggers for initramfs-tools (0.142+deb12u3) ... update-initramfs: Generating /boot/initrd.img-6.6.63-current-bcm2712 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152 4. I notice the initrd was still generated for the old kernel image, which is understandable based what is currently installed pi@nextcloudpi:~$ uname -a Linux nextcloudpi 6.6.63-current-bcm2712 #2 SMP PREEMPT Wed Nov 27 10:28:46 UTC 2024 aarch64 GNU/Linux pi@nextcloudpi:~$ dpkg -l | grep linux-image ii linux-image-current-bcm2712 24.11.1 arm64 Armbian Linux current kernel image 6.6.63-current-bcm2712 5. Therefore, I went ahead to install the new 6.12 kernel package pi@nextcloudpi:~$ sudo apt install linux-image-current-bcm2711 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-image-current-bcm2711 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 34.5 MB of archives. After this operation, 212 MB of additional disk space will be used. Get:1 https://mirrors.ustc.edu.cn/armbian bookworm/main arm64 linux-image-current-bcm2711 arm64 25.8.1 [34.5 MB] Fetched 34.5 MB in 5s (7,198 kB/s) Selecting previously unselected package linux-image-current-bcm2711. (Reading database ... 51028 files and directories currently installed.) Preparing to unpack .../linux-image-current-bcm2711_25.8.1_arm64.deb ... Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'preinst' starting. Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'preinst' finishing. Unpacking linux-image-current-bcm2711 (25.8.1) ... Setting up linux-image-current-bcm2711 (25.8.1) ... Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'postinst' starting. update-initramfs: Generating /boot/initrd.img-6.12.44-current-bcm2711 Armbian: update last-installed kernel symlink to 'Image'... '/boot/Image' -> 'vmlinuz-6.12.44-current-bcm2711' Armbian: Debian compat: linux-update-symlinks install 6.12.44-current-bcm2711 boot/vmlinuz-6.12.44-current-bcm2711 I: /vmlinuz is now a symlink to boot/vmlinuz-6.12.44-current-bcm2711 I: /initrd.img is now a symlink to boot/initrd.img-6.12.44-current-bcm2711 Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'postinst' finishing. 6. Everything looked right to me as there are no errors like before got reported during update-initramfs: pi@nextcloudpi:~$ sudo apt remove linux-image-current-bcm2712 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: linux-image-current-bcm2712 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 155 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 54440 files and directories currently installed.) Removing linux-image-current-bcm2712 (24.11.1) ... Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'prerm' starting. Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'prerm' finishing. Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'postrm' starting. update-initramfs: Deleting /boot/initrd.img-6.6.63-current-bcm2712 Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'postrm' finishing. 7. As a final check, I ran the upgrade script again pi@nextcloudpi:~$ sudo armbian-upgrade Hit:1 https://mirrors.ustc.edu.cn/debian bookworm InRelease Hit:2 https://mirrors.ustc.edu.cn/debian bookworm-updates InRelease Hit:3 https://mirrors.ustc.edu.cn/debian bookworm-backports InRelease Hit:4 https://mirrors.ustc.edu.cn/debian-security bookworm-security InRelease Hit:5 https://mirrors.ustc.edu.cn/armbian bookworm InRelease Hit:6 https://github.armbian.com/configng stable InRelease Hit:7 https://packages.sury.org/php bookworm InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 8. That's it. After rebooting, I was greeted with a RPi logo on a black page, with some messaging scrolling (trying to attach a photo but failed). It never got to the point to boot the kernel image or systemd booting sequence.

RK3576 nanopi M5 cannot start Waydrod I am trying to use Waydrod on the nanopi M5, and I am starting it up CONFIG_ANDROID_BINDER_IPC=y CONFIG_ANDROID_BINDERFS=y CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder" However, during the actual startup of Waydrod, there was a continuous black screen crash and restart. The following is the error log: nano@nanopi-m5:$ waydroid show-full-ui [13:55:56] Introspect error on :1.103:/ContainerManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [13:56:21] Failed to unfreeze container. Trying to launch anyways... [13:57:06] Failed to get service waydroidplatform, trying again... [13:57:07] Failed to get service waydroidplatform, trying again... [13:57:08] Failed to get service waydroidplatform, trying again... [13:57:09] Failed to get service waydroidplatform, trying again... [13:57:10] Failed to get service waydroidplatform, trying again... [13:57:11] Failed to get service waydroidplatform, trying again... [13:57:12] Failed to get service waydroidplatform, trying again... [13:57:13] Failed to get service waydroidplatform, trying again... [13:57:14] Failed to get service waydroidplatform, trying again... [13:57:15] Failed to get service waydroidplatform, trying again... [13:57:16] Failed to get service waydroidplatform, trying again...nano@nanopi-m5:$ waydroid log (009909) [13:52:01] % lxc-info --version 5.0.3 (009909) [13:52:01] % mkdir -p /var/lib/waydroid/lxc/waydroid (009909) [13:52:01] % sh -c cat "/usr/lib/waydroid/data/configs/config_base" "/usr/lib/waydroid/data/configs/config_3" "/usr/lib/waydroid/data/configs/config_4" > "/var/lib/waydroid/lxc/waydroid/config" (009909) [13:52:01] % sed -i s/LXCARCH/aarch64/ /var/lib/waydroid/lxc/waydroid/config (009909) [13:52:01] % cp -fpr /usr/lib/waydroid/data/configs/waydroid.seccomp /var/lib/waydroid/lxc/waydroid/waydroid.seccomp (009909) [13:52:01] % systemctl is-active -q apparmor (009909) [13:52:01] % mv /var/lib/waydroid/config_nodes /var/lib/waydroid/lxc/waydroid (006325) [13:52:01] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH STOPPED (006325) [13:52:01] % modprobe -q ashmem_linux (006325) [13:52:01] % chmod 666 -R /dev/binder (006325) [13:52:01] % chmod 666 -R /dev/vndbinder (006325) [13:52:01] % chmod 666 -R /dev/hwbinder (010960) [13:53:11] Starting waydroid session (006325) [13:53:11] % /usr/lib/waydroid/data/scripts/waydroid-net.sh start vnic is waydroid0 (006325) [13:53:11] % systemctl is-active -q nfcd (006325) [13:53:11] % chmod 777 -R /dev/sw_sync (006325) [13:53:11] % chmod 777 -R /sys/kernel/debug/sync/sw_sync (006325) [13:53:11] % chmod 777 -R /dev/dri/renderD130 (006325) [13:53:11] % chmod 777 -R /dev/dri/renderD129 (006325) [13:53:11] % chmod 777 -R /dev/dri/renderD128 (006325) [13:53:11] % chmod 777 -R /dev/fb0 (006325) [13:53:11] % chmod 777 -R /dev/dma_heap/reserved (006325) [13:53:11] % chmod 777 -R /dev/dma_heap/system-uncached (006325) [13:53:11] % chmod 777 -R /dev/dma_heap/system (006325) [13:53:11] % mv /var/lib/waydroid/config_session /var/lib/waydroid/lxc/waydroid (006325) [13:53:11] % mount -o ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs (006325) [13:53:11] % mkdir -p /var/lib/waydroid/overlay_work/system (006325) [13:53:11] % mount -t overlay -o ro,lowerdir=/var/lib/waydroid/overlay:/var/lib/waydroid/rootfs,upperdir=/var/lib/waydroid/overlay_rw/system,workdir=/var/lib/waydroid/overlay_work/system,xino=off overlay /var/lib/waydroid/rootfs (006325) [13:53:11] % mount -o ro /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor (006325) [13:53:11] % mkdir -p /var/lib/waydroid/overlay_work/vendor (006325) [13:53:11] % mount -t overlay -o ro,lowerdir=/var/lib/waydroid/overlay/vendor:/var/lib/waydroid/rootfs/vendor,upperdir=/var/lib/waydroid/overlay_rw/vendor,workdir=/var/lib/waydroid/overlay_work/vendor,xino=off overlay /var/lib/waydroid/rootfs/vendor (006325) [13:53:11] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop (006325) [13:53:11] Save config: /var/lib/waydroid/waydroid.cfg (006325) [13:53:11] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init (006325) [13:53:11] New background process: pid=11037, output=background (006325) [13:53:11] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH RUNNING (010960) [13:53:11] Skipping clipboard manager service because of missing pyclip package (011121) [13:55:27] Session is already running (011139) [13:55:56] Introspect error on :1.103:/ContainerManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (011139) [13:55:56] Executing introspect queue due to error (011139) [13:56:21] Failed to unfreeze container. Trying to launch anyways... (011139) [13:57:06] Failed to get service waydroidplatform, trying again... (006325) [13:57:06] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH RUNNING (011139) [13:57:07] Failed to get service waydroidplatform, trying again... (011139) [13:57:08] Failed to get service waydroidplatform, trying again... (011139) [13:57:09] Failed to get service waydroidplatform, trying again... (011139) [13:57:10] Failed to get service waydroidplatform, trying again... (011139) [13:57:11] Failed to get service waydroidplatform, trying again... (011139) [13:57:12] Failed to get service waydroidplatform, trying again... (011139) [13:57:13] Failed to get service waydroidplatform, trying again... (011139) [13:57:14] Failed to get service waydroidplatform, trying again... (011139) [13:57:15] Failed to get service waydroidplatform, trying again... (011139) [13:57:16] Failed to get service waydroidplatform, trying again... (012115) [13:57:27] % tail -n 60 -F /var/lib/waydroid/waydroid.log (012115) [13:57:27] *** output passed to waydroid stdout, not to this log *** nano@nanopi-m5:~sudo systemctl status waydroid-containerer ● waydroid-container.service - Waydroid Container Loaded: loaded (/usr/lib/systemd/system/waydroid-container.service; enabled; preset: enabled) Active: active (running) since Sun 2025-09-21 13:17:05 CST; 41min ago Main PID: 6325 (waydroid) Tasks: 6 (limit: 9464) Memory: 21.4M (peak: 92.5M) CPU: 4min 20.835s CGroup: /system.slice/waydroid-container.service ├─ 6325 /usr/bin/python3 /usr/bin/waydroid -w container start └─11005 dnsmasq --conf-file=/dev/null -u dnsmasq --strict-order --bind-interfaces --pid-file=/run/waydroid-lxc/dnsmasq.pid --listen-address 192.168.240.1 --dhcp-range 192.168.240.2,192.168.240.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=waydroid0 -> 9月 21 13:17:05 nanopi-m5 systemd[1]: Started waydroid-container.service - Waydroid Container. 9月 21 13:17:52 nanopi-m5 waydroid[6552]: [13:17:52] Downloading https://sourceforge.net/projects/waydroid/files/images/system/lineage/waydroid_arm64/lineage-20.0-20250809-VANILLA-waydroid_arm64-system.zip/download 9月 21 13:34:17 nanopi-m5 waydroid[6552]: [13:34:17] Validating system image 9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: started, version 2.90 cachesize 150 9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth cryptohash DNSSEC loop-detect inotify dumpfile 9月 21 13:53:11 nanopi-m5 dnsmasq-dhcp[11005]: DHCP, IP range 192.168.240.2 -- 192.168.240.254, lease time 1h 9月 21 13:53:11 nanopi-m5 dnsmasq-dhcp[11005]: DHCP, sockets bound exclusively to interface waydroid0 9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: reading /etc/resolv.conf 9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: using nameserver 127.0.0.53#53 9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: read /etc/hosts - 10 names nano@nanopi-m5:~$ systemctl status dbus ● dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; static) Active: active (running) since Sat 2025-09-20 21:30:20 CST; 16h ago TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) Main PID: 1455 (dbus-daemon) Tasks: 1 (limit: 9464) Memory: 3.5M (peak: 3.8M) CPU: 2.817s CGroup: /system.slice/dbus.service └─1455 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only 9月 21 13:16:57 nanopi-m5 dbus-daemon[1455]: [system] Reloaded configuration 9月 21 13:17:02 nanopi-m5 dbus-daemon[1455]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=1527 comm="/usr/sbin/NetworkManager --no-daemon") 9月 21 13:17:02 nanopi-m5 dbus-daemon[1455]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 9月 21 13:17:11 nanopi-m5 dbus-daemon[1455]: Unknown username "gnome-remote-desktop" in message bus configuration file 9月 21 13:17:11 nanopi-m5 dbus-daemon[1455]: Unknown username "whoopsie" in message bus configuration file 9月 21 13:17:11 nanopi-m5 dbus-daemon[1455]: [system] Reloaded configuration 9月 21 13:23:17 nanopi-m5 dbus-daemon[1455]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.94' (uid=1000 pid=4015 comm="/usr/bin/gnome-control-center network") 9月 21 13:23:17 nanopi-m5 dbus-daemon[1455]: [system] Successfully activated service 'org.freedesktop.hostname1' 9月 21 13:53:11 nanopi-m5 dbus-daemon[1455]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=1527 comm="/usr/sbin/NetworkManager --no-daemon") 9月 21 13:53:11 nanopi-m5 dbus-daemon[1455]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' nano@nanopi-m5:$ nano@nanopi-m5:$ sudo lxc-attach -n waydroid -- systemctl status dbus lxc-attach: waydroid: ../src/lxc/attach.c: get_attach_context: 406 Connection refused - Failed to get init pid lxc-attach: waydroid: ../src/lxc/attach.c: lxc_attach: 1470 Connection refused - Failed to get attach context nano@nanopi-m5:$ nano@nanopi-m5:$ ls -l /var/lib/waydroid/ ls -l /var/lib/waydroid/lxc/waydroid/ total 52 drwxr-xr-x 2 root root 4096 9月 21 13:52 cache_http drwxr-xr-x 2 root root 4096 9月 21 13:52 host-permissions drwxr-xr-x 2 root root 4096 9月 21 13:51 images drwxr-xr-x 3 root root 4096 9月 21 13:52 lxc drwxr-xr-x 3 root root 4096 9月 21 13:52 overlay drwxr-xr-x 4 root root 4096 9月 21 13:52 overlay_rw drwxr-xr-x 4 root root 4096 9月 21 13:53 overlay_work drwxr-xr-x 1 root root 4096 9月 21 13:52 rootfs -rw-r--r-- 1 root root 472 9月 21 13:52 waydroid_base.prop -rw-r--r-- 1 root root 486 9月 21 13:53 waydroid.cfg -rw-rw-rw- 1 root root 6558 9月 21 13:57 waydroid.log -rw-r--r-- 1 root root 776 9月 21 13:53 waydroid.prop total 16 -rw-r--r-- 1 root root 989 9月 21 13:52 config -rw-r--r-- 1 root root 1860 9月 21 13:52 config_nodes -rw-r--r-- 1 root root 311 9月 21 13:53 config_session -rw-r--r-- 1 root root 346 6月 24 17:18 waydroid.seccomp nano@nanopi-m5:~$ How to reproduce? At present, RK3576 cannot use Waydrod when opening IPC and Android binder. Perhaps it is due to the absence of VNet ANDROID_SHMEM. On which OS are you observing this problem? (for easier diagnosis please provide logs with armbianmonitor -u) Armbian Ubuntu 24.04 Noble

Thank you, it looks like my Nvme was bad. It works now!

I switch to vendor kernel 6.1.115 - its work

Hi All Well I am getting nowhere fast. When plugging the board into a Rpi Zero 2w , i2cdetect -l shows i2c-1 and i2c-2 i2cdetect -y 1 shows 00x48 i2cdetect -y 2 shows oox49 (my second board) and a few others like 3a,50,59 Re-wrote the image on the Opi Zero 2w to Debian as I was getting tired of the booting problems with ArmBian. Followed the manual on ALL the instructions. i2cdetect -l shows i2c-0 i2c-1 ,i2c-2 and i2c-3 i2cdetect -y 0 does not show any adapters connected i2cdetect -y 1 shows UU on 36 i2cdetect -y 2 shows 30 and 50 i2cdetect -y 3 does not show any adapters VERY SLOWLY. Orangepi-config /system/Hardware has been tried with just i2c-0 ticked or all three ticked. Tried ticking phi2c-0 to 3 but that made no difference, still no 00x48 visible anywhere. I have tried about 6 different OS Images, all to no avail. Even tried the Rpi image shown on the Opi site. So, I have to conclude (unless someone corrects me) that it is the board that is the problem or some firmware on the board. Not sure if I should learn how to upgrade the firmware. Regards

@Igor When I first start it up, I get an error! Even if I install the packages manually, the GNOMRlE interface does not switch to Portuguese! That's strange!

In the case of the Orange PI 5 Pro, just remove OUT1 from mute mode and the ES8388 will work fine! By default, OUT1 is in MM (mute). @laibsch

I recently had to modify a device tree file for a different reason. I showed what I did (and how I did it) here: https://forum.armbian.com/topic/52118-hdmi-audio-and-analog-audio-do-not-work-on-opi5plus/?do=findComment&comment=224923 To summarize, I used the device-tree-compiler package (command line: dtc) to convert the device tree binary (.dtb) file to a device tree source (.dts) file. Then I edited the .dts file, then converted it back. The process won't show you all the variable names, but the resulting .dts is readable enough to likely see what and where you need to change... and even moreso if you have the original (pre-compiled) .dts file to compare it with. If you need to match variable names with specific numbers, they will likely be #defined in the #includes at the top of the original .dts file.

This will cause update-grub to add the following a devicetree line to all menu entries. This example is based on Debian Trixie's grub-efi. This example will expect dtb directories (or links) to be in the /boot directory, using the convention that I've seen Armbian use. Here is an example of a /boot directory listing for (pure) Debian Trixie with two kernels: -rw-r--r-- 1 root root 336036 Aug 27 04:10 config-6.12.43+deb13-arm64 -rw-r--r-- 1 root root 343394 Sep 6 12:48 config-6.16.3+deb13-arm64 lrwxrwxrwx 1 root root 42 Sep 20 16:17 dtb -> ../usr/lib/linux-image-6.16.3+deb13-arm64/ lrwxrwxrwx 1 root root 43 Sep 20 16:17 dtb-6.12.43+deb13-arm64 -> ../usr/lib/linux-image-6.12.43+deb13-arm64/ lrwxrwxrwx 1 root root 42 Sep 20 16:18 dtb-6.16.3+deb13-arm64 -> ../usr/lib/linux-image-6.16.3+deb13-arm64/ drwxr-xr-x 3 root root 4096 Sep 20 15:13 efi drwxr-xr-x 5 root root 4096 Sep 20 16:26 grub lrwxrwxrwx 1 root root 29 Sep 15 21:30 initrd.img -> initrd.img-6.16.3+deb13-arm64 -rw------- 1 root root 42521317 Sep 20 16:26 initrd.img-6.12.43+deb13-arm64 -rw------- 1 root root 43760872 Sep 20 16:25 initrd.img-6.16.3+deb13-arm64 lrwxrwxrwx 1 root root 30 Sep 15 20:38 initrd.img.old -> initrd.img-6.12.43+deb13-arm64 -rw-r--r-- 1 root root 83 Aug 27 04:10 System.map-6.12.43+deb13-arm64 -rw-r--r-- 1 root root 92 Sep 6 12:48 System.map-6.16.3+deb13-arm64 lrwxrwxrwx 1 root root 26 Sep 15 21:30 vmlinuz -> vmlinuz-6.16.3+deb13-arm64 -rw-r--r-- 1 root root 37449664 Aug 27 04:10 vmlinuz-6.12.43+deb13-arm64 -rw-r--r-- 1 root root 41507328 Sep 6 12:48 vmlinuz-6.16.3+deb13-arm64 lrwxrwxrwx 1 root root 27 Sep 15 20:38 vmlinuz.old -> vmlinuz-6.12.43+deb13-arm64 Note: The relative pathways of the dtb links above assume that the /boot directory is part of the main OS partition, not on its own boot partition. Otherwise you'd need to copy those directories to /boot/ as Armbian does. For The Current Partition's OS Entries (each devicetree will be specific to the respective kernel) 1. Open the file with a text/source editor (using sudo): /etc/grub.d/10_linux 2. Find every line that looks something like this (currently on my system, there is only one, and it's line 189) linux ${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${args} 3. Just above it, add your own system's version of this line: devicetree ${rel_dirname}/dtb-${version}/[VENDOR SUB-DIRECTORY]/[SBC PRODUCT].dtb Specific Example: OrangePI-5-Plus devicetree ${rel_dirname}/dtb-${version}/rockchip/rk3588-orangepi-5-plus.dtb Specific Example from the resulting grub.cfg, of the current trixie-backport kernel, again on the OrangePI-5-Plus: devicetree /boot/dtb-6.16.3+deb13-arm64/rockchip/rk3588-orangepi-5-plus.dtb For Other Partitions' OS Entries, via os-prober (I'm unfamiliar with the variables in this so each devicetree will be the same generic path, regardless of kernel) 1. Open the file with a text/source editor (using sudo): /etc/grub.d/30_os-prober 2. Find every line that looks something like this (currently on my system, there are two, lines 277 and 297) linux ${LKERNEL} ${LPARAMS} 3. Just above it, add your own system's version of this line: devicetree /boot/dtb/[VENDOR SUB-DIRECTORY]/[SBC PRODUCT].dtb Specific Example: OrangePI-5-Plus devicetree /boot/dtb/rockchip/rk3588-orangepi-5-plus.dtb Then run update-grub, and take a look at the resulting /boot/grub/grub.cfg

Yes, current broke at some point. More up to date packages should be available via apt. In general the support for rk3588 in 6.12 (current as of today) is barely there but there won't be updates regarding that matter, bug fixes only due to its LTS nature. Better use vendor or edge.

Great, svvolf! This fix boot problem on OPI Zero v1 (Armbian v25.8.1, Linux 6.12.43-current-sunxi) 😁 Thank you!

Hi, I have downloaded and tested the 6.12 kernel Minimal/IOT images and they are not booting. I downloaded trixie 6.1, booted, then manually installed latest 6.12 with armbian-config and the reboot failed. I re-flashed sd card with 6.1, installed edge 6.16.4 (latest) with armbian-config and it booted fine.

T'is one reason to prefer boards that take 12V power. and yes, barrel-connectors, but I can't think of any recent boards that use 5V and barrel connectors. NanoPi-M4 vs NanoPC-T4, with a WD Blue SN500, the T4 was stable. the M4 was not. yes, the M4 used the official power supply.

As far as I know, the permissions of /var/log/postgresql after a reboot are recreated from those on /var/log.hdd/postgresql. So if you modify those as well (remove the sticky bit), the workaround should be permanent. Thanks for highlighting this problem, I've encountered the very same issue, but didn't realize it was caused by this somewhat peculiar directory permission. So I just applied your workaround (plus my extension) and hope it will fix this once and for all.

I think there are some userspace drivers needed as well. Armbian provides the kernel module only. Not exactly sure what's needed but I think the stuff is from here: https://github.com/airockchip/rknn-toolkit2/tree/master/rknpu2

I see. Well there is a similar topic, maybe this can give some clues: https://forum.armbian.com/topic/50228-i2s-audio-not-working-on-orange-pi-zero-2w-allwinner-h618-with-max98357a/

Can someone tell me the major/minor device numbers for the /dev/rknpu device? It wasn't created in the image that I'm using. I'm trying to determine if the built-in npu has enough functionality to test a llm: # cat /sys/kernel/debug/rknpu/version RKNPU driver: v0.9.8 # I'm running the latest of the linux-image-vendor-rk35xx=25.5.1 v6.1.115 $ uname -a Linux cm3588-nas 6.1.115-vendor-rk35xx #1 SMP Wed Aug 13 03:55:09 UTC 2025 aarch64 GNU/Linux $ # LD_LIBRARY_PATH=/usr/lib/aarch64-linux-gnu python3 server.py Loaded RKLLM library from '/usr/lib/aarch64-linux-gnu/librkllmrt.so' RKLLM_LOG_LEVEL: 1 Initializing model with parameters: Path: /src/models/tinyllama-v1-rk3588/tinyllama-v1.0-1.1B-rk3588.rkllm Max Context: 30000 Max New Tokens: -1 N_Keep: 32 Use GPU: True Is Async (Library Flag): False E RKNN: [23:47:17.469] failed to open rknpu module, need to insmod rknpu dirver! E RKNN: [23:47:17.469] failed to open rknn device! E RKNN: [23:47:17.570] Device is not available Get device properties failed Error: rkllm_init failed (code 1). Failed to initialize RKLLM model. Server not starting. # ls -l /dev/rknpu ls: cannot access '/dev/rknpu': No such file or directory #

Unfortunately, LLM is wrong here. There are MAX98357A boards, such as the violet one, which support (L+R)/2 and single/selected channel modes. I was able to configure the board using ESP32 and a sinus wave, so I can confirm it is possible and the board is not malfunctioning. For some reason, the sunxi driver (or ALSA) misbehaves, and I can't determine where the problem is.

Hi @Gunjan Gupta, Thanks for the info. I'm trying to do something similar but on a different board. Running the "uboot-patch" build command just seems to download uboot?? There is no pause for me to make changes then to hit enter to continue. Has the process changed or am I doing something wrong? Many Thanks, Fiery