Search the Community

Updated: The Armbian vendor kernel version now includes Panthor, and will soon be able to run it as well. Waydroid images: https://github.com/WillzenZou/armbian_fork_build/releases/download/willzen-armbian-24.5.0/2.waydroid-panthorv10-240416-v1.img.tar.gz Note: Waydroid needs to be run in the Wayland desktop environment. (Such as Gnome wayland, KDE wayland session) What's work: OpenGL ES is ok, I have tested some game: Mincecrat, gameSHINE, Monument Valley 2 What's not work: Vulkan. Video hardware decode and encode. How to use Waydroid 1. To install Waydroid, refer to the tutorial : https://docs.waydro.id/faq/using-custom-waydroid-images https://docs.waydro.id/usage/waydroid-command-line-options sudo apt install curl ca-certificates -y curl https://repo.waydro.id | sudo bash sudo apt install waydroid 2. Extract Waydroid system image waydroid-panthorv10-240416-v1.img.tar.gz to /usr/share/waydroid-extra/images and initialize it, there are system.img and vendor.img in it sudo waydroid init -f -i /usr/share/waydroid-extra/images 3. Other more useful parameters that need to be operated after waydroid session start Enable/disable multi-window: waydroid prop set persist.waydroid.multi_windows true waydroid prop set persist.waydroid.multi_windows false Install and start the app (also visible in the app menu after installation): waydroid app install com.app.apk waydroid app launch com.app List of apps: waydroid app list source code(needs morre work): https://github.com/WillzenZou/android_external_mesa3d

Hi, Like the topic says, both NICs are underperforming, they are connected to a Gb switch which I use and benched with other machines, neither iperf nor iperf3 (threaded and not threaded) go higher than 700Mbps. Another server plugged on the same switch reaches Gb steadily. I applied CPU affinity so both IRQ's are handled by the A76 cores but it makes no difference. OS: Armbian 24.5.5 Bookworm, uname -a: Linux geonosis 6.1.75-vendor-rk35xx #1 SMP Fri Jul 19 14:49:03 UTC 2024 aarch64 GNU/Linux There's not much running on the board for now.

