Search the Community

Hello team, I encountered a dependency conflict while trying to upgrade the package armbian-bsp-cli-panther-x2-current to version 25.8.2. The issue seems to be a mismatch in the required version of base-files. Here's a summary of the issue: Attempted upgrade command: apt install armbian-bsp-cli-panther-x2-current Error message: armbian-bsp-cli-panther-x2-current : Depends: base-files (>= 25.8.2) but 25.8.1-12.4+deb12u11-bookworm is to be installed Currently installed version of base-files: base-files: 25.8.1-12.4+deb12u11-bookworm (installed) Available versions for base-files from the repository (apt policy base-files): Installed: 25.8.1-12.4+deb12u11-bookworm Candidate: 25.8.1-12.4+deb12u11-bookworm Version table: 25.8.1-12.4+deb12u11-bookworm 500 25.5.1-12.4+deb12u11-bookworm 500 ... It appears that the repository ( http://apt.armbian.com/pool/bookworm-utils/b/base-files ) does not provide the required version of base-files (25.8.2) for the arm64 architecture. Only the armhf architecture package is available, but armbian-bsp-cli-panther-x2-current depends on the arm64 version. Could you please help investigate the issue or confirm whether the repository will be updated to include version 25.8.2 of base-files? Thank you for your support!

...

For those with a Radxa Cubie A7A, I made a custom Armbian Build using the BSP kernel. https://github.com/NickAlilovic/build/releases/tag/Radxa-a7a-v0.2 https://github.com/NickAlilovic/build/tree/Radxa-A7A Now supports automatic first boot configuration by default. No need for a usb serial device to boot into a desktop image. First boot takes awhile to load. If you are using a server image you need a usb serial device/ssh to interact with the console. There is no Framebuffer console support in the BSP kernel. If you want to edit the automatic first boot configuration read the documentation. https://docs.armbian.com/User-Guide_Autoconfig/ Username: radxa password: radxa

Hi all, I would like to ask support for the board EMB-3531. I'm having problem with booting this board from SD card. Here are some informations about this board. I hope that someone can help me with it. Thank you so much! I try to erase the emmc and flash the MiniLoaderAll.bin but it doesn't help. Or i don't have a correct image with armbian for this board. https://my.kos.org.cn:5154/rockchip/EMB3531/emb3531.pdf

This post from February 2025 claims that RP5 and RPMini are supported: https://www.armbian.com/newsflash/armbian-v25-2/ however, I can't find them on the downloads page. I also don't currently own an RPMini, I am tempted to buy one but I wanted to make sure it was supported first. What's the state of support right now?

Hello everyone! Saw that some luckfox boards were getting supported and I was like: YES!!! Flashed an sd-card with the community image. Latest I could find is 25.11.0-trunk.413. And plonked in my working Luckfox Lyra Zero W and it failed to boot. From what I gather there seems to be a missing partition called "misc" and I think it is expected about after the current unallocated 16MB(16,777,216 bytes). I tried creating a 4MB partition after the current unallocated space but it complained about something called "Magic" and my limited u-boot/rockchip/embedded linux experience made me get lost there. This is the serial output: Where the "No misc partition" is where I began. My current board has buildroot flashed to the SPI and boots if i don't have any sd-card inserted. DDR 0ac6b06a19 typ 24/11/13-17:22:47,fwver: v1.04 tREFI:4x, sr_idle:93, pd_idle:13 PHY drv:clk:40,ca:48,DQ:40,odt:240 vrefinner:50%, vrefout:50% dram drv:40,odt:120 sr_dq:0, sr_ca:0, sr_clk:0 rg:0xc-0x1-0x2, 0x3d-0x0-0x2,status:a007 rdtrn:0x14-0x30-0x4c(0x38) wrtrn:0x3-0x20-0x3d(0x3a) DDR3, 750MHz BW=16 Col=10 Bk=8 CS0 Row=15 CS=1 Size=512MB out U-Boot SPL board init U-Boot SPL 2017.09-g4d88b0a #hxj (Jul 30 2025 - 20:08:42) sfc cmd=03H(6BH-x4) SPI Nand ID ef aa 22 unrecognized JEDEC id bytes: ff, ef, aa Trying to boot from MMC1 No misc partition spl: partition error Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking op-tee 0x00001000 ... sha256(93603ca22c...) + OK ## Checking u-boot 0x00100000 ... sha256(606b868a00...) + OK ## Checking fdt-1 0x0018baf0 ... sha256(6ae9f912c7...) + OK Jumping to U-Boot(0x00001000) I/TC: I/TC: OP-TEE version: 3.13.0-958-g46dcf51e88a #chenjh (gcc version 10.2.1 20201103 (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16))) #2 Thu Mar 6 10:17:27 CST 2025 arm, fwver: v2.10 I/TC: Status: cluster=0xc00, core=0xe100, bootcpu=0 I/TC: Next entry point address: 0x03f011a7 I/TC: OP-TEE memory size: TEEOS 0x5e000 TA 0x1000 SHM 0x1000 I/TC: Primary CPU initializing I/TC: Primary CPU switching to normal world boot

