Search the Community

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

Hello! Just wondered if an armbian image was planned for the Odroid M1S? Thank you in advance!

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, is BPI-6202/6204 supported? It should have A40I CPU, like the M2 Ultra (which is actually supported)

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?

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.

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! :)

Hello, I'm developing a Custom Armbian for the RSB-4411 (the motherboard that uses like the Raise3D E2). For the moment, it's in the experimental phase because I can't get it to boot. It goes CRC-ERROR when I boot into the debug port on my motherboard. Source codes Armbian build: https://github.com/AstromanGaming/build Linux Kernel: https://github.com/AstromanGaming/Linux-i.MX-Fork U-boot: https://github.com/AstromanGaming/U-boot-i.MX-Fork If someone or I manage to make it boot, that would be great! 🙂 PS: I'm new to this community, if I do something wrong, please let me know.

Would it be easy to port Armbian on the Pipo M6 Pro and integrate additional device drivers to provide support for the touchscreen, the front and back camera and the sound? https://www.geekbuying.com/item/Pipo-M6Pro-GPS-Android-4-2-RK3188-Quad-Core-1-6GHz-Tablet-PC-9-7-inch-Retina-Capacitive-Touch-Screen-2048-1536-2GB-16GB-319264.html Is this something feasible in the first place? Anybody out there who want to help me on this project?

Hi everyone, I'm using the RTL8189FS WiFi module and noticed that the driver included in the current Armbian GitHub repository (https://github.com/armbian) seems to be quite outdated. I'd like to ask: - What is the current version of the RTL8189FS driver? - Is there a newer version available? Thanks in advance!