Long story short, I accidentally removed all the contents of the /boot folder 😢. I'm running minimal Armbian 24.5.1 Bookworm with Linux 6.1.43-vendor-rk35xx on Orange pi 5 plus. It all started with a failed apt update indicating there wasn't enough space in the boot partition. The update was trying to install 6.1.75-vendor-rk35xx kernel, so I decided to remove the old one from the boot to free up some space. Instead, I accidentally applied 'rm -r' to the entire /boot folder. My SBC is working fine now, but I'm afraid it won't boot on next restart, so I'm looking for a way to recover the files. So far, I performed apt upgrade, which put the new 6.1.75-vendor-rk35xx kernel in the boot, but I'm not sure if it installed correctly - there was a warning that it couldn't be done automatically since there were no headers. I also copied armbianEnv.txt and boot.cmd from Armbian_24.5.3_Orangepi5-plus_bookworm_vendor_6.1.43_minimal.img so now armbianEnv.txt looks like below: verbosity=1 bootlogo=false console=both overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588-orangepi-5-plus.dtb rootdev=UUID=0af659d6-5b18-4106-9904-3ec2a1445b8a rootfstype=ext4 Finally I used u-boot-tools to make boot.scr: mkimage -C none -A arm -T script -d boot.cmd boot.scr Did I miss anything, or am I good to try restarting the SBC and see how it goes 😅? The original contents: total 74660 4 -rw-r--r-- 1 1003 1003 254 Jul 23 23:40 armbianEnv.txt 4 -rw-r--r-- 1 root root 1536 Sep 10 2023 armbian_first_run.txt.template 40 -rw-r--r-- 1 root root 38518 Sep 10 2023 boot.bmp 4 -rw-r--r-- 1 1003 1003 3820 Sep 10 2023 boot cmd 4 -rw-rw-r-- 1 root root 3892 Sep 10 2023 boot.scr 240 -rw-r--r-- 1 root root 243278 May 20 15:52 config-6.1.43-vendor-rk35xx 0 lrwxrwxrwx 1 root root 24 Jul 24 00:44 dtb -> dtb-6.1.43-vendor-rk35xx 4 drwxr-xr-x 3 root root 4096 Jun 12 12:21 dtb-5.10.160-legacy-rk35xx 4 drwxr-xr-x 3 root root 4096 Jun 17 20:40 dtb-6.1.43-vendor-rk35xx 0 lrwxrwxrwx 1 root root 28 Jul 24 00:44 Image -> vmlinuz-6.1.43-vendor-rk35xx 15452 -rw-r--r-- 1 root root 15816813 Jul 24 00:30 initrd.img-6.1.43-vendor-rk35xx 16 drwx------ 2 root root 16384 Sep 10 2023 lost+found 4 drwxr-xr-x 2 root root 4096 Feb 23 21:28 overlay-user 6836 -rw-r--r-- 1 root root 6998291 May 20 15:52 System.map-6.1.43-vendor-rk35xx 0 lrwxrwxrwx 1 root root 28 Jul 24 00:30 uInitrd -> uInitrd-6.1.43-vendor-rk35xx 15452 -rw-r--r-- 1 root root 15816877 Jul 24 00:30 uInitrd-6.1.43-vendor-rk35xx 36596 -rw-r--r-- 1 root root 37468672 May 20 15:52 vmlinuz-6.1.43-vendor-rk35xx After recover: total 74296 4 -rw-r--r-- 1 root root 181 Jul 25 01:14 armbianEnv.txt 0 -rw-r--r-- 1 root root 0 Jul 24 02:03 armbianEnv.txt.out 40 -rw-r--r-- 1 root root 38518 Jul 25 00:41 boot.bmp 8 -rw-r--r-- 1 root root 4159 Jul 25 00:13 boot.cmd 8 -rw-r--r-- 1 root root 4231 Jul 25 00:35 boot.scr 240 -rw-r--r-- 1 root root 243875 Jul 21 11:42 config-6.1.75-vendor-rk35xx 0 lrwxrwxrwx 1 root root 24 Jul 24 01:11 dtb -> dtb-6.1.75-vendor-rk35xx 4 drwxr-xr-x 3 root root 4096 Jul 24 01:11 dtb-6.1.75-vendor-rk35xx 0 lrwxrwxrwx 1 root root 28 Jul 24 01:12 Image -> vmlinuz-6.1.75-vendor-rk35xx 15460 -rw-r--r-- 1 root root 15827858 Jul 24 01:12 initrd.img-6.1.75-vendor-rk35xx 6756 -rw-r--r-- 1 root root 6917422 Jul 21 11:42 System.map-6.1.75-vendor-rk35xx 0 lrwxrwxrwx 1 root root 28 Jul 24 01:12 uInitrd -> uInitrd-6.1.75-vendor-rk35xx 15460 -rw-r--r-- 1 root root 15827922 Jul 24 01:12 uInitrd-6.1.75-vendor-rk35xx 36316 -rw-r--r-- 1 root root 37186048 Jul 21 11:42 vmlinuz-6.1.75-vendor-rk35xx

Hi all, Just want to share this issue i came across from my recently purchased OPI5+ 32GB version. I noticed it freezes when transferring .img from micro SD card to eMMC or NVMe drives via the command line. Now the img file are armbian OS and no its not the img file issue. at times I can get it to around 70seconds and it will freeze. hard reboot is required, unable to complete the transfer. I have also tried to reduce the bs=10 speed but still the same. Now i have also got the 16GB version and this works fine with no issues... Good chance there is something wrong with this latest hardware.. ? ?

After upgrading to kernel 6.10.1-edge-rockchip-rk3588 I started getting: fdee0000.hdmi_receiver: hdmirx_wait_lock_and_get_timing: HDMI pull out, return on the console. This repeats constantly and quite rapidly, and just doesn't stop. I can silence it by plugging a monitor into HDMI port, but... I prefer to run my board headless (serial + net). Does anybody know any other way to get rid of this? This "feature" was absent with the -rc7 kernel.