Hey everyone, I'm eyeing the Orange Pi 6 Plus for some edge AI projects, given its 12-core CIX SoC, up to 28.8 TOPS NPU, and massive RAM options (16/32/64GB LPDDR5). Has anyone gotten Ollama running on it with NPU acceleration? Does it support it out of the box, or do you need to convert models (e.g., to INT4/INT8 formats) using custom tools like rkllama or similar? Additionally, with the higher RAM, can it handle bigger LLMs (like 13B+ models) more smoothly than lower-spec SBCs? Any benchmarks or tips on setups (e.g., Ubuntu/Debian installs, frameworks like MLC-LLM)? I'd love to hear real-world experiences—thanks!

I saw some initial work on supporting uugear's vivid unit (rk3399 based). I was wondering in what state that is, what is required to complete that work and if there are plans to add that support to the mainline? Thanks in advance, Markus

Hi all, digging into the Orange Pi 6 Plus specs for a potential build. Can anyone confirm the M.2 slots (the two Key-M 2280 ones) are PCIe Gen 4 with x4 lanes each? Official docs mention NVMe support but are light on details. I'm curious if this could handle a low-end GPU like an RX 570 (or even lower) through an NVMe-to-PCIe adapter/riser—thinking for light gaming or compute tasks. Has anyone tried eGPU setups on this board or similar ARM SBCs? What about power delivery, drivers, and performance? Running Linux (Ubuntu/Debian probably). Thanks for any insights or benchmarks!

Hello, is BPI-6202/6204 supported? It should have A40I CPU, like the M2 Ultra (which is actually supported)

Hi I've made a new kernel Auxiliary Display Driver for TM16XX and compatible LED controllers. This driver supports various LED controller chips, including TM16XX family, FD6XX family, PT6964, and HBS658. It provides support for both I2C and SPI interfaces. I wanted it to manage the hardware on the kernel space while having an easy sysfs user space interface. It also aims to reduce the code to maintain by relaying on existing kernel features instead of recoding them. Plus, you can switch to hardware i2c/spi (instead of software gpio) depending on the pins used. You can use "vfdconf-convert" to convert your existing vfd.conf to its device-tree version. Or you can use the already converted vfd.conf of https://github.com/arthur-liberman/vfd-configurations that are listed in the device table. You don't need to manually edit your device tree, the "make" command will apply the device tree source overlay to your dtb. It comes with a service written as a simple bash script. So it's easily customizable without having to write custom C code. Instructions and source code at https://github.com/jefflessard/tm16xx-display/ Could you please give it a try and report your feedback?