Hi Gents, I would like to ask for your help or tips and tricks in the following problem... Basically to keep the long story short, I have a custom board with RK3566 and 2 GB of RAM, 32 GB Samsung emmc on it ... basically if you are familliar it is a Linxdot Helium miner which has some problems with the onboard Lora module. I had tried to flash using RKDevTool a few Debian version that I found for Rk3566 but not all of them worked properly. All the time I was able to reflash it by using RKDevTool by pressing the button while I powered up the board but after flashing the Armbian minnimal for Orange Pi3B I can't use the RKDevTool anymore, it is simply not seeing the board anymore (No device found). I have an UART 3.5mm Jack type port, I had a homemade cable so I was able to create the user at the first boot, I am able to log in, but there is no HDMI, the ethernet port is no recognized, WiFi also not recognized, I am plug in a USB Flash stick and I am not seeing it in the lsblk command output, so basically I have now a very basic board. (I know, I am stupid, but I was thinking that I can't damage it because the RKDevTool was working fine under all previous circumstances). My question would be, if there is any possibility somehow to restore the functionality to be able to boot it in MaskMode for the RKDevTool or any other solution to make at least the Ethernet and USB ports to work? There are no other button, just 2, one reset and one user button on it. All the time I had to keep pressed the user button in order to be detected by the RK tool. There are no jumpers on the board (at least I can't find them) which I can short to stop the emmc from booting or similar things Many thanks in advance ! The booting process: ▒▒▒DDR V1.18 f366f69a7d typ 23/07/17-15:48:58 ln LP4/4x derate en, other dram:1x trefi ddrconfig:15 DDR4, 324MHz BW=32 Col=10 Bk=4 BG=2 CS0 Row=16 CS=1 Die BW=16 Size=2048MB tdqss: cs0 dqs0: 192ps, dqs1: 144ps, dqs2: 96ps, dqs3: 96ps, change to: 324MHz clk skew:0x8d change to: 528MHz clk skew:0x8d change to: 780MHz clk skew:0x8d change to: 1056MHz(final freq) clk skew:0x8d PHY drv:clk:37,ca:37,DQ:37,odt:139 vrefinner:50%, vrefout:61% dram drv:34,odt:120 cs 0: the read training result: DQS0:0x3c, DQS1:0x39, DQS2:0x36, DQS3:0x3b, min : 0x7 0xa 0xb 0x8 0x2 0x4 0x4 0x2 , 0x3 0x7 0x1 0x4 0x4 0x6 0x8 0x2 , 0x5 0x6 0x3 0x6 0x2 0x1 0x2 0x4 , 0x8 0x6 0x6 0x0 0x5 0x8 0x9 0x6 , mid :0x24 0x27 0x28 0x25 0x1f 0x21 0x21 0x1f ,0x21 0x23 0x1e 0x22 0x22 0x23 0x24 0x1f , 0x21 0x23 0x20 0x22 0x1f 0x1d 0x1f 0x21 ,0x26 0x23 0x23 0x1d 0x22 0x26 0x26 0x23 , max :0x42 0x45 0x46 0x43 0x3c 0x3e 0x3f 0x3c ,0x3f 0x40 0x3b 0x40 0x40 0x40 0x41 0x3d , 0x3e 0x40 0x3e 0x3f 0x3c 0x3a 0x3d 0x3e ,0x44 0x40 0x41 0x3a 0x40 0x44 0x44 0x41 , range:0x3b 0x3b 0x3b 0x3b 0x3a 0x3a 0x3b 0x3a ,0x3c 0x39 0x3a 0x3c 0x3c 0x3a 0x39 0x3b , 0x39 0x3a 0x3b 0x39 0x3a 0x39 0x3b 0x3a ,0x3c 0x3a 0x3b 0x3a 0x3b 0x3c 0x3b 0x3b , the write training result: DQS0:0xa6, DQS1:0xa0, DQS2:0x99, DQS3:0x99, min :0x8c 0x92 0x90 0x8f 0x88 0x89 0x8a 0x89 0x8f ,0x85 0x89 0x84 0x89 0x89 0x8b 0x8b 0x85 0x85 , 0x84 0x85 0x84 0x85 0x83 0x81 0x83 0x85 0x82 ,0x7f 0x7d 0x7c 0x7a 0x81 0x81 0x82 0x7e 0x7e , mid :0xa8 0xab 0xab 0xa9 0xa1 0xa4 0xa3 0xa2 0xa9 ,0x9f 0xa2 0x9e 0xa3 0xa2 0xa3 0xa4 0x9f 0x9f , 0x9e 0x9e 0x9f 0xa0 0x9c 0x9b 0x9a 0x9c 0x9d ,0x9b 0x97 0x97 0x95 0x9a 0x9c 0x9c 0x9a 0x99 , max :0xc5 0xc5 0xc7 0xc3 0xbb 0xc0 0xbc 0xbb 0xc4 ,0xba 0xbb 0xb8 0xbd 0xbb 0xbc 0xbe 0xba 0xb9 , 0xb9 0xb8 0xba 0xbb 0xb6 0xb5 0xb2 0xb4 0xb8 ,0xb7 0xb2 0xb3 0xb0 0xb3 0xb7 0xb6 0xb6 0xb5 , range:0x39 0x33 0x37 0x34 0x33 0x37 0x32 0x32 0x35 ,0x35 0x32 0x34 0x34 0x32 0x31 0x33 0x35 0x34 , 0x35 0x33 0x36 0x36 0x33 0x34 0x2f 0x2f 0x36 ,0x38 0x35 0x37 0x36 0x32 0x36 0x34 0x38 0x37 , out U-Boot SPL 2023.10-rc4-armbian (Feb 10 2024 - 01:24:45 +0000) Trying to boot from MMC1 ## Checking hash(es) for config config-1 ... OK ## Checking hash(es) for Image atf-1 ... sha256+ OK ## Checking hash(es) for Image u-boot ... sha256+ OK ## Checking hash(es) for Image fdt-1 ... sha256+ OK ## Checking hash(es) for Image atf-2 ... sha256+ OK ## Checking hash(es) for Image atf-3 ... sha256+ OK ## Checking hash(es) for Image atf-4 ... sha256+ OK ## Checking hash(es) for Image atf-5 ... sha256+ OK ## Checking hash(es) for Image atf-6 ... sha256+ OK INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-607-gbf602aff1:cl NOTICE: BL31: Built : 10:16:03, Jun 5 2023 INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: pmu v1 is valid 220114 INFO: dfs DDR fsp_param[0].freq_mhz= 1056MHz INFO: dfs DDR fsp_param[1].freq_mhz= 324MHz INFO: dfs DDR fsp_param[2].freq_mhz= 528MHz INFO: dfs DDR fsp_param[3].freq_mhz= 780MHz INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0xa00000 INFO: SPSR = 0x3c9 U-Boot 2023.10-rc4-armbian (Feb 10 2024 - 01:24:45 +0000) Model: Rockchip RK3566 OPi 3B DRAM: 2 GiB PMIC: RK8090 (on=0x40, off=0x00) Core: 338 devices, 32 uclasses, devicetree: separate MMC: mmc@fe2b0000: 1, mmc@fe2c0000: 2, mmc@fe310000: 0 Loading Environment from nowhere... OK In: serial@fe660000 Out: serial@fe660000 Err: serial@fe660000 Model: Rockchip RK3566 OPi 3B Net: eth0: ethernet@fe010000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 ** Booting bootflow 'mmc@fe310000.bootdev.part_1' with script Boot script loaded from mmc 0:1 204 bytes read in 12 ms (16.6 KiB/s) 8023386 bytes read in 204 ms (37.5 MiB/s) 35062272 bytes read in 767 ms (43.6 MiB/s) 166117 bytes read in 54 ms (2.9 MiB/s) Working FDT set to a100000 Failed to load '/boot/dtb/rockchip/overlay/rk35xx-fixup.scr' Unknown command 'kaslrseed' - try 'help' Moving Image from 0x2080000 to 0x2200000, end=4420000 ## Loading init Ramdisk from Legacy Image at 0a200000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8023322 Bytes = 7.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 0a100000 Booting using the fdt blob at 0xa100000 Working FDT set to a100000 Loading Ramdisk to 7c71d000, end 7cec3d1a ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000007c68c000, end 000000007c71cfff ... OK Working FDT set to 7c68c000 Starting kernel ... Armbian_community 24.5.0-trunk.6 Bookworm ttyFIQ0 orangepi3b login:

The alpha version of Armbian images for R57 with kernel edge 6.15 is now available Kernel is powered by HW panfrost acceleration on Gnome (wayland) and on XFCE (x11). Please note that in this version, the primary settings are enabled on the UART console, and to use the keyboard, you need to log in as ROOT with the password 1234 https://disk.yandex.ru/d/1M9FUcTqn5kEOw offtopic Libreelec for Mekotronics R57 https://forum.libreelec.tv/thread/20823-unofficial-le-for-rk356x-rk3328-rk3399-rk3588-s-rk3576/?postID=199809#post199809 Armbian 25.04 Noble ttyS0 r57 login: root Password: ____ ____ _____ | _ \| ___|___ | | |_) |___ \ / / | _ < ___) |/ / |_| \_\____//_/ Welcome to Armbian 25.04 Noble with bleeding edge Linux 6.15.0-rc1-station-m3-p No end-user support: built from trunk System load: 23% Up time: 2 min Memory usage: 14% of 3.81G IP: 192.168.1.28 Usage of /: 36% of 14G [ 8 security updates available, 15 updates total: apt upgrade ] Last check: 2025-05-03 16:41 [ General system configuration (beta): armbian-config ] root@r57:~# neofetch -------- █ █ █ █ █ █ █ █ █ █ █ OS: Armbian (25.04) aarch64 ███████████████████████ Host: Blueberry RK3576 EDGE V10 Board ▄▄██ ██▄▄ Kernel: 6.15.0-rc1-station-m3-p ▄▄██ ███████████ ██▄▄ Uptime: 2 mins ▄▄██ ██ ██ ██▄▄ Packages: 1509 (dpkg) ▄▄██ ██ ██ ██▄▄ Shell: bash 5.2.21 ▄▄██ ██ ██ ██▄▄ Resolution: 1920x1080 ▄▄██ █████████████ ██▄▄ Terminal: /dev/ttyS0 ▄▄██ ██ ██ ██▄▄ CPU: (8) @ 2.208GHz ▄▄██ ██ ██ ██▄▄ Memory: 786MiB / 3900MiB ▄▄██ ██ ██ ██▄▄ ▄▄██ ██▄▄ ███████████████████████ █ █ █ █ █ █ █ █ █ █ █ root@r57:~#

Hello Everyone I have added Armbian for the Heltec HT-M2808 Helium Miner https://github.com/armbian/build/pull/6989#event-13647037453 https://heltec.org/project/ht-m2808/ To Compile ./compile.sh build BOARD=rk3328-heltec BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=no KERNEL_CONFIGURE=yes KERNEL_GIT=shallow RELEASE=bookworm You can obviously decide to go with a desktop environment (board has no HDMI) or use a different release. How to Flash 1) Install Rockchip Flash Tools 2) Download bootloader (rk3328_loader_ddr333_v1.16.250.bin) attached here. 3) Boot device into LOADER mode. Plug USB Cable in to back of the unit, powered off. On the back of the device. Use a small pin and hold the reset button (unit powered off) THEN insert the power cable while the reset button is pressed 4) Follow the flash procedure found here. Maskrom Pin If you get stuck and need to reflash, there's a good chance holding the reset button will not work to get back into LOADER mode. To boot directly to MASKROM, you can short this pin Needed 1) Wifi/BT does not work currently 2) SPI not recognized 3) LEDs not working 4) Likely other things, but the OS is 90% functional. rk3328_loader_ddr333_v1.16.250.bin

Hi, I wanted to install Armbian to my old Asus eee PC. So I made live USB containing the .iso and boot from there. I can login as root fine, but when running armbian-install, I only see the option of installing to sdb (my USB drive), but not to my sda (the laptop local drive). I am not sure what's the problem. Do I have to do something to the partition in sda? Currently Alpine Linux is installed in the local drive. Previous installation was Lubuntu (14, I think?). I want to run pi-hole and there are not many supported OSes for pi-hole that still support x86, so I would like to make it work. Armbian version: Armbian 25.5.1 Bookworm Minimal

I’m using an Android TV Box X96 X6. Right now, I want to find a way to install Armbian on it, but I haven’t been able to figure it out yet. I’d appreciate any help or guidance from the community.