Hello everyone! I was struggling to make wiring work on OrangePi 5 Plus armbian. Tried everything and came up with a solution that worked for me. I was constantly getting these errors: wiringPiSetup: mmap (PWM) failed: Operation not permitted wiringPiSetup: mmap (GPIO) failed: Operation not permitted I'm on 23.8.2. 1. Install armbian and update apt sudo apt update 2. As stated in OrangePi5Plus wiki page I got .deb installer for wiringPi on OrangePi Now here's the link to this file: https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/cache/debs/arm64/wiringpi_2.51.deb 3. The most important step was described here: https://github.com/Joshua-Riek/ubuntu-rockchip/issues/273 echo "BOARD=orangepi5plus" | sudo tee /etc/orangepi-release Somehow this solves the issue. No idea how these things work tbh... 4. Check if pins are detected via gpio readall or add sudo sudo gpio readall You should get a table with all the pins and numbers like this: 5. Install wiringop-python just as stated in the manual: http://www.orangepi.org/orangepiwiki/index.php/Orange_Pi_5_Plus#How_to_install_wiringOP-Python # get the dependencies sudo apt-get update sudo apt-get -y install git swig python3-dev python3-setuptools # clone wiringOP-python repo, the branch should be "next" and NOT "main" or "master" git clone --recursive https://github.com/orangepi-xunlong/wiringOP-Python -b next cd wiringOP-Python git submodule update --init --remote python3 generate-bindings.py > bindings.i sudo python3 setup.py install The wiringOP-Python should be working now.

I bought a wifi dongle (for 3 pounds on ebay!) having a realtek chip 8821cu. There were some disconnects from time to time, and I was unable to find out why from the logs. Few days ago I installed and recompiled the realtek drivers from https://github.com/lwfinger/rtw88, got some new modules, replaced the modules in the directory /lib/modules/6.1.43-vendor-rk35xx/kernel/drivers/net/wireless/realtek/rtw88 Since then, I have no more disconnect. This may helps someone maybe.

So I was messing around with my new OrangePi-5+ and installed the EDK2 UEFI firmware for Rockchip RK3588 platforms onto the SPI flash (/dev/mtdblock0). After which I tried all sorts of images and kernels with varying success, only the 5.10.160-legacy-rk3588 kernel would really have a working display. Until I tried a generic UEFI arm64 image (Jammy-CLI on a USB stick) which gave a working display, albeit at 1080p max. (my monitor is 4K) with no acceleration (after the extra steps), and installed the Mate desktop (just my preference). The big caveat is that it does not recognize the SD-card, EMMC or SPI-flash, just regular drives (e.g. sda/nvme0n1 etc) and I'm sure a lot of other hardware isn't properly recognized either. But all of that was fixed by simply installing the old legacy kernel with apt, making a symbolic link to the correct dtb in /boot and updating grub, and a reboot later everything worked fine, the desktop popped up in 4K with acceleration and all. In the end I installed the whole thing to an NVME with armbian-config, which didn't create the separate EFI partition, so I had to corrected it manually, but that is another story. What surprises me is that the UEFI-arm64 kernel does not seem to need a Device-Tree-Blob, in fact it doesn't even boot with its own rk3588-orangepi-5-plus.dtb. Anyway if anyone want's to try this I'd suggest using Balena etcher to write the ED2K firmware onto an SD-card, and a generic UEFI armbian to an USB stick so you won't have to mess up anything permanently. Plug the stick in a USB2 port as it chokes during boot on the USB3 (blue) ports. And you will need a lot of patience as booting from a USB2 stick will be rather slow to say the least. Install legacy kernel: sudo apt update sudo apt install linux-image-legacy-rk35xx Create the symbolic link: (If you try this on another board or with another kernel version, you will need to adjust the link for the appropriate DTB instead) sudo ln -s /usr/lib/linux-image-5.10.160-legacy-rk35xx/rockchip/rk3588-orangepi-5-plus.dtb /boot/dtb-5.10.160-legacy-rk35xx Bonus tip, set the legacy kernel as a GRUB's default: (optional, adjust for different kernels) sudo echo 'GRUB_DEFAULT="Armbian GNU/Linux, with Linux 5.10.160-legacy-rk35xx"' > /etc/default/grub.d/99-legacy.cfg GRUB should now automatically pick up on the DTB after updating: sudo update-grub So far the only downside I have found is that the audio outputs are all labeled "Built-in Audio Stereo", which was easy to solve by adding some udev-rules as the Armbian build system does when building a regular OrangePi-5+ image.