Hello, I am planning to desgin a Computer-on-Board, but would like to know what are the minimal specs needed for it to run a graphical user interface with a desktop. Doing a simple Google Search gives me two answers: "512 MB RAM memory, at least 8 GB of storage (on a quality SD card or eMMC), a 4-core processor, and wired networking. For a more advanced Armbian build framework, you'll require a system with at least 8GB of RAM and 50GB of disk space, although specific requirements vary depending on the hardware." My main issue with this is that it doesn't explain directly if 512 MB of RAM and a 4-core processor (and what frequency?) are enough for the most lightweight GUI desktop.

I'm looking for Orange Pi RV2 RISC-V support. This board is gaining popularity due to the Orange Pi manufacturer's good reputation with Arm. I have successfully built both Orange Pi and Raspberry Pi aarch64 builds on Debian from source so I'd like to know how to build Armbian for Orange Pi RV2 riscv64. What would I need to modify in the build process? Thanks!!

https://www.cnx-software.com/2025/10/25/35-orange-pi-4-pro-an-allwinner-a733-edge-ai-sbc-with-up-to-16gb-lpddr5-wifi-6/ https://www.cnx-software.com/2025/07/07/allwinner-a527-t527-and-a733-datasheets-user-manuals-and-linux-sdk-released/ http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-4-Pro.html Another Allwinner board dropped figuring out the wifi chip is always hard, seem to be https://www.taobao.com/list/item/931793873067.htm https://pine64.sfo3.cdn.digitaloceanspaces.com/doc/datasheet/oz64/AIC8800DC Datasheet v1.0.pdf as usual, it is uncertain if drivers and firmware is after all available. Ethernet according to CNX seemed to be YT8531CA Ethernet seemed to be same as that in OrangePi Zero 3 https://www.cnx-software.com/2023/07/03/orange-pi-zero-3-allwinner-h618-sbc-ships-with-up-to-4gb-ram/ WiFi is 'more critical' these days, if it is closed sourced and no firmware, then it is good as just a door stop. Then that thare are other stuff the figure out especially the : - DRAM controller, - and various DRAM timing and configuration aspects - many other low level specific stuff to even have u-boot to boot it up to the linux prompt. - then the other devices e.g. uart etc. - then HDMI - then gpu acceleration (or at least display video, not playing media yet) - then media - and finally NPU, don't seemed documented yet - many more known or unknown unknowns, audio etc

I have completed a build for the turing-rk1 SBC with an aim toward getting a functioning graphical console, and possibly installing desktop packages later. I built an image without issue that picked up kernel 6.17.2. git commit: 09160da3b9c1231cf20837e8c857f7e605130449 main branch Command used: ./compile.sh RELEASE=trixie CARD=turing-rk1 BRANCH=edge Image created: Armbian-unofficial_25.11.0-trunk_Turing-rk1_trixie_edge_6.17.2.img When booted, I get an error from dmesg about VOP drivers and HDMI video does not turn on. Is this normal for this board or am I doing something wrong? [ 0.965616] rckchip-drm display-subsystem: [drm:rockchip_drm_platform_probe] *ERROR* No available vop found for display-subsystem. The git commit that introduced this board in Armbian does appear to include GPU support, though I'm not really sure if that means the HDMI output should be working. https://github.com/armbian/build/commit/d564431dc2e2a16dff8d21391603702b43de06b1#diff-1d2956e936e3a376577f803ce53091b41ed47e906602165217f78912496eac63 Maybe I need to build w/ kernel 6.11.x to enable GPU support with these patches? Can someone clarify?

Let's Encrypt Certificate has expired for apt.armbian.com openssl s_client -connect apt.armbian.com:443 -servername apt.armbian.com < /dev/null 2>&1 | grep -E "(Verify return code|subject|issuer|notBefore|notAfter)" notAfter=Sep 25 23:05:16 2025 GMT notAfter=Sep 25 23:05:16 2025 GMT subject=CN=apt.armbian.com issuer=C=US, O=Let's Encrypt, CN=E6 Verify return code: 10 (certificate has expired)