I get this error on https://fi.mirror.armbian.de/dl/orangepi5-plus/archive/Armbian_24.5.3_Orangepi5-plus_bookworm_vendor_6.1.43_minimal.img.xz Jul 14 18:03:22 ek-arm kernel: ********************************************************** Jul 14 18:03:22 ek-arm kernel: ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE ** Jul 14 18:03:22 ek-arm kernel: ** ** Jul 14 18:03:22 ek-arm kernel: ** trace_printk() being used. Allocating extra memory. ** Jul 14 18:03:22 ek-arm kernel: ** ** Jul 14 18:03:22 ek-arm kernel: ** This means that this is a DEBUG kernel and it is ** Jul 14 18:03:22 ek-arm kernel: ** unsafe for production use. ** Jul 14 18:03:22 ek-arm kernel: ** ** Jul 14 18:03:22 ek-arm kernel: ** If you see this message and you are not debugging ** Jul 14 18:03:22 ek-arm kernel: ** the kernel, report this immediately to your vendor! ** Jul 14 18:03:22 ek-arm kernel: ** ** Jul 14 18:03:22 ek-arm kernel: ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE ** Jul 14 18:03:22 ek-arm kernel: ********************************************************** It is in the boot log. According to the message there is a problem to solve here.

Hi there, I've been trying to enable g_ether and USB OTG on my Orange PI 5+. I've tried things like editing /boot/orangepiEnv.txt and adding module-load dwc2,g_ether. However, I don't get any usb0 interface pop up which indicates to me that the USB/OTG mode is not set to peripheral on the settings. I'm not sure how to go about it? Would anyone be able to advise? I want to use the power port for also Ethernet.

Hello, I want to setup a Orange Pi 5 Plus to use a PCIe GPU to run games with. I can see that the GPU card is detected in lspci, but am not sure how to switch to it. I do have multiple old and new cards I can try if needed. Any advice would be appreciated.

RTL8852BE is the official recommended Wifi module for Orange Pie 5 PLUS, but it is not available in Armbian 24.5.1 Linux Vendor Kernel 6.1 without a driver module. Hope the official driver will be added to the 6.1 kernel. Thanks.

Hello Is it possible to install Emby Server in Orange Pi5 plus? Regards Hugo

Hello everybody. I own a Orange Pi 5 Plus with Debian and 3 partitions: boot, root and storage (fat, ext4, ext4). Now I want to try Armbian but I don't want to overwrite the storage partition, so I shoudn't use dd to write the .img file. Ant tip to solve this situation? Thanks.

Hi, I have installed Ubuntu Jammy on my Orange pi 5 plus board a while ago, I was wondering if I could upgrade to the new Noble release of armbian for OPI5 plus without having to reinstall the whole image and without breaking the system, I upgraded the kernel to the latest version with no issues, I just wanted to know the correct and safest way of upgrading the Noble release of Armbian. Thank you in advance.

I am using Orange Pi 5 Plus with eMMC. I tried to install a program I need, but an error occurred saying that installation was not possible because SecureBoot was disabled on the system. So I need to enable SecureBoot, how do I do that? Thank you.

Hi guys We're trying to run SPI with Linuxcnc. But sometimes SPI latency with other hardware (FPGA) gets big. The operating system is armbian and I could install a real-time kernel on it so I know it shouldn't be real-time issue with kernel. We've noticed that it might be the spidev driver issue that is not real-time. And now we're gonna communicate with low-level SPI. Bit I dont know how? can any one please help me?

Dear Armbian Community, I hope this message finds you well. I am encountering an issue with PWM on my Orange PI 5 Plus running Armbian. Despite my attempts, I am unable to utilize PWM via GPIO pins. Upon navigating to /sys/class/pwm, I can only see the pin designated for controlling the fan. The PWM pins on the GPIO are not visible. I have successfully controlled GPIO pins using WiringPi and Go Lang Periph libraries; however, when attempting to use PWM via GPIO, I encounter the following error: I have also checked the “hardware setup” screen in armbian-config, where I can see two hardware components listed, but PWMs are not among them. For your reference, here is the output of armbianmonitor -U: https://paste.armbian.com/uvejirijen.yaml I would greatly appreciate any guidance or assistance on how to resolve this issue and enable PWM functionality on my Orange PI 5 Plus. Thank you very much in advance for your help.

When connected to some PC monitors, the image is larger than the physical screen: about 20 pixels at the top and bottom sides, and 50 pixels at the right and left sides are missing. This happens as soon as the board boots (without logo), the start of lines are truncated, and this also happens on text ttys (Ctrl + Alt + F1..6). I guess it's about a boot env variable, but I could not find it.

Hello everyone I was trying to look for information in the forum but I can't find any topic where this specific issue is discussed. I also looked for help in the omv forum and they told me it was a problem with the distribution, hopefully you can help me. My system running Armbian_24.5.1_Orangepi5-plus_bookworm_vendor_6.1.43_minimal Install OMV, omv extras, i try to configure the compose folders and i get the 500 internal server error, clear cache, update and reboot system but there is no change, a moderator asked me for the log by executing the following command "Your error output is incomplete. What is the output of: sudo omv-salt deploy run compose" < orangepi5-plus: ---------- ID: configure_compose_scheduled_backup Function: file.managed Name: /etc/cron.d/omv-compose-backup Result: True Comment: File /etc/cron.d/omv-compose-backup is in the correct state Started: 13:23:54.827198 Duration: 788.193 ms Changes: ---------- ID: configure_compose_scheduled_update Function: file.managed Name: /etc/cron.d/omv-compose-update Result: True Comment: File /etc/cron.d/omv-compose-update is in the correct state Started: 13:23:55.616066 Duration: 741.905 ms Changes: ---------- ID: configure_compose_scheduled_prune Function: file.managed Name: /etc/cron.d/omv-compose-prune Result: True Comment: File /etc/cron.d/omv-compose-prune is in the correct state Started: 13:23:56.358647 Duration: 830.032 ms Changes: ---------- ID: configure_etc_docker_dir Function: file.directory Name: /etc/docker Result: True Comment: The directory /etc/docker is in the correct state Started: 13:23:57.189369 Duration: 5.514 ms Changes: ---------- ID: /etc/docker/daemon.json Function: file.serialize Result: True Comment: File /etc/docker/daemon.json updated Started: 13:23:57.195458 Duration: 325.608 ms Changes: ---------- diff: --- +++ @@ -1,3 +1,3 @@ { - "data-root": "/docker" + "data-root": "/var/lib/docker" } ---------- ID: docker_install_packages Function: pkg.installed Result: False Comment: An error was encountered while installing package(s): W: GPG error: http://armbian.tnahosting.net/apt bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 E: The repository 'http://apt.armbian.com bookworm InRelease' is not signed. Started: 13:24:03.303368 Duration: 30382.731 ms Changes: ---------- ID: docker_compose_install_packages Function: pkg.installed Result: True Comment: All specified packages are already installed Started: 13:24:33.686899 Duration: 67.916 ms Changes: ---------- ID: docker_purged_packages Function: pkg.purged Result: True Comment: None of the targeted packages are installed or partially installed Started: 13:24:33.755621 Duration: 4.062 ms Changes: ---------- ID: docker Function: service.running Result: False Comment: Failed to start docker.service: Unit docker.service not found. Started: 13:24:33.835516 Duration: 673.894 ms Changes: ---------- ID: /etc/systemd/system/docker.service.d/waitAllMounts.conf Function: file.managed Result: True Comment: File /etc/systemd/system/docker.service.d/waitAllMounts.conf is in the correct state Started: 13:24:34.510203 Duration: 306.575 ms Changes: ---------- ID: systemd_daemon_reload_docker Function: cmd.run Name: systemctl daemon-reload Result: True Comment: State was not run because none of the onchanges reqs changed Started: 13:24:34.822264 Duration: 0.026 ms Changes: ---------- ID: create_usr_local_bin_dir Function: file.directory Name: /usr/local/bin Result: True Comment: The directory /usr/local/bin is in the correct state Started: 13:24:34.822649 Duration: 5.271 ms Changes: ---------- ID: /usr/local/bin/docker-compose Function: file.symlink Result: True Comment: Symlink /usr/local/bin/docker-compose is present and owned by root:root Started: 13:24:34.828399 Duration: 17.703 ms Changes: Summary for orangepi5-plus ------------- Succeeded: 11 (changed=1) Failed: 2 ------------- Total states run: 13 Total run time: 34.149 s [ERROR ] Command 'apt-get' failed with return code: 100 [ERROR ] stdout: Get:1 file:/var/cache/openmediavault/archives InRelease Ign:1 file:/var/cache/openmediavault/archives InRelease Get:2 file:/var/cache/openmediavault/archives Release Ign:2 file:/var/cache/openmediavault/archives Release Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Get:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Get:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Get:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Get:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Get:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Get:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Get:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Contents (deb) Ign:4 file:/var/cache/openmediavault/archives Contents (deb) Get:5 file:/var/cache/openmediavault/archives Contents (deb) Ign:5 file:/var/cache/openmediavault/archives Contents (deb) Hit:6 http://deb.debian.org/debian bookworm InRelease Get:7 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB] Get:8 http://deb.debian.org/debian bookworm-backports InRelease [56.5 kB] Get:9 http://security.debian.org bookworm-security InRelease [48.0 kB] Get:10 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB] Get:11 http://httpredir.debian.org/debian bookworm-backports InRelease [56.5 kB] Hit:12 https://download.docker.com/linux/debian bookworm InRelease Hit:13 https://openmediavault.github.io/packages sandworm InRelease Hit:14 https://openmediavault-plugin-developers.github.io/packages/debian sandworm InRelease Hit:16 http://packages.openmediavault.org/public sandworm InRelease Get:15 http://armbian.tnahosting.net/apt bookworm InRelease [53.3 kB] Err:15 http://armbian.tnahosting.net/apt bookworm InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 Reading package lists... [ERROR ] stderr: W: GPG error: http://armbian.tnahosting.net/apt bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 E: The repository 'http://apt.armbian.com bookworm InRelease' is not signed. [ERROR ] retcode: 100 [ERROR ] An error was encountered while installing package(s): W: GPG error: http://armbian.tnahosting.net/apt bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 E: The repository 'http://apt.armbian.com bookworm InRelease' is not signed. [ERROR ] The named service docker is not available [ERROR ] Command '/usr/bin/systemd-run' failed with return code: 5 [ERROR ] stderr: Running scope as unit: run-r49a37263aed24bcf951c96199f63b03d.scope Failed to stop docker.service: Unit docker.service not loaded. [ERROR ] retcode: 5 [ERROR ] Command '/usr/bin/systemd-run' failed with return code: 5 [ERROR ] stderr: Running scope as unit: run-r56af566a7663456985ec54392976e370.scope Failed to start docker.service: Unit docker.service not found. [ERROR ] retcode: 5 [ERROR ] Failed to start docker.service: Unit docker.service not found. root@orangepi5-plus:~# > *****"the plugin can't fix this. Your armbian repos are broken because either the gpg key is missing or your system time is off. I don't know how it could the former on a fresh install."****** and he mentions to me that the repo is having problems due to lack of a gpg key and that he doesn't know how to fix it; I tested kernel 6.8 I could configure the docker compose well, but the USB and HDD fans had failures randomly if someone could guide me to find a solution because so far it is the only kernel that has worked with all the hardware available in the sbc. 👀