I am using kernel 6.12.45 with rk3568 , everything is displayed on my monitor. A colleague's computer does not work on 3 of the 4 monitors. the error is the same as in the theme / kernel: rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes , since it seems that no one is watching that topic, I decided to raise this issue. Has anyone encountered such a problem?

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

Hello. I have not been able to make the ethernet port working on a MKS Pi board with the latest armbian image found here : https://www.armbian.com/mks-pi/ I don't even get a link led ON on the ethernet connector when connected. Can anyone offer guidance? Thanks! P.S. I could not find a MKS-PI tag in the tag menu to identify this thread correctly. Can anyone fix this?

Hello, Thru various and sundry means, I have acquired this unusual specimen; a ZeroDesktop MiiPC M1140. This was originally intended to be a "family desktop PC" that runs on Android Jelly Bean and was released in 2013. It looks like a TV box had a child with a NUC. The machine runs a Marvell Armada 1500 Plus processor with 1GB of RAM and 4GB of storage. The company, Zerodesktop, ran a Kickstarter campaign to fund producing these - my model is one of the Kickstarter Editions. I know that the Marvell Armada 1500 was used in the Google Chromecast 2, along with a bunch of set top boxes. ZeroDesktop no longer exists as a company, having only produced these machines between 2013-14 then going belly up. There are no software updates to the Android system available (nor any mention of the device or the Armada 1500 as a supported processor for Android distributions at all). The only resources online about this device are about 7 out of date (mostly negative) tech reviews from the era. I want to make this thing run Armbian. Does anyone have a clue how to do it? I see that there are 2 development boards made by Marvell listed here but they are vastly different processors. I'm definitely an advanced user but have never compiled my own build before, especially when the system components are so mysterious and info is unavailable like this. I am up for the challenge if anyone can assist. Thank you!

Windows wont let me edit/access the SD card once the iso has been written to it. Any help?

Trouble setting up lvm2. vgcreate wrong because drive order is not now the plugin order on hub according to dmeg. interchanged cables vs ports for out of order discovery and rebooted but problem unchanged ack dmesg. So how do I blow away the volume_group that does not get made due to this error, so I can re vgcreate a new lvm? An hour later, I have tried, rearranging cable vs ports on the hub but the rusty drive stays at /dev/sdd# when it was /dev/sdf# b4 everything was partitioned. What the heck is going on? For this to stand a snow balls chance in hell of working, I MUST have stable drive id's. Can vgcreate use PARTUUID's instead of /dev/sda /dev/sdb etc as identifiers? Thank you, Gene1934 Thank you.

TI SK-AM62A7 is not supported by Armbian, can I use Armbian and create a custom debian based image for TI SK-AM62A7. Support for TI SK-AM62 is there. Kindly guide me on how can I start building my custom image for TI-SK AM62A7.

Hi! I have an old Allwinner A10 based tablet that runs on Android. I want to install some other OS on it. I tried the instructions on linux-sunxi.org and created a page for the tablet: https://linux-sunxi.org/Softwinners_crane I extracted the FEX file from an image I got from the manufacturers a long time ago: http://github.com/linux-sunxi/sunxi-boards/pull/72/files The linux-sunxi mailing list pointed out that my tablet is similar to Topwise A721, so I used that dts file to compile u-boot and the kernel, and tried to boot it through an SD card. Trying to boot that, u-boot starts, and then gets stuck at "Starting kernel..." Then I found this: After following this and building armbian, I realised that there is no script.bin to replace anymore (I'm guessing because now we use device trees?), so unable to boot this as well. What should I do to make this work with armbian? My guess is that I need to create a new dts or correct the Topwise A721 dts (https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/allwinner/sun4i-a10-topwise-a721.dts) and then try again. The only problem is that I have no experience with device trees. Would really appreciate help on getting this to work, thanks! :)