I must be doing something stupid. After having switched the branch "Multimedia" as M, no module are generated at all and I end up with error like: 🔨] ERROR: modpost: "dma_contiguous_default_area" [drivers/media/common/videobuf2/videobuf2-cma-sg.ko] undefined! [🔨] ERROR: modpost: "cma_release" [drivers/media/common/videobuf2/videobuf2-cma-sg.ko] undefined! [🔨] ERROR: modpost: "cma_alloc" [drivers/media/common/videobuf2/videobuf2-cma-sg.ko] undefined! Reading documentation to buld armbian, it only mention docker. I have been (last year) generating kernel on the machine itself (the orange pi 5 plus), this is not supported? thanks.

Hi all I hava an orange pi 5 plus with a 512GO NVME SSD. I have installed the latest version od Armbian to a SD card it work well, but for speed reason i would like to install the OS to th SSD drive and boot from this device and no longer from the SD card. Is there a way to do this ? i mean from u-boot point of view? i can keep a SD card inside it to store u boot but i would like to move usr var and such to SSD Thanks in advance for your answers comment or ideas W.

I've done quite a bit of searching and can't find anyone else reporting this specific issue. As the title says any 6.8 image I try fails to boot. The LED is red for approx 4 seconds, turns green for 2 or 3 seconds, and then turns red again and stays that way no matter how long I wait. There is never any video regardless of which HDMI port I use. I've tried the following images: Armbian_24.8.0-trunk.85_Orangepi5-plus_noble_edge_6.8.12_gnome-oibaf_desktop.img.xz Armbian_24.5.1_Orangepi5-plus_noble_edge_6.8.10_gnome-oibaf_desktop.img.xz Armbian_24.5.1_Orangepi5-plus_noble_edge_6.8.10_xfce_desktop.img.xz Armbian_24.5.1_Orangepi5-plus_bookworm_edge_6.8.10_cinnamon_desktop.img.xz 6.1 images work fine. I get the immediate blinking purple-ish indicator and video with the middle HDMI port. Armbian_24.5.1_Orangepi5-plus_bookworm_vendor_6.1.43_cinnamon_desktop.img.xz Armbian_24.5.1_Orangepi5-plus_bookworm_vendor_6.1.43_minimal.img.xz The closest thing to my problem I could find was this I'm aware these folks are using 5B not 5 Plus but I went ahead and tried this anyway unplugging the HDMI to see if it would boot. That didn't work either. I know sometimes certain image writers work while others don't. I've tried writing these images in balena etcher, rufus, and raspberry pi writer. This doesn't seem to effect the situation. Any help would be greatly appreciated. Thank you!

I installed latest vendor image and because of the wifi issues I switched to the edge kernel. I messed up my fstab, couldn't connect with ssh, so I plugged it to my monitor and a keyboard, but there was no video. Eventually, I fixed it by booting vendor image from my sd card, but I got curious. I know, that vendor image just works, so I flashed edge image to my sd card to see what's wrong. The monitor recognizes the presence of the board, but it's just a black screen. I can ssh to the board, so the image definitely booted, but there's just no video. Here's the log from my original installation. I kept 6.8 kernel because the video is not important to me.

After looking at this message from @Seb042 I thought it would be better to open a new topic to discuss this. From what I saw from my install: $ dmesg ... [ 6.166453] iwlwifi 0002:21:00.0: api flags index 2 larger than supported by driver [ 6.166480] iwlwifi 0002:21:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28 [ 6.167021] iwlwifi 0002:21:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm [ 6.267334] iwlwifi 0002:21:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [ 6.273748] iwlwifi 0002:21:00.0: reporting RF_KILL (radio disabled) [ 6.450150] iwlwifi 0002:21:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x1f [ 6.450175] iwlwifi 0002:21:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f [ 6.450189] iwlwifi 0002:21:00.0: WFPM_AUTH_KEY_0: 0x90 [ 6.450206] iwlwifi 0002:21:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0 [ 6.450997] iwlwifi 0002:21:00.0: Detected RF GF, rfid=0x10d000 [ 6.517606] iwlwifi 0002:21:00.0: base HW address: ab:cd:ef:01:23:45 [ 6.571168] iwlwifi 0002:21:00.0 wlP2p33s0: renamed from wlan0 ... I had the same error, with the same chip (AX210). I looked for each of the message and maybe, and this is just an assumption, we, AX201 users, will have to wait until the the driver is updated for the 6.7 line? Is that right?