Orange Pi 5 Plus Latest Topics

Orange Pi 5 Plus – Armbian image fails to boot from both TF card and eMMC, while Joshua Riek's Ubuntu image boots fine

Tue, 11 Aug 2026 03:19:01 +0000

Board: Orange Pi 5 Plus (RK3588)
Armbian image used: Downloaded from https://armbian.cn/boards/orangepi5-plus (Ubuntu 26.04, .img format)
Comparison image: Joshua Riek's Ubuntu for Rockchip – https://joshua-riek.github.io/ubuntu-rockchip-download/boards/orangepi-5-plus.html
Problem Description
I downloaded the Armbian image for Orange Pi 5 Plus from the official Armbian page and flashed it to both a TF card and eMMC. The board fails to boot in either case. However, when I flash Joshua Riek's Ubuntu image using the exact same methods, the board boots successfully without any issues.
I have compared the partition layouts of both images and found them to be essentially identical:
Both use a single ext4 partition scheme.
Both leave approximately 16 MB of unallocated space before the ext4 partition (which is where the RK3588 BootROM expects to find the bootloader at the 32 KB and 8 MB offsets).
Both contain the necessary .dtb files and kernel inside the /boot directory of the ext4 partition.
Given that the partition structures are the same, I am unable to understand why one image boots and the other does not.
What I Have Tried
Flashed the Armbian image to a TF card using balenaEtcher – The board does not boot (no display output, no serial console activity).
Flashed the Armbian image to eMMC using RKDevTool – The board does not boot.
Flashed Joshua Riek's Ubuntu image to a TF card using balenaEtcher – Boots successfully.
Flashed Joshua Riek's Ubuntu image to eMMC using RKDevTool – Boots successfully.
Erased the SPI Flash – I have already cleared the onboard SPI Flash to rule out any interference from a previously installed bootloader. This was done using the following command from within the working Ubuntu system:
sudo dd if=/dev/zero of=/dev/mtdblock0 bs=1M count=4
After erasing, the Armbian image still fails to boot from both TF card and eMMC.
Compared partition tables – Both images show the same layout: ~16 MB of unallocated space before the ext4 partition. I have verified that the partition start offsets are identical.
My Analysis
Since the SPI Flash has been erased and both images share the same partition structure, the issue likely lies in one of the following areas:
The bootloader data in the pre-partition area (the first 16 MB) may be missing or invalid in the Armbian image. The RK3588 BootROM looks for the first-stage bootloader (idbloader) at the 32 KB offset and the second-stage bootloader (u-boot.itb) at the 8 MB offset. It is possible that the Armbian image does not contain valid data at these offsets, while Joshua Riek's image does.
The bootloader format or signing may be incompatible. Even if data exists at the correct offsets, it might not conform to what the RK3588 BootROM expects (e.g., missing Rockchip header, incorrect signing, or wrong image format).
The Armbian image may use a different boot flow (e.g., expecting to chain-load from a FAT32 boot partition) that does not match the Orange Pi 5 Plus hardware boot sequence.
Questions
Does the Armbian image for Orange Pi 5 Plus include a valid idbloader and u-boot at the correct offsets (32 KB and 8 MB) within the pre-partition area?
Is there any additional step required to make the Armbian image bootable on Orange Pi 5 Plus, such as manually writing a bootloader or running a setup script after flashing?
Is the Armbian image for this board known to work when flashed via balenaEtcher or RKDevTool, or is a different flashing method required?
Environment
Board: Orange Pi 5 Plus (RK3588)
Armbian image: Ubuntu 26.04 from https://armbian.cn/boards/orangepi5-plus
Flashing tools used: balenaEtcher (for TF card), RKDevTool (for eMMC)
SPI Flash status: Erased (confirmed)
Comparison image: Joshua Riek's Ubuntu for Rockchip (boots successfully with the same tools and methods)
Any help or guidance would be greatly appreciated. I am happy to provide additional logs or hex dumps of the boot area if needed.

HDMI audio and analog audio do not work on Opi5Plus

Mon, 26 May 2025 01:01:33 +0000

I have built and used it with the latest source and still HDMI audio and analog audio does not work.

Is there any way to get HDMI audio to work other than using the vendor kernel?

Orange Pi 5 Plus (16GB) hard crashes during transcoding of HEVC 4K HDR10 video in Jellyfin

Wed, 18 Feb 2026 22:36:29 +0000

I am running Ubuntu 24.04 Noble (Armbian Linux 6.1.115-vendor-rk35xx) and no additional packages affecting VPU performance have been installed; everything is stock. Jellyfin is running in Docker, and transcoding works perfectly, except for some movies.

I tried to play a 4K video in Chrome (native HEVC support), set the bitrate to 40mbps, and the video played normally at a transcoding speed of about 3x, but after a while, Orange Pi crashed. In Firefox inside neko (where there is no hardware acceleration and HEVC), the crash happened even faster, after ~2 seconds of playback.

The crash happens as if the board loses power: journalctl is not saved, nothing is visible via ssh. I use a 100W Baseus GaN Pro Desktop Power Strip (model CCGAN100-1ACE) and the Orange Pi is the only device connected to it. I also have a 100W cable that shows the current consumption in watts. During transcoding, it showed 10, and then the board hard rebooted again, so I don't think this is related to power issues.

Before that, I used Ubuntu 24.04 from Joshua Riek, and there was a problem with the Mali driver crashing under heavy load or simply after a while. A similar hard reboot also occurred if the driver was “too slow” to crash.

Here is Jellyfin's video info:

Spoiler

Video
Title: Deepwater Horizon (2016) - 4K - HEVC - Dolby Vision Profile 8.1 (HDR10)
Codec: HEVC
AVC: No
Profile: Main 10
Level: 153
Resolution: 3840x2160
Aspect ratio: 16:9
Anamorphic: No
Interlaced: No
Framerate: 23.976025
Bitrate: 97917 kbps
Bit depth: 10 bit
Video range: HDR
Video range type: DOVIWithHDR10
DV title: Dolby Vision Profile 8.1 (HDR10)
DV version major: 1
DV version minor: 0
DV profile: 8
DV level: 6
DV rpu preset flag: 1
DV el preset flag: 0
DV bl preset flag: 1
DV bl signal compatibility id: 1
Color space: bt2020nc
Color transfer: smpte2084
Color primaries: bt2020
Pixel format: yuv420p10le
Ref frames: 1

ffprobe:

Spoiler

  Stream #0:0(eng): Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x2160 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn (default)
    Metadata:
      title           : Deepwater Horizon (2016)
      BPS             : 76184352
      DURATION        : 01:47:19.350000000
      NUMBER_OF_FRAMES: 154390
      NUMBER_OF_BYTES : 61322213457
      _STATISTICS_WRITING_APP: mkvmerge v67.0.0 ('Under Stars') 64-bit
      _STATISTICS_WRITING_DATE_UTC: 2022-05-17 10:46:34
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
    Side data:
      DOVI configuration record: version: 1.0, profile: 8, level: 6, rpu flag: 1, el flag: 0, bl flag: 1, compatibility id: 1

I also have a 4 GB model of Orange Pi 5 (not B), and there were no problems with transcoding this video; it was just slow due to the small amount of RAM.

I don't even know where to start. What should I do to at least understand the cause of this issue?

opi 5 plus using the Armbian OS

Thu, 19 Feb 2026 11:01:00 +0000

i recently purchased an orange pi 5 plus 16gb with the wifi / bt card, the aluminum wifi case, fan and 1tb ssd. when i go to the official website i see different images there none of which seem to work 100%. i mean i was able to get each up and running but what i noticed is that the graphical drivers would not load. i saw a youtube video claiming armbian has the right driver support for the mali 610 gpu. can someone assist me getting this to work? im big into emulation gaming and right now it doesnt even have Vulkan support i crave. someone help thanks

Thank you!

Wed, 02 Sep 2026 01:38:54 +0000

I was able to install the latest Armbian/Ubuntu-Resolute 26.8.3 image on my Orange Pi 5 Plus without a lot of fanfare. It took a bit of hunting around to find the correct process to get the image written to an SD card with the new Armbian Imager and then push that image to my emmc storage after it booted, but it was rather painless otherwise. It seems to work without any issues on my 2.5GB/10GB network and is acting as my home Jellyfin media server for now. It was doing that before running Ubuntu 24.04 with a an older 6.1 kernel from the vendor. Zero complaints with the old setup, but I wanted a newer and better supported kernel build given all the excitement around the AI-enabled hacker juggernaut.

Ok, so now for my question. The kernel appears to be:

Linux orangepi5-plus 6.18.44-current-rockchip64 #1 SMP PREEMPT Sun Aug 9 18:25:30 UTC 2026 aarch64 GNU/Linux

whereas the current kernel for my X86/Ryzen 9950x ubuntu box running Ubuntu 26.04 is:

Linux myhost 7.0.0-30-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 31 18:22:54 UTC 2026 x86_64 GNU/Linux

I was wondering why the arm64 systems are not moving up to the version 7 kernel. Not a complaint....just curious.

Very happy with how things are working. Well done by everyone who worked on this!

---snip---

v26.8.3 for Orange Pi 5 Plus running Armbian Linux 6.18.44-current-rockchip64

Packages: Ubuntu stable (resolute)
IPv4: (redacted)

Performance:

Load: 1% Uptime: 13h 57m
Memory usage: 10% of 15.43G
CPU temp: 39°C Usage of /: 4% of 229G

Best,

Kernel vendor or current

Wed, 03 Jun 2026 17:52:44 +0000

I'm using Armbian Orange Pi 5 Plus based on Debian 13 with vendor kernel

 v26.2.1 for Orange Pi 5 Plus running Armbian Linux 6.1.115-vendor-rk35xx

I'm thinking about switching to Armbian based on Debian 13 with kernel current 6.18.33 because 6.1.115 is an old one => current the kernel is more recent

Is that a good idea to swith to vendor kernel to current ?

How can I do this ?

Armbian_25.11.1_Orangepi5-plus_trixie_current_6.12.58_minimal.img does not boot

Sun, 08 Mar 2026 08:03:52 +0000

Dear team,

On Armbian_25.11.1_Orangepi5-plus_trixie_current_6.12.58_minimal.img
not possible to boot kernel, only u-boot seems available ?

Bellow is the debug log on tty

DDR V1.13 25cee80c4f cym 23/08/11-09:31:58
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB
Manufacturer ID:0xff
CH0 RX Vref:28.5%, TX Vref:22.8%,21.8%
CH1 RX Vref:27.1%, TX Vref:21.8%,21.8%
CH2 RX Vref:27.9%, TX Vref:21.8%,21.8%
CH3 RX Vref:28.5%, TX Vref:20.8%,20.8%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09-orangepi (Nov 15 2023 - 16:53:25)
Trying to boot from MMC1
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(7612223b82...) + OK
## Checking u-boot 0x00a00000 ... sha256(e17d8b540a...) + OK
## Checking fdt-1 0x00ad1370 ... sha256(5411c775cf...) + OK
## Checking atf-2 0x000f0000 ... sha256(b2af21b504...) + OK
## Checking atf-3 0xff100000 ... sha256(70505bb764...) + OK
Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000)
Total: 719.759 ms

....and nothing

I also changed the verbosity level in /boot/armbianEnv.txt, but
without success!

Thanks in advance for your help

Armbian Build Failure

Fri, 31 Jul 2026 20:08:43 +0000

I am trying to build armbian image via WSL 2, as I have done hundreds of times in the past. I ensured that the wsl2 distro (Ubuntu) was up to date via apt update and apt upgrade, and ran git pull was issued within /build folder prior to issuing ./compile.sh.

Several files failed to download during the build including:

[💲|🔨] E: Failed to fetch http://security.debian.org/dists/trixie-security/main/binary-arm64/Packages 404 Not Found [IP: 151.101.130.132 80]
[💲|🔨] E: Failed to fetch http://deb.debian.org/debian/dists/trixie/main/i18n/Translation-en 404 Not Found [IP: 151.101.130.132 80]
[💲|🔨] E: Failed to fetch http://deb.debian.org/debian/dists/trixie-updates/main/binary-arm64/Packages 404 Not Found [IP: 151.101.130.132 80]
[💲|🔨] E: Failed to fetch http://deb.debian.org/debian/dists/trixie-backports/main/binary-arm64/Packages 404 Not Found [IP: 151.101.130.132 80]

...

[💲|🔨] E: Some index files failed to download. They have been ignored, or old ones used instead.
[💲|🚸] Command failed, retrying in 5s [ chroot_sdcard_apt_get_update ]
[💲|🔨] Get:1 http://deb.debian.org/debian trixie InRelease [140 kB]
[💲|🔨] Get:2 http://security.debian.org trixie-security InRelease [43.4 kB]
[💲|🔨] Hit:3 http://github.armbian.com/configng stable InRelease
[💲|🔨] Get:4 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB]
[💲|🔨] Get:5 http://deb.debian.org/debian trixie-backports InRelease [54.0 kB]
[💲|🔨] Get:6 http://security.debian.org trixie-security/main arm64 Packages [231 kB]
[💲|🔨] Get:7 http://security.debian.org trixie-security/main Translation-en [140 kB]
[💲|🔨] Get:8 http://security.debian.org trixie-security/non-free-firmware Translation-en [352 B]
[💲|🔨] Err:6 http://security.debian.org trixie-security/main arm64 Packages
[💲|🔨] Could not change permissions for temporary file /var/lib/apt/lists/partial/security.debian.org_dists_trixie-security_main_binary-arm64_Packages.nhGqj8 - fchmod (1: Operation not permitted)
[💲|🔨] Ign:7 http://security.debian.org trixie-security/main Translation-en
[💲|🔨] Ign:8 http://security.debian.org trixie-security/non-free-firmware Translation-en
[💲|🔨] Ign:6 http://security.debian.org trixie-security/main arm64 Packages
[💲|🔨] Ign:7 http://security.debian.org trixie-security/main Translation-en
[💲|🔨] Ign:8 http://security.debian.org trixie-security/non-free-firmware Translation-en
[💲|🔨] Err:6 http://security.debian.org trixie-security/main arm64 Packages
[💲|🔨] 404 Not Found [IP: 151.101.130.132 80]
[💲|🔨] Ign:7 http://security.debian.org trixie-security/main Translation-en
[💲|🔨] Ign:8 http://security.debian.org trixie-security/non-free-firmware Translation-en
[💲|🔨] Get:9 http://deb.debian.org/debian trixie/main arm64 Packages [9607 kB]
[💲|🔨] Ign:9 http://deb.debian.org/debian trixie/main arm64 Packages
[💲|🔨] Get:10 http://deb.debian.org/debian trixie/main Translation-en [6484 kB]
[💲|🔨] Ign:10 http://deb.debian.org/debian trixie/main Translation-en
[💲|🔨] Get:11 http://deb.debian.org/debian trixie/main all Contents (deb) [37.7 MB]
[💲|🔨] Ign:11 http://deb.debian.org/debian trixie/main all Contents (deb)
[💲|🔨] Get:12 http://deb.debian.org/debian trixie/main arm64 Contents (deb) [12.6 MB]
[💲|🔨] Get:13 http://deb.debian.org/debian trixie/contrib arm64 Packages [48.4 kB]
[💲|🔨] Get:14 http://deb.debian.org/debian trixie/contrib Translation-en [49.6 kB]
[💲|🔨] Ign:12 http://deb.debian.org/debian trixie/main arm64 Contents (deb)
[💲|🔨] Get:15 http://deb.debian.org/debian trixie/contrib arm64 Contents (deb) [115 kB]
[💲|🔨] Get:16 http://deb.debian.org/debian trixie/contrib all Contents (deb) [134 kB]
[💲|🔨] Get:17 http://deb.debian.org/debian trixie/non-free arm64 Packages [74.4 kB]
[💲|🔨] Get:18 http://deb.debian.org/debian trixie/non-free Translation-en [67.1 kB]
[💲|🔨] Get:19 http://deb.debian.org/debian trixie/non-free arm64 Contents (deb) [45.3 kB]
[💲|🔨] Ign:13 http://deb.debian.org/debian trixie/contrib arm64 Packages
[💲|🔨] Get:20 http://deb.debian.org/debian trixie/non-free all Contents (deb) [831 kB]
[💲|🔨] Get:21 http://deb.debian.org/debian trixie/non-free-firmware arm64 Packages [6484 B]
[💲|🔨] Get:22 http://deb.debian.org/debian trixie/non-free-firmware Translation-en [4704 B]
[💲|🔨] Get:23 http://deb.debian.org/debian trixie/non-free-firmware all Contents (deb) [27.0 kB]
[💲|🔨] Get:24 http://deb.debian.org/debian trixie/non-free-firmware arm64 Contents (deb) [288 B]
[💲|🔨] Get:25 http://deb.debian.org/debian trixie-updates/main arm64 Packages [4424 B]
[💲|🔨] Get:26 http://deb.debian.org/debian trixie-updates/main Translation-en [2496 B]
[💲|🔨] Get:27 http://deb.debian.org/debian trixie-updates/main arm64 Contents (deb) [9913 B]
[💲|🔨] Get:28 http://deb.debian.org/debian trixie-updates/main all Contents (deb) [25.5 kB]
[💲|🔨] Ign:14 http://deb.debian.org/debian trixie/contrib Translation-en
[💲|🔨] Ign:15 http://deb.debian.org/debian trixie/contrib arm64 Contents (deb)
[💲|🔨] Ign:16 http://deb.debian.org/debian trixie/contrib all Contents (deb)
[💲|🔨] Ign:17 http://deb.debian.org/debian trixie/non-free arm64 Packages
[💲|🔨] Ign:18 http://deb.debian.org/debian trixie/non-free Translation-en
[💲|🔨] Ign:19 http://deb.debian.org/debian trixie/non-free arm64 Contents (deb)
[💲|🔨] Ign:20 http://deb.debian.org/debian trixie/non-free all Contents (deb)
[💲|🔨] Ign:21 http://deb.debian.org/debian trixie/non-free-firmware arm64 Packages
[💲|🔨] Ign:22 http://deb.debian.org/debian trixie/non-free-firmware Translation-en
[💲|🔨] Ign:23 http://deb.debian.org/debian trixie/non-free-firmware all Contents (deb)
[💲|🔨] Ign:24 http://deb.debian.org/debian trixie/non-free-firmware arm64 Contents (deb)
[💲|🔨] Ign:25 http://deb.debian.org/debian trixie-updates/main arm64 Packages
[💲|🔨] Ign:26 http://deb.debian.org/debian trixie-updates/main Translation-en
[💲|🔨] Ign:27 http://deb.debian.org/debian trixie-updates/main arm64 Contents (deb)
[💲|🔨] Ign:28 http://deb.debian.org/debian trixie-updates/main all Contents (deb)
[💲|🔨] Get:9 http://deb.debian.org/debian trixie/main arm64 Packages [13.2 MB]
[💲|🔨] Get:29 http://deb.debian.org/debian trixie-backports/main arm64 Packages [317 kB]
[💲|🔨] Ign:9 http://deb.debian.org/debian trixie/main arm64 Packages
[💲|🔨] Get:30 http://deb.debian.org/debian trixie-backports/main Translation-en [227 kB]
[💲|🔨] Ign:29 http://deb.debian.org/debian trixie-backports/main arm64 Packages
[💲|🔨] Ign:30 http://deb.debian.org/debian trixie-backports/main Translation-en
[💲|🔨] Get:31 http://deb.debian.org/debian trixie-backports/main arm64 Contents (deb) [9012 kB]
[💲|🔨] Ign:31 http://deb.debian.org/debian trixie-backports/main arm64 Contents (deb)
[💲|🔨] Get:32 http://deb.debian.org/debian trixie-backports/main all Contents (deb) [6272 kB]
[💲|🔨] Get:33 http://deb.debian.org/debian trixie-backports/contrib arm64 Packages [7236 B]
[💲|🔨] Get:34 http://deb.debian.org/debian trixie-backports/contrib Translation-en [7184 B]
[💲|🔨] Ign:32 http://deb.debian.org/debian trixie-backports/main all Contents (deb)
[💲|🔨] Get:35 http://deb.debian.org/debian trixie-backports/contrib all Contents (deb) [23.6 kB]
[💲|🔨] Get:36 http://deb.debian.org/debian trixie-backports/contrib arm64 Contents (deb) [22.9 kB]
[💲|🔨] Get:37 http://deb.debian.org/debian trixie-backports/non-free arm64 Packages [7308 B]
[💲|🔨] Get:38 http://deb.debian.org/debian trixie-backports/non-free Translation-en [6384 B]
[💲|🔨] Get:39 http://deb.debian.org/debian trixie-backports/non-free arm64 Contents (deb) [6515 B]
[💲|🔨] Get:40 http://deb.debian.org/debian trixie-backports/non-free all Contents (deb) [35.1 kB]
[💲|🔨] Get:41 http://deb.debian.org/debian trixie-backports/non-free-firmware arm64 Packages [6484 B]
[💲|🔨] Get:42 http://deb.debian.org/debian trixie-backports/non-free-firmware Translation-en [4372 B]
[💲|🔨] Get:43 http://deb.debian.org/debian trixie-backports/non-free-firmware all Contents (deb) [36.6 kB]
[💲|🔨] Get:44 http://deb.debian.org/debian trixie-backports/non-free-firmware arm64 Contents (deb) [184 B]
[💲|🔨] Ign:33 http://deb.debian.org/debian trixie-backports/contrib arm64 Packages
[💲|🔨] Ign:34 http://deb.debian.org/debian trixie-backports/contrib Translation-en
[💲|🔨] Get:10 http://deb.debian.org/debian trixie/main Translation-en [34.8 MB]
[💲|🔨] Ign:35 http://deb.debian.org/debian trixie-backports/contrib all Contents (deb)
[💲|🔨] Get:10 http://deb.debian.org/debian trixie/main Translation-en [34.8 MB]
[💲|🔨] Ign:36 http://deb.debian.org/debian trixie-backports/contrib arm64 Contents (deb)
[💲|🔨] Get:10 http://deb.debian.org/debian trixie/main Translation-en [34.8 MB]
[💲|🔨] Ign:37 http://deb.debian.org/debian trixie-backports/non-free arm64 Packages
[💲|🔨] Ign:38 http://deb.debian.org/debian trixie-backports/non-free Translation-en
[💲|🔨] Ign:10 http://deb.debian.org/debian trixie/main Translation-en
[💲|🔨] Ign:39 http://deb.debian.org/debian trixie-backports/non-free arm64 Contents (deb)
[💲|🔨] Ign:11 http://deb.debian.org/debian trixie/main all Contents (deb)
[💲|🔨] Ign:12 http://deb.debian.org/debian trixie/main arm64 Contents (deb)
[💲|🔨] Ign:14 http://deb.debian.org/debian trixie/contrib Translation-en
[💲|🔨] Ign:15 http://deb.debian.org/debian trixie/contrib arm64 Contents (deb)
[💲|🔨] Ign:16 http://deb.debian.org/debian trixie/contrib all Contents (deb)
[💲|🔨] Ign:18 http://deb.debian.org/debian trixie/non-free Translation-en
[💲|🔨] Ign:19 http://deb.debian.org/debian trixie/non-free arm64 Contents (deb)
[💲|🔨] Ign:20 http://deb.debian.org/debian trixie/non-free all Contents (deb)
[💲|🔨] Ign:40 http://deb.debian.org/debian trixie-backports/non-free all Contents (deb)
[💲|🔨] Ign:22 http://deb.debian.org/debian trixie/non-free-firmware Translation-en
[💲|🔨] Ign:41 http://deb.debian.org/debian trixie-backports/non-free-firmware arm64 Packages
[💲|🔨] Ign:42 http://deb.debian.org/debian trixie-backports/non-free-firmware Translation-en
[💲|🔨] Ign:43 http://deb.debian.org/debian trixie-backports/non-free-firmware all Contents (deb)
[💲|🔨] Ign:44 http://deb.debian.org/debian trixie-backports/non-free-firmware arm64 Contents (deb)
[💲|🔨] Ign:23 http://deb.debian.org/debian trixie/non-free-firmware all Contents (deb)
[💲|🔨] Ign:13 http://deb.debian.org/debian trixie/contrib arm64 Packages
[💲|🔨] Ign:24 http://deb.debian.org/debian trixie/non-free-firmware arm64 Contents (deb)
[💲|🔨] Ign:25 http://deb.debian.org/debian trixie-updates/main arm64 Packages
[💲|🔨] Ign:26 http://deb.debian.org/debian trixie-updates/main Translation-en
[💲|🔨] Ign:17 http://deb.debian.org/debian trixie/non-free arm64 Packages
[💲|🔨] Ign:21 http://deb.debian.org/debian trixie/non-free-firmware arm64 Packages
[💲|🔨] Ign:27 http://deb.debian.org/debian trixie-updates/main arm64 Contents (deb)
[💲|🔨] Ign:28 http://deb.debian.org/debian trixie-updates/main all Contents (deb)
[💲|🔨] Ign:9 http://deb.debian.org/debian trixie/main arm64 Packages
[💲|🔨] Ign:29 http://deb.debian.org/debian trixie-backports/main arm64 Packages
[💲|🔨] Ign:30 http://deb.debian.org/debian trixie-backports/main Translation-en
[💲|🔨] Ign:31 http://deb.debian.org/debian trixie-backports/main arm64 Contents (deb)
[💲|🔨] Ign:32 http://deb.debian.org/debian trixie-backports/main all Contents (deb)
[💲|🔨] Ign:33 http://deb.debian.org/debian trixie-backports/contrib arm64 Packages
[💲|🔨] Ign:34 http://deb.debian.org/debian trixie-backports/contrib Translation-en
[💲|🔨] Ign:35 http://deb.debian.org/debian trixie-backports/contrib all Contents (deb)
[💲|🔨] Ign:36 http://deb.debian.org/debian trixie-backports/contrib arm64 Contents (deb)
[💲|🔨] Ign:37 http://deb.debian.org/debian trixie-backports/non-free arm64 Packages
[💲|🔨] Ign:38 http://deb.debian.org/debian trixie-backports/non-free Translation-en
[💲|🔨] Err:10 http://deb.debian.org/debian trixie/main Translation-en
[💲|🔨] Could not change permissions for temporary file /var/lib/apt/lists/partial/deb.debian.org_debian_dists_trixie_main_i18n_Translation-en.6lDWKP - fchmod (1: Operation not permitted)
[💲|🔨] 404 Not Found [IP: 151.101.130.132 80]
[💲|🔨] Ign:39 http://deb.debian.org/debian trixie-backports/non-free arm64 Contents (deb)
[💲|🔨] Ign:11 http://deb.debian.org/debian trixie/main all Contents (deb)
[💲|🔨] Ign:12 http://deb.debian.org/debian trixie/main arm64 Contents (deb)
[💲|🔨] Ign:14 http://deb.debian.org/debian trixie/contrib Translation-en
[💲|🔨] Ign:15 http://deb.debian.org/debian trixie/contrib arm64 Contents (deb)
[💲|🔨] Ign:16 http://deb.debian.org/debian trixie/contrib all Contents (deb)
[💲|🔨] Ign:18 http://deb.debian.org/debian trixie/non-free Translation-en
[💲|🔨] Ign:19 http://deb.debian.org/debian trixie/non-free arm64 Contents (deb)
[💲|🔨] Ign:20 http://deb.debian.org/debian trixie/non-free all Contents (deb)
[💲|🔨] Ign:40 http://deb.debian.org/debian trixie-backports/non-free all Contents (deb)
[💲|🔨] Ign:41 http://deb.debian.org/debian trixie-backports/non-free-firmware arm64 Packages
[💲|🔨] Ign:42 http://deb.debian.org/debian trixie-backports/non-free-firmware Translation-en
[💲|🔨] Ign:43 http://deb.debian.org/debian trixie-backports/non-free-firmware all Contents (deb)
[💲|🔨] Ign:44 http://deb.debian.org/debian trixie-backports/non-free-firmware arm64 Contents (deb)
[💲|🔨] Err:25 http://deb.debian.org/debian trixie-updates/main arm64 Packages
[💲|🔨] Could not change permissions for temporary file /var/lib/apt/lists/partial/deb.debian.org_debian_dists_trixie-updates_main_binary-arm64_Packages.dfYzCj - fchmod (1: Operation not permitted)
[💲|🔨] 404 Not Found [IP: 151.101.130.132 80]
[💲|🔨] Ign:26 http://deb.debian.org/debian trixie-updates/main Translation-en
[💲|🔨] Ign:27 http://deb.debian.org/debian trixie-updates/main arm64 Contents (deb)
[💲|🔨] Ign:28 http://deb.debian.org/debian trixie-updates/main all Contents (deb)
[💲|🔨] Err:29 http://deb.debian.org/debian trixie-backports/main arm64 Packages
[💲|🔨] Could not change permissions for temporary file /var/lib/apt/lists/partial/deb.debian.org_debian_dists_trixie-backports_main_binary-arm64_Packages.omGzKL - fchmod (1: Operation not permitted)
[💲|🔨] 404 Not Found [IP: 151.101.130.132 80]
[💲|🔨] Ign:30 http://deb.debian.org/debian trixie-backports/main Translation-en
[💲|🔨] Ign:31 http://deb.debian.org/debian trixie-backports/main arm64 Contents (deb)
[💲|🔨] Ign:32 http://deb.debian.org/debian trixie-backports/main all Contents (deb)
[💲|🔨] Ign:33 http://deb.debian.org/debian trixie-backports/contrib arm64 Packages
[💲|🔨] Ign:34 http://deb.debian.org/debian trixie-backports/contrib Translation-en
[💲|🔨] Ign:35 http://deb.debian.org/debian trixie-backports/contrib all Contents (deb)
[💲|🔨] Ign:36 http://deb.debian.org/debian trixie-backports/contrib arm64 Contents (deb)
[💲|🔨] Ign:37 http://deb.debian.org/debian trixie-backports/non-free arm64 Packages
[💲|🔨] Ign:38 http://deb.debian.org/debian trixie-backports/non-free Translation-en
[💲|🔨] Ign:39 http://deb.debian.org/debian trixie-backports/non-free arm64 Contents (deb)
[💲|🔨] Fetched 285 kB in 4s (76.3 kB/s)
[💲|🔨] Reading package lists...
[💲|🔨] E: Failed to fetch http://security.debian.org/dists/trixie-security/main/binary-arm64/Packages 404 Not Found [IP: 151.101.130.132 80]
[💲|🔨] E: Failed to fetch http://deb.debian.org/debian/dists/trixie/main/i18n/Translation-en 404 Not Found [IP: 151.101.130.132 80]
[💲|🔨] E: Failed to fetch http://deb.debian.org/debian/dists/trixie-updates/main/binary-arm64/Packages 404 Not Found [IP: 151.101.130.132 80]
[💲|🔨] E: Failed to fetch http://deb.debian.org/debian/dists/trixie-backports/main/binary-arm64/Packages 404 Not Found [IP: 151.101.130.132 80]
[💲|🔨] E: Some index files failed to download. They have been ignored, or old ones used instead.
[💲|🚸] Command failed, retrying in 5s [ chroot_sdcard_apt_get_update ]
[💲|🚸] Command failed 3 times, giving up [ chroot_sdcard_apt_get_update ]
[💲|💥] Error 1 occurred in main shell [ at /mnt/c/Users/quepi/build/lib/functions/rootfs/distro-agnostic.sh:314
install_distribution_agnostic() --> lib/functions/rootfs/distro-agnostic.sh:314
do_with_logging() --> lib/functions/logging/section-logging.sh:81
build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:25
full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36
do_with_default_build() --> lib/functions/main/default-build.sh:42
cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25
armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136
cli_entrypoint() --> lib/functions/cli/entrypoint.sh:216
main() --> compile.sh:50
]
[💲|💥] Cleaning up [ please wait for cleanups to finish ]
[💲|🌿] Unmounting recursively [ SDCARD - be patient ]
[💲|🌿] Unmounting recursively [ MOUNT - be patient ]
[💲|✨] Repeat Build Options [ ./compile.sh build BOARD=orangepi5-plus BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_ENVIRONMENT=xfce DESKTOP_TIER=full KERNEL_CONFIGURE=no RELEASE=trixie ]
[💲|🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-aac38346-d1ad-4565-92ed-16342eb173a6.log.ans ]
[💲|🌱] Share log manually: [ use one of the commands below (or add SHARE_LOG=yes next time!) ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-aac38346-d1ad-4565-92ed-16342eb173a6.log.ans https://paste.armbian.com/log ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-aac38346-d1ad-4565-92ed-16342eb173a6.log.ans https://paste.armbian.de/log ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-aac38346-d1ad-4565-92ed-16342eb173a6.log.ans https://paste.next.armbian.com/log ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-aac38346-d1ad-4565-92ed-16342eb173a6.log.ans https://paste.armbian.eu/log ]

No image was created in /build/output/images/.

What is a work around?

log-build-aac38346-d1ad-4565-92ed-16342eb173a6.log log-build-aac38346-d1ad-4565-92ed-16342eb173a6.log.ans summary-build-aac38346-d1ad-4565-92ed-16342eb173a6.md

[Hardware bug] Orange Pi 5 Plus rev 1.3.1 — floating vias kill Type-C (USB3.1) & FAN: investigation and hardware fix

Thu, 23 Jul 2026 16:09:38 +0000

I have an Orange Pi 5 Plus 16GB board, revision "1.3.1". I've been using it for about a year with official Armbian, Vendor kernel 6.1. The only issues I noticed were a non-working Type-C port and FAN connector. I thought it was an OS or DTS (Device Tree) bug... But it turned out to be a hardware problem.

It started when I got another Orange Pi 5 Plus 8GB board for repair (needed to resolder the Type-C power connector). Same revision "1.3.1".

Скрытый текст

(left is my 16GB board, right is the 8GB board for repair; the PCB solder mask is slightly different in shade of blue — probably different manufacturers or production batches)

I inspected it under a microscope and found that both boards have floating (unconnected) vias — the ones that should control the FAN transistor, and also the EN-pin for the Type-C (USB3.1) power.

Скрытый текст

So these are defective boards from some unknown revision where these vias are simply missing.

On top of that, even if you force-enable the Type-C (USB3.1) EN pin — it still won't work. The reason is that the data lines are connected to TYPEC1 pins on the SoC, not TYPEC0 as shown in the OPI 5 PLUS_V1_3_1_Schematic.pdf

So you need a DTS fix to enable the port via the correct node. The HUSB311 chip is also useless in this case. I don't know what exactly this revision is or why these errors exist.

Fix: enabling power on the Type-C port

To get the front Type-C (USB3.1) port working, I soldered the EN pin from the Power Switch — which was going ~~TYPEC5V_PWREN_H~~ Nowhere — to the nearest 3V3 Ethernet power rail. Now the Type-C port gets power after boot.

Скрытый текст

The second step is to create a DTS overlay to make the port actually work:

File: rk3588-orangepi-5-plus-TypeC-fix-hardware.dts

/dts-v1/;
/plugin/;

/ {
    model = "Orange Pi 5 Plus";
    compatible = "rockchip,rk3588-orangepi-5-plus", "rockchip,rk3588";

    fragment@0 {
        target = <&usbdrd_dwc3_1>;
        __overlay__ {
            dr_mode = "host";
            maximum-speed = "super-speed";
            snps,xhci-trb-ent-quirk;
        };
    };
};

To apply the overlay, copy the file to your board and run:

cd 
sudo armbian-add-overlay rk3588-orangepi-5-plus-TypeC-fix-hardware.dts

Also worth noting: since HUSB311 is missing on this revision, the CC1/CC2 orientation detection doesn't work properly. In practice this means: plug in a USB-C cable one way — the device shows up as USB2.0 (HighSpeed). Flip the cable 180° and replug — it shows up as USB3.0 (SuperSpeed). This happens because only CC1 or CC2 is connected (not both).

If you need a PWM fan

The PWM signal via for the FAN transistor is also floating on this revision — it goes ~~FAN_CTL_H~~ Nowhere. You can solder to it (either to the end of the nearby SMD resistor or scrape the VIA pad directly) and connect it to any free pin on the 40-pin header. Then update the DTS to assign that pin for fan control instead of the original one.

P.S. Sorry for the low quality photos.

Source: 4PDA

Android + Armbian + Ubuntu on the Same NVMe SSD (Orange Pi 5 Plus)

Fri, 10 Jul 2026 04:51:22 +0000

Introduction
This guide describes a tested method for running Android, Armbian, and Ubuntu on the same NVMe SSD of the Orange Pi 5 Plus.
This is not an official Orange Pi installation procedure. The entire workflow was developed through extensive real-world testing.
The following configuration has been successfully verified:
✅ Android boots from the NVMe SSD.
✅ Armbian boots from the same NVMe SSD via UEFI.
✅ Ubuntu boots from the same NVMe SSD via UEFI.
✅ All three operating systems coexist on a single NVMe SSD.
✅ Armbian and Ubuntu share the same EFI partition.
✅ Android, Armbian, and Ubuntu can share a common data partition.

1. Requirements
Hardware
Orange Pi 5 Plus.
An NVMe SSD (the larger the better, and it must have a larger capacity than the eMMC to provide free space for Armbian and Ubuntu).
A 16GB or 32GB eMMC module (16GB recommended).
A microSD card for UEFI.
A PC/Laptop or an NVMe USB enclosure for partition management.

A microSD card can also be used instead of eMMC for Android, but a large-capacity card is not recommended because it reduces the available space for Linux on the NVMe SSD.

Software
Android ROM (tested and verified; the AGTV ROM can be flashed directly to the eMMC using rkdeveloptool).
Armbian.
Ubuntu.
UEFI image.
BalenaEtcher, Rufus, or any software capable of writing IMG files to a microSD card.
A partition manager such as GParted, DiskGenius, or MiniTool Partition Wizard.

2. Boot Method
Android
Android uses the standard Rockchip boot process.
Requirements:
The SPI flash must be empty or completely erased.
Android boots directly from the NVMe SSD.
Armbian and Ubuntu
Armbian and Ubuntu boot through UEFI.
Write the UEFI image to a microSD card.
Insert the microSD card whenever you want to boot Linux.
Both operating systems share the same EFI partition on the NVMe SSD.

3. NVMe Partition Layout
The NVMe SSD contains two groups of partitions.
Android
Keep all Android system partitions intact, for example:
boot
vendor_boot
dtbo
vbmeta
super
metadata
userdata
...
Do not modify any Android system partition.
Linux
Create the following additional partitions:
EFI
Armbian RootFS
Ubuntu RootFS
Data
The Data partition can be shared between Armbian and Ubuntu.

4. Preparing Android
Flash Android to the eMMC.
Boot Android and verify that everything works correctly.
Boot Armbian or Ubuntu from a microSD card or an external SSD (this Linux installation will later be used to copy its RootFS to the NVMe SSD after partitioning).
Back up the entire eMMC using the dd command.
Restore the Android image from the eMMC to the NVMe SSD using dd.
After this step, the NVMe SSD will contain the complete Android partition layout.
Since the NVMe SSD is larger than the eMMC:
The beginning of the NVMe SSD will contain all Android partitions.
The remaining space will remain Unallocated, which will later be used for the Linux partitions.
Next, erase all data on the eMMC and remove the eMMC module from the Orange Pi 5 Plus. Then power on the board and verify that Android boots successfully from the NVMe SSD. This confirms that the system is running entirely from the NVMe drive rather than from the eMMC.

5. Creating Space for Linux
Keep all Android partitions unchanged.
Using tool on either Windows or Linuxuse the Unallocated space located after the Android partitions, create the following partitions:
EFI (used to boot Armbian and Ubuntu through UEFI)
Armbian
Ubuntu
Data

6. Installing Armbian
Restore or copy the Armbian RootFS to the Armbian partition on the NVMe SSD.
Copy the EFI boot files to the EFI partition.
Update the UUIDs if necessary.
Verify that Armbian boots successfully through UEFI.

7. Installing Ubuntu
Restore or copy the Ubuntu RootFS to the Ubuntu partition on the NVMe SSD.
Copy the EFI boot files to the EFI partition.
Update the UUIDs if necessary.
Verify that Ubuntu boots successfully through UEFI.

8. Booting the Operating Systems
Boot Android
Remove the microSD card containing the UEFI bootloader.
Make sure the SPI flash is empty.
[7/10/2026 10:56 AM] Vũ Minh Tâm: The Orange Pi 5 Plus will boot Android directly from the NVMe SSD.
Boot Armbian or Ubuntu
Insert the microSD card containing the UEFI bootloader.
Select the desired operating system from the UEFI boot menu.
The selected Linux system will boot from its corresponding partition on the NVMe SSD.

9. Current Status
The following configuration has been successfully verified:
✅ Android running from the NVMe SSD.
✅ Armbian running from the NVMe SSD.
✅ Ubuntu running from the NVMe SSD.
✅ Armbian and Ubuntu share the same EFI partition.
✅ Android, Armbian, and Ubuntu can share a common Data partition (NTFS is recommended).
✅ Switching between Android and Linux only requires inserting or removing the microSD card.

10. Notes
This method has only been tested on the Orange Pi 5 Plus.
It is based entirely on real-world testing and is not an official Orange Pi installation procedure.
Some adjustments may be required when using different firmware versions, bootloaders, or hardware revisions.
It is strongly recommended to back up both the eMMC and the NVMe SSD before modifying the partition layout.

11. Discussion
If you have successfully implemented a similar setup or know of a simpler approach, feel free to share your experience. Any suggestions or improvements are welcome and will help make this guide even better.

NPU not working in OrangePi5Plus Vendor Kernel

Sun, 07 Jun 2026 06:18:16 +0000

Hello All.. I am trying to get rknpu working properly. I have resolute minimal install with 6.1 vendor kernel installed. Default install does not have `/dev/rknpu` and shows error with loading the rknpu driver. Can any one help resolve this? This is with fresh install of the OS on the NVME drive: There is no NPU option in the dtb list for orangepi5plus.

Quote

Linux opi5plus 6.1.115-vendor-rk35xx #1 SMP Mon May 18 05:13:49 UTC 2026 aarch64 GNU/Linux

PRETTY_NAME="Armbian 26.5.1 resolute"
NAME="Ubuntu"
VERSION_ID="26.04"
VERSION="26.04 (Resolute Raccoon)"
VERSION_CODENAME=resolute
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.armbian.com"
SUPPORT_URL="https://forum.armbian.com"
BUG_REPORT_URL="https://www.armbian.com/bugs"
PRIVACY_POLICY_URL="https://www.armbian.com"
UBUNTU_CODENAME=resolute
LOGO="armbian-logo"
ARMBIAN_PRETTY_NAME="Armbian 26.5.1 resolute"

This is the error in dmesg

[   15.981999] RKNPU fdab0000.npu: Adding to iommu group 0
[   15.982175] RKNPU fdab0000.npu: RKNPU: rknpu iommu is enabled, using iommu mode
[   15.982308] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree
[   15.985241] RKNPU fdab0000.npu: Looking up mem-supply from device tree
[   15.988551] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdab0000-0xfdabffff]
[   15.988583] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdac0000-0xfdacffff]
[   15.988603] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdad0000-0xfdadffff]
[   15.989174] [drm] Initialized rknpu 0.9.8 20240828 for fdab0000.npu on minor 1
[   15.993547] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree
[   15.996066] RKNPU fdab0000.npu: RKNPU: bin=0
[   15.996288] RKNPU fdab0000.npu: leakage=8
[   15.996320] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree
[   15.996356] debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present!
[   16.005738] RKNPU fdab0000.npu: pvtm=868
[   16.011925] RKNPU fdab0000.npu: pvtm-volt-sel=3
[   16.012005] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree
[   16.012037] debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present!
[   16.012656] RKNPU fdab0000.npu: Looking up mem-supply from device tree
[   16.014725] RKNPU fdab0000.npu: avs=0
[   16.014836] RKNPU fdab0000.npu: rockchip_pvtpll_set_volt_sel: error cfg clk_id=6 voltsel (-1)
[   16.015007] RKNPU fdab0000.npu: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=800000000 h_table=0

solved: usb-c not working on Gnome Armbian 26.2.1 noble with 6.19.0-edge-rockchip64, 6.12.58-current-rockchip64

Fri, 08 May 2026 09:24:46 +0000

I managed to fix an issue with the usb-c port of the orange pi 5 plus. It seems the device is not activated unless you put it in host mode yourself:

as user root:

echo host >/sys/kernel/debug/usb/fc000000.usb/mode

I have tried a usb-c network card and usb stick. Both work after this command!

I noticed this when I installed the 6.1.115-vendor-rk35xx kernel. This one does not need this setting, it switches automatically from device mode to host and vice versa.

I had alot of problems with analog sound on older kernels, e.g. youtube just hangs unless you mute the sound.

But sound in noble 6.19.0-edge-rockchip64 works now, I switched to pipewire however.

Thanks to the maintainers of Armbian and OrangePi for this awesomeness!

The microphone (on Android) does not work after installing Armbian?

Sat, 11 Apr 2026 20:38:01 +0000

Hello, good afternoon. I'm using a translator, so I apologize if it's not clear.

I have an Orange Pi 5 Plus SBC which I have Android installed on the m2 drive. I install Armbian on a microSD card.

I don't remember what problem I was having, but I had to format the SPI Flash. After that, the Armbian version worked fine.

Also, after formatting the SPI Flash, my microphone stopped working on Android (it works on Armbian).

Could this be due to formatting the SPI Flash?

Thank you.

Edge fs2fs build does not boot.

Mon, 06 Apr 2026 18:54:17 +0000

Built image with such flags:

Quote

./compile.sh build BOARD=orangepi5-plus BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes FIXED_IMAGE_SIZE=3000 KERNEL_CONFIGURE=no RELEASE=trixie ROOTFS_TYPE=f2fs

Etched img to sdcard and SBC has no response on power up.

U-boot log:

Quote

DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18
ch0 ttot10
ch1 ttot10
ch2 ttot10
ch3 ttot10
ch0 ttot16
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB
ch1 ttot16
channel[1] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB
ch2 ttot16
channel[2] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB
ch3 ttot16
channel[3] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB
Manufacturer ID:0xff
DQS rds:l0,h2
CH0 RX Vref:28.9%, TX Vref:22.8%,22.8%
DQ rds:h1 h2 h4 h3 l1 h2 h1 h1, h3 l0 h1 h2 h1 h3 h3 h1

DQS rds:l0,h1
CH1 RX Vref:29.3%, TX Vref:21.8%,21.8%
DQ rds:h1 h1 l0 h1 h1 h1 h6 h1, l0 h3 l0 h4 l0 h4 h1 l0

DQS rds:l0,h1
CH2 RX Vref:29.7%, TX Vref:23.8%,21.8%
DQ rds:h1 h1 h1 h7 l0 h1 h4 h1, h3 h4 h2 h2 l0 l1 h2 h4

DQS rds:h1,l0
CH3 RX Vref:30.5%, TX Vref:21.8%,22.8%
DQ rds:h1 l0 h3 h6 h1 h3 h1 h3, h4 h3 h3 l0 h2 h1 h1 h1

stride=0x2, ddr_config=0x4
hash ch_mask0-1 0x20 0x40, bank_mask0-3 0xa00 0x1400 0x2800 0x0, rank_mask0 0x401000
change to F1: 528MHz
ch0 ttot10
ch1 ttot10
ch2 ttot10
ch3 ttot10
change to F2: 1068MHz
ch0 ttot12
ch1 ttot12
ch2 ttot12
ch3 ttot12
change to F3: 1560MHz
ch0 ttot14
ch1 ttot14
ch2 ttot14
ch3 ttot14
change to F0: 2112MHz
ch0 ttot16
ch1 ttot16
ch2 ttot16
ch3 ttot16
out

U-Boot SPL 2024.10-rc3-armbian-2024.10-rc3-Sd11a-Pe466-H89d7-V74ff-Bb703-R448a-dirty (Oct 16 2025 - 03:36:30 +0000)
Trying to boot from SPI
## 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
INFO: Preloader serial: 2
NOTICE: BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48
NOTICE: BL31: Built : 15:02:44, Dec 19 2024
INFO: spec: 0x1
INFO: code: 0x88
INFO: ext 32k is not valid
INFO: ddr: stride-en 4CH
INFO: GICv3 without legacy support detected.
INFO: ARM GICv3 driver initialized in EL3
INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
INFO: l3 cache partition cfg-0
INFO: system boots from cpu-hwid-0
INFO: disable memory repair
INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz
INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz
INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz
INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz
INFO: BL31: Initialising Exception Handling Framework
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 2024.10-rc3-armbian-2024.10-rc3-Sd11a-Pe466-H89d7-V74ff-Bb703-R448a-dirty (Oct 16 2025 - 03:36:30 +0000)

Model: Xunlong Orange Pi 5 Plus
DRAM: 32 GiB (effective 31.7 GiB)
Core: 331 devices, 30 uclasses, devicetree: separate
MMC: mmc@fe2c0000: 1, mmc@fe2e0000: 0
Loading Environment from nowhere... OK
In: serial@feb50000
Out: serial@feb50000
Err: serial@feb50000
Model: Xunlong Orange Pi 5 Plus
rockchip_dnl_key_pressed: no saradc device found
Net: No ethernet found.
Hit any key to stop autoboot: 0
Scanning for bootflows in all bootdevs
Seq Method State Uclass Part Name Filename
--- ----------- ------ -------- ---- ------------------------ ----------------
Scanning global bootmeth 'efi_mgr':
No EFI system partition
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
0 efi_mgr ready (none) 0
** Booting bootflow '' with efi_mgr
Loading Boot0000 'mmc 1' failed
Loading Boot0001 'mmc 0' failed
EFI boot manager: Cannot load any image
Boot failed (err=-14)
Scanning bootdev 'mmc@fe2c0000.bootdev':
Scanning bootdev 'mmc@fe2e0000.bootdev':
pcie_dw_rockchip pcie@fe150000: PCIe-4 Link Fail
pcie_dw_rockchip pcie@fe150000: PCIe-4 Link Fail
scanning bus for devices...
Bus usb@fc800000: USB EHCI 1.00
Bus usb@fc840000: USB OHCI 1.0
Bus usb@fc880000: USB EHCI 1.00
Bus usb@fc8c0000: USB OHCI 1.0
scanning bus usb@fc800000 for devices... 1 USB Device(s) found
scanning bus usb@fc840000 for devices... 1 USB Device(s) found
scanning bus usb@fc880000 for devices... 1 USB Device(s) found
scanning bus usb@fc8c0000 for devices... 1 USB Device(s) found
pcie_dw_rockchip pcie@fe150000: PCIe-4 Link Fail

Warning: eth_rtl8169 MAC addresses don't match:
Address in DT is c0:74:2b:fd:6e:96
Address in environment is ee:33:fd:a3:99:d0
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17

Retry time exceeded; starting again
pcie_dw_rockchip pcie@fe150000: PCIe-4 Link Fail
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17

Retry time exceeded; starting again
No more bootdevs
--- ----------- ------ -------- ---- ------------------------ ----------------
(1 bootflow, 1 valid)
=>

OS boots normally if I use ext4, but would like to stick to f2fs.
Btrfs or f2fs used to work if I used 7 months old armbian-build git checkpoint but not any more.
Anyone else had similar problems?

Stable edge switch

Sun, 25 Jan 2026 14:22:52 +0000

Hi,

I've read on here that you can apparently switch to a stable edge branch through Armbian Config, but the closest I can find is 'switch to rolling packages repository' and 'distribution upgrade to rolling unstable'. Are either of these correct? I'm running the Ubuntu Noble 6.12 kernel, btw.

Many thanks.

New kernels / Armbian version

Wed, 21 Jan 2026 15:13:36 +0000

Hi there,

I'm really happy with Armbian on my Oprange Pi 5 Plus but recently I noticed that I'm not getting kernel updates so often as before. I use rockchip-edge branch and I'm stuck at kernel "6.18.0-rc6-edge-rockchip64". I know there are new versions being tested (https://github.com/armbian/os/pkgs/container/os%2Fkernel-rockchip64-edge), will they be released to armbian? Maybe you are working hard on Armbian version 26.2 and I'm just anxious

Thanks in advance!

Orange pi 5 plus issue with 3.5mm headset microphome

Sat, 17 Jan 2026 22:33:39 +0000

It was found that 3.5mm jack has issue with using headset. Speakers are work good on my "uname -a Linux orangepi5-plus 6.19.0-rc5-edge-rockchip64 #1 SMP PREEMPT Mon Jan 12 03:03:14 UTC 2026 aarch64 aarch64 aarch64 GNU/Linux" system but micro is silent. By debugging it was found that register 0x2b(43) "DAC Control 21" has difference between actually used es8388 on OP5+ and original driver's IC es8328. Also microphone bias was never activated by bits 2,3 in register 0x03. I create patch and now microphone work properly. I don't know how to properly share this patch so I will attache it here.

orangepi-5-plus_ES8388_Microphone.patch

Wake on lan (WOL) is not working on orange pi 5 plus

Sat, 03 Aug 2024 07:58:47 +0000

Hi all

Cannot make usable wol on my orange pi 5 plus.

Os: Armbian 24.5.1 Bookworm with Linux 6.1.75-vendor-rk35xx

WOL tested in magic or unicast settings or all flags enabled (phy, unicast, multicast, broadcast, arp, magic)

Test sending wol packets with running tcpdump -i enP3p49s0 '(udp and port 7) or (udp and port 9)' show that orange pi successfully receive wol packets on speeds 1000 or even 10 mbps while powered on. But after sending orange pi to suspend or power off I cannot bring it online via WOL. So I suppose network component outside orange pi is ok and it is something wrong with orange pi.

Any ideas?

Orange Pi 5 Plus USB/WoL/WWoL Wake-up Fix and WiFi Adapter Support

Thu, 11 Dec 2025 13:26:30 +0000

Continuing the tradition (1, 2) of micro-optimizations for single-board computers that come into my hands.

This time I ~~optimized~~ or rather fixed the wake-up function via USB/WoL/WWoL on the Orange Pi 5 Plus. Also got the WiFi adapter RTW8852BE/RTW8852CE working (at least those are the ones I tested).

I tested exclusively on the Vendor 6.1.x kernel since the main wake-up features via USB/PCIE/GPIO1-GPIO4 only work in it. I don't currently have the ability to test the new current kernel and I doubt that Power Management will work fully there.

Armbian for Orange Pi 5 Plus from the official website, Vendor kernel (kernel 6.1.115-vendor-rk35xx), what does NOT work by default:

1. No WiFi modules that insert into the PCI-E M.2 socket E-Key work - fixed in dts below

2. Wake-up from USB (mouse/keyboard/even Bluetooth dongle) doesn't work - fixed in dts below

3. WoL via Ethernet (on two ports) - fixed in dts below

I also conducted power consumption measurements in all these wake-up modes.

Let's start with Ethernet ports (WoL won't work by default due to incomplete dts profile). You need to create an overlay file, links I've attached it to this message.

To apply this overlay, you need to copy it somewhere on the single-board computer and execute the command:

cd  to rk3588-orangepi-5-plus-Wakeup-GPIO-RTC-USB-WoL-fixes.dts>
sudo armbian-add-overlay rk3588-orangepi-5-plus-Wakeup-GPIO-RTC-USB-WoL-fixes.dts

Reboot.
(if it doesn't boot at all with it or something doesn't work, you can remove these changes from the /boot/overlay-user/ folder)

Wake-up Timer Test:

sudo sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" 
sudo sh -c "echo `date '+%s' -d '+ 1 minutes'` > /sys/class/rtc/rtc0/wakealarm"
sudo systemctl suspend

(here we set wake-up in 1 minute from current time, you can choose seconds/minutes/hours and so on, maybe even days - haven't tested. Installing a battery on RTC is not necessary, Type-C power is sufficient)

Power Consumption:

Testing was performed on Imax B6 Evo / OWON HDS242S.
Please note, power consumption of m.2 SSD, SD-card, eMMC is not accounted for here (ideally they should be powered off in sleep mode), but USB devices were not used, bare single-board computer was tested, each module will have its own consumption, especially USB-connected devices, add your values to the sleep mode consumption.

Wake-up only via GPIO0 (this includes power button), RTC

In this power-saving mode only the rk3588-orangepi-5-plus-Wakeup-GPIO0-RTC-only-fixes.dts profile is used, keep this in mind, it's not compatible with other dts, you need to choose only one option.
I got these values:

sudo shutdown -h now | 5.4V | 0.005W | 0.001A
sudo systemctl suspend | 5.4V | 0.14W | 0.027A

Wake-up via GPIO0, GPIO1-4, RTC, USB, WoL

In this power-saving mode only the rk3588-orangepi-5-plus-Wakeup-GPIO-RTC-USB-WoL-fixes.dts profile is used, keep this in mind, it's not compatible with other dts, you need to choose only one option.

sudo systemctl suspend | 5.4V | 0.25W | 0.046A
RTL8125B (eth0 or eth1, can even be both):
sudo ethtool -s eth0 wol g && sudo systemctl suspend | 5.4V | 0.33W | 0,061A
RTW8852BE (external rtw8852be driver (rtw89 doesn't support WWoL for RTW8852BE in vendor 6.1 kernel)):
sudo iw phy0 wowlan enable any && sudo systemctl suspend | 5.4V | 0.30W | 0,055A
RTW8852CE (built-in rtw89 driver in the build):
sudo iw phy0 wowlan enable magic-packet && sudo systemctl suspend | 5.4V | 0.27W | 0,051A

(I want to note that the Ethernet ports on Orange Pi 5 Plus in WoL mode don't light up and don't show link activity, you can only find out if the link is working on the router or on the device to which the single-board computer is connected. In magic-packet standby mode the link switches to 10Mbit and for example on the router loses the assigned IP address, you can find out if the device is alive only by ARP scanning on the router itself or by the link light indication on the router itself. The same applies to WWoL (WiFi) - only on the router or device to which the single-board computer is connected can you check in active clients mode or ARP scan for the presence of MAC address)

My Armbian build from the official website on Vendor 6.1 kernel where rtw89 (WiFi) modules are already compiled and pre-installed in the kernel has a peculiarity that this driver supports WWoL function only for RTW8852CE - this is a slightly different chip than the official proprietary WiFi module for Orange Pi 5 Plus which uses RTW8852BE. For WWoL to work on RTW8852BE you need to install a third-party driver, for example I recommend from this source.

How to use WoL, WWoL:

For wired network use ip and ethtool utilities, for wireless network iw.

WoL over LAN

Скрытый текст

1. Find out which interface is currently active:

ip a

Output will be like:

deoptim@orangepi5-plus:~$ ip a
1: lo: ,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: dummy0: ,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 26:97:84:xx:xx:xx brd ff:ff:ff:ff:ff:ff
3: eth0: ,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether c0:74:2b:xx:xx:x1 brd ff:ff:ff:ff:ff:ff
    altname enP3p49s0
4: eth1: ,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether c0:74:2b:xx:xx:x2 brd ff:ff:ff:ff:ff:ff
    altname enP4p65s0
    inet 192.168.1.125/24 brd 192.168.1.255 scope global dynamic noprefixroute eth1
       valid_lft 23221sec preferred_lft 23221sec
    inet6 fd38:xxxx:xxxx:0:xxxx:xxxx:xxxx:xxxx/64 scope global temporary dynamic
       valid_lft 602822sec preferred_lft 84108sec
    inet6 fd38:xxxx:xxxx:0:xxxx:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 4293886216sec preferred_lft 4293886216sec
    inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
5: wlan0: ,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 38:b8:00:xx:xx:xx brd ff:ff:ff:ff:ff:ff
    altname wlP2p33s0
    inet 192.168.1.110/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 23226sec preferred_lft 23226sec
    inet6 fd38:xxxx:xxxx:0:xxxx:xxxx:xxxx:xxxx/64 scope global temporary dynamic
       valid_lft 602829sec preferred_lft 83865sec
    inet6 fd38:xxxx:xxxx:0:xxxx:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 4293886216sec preferred_lft 4293886216sec
    inet6 fe80::xxxx:xxxx:xxxx:xxx/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
deoptim@orangepi5-plus:~$

(where for example wired interface is active on eth1 (since IP is assigned), remember or write down its MAC address c0:74:2b:xx:xx:x2)

2. Activate WoL on this interface:

sudo ethtool -s eth1 wol g

(many options and ways to wake up are available, g = magic-packet, other possible variants are p,u,m,b,g - see documentation)

3. Go to sleep:

sudo systemctl suspend

4. Try to wake up the single-board computer using some WoL utility (Windows/Linux/Android) over local network (within your home network).

WWoL over WiFi

Скрытый текст

1. Find out the MAC address of your PCI-E WiFi adapter, for example with command:

iw dev

Output like this:

deoptim@orangepi5-plus:~$ iw dev
phy#0
        Interface wlan0
                ifindex 5
                wdev 0x1
                addr d0:39:57:xx:xx:xx
                ssid Keenetic_2A28
                type managed
                channel 40 (5200 MHz), width: 80 MHz, center1: 5210 MHz
                txpower 12.00 dBm
deoptim@orangepi5-plus:~$

2. After that you can try to activate WWoL function with command:

sudo iw phy0 wowlan enable magic-packet

(for rtw89 driver: besides magic-packet, for RTL8852CE also supported are other wake-up variants disconnect, pattern match, they can be combined together
for rtw8852be/ce driver: only any variant is available, wake-up variants are set by module parameter rtw_wakeup_event)

3. And try to sleep:

sudo systemctl suspend

4. Try to wake up the single-board computer using some WoL utility (Windows/Linux/Android) over local network (within your home network).

External Drivers:

For RTW8852BE/RTW8852CE and others there are fairly recent drivers (at the time of writing this manual), here's a brief instruction on how to install them on Orange Pi 5 Plus.

Скрытый текст

1. Install dependencies:

sudo apt update
sudo apt install build-essential linux-headers-vendor-rk35xx make dkms git

2. Pre-add rtw89 driver to blacklist (for example for CE), work via wired network for now:

edit as root /boot/armbianEnv.txt in parameter extraargs= add to existing parameters "module_blacklist=rtw89_core,rtw89_pci,rtw89_8852с,rtw89_8852сe" without quotes

3. Clone repository with driver:

git clone --depth 1 https://github.com/saloonatic/realtek_wifi_driver.git

4. Navigate to path depending on which module you have, for example:

cd realtek_wifi_driver/rtl8852ce/

5. Edit Makefile and add at the beginning of file:

ARCH=arm64

find parameters and set =y or =n for them:

Цитата

CONFIG_PCI_RTW_MSI = n
CONFIG_WIFI_MONITOR = y
CONFIG_RTW_DEBUG = n
CONFIG_PROC_DEBUG = n
CONFIG_WOWLAN = y
CONFIG_WAKEUP_TYPE = 0x05

If you want two virtual interfaces for one card (wlan0 and wlan1), for example if you want AP+STA (client + access point but only on the same channel) or STA+STA (two networks with backup internet but only on the same channel), then also enable option:

Цитата

CONFIG_CONCURRENT_MODE = y

6. Create file default-editor.txt:

echo nano > default-editor.txt

7. Run installation:

sudo ./install-driver.sh

Should compile and install driver without problems and reboot.

Issues:

Скрытый текст

1. On some builds suspend mode is disabled, it's not in the menu and not available through console:

deoptim@orangepi5-plus:~$ sudo systemctl suspend
Call to Suspend failed: Sleep verb 'suspend' is disabled by config
deoptim@orangepi5-plus:~$

In this case you need to remove the configuration:

deoptim@orangepi5-plus:~$ cat /etc/systemd/sleep.conf.d/00-disable.conf
[Sleep]
AllowSuspend=no
AllowHibernation=no
AllowHybridSleep=no
AllowSuspendThenHibernate=no
deoptim@orangepi5-plus:~$ sudo rm /etc/systemd/sleep.conf.d/00-disable.conf

And edit the file /etc/systemd/sleep.conf with enabled configuration (there it's enough to remove the # sign from the line):

AllowSuspend=yes

Reboot.

2. There are problems with built-in WiFi driver rtw89 for RTW8852BE/RTW8852CE (at the time of writing this post: 6.1.115-vendor-rk35xx). The first problem is that in the official dts profile for Orange Pi 5 Plus there is a "rockchip,skip-scan-in-resume" parameter in the section for pcie2x1l0 (M.2 E-key) - this is a harmful parameter. Even without using WWoL function, due to this option the driver doesn't exit from regular sleep correctly. Either it's necessary to edit the main dts file (which is dangerous) and remove this parameter, or get out of this situation with a script after wake-up of the following type:

sudo nano /lib/systemd/system-sleep/fix-wifi.sh

#!/bin/bash

case $1/$2 in
  post/*)
    echo "Waking up from suspend..."
    # Or remove "rockchip,skip-scan-in-resume" option in main dts profile,
    # or use this Bug workaround
    # Force reset of PCI device after sleep
    # (to know your controller address use "lspci" tool)
    echo 1 | tee /sys/bus/pci/devices/0002\:21\:00.0/reset
    ;;
esac

sudo chmod +x /lib/systemd/system-sleep/fix-wifi.sh

The second problem lies in using WWoL on rtw89 - if once after reboot it will wake from magic-packet, but the second time (if not rebooted) it won't wake up and kernel will hang - these are bugs of rtw89 itself.

An acceptable way out of this situation as mentioned is to use external driver, when using these drivers, it doesn't matter whether there is "rockchip,skip-scan-in-resume" parameter in main dts or not, you don't need to edit it.

File: rk3588-orangepi-5-plus-Wakeup-GPIO-RTC-USB-WoL-fixes.dts

File: rk3588-orangepi-5-plus-Wakeup-GPIO0-RTC-only-fixes.dts

Original Link 4PDA

Expected default graphics acceleration for RK3588?

Mon, 24 Nov 2025 20:41:22 +0000

I understand that panthor is not supported for wayland but in that case I would expect libmali to fill in... but I ended up with lvmpipe.

The overlay along with another recent post led me to believe that panthor was the expected default and libmali was an artifact, but I'm now questioning that after finding a thread identifying use cases where libmali can be preferred and a comment suggesting panthor wouldn't be available until 6.13.

As a result, I am now questioning if there is a reason that software acceleration is the default and the user is expected to determine which path they want to go?

I know support for the hardware has been slow going so I understand that it's not well supported yet, but hoping to get a better handle on expectations.

Is there an expected default for a Rockchip RK3588 SoC with the Mali‑G610 GPU? Does it vary between 6.1/6.12 and the desktop/server builds?

Debian Images

Thu, 04 Dec 2025 15:55:55 +0000

Why so few Debian (Trixie) images with this batch of newly released images? Not one full desktop image for Debian?

Custom Build on new version(25.11.0 ) is not enabling Panfrost (Mali) GPU driver (BOARD=orangepi5-plus BRANCH=vendor RELEASE=noble DESKTOP=cinnamon)

Mon, 27 Oct 2025 17:13:02 +0000

Hi Guys,
I just did a new custom Armbian build ./compile.sh BOARD=orangepi5-plus BRANCH=vendor RELEASE=noble KERNEL_ONLY=yes KERNEL_CONFIGURE=no.
The image is Armbian-unofficial_25.11.0-trunk_Orangepi5-plus_noble_vendor_6.1.115_cinnamon_desktop and when I installed it on orangepi I see it is not supporting Panfrost/Mail:
glxinfo | grep -E "OpenGL renderer|OpenGL version"
OpenGL renderer string: llvmpipe (LLVM 20.1.2, 128 bits) OpenGL version string: 4.5 (Compatibility Profile) Mesa 25.0.7-0ubuntu0.24.04.2

but for older image Old_Armbian-unofficial_25.08.0-trunk_Orangepi5-plus_noble_vendor_6.1.115_cinnamon_desktop All was well
glxinfo | grep -E "OpenGL renderer|OpenGL version"
OpenGL renderer string: Mali-G610 (Panfrost) OpenGL version string: 3.1 Mesa 25.0.7-0ubuntu0.24.04.2

I did need to enable "ARM Mail Display Processor" under Device Drivers -> Graphics support -> ARM devices before I perform custom build.
And I did this for both OS version 25.11.0 and 25.08.0.
But newer version is not able to use it.
Thanks

Manish

Can't boot Armbian noble vendor gnome

Fri, 21 Nov 2025 18:23:34 +0000

I have tried to download at least 3 times this image:

Armbian_25.8.1_Orangepi5-plus_noble_vendor_6.1.115_gnome_desktop.img.xz

All sha256sum verified Ok.

And wrote 5 times on 3 different SDCards, and this img does not boot on my OPI-5-Plus.

No image on monitor, partition armbi_root not expanded, no green lights... Just unusable (for me).

Other img's that boot are OK: Deb-xfce, noble-cinnamon, noble-neon...

Someone got success with this img???

I'm looking for a distro that works well on OPI5-Plus, well configured, and that works with HDMI audio.

The best for now is Noble-Cinnamon but failed to setup Menu button, and I cant find support until now to solve this issue.

Thanks,

Cury

Orange Pi 5 Plus TPM2.0 Overlay

Fri, 14 Nov 2025 13:38:43 +0000

Hello,

I've been using https://joshua-riek.github.io/ubuntu-rockchip-download/boards/orangepi-5-plus.html with a custom kernel that I built to activate my TPM2.0 device and it works.

Now I'm asked to use an UEFI compatible image with my Orange Pi 5 Plus. So what I did is more or less the same thing that in here

But instead of the legacy kernel I used the 6.1.115-rockchip-vendor-rk35xx kernel and my device booted, I got an HDMI output, etc. And then I updated it to my custom kernel (6.1.0-1027-rockchip) that has the necessary configurations to allow TPM over SPI.

Now I'm trying to activate my TPM2.0 as I did before. To do that I added my compiled *.dtbo (rk3588-spi0-tpm-cs1.dtbo) to /boot/dtb/rockchip/overlay and activated it with armbian-config.

After reboot this is my /boot/armbianEnv.txt

orangepi@uefi-arm64:~$ cat /boot/armbianEnv.txt
verbosity=1
bootlogo=true
console=both
extraargs=cma=256M
overlay_prefix=rk3588
fdtfile=rockchip/rk3588-orangepi-5-plus.dtb
rootdev=UUID=3e555b58-fdf4-4e2f-a3af-a8ecfd8034b6
rootfstype=ext4
overlays=spi0-tpm-cs1
param_spidev_spi_bus=0

However I still can't see my tpm under /dev/.

I don't know what I'm missing, I'm quite new to this sorry

Thank you for your time

CEC command support for custom build( BOARD=orangepi5-plus BRANCH=vendor RELEASE=noble ENABLE_EXTENSIONS=mesa-vpu)

Wed, 29 Oct 2025 20:11:25 +0000

Hi ,
I am trying to configure orangepi to turn on and turn off tv. I installed and used cec-ctl to register the boad as playbac device. And then was able to put the TV on standby mode via sudo cec-ctl --device /dev/cec0 --standby --to 0

but not able to find how to turn ON the TV.

Can someone please help.
Thanks
Manish

WiringOP & Python on OrangePi 5 plus

Tue, 12 Dec 2023 19:47:20 +0000

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

Quote

Note that wiringOP has been pre-installed in the linux image released by Orange Pi. Unless the code of wiringOP is updated, there is no need to re-download, compile and install, just use it directly.

The storage path of the compiled wiringOP deb package in orangepi-build is:

orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.deb

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.

How to compile Ubuntu22.04 Gnome OS in offline mode

Tue, 14 Oct 2025 01:54:40 +0000

due to network limitations， how to compile Ubuntu 22.04 Gnome OS image in offline mode, build.sh need to download many debs，can I download them in advance，then install them locally. I have already downloaded kernel

and uboot.

RK3588 - Setting Up Mali & Hardware Acceleration

Tue, 13 May 2025 23:48:31 +0000

I recently bought an orange pi plus and am using the armbian 6.12 server (https://dl.armbian.com/orangepi5-plus/Noble_current_server)

I'm wanting to setup hardware acceleration for jellyfin but having trouble with the right steps. I'm using jellyfin inside docker on the orange pi inside armbian. I've found various tutorials but it seems like some of them reference things that no longer exist (like panfork seems to no longer be needed for latest mesa if I'm understanding correctly?), so wanting to see what I need to do to set this up.

So it seems like I need to disable panthor and use mali instead, but I can't find in the armbian config menu the option to do that, and not sure if I know how to get the right mali. Any help would be greatly appreciated.

armbianmonitor is at https://paste.armbian.com/nurazajipu

I've seen these tutorials/posts for reference:

* https://akashrajpurohit.com/blog/setup-jellyfin-with-hardware-acceleration-on-orange-pi-5-rockchip-rk3558/

* https://github.com/andyshrk/mesa/blob/panthor-v4/Panfrost-build-howto.md

* https://forum.jellyfin.org/t-solved-hw-transcoding-rk3588-arch-not-working?pid=54084

* `https://forum.armbian.com/topic/49115-how-to-install-opencl-on-orangepi-5-plus/`

* https://forum.jellyfin.org/t-rockchip-transcode-missing-dev-mali0

Missing ath12k driver?

Thu, 23 Oct 2025 01:11:58 +0000

Hello,

I just got a wifi 7 adapter (QCNCM865) and I was thinking the ath12k driver was available starting from kernel 6.13, I'm running the edge kernel 6.16.4 and the ath12k driver is failing to load and I can't find any wireless drivers in /usr/lib/modules/6.16.4-edge-rockchip64/kernel/net/wireless.

Do I need to rebuild the kernel with the ath12k driver? or is there a kernel version available with that driver?

Thanks for your help!

Generic UEFI-arm64 on OrangePi-5+

Sun, 25 Feb 2024 14:28:26 +0000

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.

Spoiler

Put the following lines in /etc/udev/rules.d/90-naming-audios.rules:

SUBSYSTEM=="sound", ENV{ID_PATH}=="platform-hdmi0-sound", ENV{SOUND_DESCRIPTION}="HDMI0 Audio"
SUBSYSTEM=="sound", ENV{ID_PATH}=="platform-hdmi1-sound", ENV{SOUND_DESCRIPTION}="HDMI1 Audio"
SUBSYSTEM=="sound", ENV{ID_PATH}=="platform-hdmiin-sound", ENV{SOUND_DESCRIPTION}="HDMI-In Audio"
SUBSYSTEM=="sound", ENV{ID_PATH}=="platform-dp0-sound", ENV{SOUND_DESCRIPTION}="DP0 Audio"
SUBSYSTEM=="sound", ENV{ID_PATH}=="platform-es8388-sound", ENV{SOUND_DESCRIPTION}="ES8388 Audio"

Armbian Build with Sway

Mon, 20 Jan 2025 12:02:54 +0000

I'm adding this here as I want to contribute to the community, but I'm still not sure how.

I've been playing with Armbian Build lately and found it's great for quick build images for testing purposes before it's officially made available. So I started build my own images with i3, mate, kde, and I noticed that, in my personal taste, the one that was better suited for my needs was Sway, but there's no desktop image with it. So I built a Server version and start installing it.

I know it may not be of interest of everybody, so I was planning to do it for myself, so I can continue building with the interface, but having Sway "automatically" installed.

If/when I'm able to do this, I could put this in CSC mode in the repo, or I shouldn't do that as it's going to bloat the system more as there's no interest in having yet another WM/DE available? I'm thinking of this as an alternative to i3,as I noticed that, in my board, Wayland is performing much better than XOrg/X11.

IR receiver stops working after suspend/resume

Wed, 08 Oct 2025 07:58:22 +0000

Hey @amazingfate,

I have an issue with the build-in IR receiver on my OPI5+:

   ##O#O##          OS: Armbian 25.8.1 noble aarch64 
       #######          Host: Orange Pi 5 Plus 
     ###########        Kernel: 6.1.115-vendor-rk35xx 
    #############       Uptime: 2 mins 
   ###############      Packages: 1934 (dpkg), 5 (snap) 
   ################     Shell: bash 5.2.21 
  #################     Resolution: 3840x2160 
#####################   DE: GNOME 46.0 
#####################   WM: Mutter 
  #################     WM Theme: Adwaita 
                        Theme: Adwaita [GTK2/3] 
                        Icons: Adwaita [GTK2/3] 
                        Terminal: x-terminal-emul 
                        CPU: (8) @ 1.800GHz 
                        Memory: 2585MiB / 15957MiB

After a reboot it works just fine, but once I suspend/resume it stops working. Logs look clear of errors.

I have tried to troubleshoot with ChatGPT but goin' in circles and gave up. Lastly ended up with some speculations from it like:

Quote

The driver at drivers/input/remotectl/rockchip_pwm_remotectl.c is missing pm_ops callbacks, which are used to restore hardware state after resume.

It needs something like this added:

static int rockchip_pwm_remotectl_resume(struct device *dev)
{
    struct remotectl_dev *rc_dev = dev_get_drvdata(dev);

    // Re-init or restart the device
    if (rc_dev && rc_dev->restart)
        rc_dev->restart(rc_dev);

    return 0;
}

static const struct dev_pm_ops rockchip_pwm_remotectl_pm_ops = {
    .resume = rockchip_pwm_remotectl_resume,
};

Quote

And then linked to the platform driver:

static struct platform_driver rockchip_pwm_remotectl_driver = {
    .probe = rockchip_pwm_remotectl_probe,
    .driver = {
        .name = "rockchip_pwm_remotectl",
        .pm = &rockchip_pwm_remotectl_pm_ops,
    },
};

Do you think this is the problem, or if not can I share some details so you can try to find it?

Wayland not working with Desktop images with Armbian Linux v6.12 (KDE Neon)

Mon, 21 Jul 2025 12:21:42 +0000

Hi there

I'm using Ubuntu 24.04 (Noble) KDE Neon image from may 26, 2025.

After download this image and installing it, Wayland was working fine, not problems at all.

Then, after a system upgrade, if i choose Wayland from session manager, the system freezes and i can't boot with Wayland, only X11...

Before the update, the system was smooth, now it's really laggy....Like i said, i'm using Desktop image with Armbian Linux v6.12 KDE Neon (Ubuntu 24.04)

There's something wrong with the update

Anyone knows why is this happening, and any turnaround to use Wayland again?

Bug Report: Armbian Edge Kernel 6.16.4 + xfsprogs (trixie package) = Failure To Start low-memory-monitor.service

Thu, 09 Oct 2025 01:38:32 +0000

Hardware: 		OrangePI-5-Plus (rk3588), with "32 GB" of RAM
Operating System: 	Debian Trixie (pure, except EFI boot and Armbian edge kernel)
Root File System:	Ext4 (encrypted)
Desktop:		KDE Plasma 6.3.6 (wayland, GDM3), KDE Frameworks version: 6.13.0, QT version: 6.8.2

EFI Source:		https://github.com/edk2-porting/edk2-rk3588

The boot messages, after a few starts (spaced apart) of the low-memory-monitor.service, say there's a failure to start it.

After booting is complete, here's a screenshot of the output of:

systemctl status low-memory-monitor.service

This error didn't show up until I installed a number of packages. I tracked down the offending package from the Trixie repository:

Package:	xfsprogs
Version:	6.13.0-2+b1
Size:		4774 kB
Description:	A set of commands to use the XFS filesystem, including mkfs.xfs

Once this package was removed, the error vanished, and a repeat of the above Status command reported low-memory-monitor-service as active and okay.

I also found that, while the error occurred with the Armbian edge 6.16.4 kernel, it did NOT occur with the Debian 6.16.3 kernel.

Kernel With The Error (kernel source: Armbian trixie)
---------------------
Package:    linux-image-edge-rockchip64 (Armbian Linux edge kernel image 6.16.4-edge-rockchip64)
Version:    25.8.1
Size:       282 MB


Kernel Without The Error (kernel source: Debian trixie-backports)
------------------------
Package:    linux-image-6.16.3+deb13-arm64-unsigned (Linux 6.16 for 64-bit ARMv8 machines)
Version:    6.16.3-1~bpo13+1
Size:       210 MB

I also briefly tried regressing the Armbian edge kernel from 25.8.1 (6.16.4) to the previously available version of 25.5.2, which was 6.16.0-rc3 (I think). The error occurred with that kernel as well.

An Effect of This Bug (Possibly)

When this error was showing up, I was once using the internet (firefox-esr package version 140.3.1esr-1~deb13u1) for a while, when after closing it, I discovered that my desktop background image had changed on its own. I could not change it back, no matter what I did (in the KDE settings gui). I could change it to something else, but whenever I changed it back, the altered image returned instead of what it should have been. But once I rebooted, the background was back to normal. While this one experience (very much an outlier) may not be conclusive, it is indicative of a possible memory leak.

FreeRDP - build wlfreerdp client with hwacc

Sat, 27 Sep 2025 15:39:31 +0000

       ##O#O##          OS: Armbian 25.8.1 noble aarch64 
       #######          Host: Orange Pi 5 Plus 
     ###########        Kernel: 6.1.115-vendor-rk35xx 
    #############       Uptime: 1 day, 8 hours, 17 mins 
   ###############      Packages: 1852 (dpkg), 5 (snap) 
   ################     Shell: bash 5.2.21 
  #################     Resolution: 3840x2160 
#####################   DE: GNOME 46.0 
#####################   WM: Mutter 
  #################     WM Theme: Adwaita 
                        Theme: Adwaita [GTK2/3] 
                        Icons: Adwaita [GTK2/3] 
                        Terminal: x-terminal-emul 
                        CPU: (8) @ 1.800GHz 
                        Memory: 7245MiB / 15957MiB

FreeRDP client:

freerdp2-wayland:
Инсталирана: 2.11.5+dfsg1-1build2
Кандидат:    2.11.5+dfsg1-1build2
Таблица с версиите:
*** 2.11.5+dfsg1-1build2 500
        500 http://ports.ubuntu.com noble/universe arm64 Packages
        100 /var/lib/dpkg/status

---------------------------------------------------------------------------------------------------------

This is Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=ON HAVE_AIO_H=1 HAVE_EXECINFO_BACKTRACE=1 HAVE_EXECINFO_BACKTRACE_SYMBOLS=1 HAVE_EXECINFO_BACKTRACE_SYMBOLS_FD=1 HAVE_EXECINFO_H=ON HAVE_EXECINFO_HEADER=1 HAVE_FCNTL_H=1 HAVE_GETLOGIN_R=1 HAVE_GETPWUID_R=1 HAVE_INTTYPES_H=1 HAVE_JOURNALD_H=TRUE HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_PIXMAN_REGION=OFF HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIBS= HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL=1 HAVE_SYSLOG_H=1 HAVE_SYS_EVENTFD_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_SYS_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=ON WITH_CAIRO=ON WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_URBDRC=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_EVENTFD_READ_WRITE=1 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=OFF WITH_GFX_H264=OFF WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_ICU=ON WITH_INTERNAL_MD4=OFF WITH_INTERNAL_MD5=OFF WITH_IPP=OFF WITH_JPEG=ON WITH_KERBEROS=ON WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=ON WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_OPENCL=OFF WITH_OPENH264=OFF WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=ON WITH_PAM=ON WITH_PCSC=ON WITH_PROFILER=OFF WITH_PROXY=OFF WITH_PULSE=ON WITH_SAMPLE=OFF WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY_AVAILABLE=1 WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD_AVAILABLE=1 WITH_SERVER=ON WITH_SERVER_CHANNELS=ON WITH_SERVER_INTERFACE=ON WITH_SHADOW=ON WITH_SMARTCARD_INSPECT=OFF WITH_SOXR=OFF WITH_SSE2=OFF WITH_SWSCALE=OFF WITH_THIRD_PARTY=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_VERBOSE_WINPR_ASSERT=ON WITH_WAYLAND=ON WITH_WINPR_TOOLS=ON WITH_X11=ON WITH_XCURSOR=ON WITH_XDAMAGE=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=ON WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XTEST=ON WITH_XV=ON WITH_ZLIB=ON

Hi guys,

I am using `wlfreerdp` to access remote Win 11 but the client I have installed does not support hwacc and is laggy on 4K monitor. Network is 1G LAN.

I have already built Moonlight with ffmpeg/rkmpp hwacc and it works amazing.

Can anyone advice if I can do the same, building the FreeRDP client with hwacc?

CC:@amazingfate (I know u know how to do it ;) )

XFCE will not come up on boot from nvme

Thu, 25 Sep 2025 12:27:08 +0000

HW: OrangePi5 Plus 32 32 GB RAM
512 GB NVME
5K Monitor
Image: Armbian_25.8.1_Orangepi5-plus_trixie_vendor_6.1.115_xfce_desktop.img

prepare system before each case
dd if=u-boot-V2024.04-orangepi5-plus-spi.img of=/dev/mtdblock0
flash_erase /dev/mtd0 0 0

case 1:
1. copy image to 64GB uSD
2. booting
3. system comes up with xfce
4. sudo apt-get -y update; apt-get -y upgrade
5. reboot
6. system comes up, without desktop. system is reachable with ssh

case 2:
1. copy image to 64GB uSD
2. booting
3. system comes up with xfce
4. armbian-install
5. choose boot from mtd flash
6. choose nvme0n1p1
6. update mtdblock0
7. reboot
8. system comes up, without desktop. system is reachable with ssh

any idea whats going wrong?

OrangePi 5 Plus No display output after replugging Type-C monitor following extended disconnect

Wed, 24 Sep 2025 14:23:14 +0000

the issue is as follows:
1. When using the Type-C interface to connect to an external monitor, the display works normally if the monitor is connected after the development board has started.
2. If the monitor is disconnected and then reconnected after approximately several hours (possibly more than 6 hours), the display fails to show any image.

I used the `armbianmonitor -u` command, and it output the following URL.

https://paste.armbian.com/foyecusoju

If the Type-C interface is functioning normally, the latest output from `dmesg -w` would show the following:

[ 1155.922647] xhci-hcd xhci-hcd.15.auto: xHCI Host Controller
[ 1155.922692] xhci-hcd xhci-hcd.15.auto: new USB bus registered, assigned bus number 7
[ 1155.922885] xhci-hcd xhci-hcd.15.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0002008002010010
[ 1155.922937] xhci-hcd xhci-hcd.15.auto: irq 116, io mem 0xfc000000
[ 1155.923133] xhci-hcd xhci-hcd.15.auto: xHCI Host Controller
[ 1155.923152] xhci-hcd xhci-hcd.15.auto: new USB bus registered, assigned bus number 8
[ 1155.923173] xhci-hcd xhci-hcd.15.auto: Host supports USB 3.0 SuperSpeed
[ 1155.923455] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[ 1155.923476] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1155.923491] usb usb7: Product: xHCI Host Controller
[ 1155.923502] usb usb7: Manufacturer: Linux 6.1.115-vendor-rk35xx xhci-hcd
[ 1155.923515] usb usb7: SerialNumber: xhci-hcd.15.auto
[ 1155.924750] hub 7-0:1.0: USB hub found
[ 1155.924811] hub 7-0:1.0: 1 port detected
[ 1155.925434] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
[ 1155.925607] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01
[ 1155.925625] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1155.925638] usb usb8: Product: xHCI Host Controller
[ 1155.925649] usb usb8: Manufacturer: Linux 6.1.115-vendor-rk35xx xhci-hcd
[ 1155.925660] usb usb8: SerialNumber: xhci-hcd.15.auto
[ 1155.928950] hub 8-0:1.0: USB hub found
[ 1155.929019] hub 8-0:1.0: 1 port detected
[ 1156.590377] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 10(if:DP0, flag:0x0) for vp2 dclk: 533120000
[ 1156.590574] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out2 div: 2 dclk_core2 div: 2
[ 1156.590639] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop2 to 533120000, get 533119995
[ 1156.621808] dw-dp fde50000.dp: full-training link: 4 lanes at 5400 MHz
[ 1156.635430] dw-dp fde50000.dp: clock recovery succeeded
[ 1156.644918] dw-dp fde50000.dp: channel equalization succeeded
[ 1156.657348] rockchip-vop2 fdd90000.vop: [drm] vop enable intf:200
[ 1157.337766] dw-dp fde50000.dp: test_type0 is not support
[ 1157.339516] dw-dp fde50000.dp: test_type0 is not support
[ 1159.801886] usb 7-1: new high-speed USB device number 2 using xhci-hcd
[ 1159.942247] usb 7-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[ 1159.942271] usb 7-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1159.942278] usb 7-1: Product: USB 2.0 Hub
[ 1159.978762] hub 7-1:1.0: USB hub found
[ 1159.978833] hub 7-1:1.0: 4 ports detected
[ 1160.375255] usb 7-1.3: new full-speed USB device number 3 using xhci-hcd
[ 1160.583425] usb 7-1.3: New USB device found, idVendor=222a, idProduct=0001, bcdDevice= 0.02
[ 1160.583438] usb 7-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1160.583441] usb 7-1.3: Product: ILITEK-TP
[ 1160.583443] usb 7-1.3: Manufacturer: ILITEK
[ 1160.653326] input: ILITEK ILITEK-TP as /devices/platform/usbdrd3_0/fc000000.usb/xhci-hcd.15.auto/usb7/7-1/7-1.3/7-1.3:1.0/0003:222A:0001.0005/input/input26
[ 1160.708695] input: ILITEK ILITEK-TP Mouse as /devices/platform/usbdrd3_0/fc000000.usb/xhci-hcd.15.auto/usb7/7-1/7-1.3/7-1.3:1.0/0003:222A:0001.0005/input/input28
[ 1160.709353] hid-multitouch 0003:222A:0001.0005: input,hiddev97,hidraw2: USB HID v1.10 Mouse [ILITEK ILITEK-TP] on usb-xhci-hcd.15.auto-1.3/input0

If it is not functioning normally, it will not output any content.

Can't boot on Orange pi 5 plus

Thu, 01 May 2025 05:27:19 +0000

I followed this manual

I tried to boot , led was green and red , Display did not work.

But Orange pi official images ca n boot my machine.

How can I solve this problem?

Trixie KDE Plasma 6 Wayland Rendering Bug

Fri, 12 Sep 2025 03:54:54 +0000

On the OrangePI-5-Plus, using an edge kernel, I've found that the desktop environment's GPU rendering works very smoothly on Wayland, in KDE 6 on Debian Trixie. It renders much more smoothly than gnome with Wayland (it's been my experience that the edge kernel is the only one that works).

But I've encountered a major rendering bug. It only appears in Trixie KDE Plasma 6 with Wayland rendering. It does not appear when using x11 or when using either rendering in gnome. Nor does it appear at all in Bookworm.

I have tried all kinds of things to "fix" these to no avail, including installing more wayland and mesa packages, then upgrading them to stable backports and then even to unstable testing (forky) versions. I've also tried the Debian unstable edge kernel from testing (6.16.3) as well as the Armbian stable edge kernel (6.16.4) with the same results.

I installed Debian Trixie using the Debian .iso installer (w/ EFI boot), then upgraded to their edge/testing kernel (6.16.3) from their testing/forky repository. The bug showed up in pure Debian without a drop of Armbian. Then I installed the Armbian stable edge kernel (6.16.4) to replace the Debian edge/testing kernel in that installation. The bug remained.

The rendering bug also showed up in the release version of Armbian Trixie 25.8.1 using the Armbian edge kernel.

KDE 6 Wayland Render Bug Symptom: The [ALT-TAB] Task-Switcher's Text Labels (see screenshot #1)

The major place this bug shows up is in the task switcher (using ALT-TAB). The window labels, instead of rendering as textual fonts, they render as blocks.

I tried several things with the fonts, from changing their type and size, turning on/off anti-aliasing, to changing the desktop themes, and so on. I also tried using different "task switchers" from the list. All I got were the same blocks -they just appeared in different sizes and positions with no other changes.

So I'm reasonably sure the rendering issue has nothing to do with fonts, desktop themes, Plasma settings, etc.

KDE 6 Wayland Render Bug Symptom: glmark2 (x11) verses glmark2-wayland (see screenshots #2 and #3)

Using the command-line utility: glmark2, there's an x11 version and a Wayland version. The each render to an 800x600 window. Normally the only visual difference between them is that the Wayland version has no window borders around it. But with this bug, the Wayland version renders significantly smaller on the screen, and also at a significant performance reduction (>50%).

Conclusion

I already know it isn't an Armbian issue.

I don't believe it's a kernel issue either.

I'm reasonably sure it has nothing to do with fonts, themes, or Plasma settings.

In my internet searches, I have found no other reports of this specific rendering bug that I think are relevant to whatever is happening now.

I did find some vague statements about there still being some "issues" with rendering in the upgrade from KDE 5 (using QT5 libraries) to KDE 6 (using QT6 libraries).

I also read that KDE Plasma 6 has a somewhat unique interface or relationship with Wayland and uses its own protocols with it. I think this explains why the bug doesn't show up in gnome, and also helps to isolate, to a degree, where the bug actually is.

From what I've read, apparently this issue shows up differently on different systems? It is my impression that these specific symptoms of this bug may be unique to this hardware (Rockchip rk3588 SoC) or GPU (MALI-G610 (built-in)), even though it is a clearly a software bug.

Operating System: Debian GNU/Linux 13
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.16.4-edge-rockchip64 (64-bit)
Graphics Platform: Wayland

EDIT: P.S.

I just ran Fedora's KDE Plasma 6 image. There were about a thousand updates to run on it. Plasma 6.3.4 (think) upgraded to version 6.4. And their mainline kernel (6.14 upgraded to 6.16.7 I think). The rendering bug I mentioned here did not show up either before or after those updates. So it appears the issue isn't with KDE Plasma itself either, that it's apparently on Debian's end. I noticed some of the (Debian) packages are specifically to bridge 5 and 6. I would guess that's where the problem is - apparently they didn't make a clean break.

Screenshot #1: [ALT-TAB] task-switcher

Screenshot #2: glmark2

Screenshot #3: glmark2-wayland

Orange Pi 5 Plus Camera Not Working ov13855

Fri, 05 Sep 2025 21:44:47 +0000

I made a configuration via armbian-config, but the camera does not work, here are the messages

/sys/bus/i2c/drivers/ov13855

3-0036 bind uevent unbind

sudo i2cdetect -y 3

0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- UU -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- 58 -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

dmesg | grep ov13855

[ 14.074752] platform csi2-dphy0: Fixed dependency cycle(s) with /i2c@feab0000/ov13855-1@36
[ 14.338234] ov13855 3-0036: driver version: 00.01.04
[ 14.338301] ov13855 3-0036: Failed to get power-gpios, maybe no use
[ 14.338330] ov13855 3-0036: Looking up avdd-supply from device tree
[ 14.338336] ov13855 3-0036: Looking up avdd-supply property in node /i2c@feab0000/ov13855-1@36 failed
[ 14.338365] ov13855 3-0036: supply avdd not found, using dummy regulator
[ 14.338418] ov13855 3-0036: Looking up dovdd-supply from device tree
[ 14.338424] ov13855 3-0036: Looking up dovdd-supply property in node /i2c@feab0000/ov13855-1@36 failed
[ 14.338434] ov13855 3-0036: supply dovdd not found, using dummy regulator
[ 14.338454] ov13855 3-0036: Looking up dvdd-supply from device tree
[ 14.338459] ov13855 3-0036: Looking up dvdd-supply property in node /i2c@feab0000/ov13855-1@36 failed
[ 14.338468] ov13855 3-0036: supply dvdd not found, using dummy regulator
[ 14.338484] ov13855 3-0036: could not get default pinstate
[ 14.338487] ov13855 3-0036: could not get sleep pinstate
[ 14.348869] ov13855 3-0036: Detected OV00d855 sensor, REVISION 0xb0
[ 14.863602] ov13855 3-0036: Consider updating driver ov13855 to match on endpoints
[ 14.863609] rockchip-csi2-dphy csi2-dphy0: dphy0 matches m00_b_ov13855 3-0036:bus type 5

with the original distribution the camera works

How can I enable the temperature-controlled fans instead of constantly running

Thu, 04 Sep 2025 15:26:41 +0000

Hello everyone,

I flashed the armbian into my tf cand and inserted it into my OrangePi 5 Plus, with my fans inserted to the specific socket on board (2pin, 1.25mm, 5V, PWM3_IR_M1). However, when I booted it, the fans was running constantly instead of controlled by temperature dynamically, like the official OS images that did only the fans running when the temperature over 50 celsius.

I wanna know how to configure my OS to enable the temperature-controlled fans like the official images.

The offical documents shows:
Linux uses the default pwm-fan drivers to control thye fans and the device tree was defined in orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts

Here is the code:

fan: pwm-fan {

compatible = "pwm-fan";

#cooling-cells = <2>;

pwms = <&pwm3 0 50000 0>;

cooling-levels = <0 50 100 150 200 255>;

rockchip,temp-trips = <

50000 1

55000 2

60000 3

65000 4

70000 5

>;



status = "okay";

};

Here are some descriptions regarding some columns:

pwms = <&pwm3 0 50000 0>：The fans use pwm3.

cooling-levels = <0 50 100 150 200 > 255>：Used to configure the speed levels (duty cycle of PWM). The number and magnitude of the levels can be customized. 6 levels are configured, with the speed range from 0 to 255.

rockchip,temp-trips：Used to configure the correspondence between CPU temperature and fan speed levels. This can be adjusted according to actual needs. In the above configuration, 50°C corresponds to level 1, and 70°C corresponds to level 5.

Thank you very much.

Custom Build ot working completly

Wed, 30 Jul 2025 03:50:53 +0000

Hi Guys,
Here is my requirements for an electron app running Armbian OS on orangepi5 plus to support:

Need GPU hardware acceleration to play video
Need HDMI audio
And possible NPU support.

I really need help, I did lots of custom builds to find solution support all my above requirement and I found Armbian-unofficial_25.08.0-trunk_Orangepi5-plus_noble_edge_6.16.0-rc7_cinnamon_desktop.img. But my electron add crashes after running say 8 hrs or so, means it is not very stable for us
[83833:0723/100030.362659:ERROR:ssl_client_socket_impl.cc(877)] handshake failed; returned -1, SSL error code 1, net_error -202 [83790:0723/101648.420086:ERROR:zygote_communication_linux.cc(296)] Failed to send GetTerminationStatus message to zygote [83790:0723/101648.423629:ERROR:network_service_instance_impl.cc(612)] Network service crashed, restarting service. [83790:0723/101648.434571:ERROR:zygote_communication_linux.cc(296)] Failed to send GetTerminationStatus message to zygote [83790:0723/101648.439553:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.440252:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.440865:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.441459:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.442003:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.442527:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.443115:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.443586:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.444045:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002
[83790:0723/101648.444060:FATAL:gpu_data_manager_impl_private.cc(420)] GPU process isn't usable. Goodbye.

I did try other custom build as below, but either they are lacking HDMI audio or GPU hardware acceleration.

Please help with this.
Thanks

Manish

I must disable liujianfeng1994 repo if I want watch video on youtube. Any reason.

Wed, 20 Aug 2025 19:09:18 +0000

Hi.

I am not complaining. I just would like to understand why I must deactivate https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu/ if I want watching video on Youtube.

If it's needed to disable this repo for watching video. I am ok. But why I can't read video with package from this repo?

https://paste.armbian.com/vaxedisuda

Is there an overlay for a 1024x600 display?

Fri, 08 Aug 2025 06:21:22 +0000

Is there an overlay or any other way of getting the Orange Pi 5 Plus to work with a 1024x600 display?

Armbian 25.5.1 Home Assistant Image Error

Sun, 20 Jul 2025 01:39:51 +0000

I've downloaded the Armbian 25.5.1 (Kernel 6.12) Home Assistant image (https://dl.armbian.com/orangepi5-plus/Bookworm_current_minimal-homeassistant), burned to microsd and rebooted the orange pi 5 plus. I burned the image to a microsd cards, inserted the microsd and did a hard reboot of the SBC. The error message is "Gave up waiting for root filesystem device."

Home Assistant with full Armbian desktop experience?

Wed, 23 Jul 2025 16:46:36 +0000

Is there an Armbian image with home assistant that isn't minimalistic? or Is there a way to install HA on a more robust desktop armbian 25.2 image for the Orange Pi 5 Plus? I feel the orange pi 5 is robust enough to handle HA under a desktop Armbian environment than other SBCs.

boot from nvme, install via armbian-install ?

Mon, 21 Jul 2025 17:03:02 +0000

i also have issues to move the system to the nvme ssd 😞

my base is the Armbian 25.5.1 with 6.1.115 (vendor kernel) image ....
"copied" (usbimager) it to the sdcard and its booting ... 🙂

so I upgraded the system on the sdcard, still running 🙂

I read some posts and advices ....

so I partioned the nvme with one big partition (/dev/nvme0n1p1)

running armbian-install
choosing option 7, (loading/upgrading bootloader to mtd )
after this i choose option 4 (boot from mtd, system on sata, usb ... )

only possible selection was /dev/nvme0n1 ... looked ok
said yes to everything

no Error

system goes to shutdown /power off

removed power, removed sdcard

plugin power again .... and ... no boot 😞

serial console saying:

DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18
ch0 ttot10
ch1 ttot10
ch2 ttot10
ch3 ttot10
ch0 ttot18
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
ch1 ttot18
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
ch2 ttot18
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
ch3 ttot18
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
Manufacturer ID:0xff
DQS rds:h1,h1
CH0 RX Vref:27.1%, TX Vref:21.8%,22.8%
DQ rds:h1 l0 h2 l0 h1 h5 l0 l0, l0 h3 l0 h3 h7 h2 l0 h1

DQS rds:l0,h1
CH1 RX Vref:28.5%, TX Vref:23.8%,23.8%
DQ rds:h1 h2 h1 h3 h1 h3 l0 h1, h1 h4 h1 h4 h1 h3 l0 h4

DQS rds:l0,h1
CH2 RX Vref:27.5%, TX Vref:23.8%,22.8%
DQ rds:h1 h3 h2 h1 h1 h6 h4 h1, h1 h2 h6 l0 h6 h2 h6 h3

DQS rds:h1,l0
CH3 RX Vref:29.7%, TX Vref:21.8%,20.8%
DQ rds:h5 h3 h2 h1 h3 h2 h2 h2, h5 h2 h1 h2 h4 l0 l0 h5

stride=0x2, ddr_config=0x4
hash ch_mask0-1 0x20 0x40, bank_mask0-3 0xa00 0x1400 0x2800 0x0, rank_mask0 0x401000
change to F1: 528MHz
ch0 ttot10
ch1 ttot10
ch2 ttot10
ch3 ttot10
change to F2: 1068MHz
ch0 ttot14
ch1 ttot14
ch2 ttot14
ch3 ttot14
change to F3: 1560MHz
ch0 ttot16
ch1 ttot16
ch2 ttot16
ch3 ttot16
change to F0: 2112MHz
ch0 ttot18
ch1 ttot18
ch2 ttot18
ch3 ttot18
out
U-Boot SPL board init
U-Boot SPL 2017.09-armbian-2017.09-S3e40-P187d-He5fc-Ve691-Bb703-R448a (May 30 2025 - 10:51:06)
sfc cmd=03H(6BH-x4)
Trying to boot from MMC2
MMC: no card present
mmc_init: -123, time 0
spl: mmc init failed with error: -123
Trying to boot from MTD2
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(7612223b82...) + OK
## Checking uboot 0x00200000 ... sha256(11a994b967...) + OK
## Checking fdt 0x00354c30 ... sha256(e3b0c44298...) + OK
fdt_record_loadable: FDT_ERR_BADMAGIC
## Checking atf-2 0xff100000 ... sha256(70505bb764...) + OK
fdt_record_loadable: FDT_ERR_BADMAGIC
## Checking atf-3 0x000f0000 ... sha256(b2af21b504...) + OK
fdt_record_loadable: FDT_ERR_BADMAGIC
Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)
Total: 496.285/765.931 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48
NOTICE:  BL31: Built : 15:02:44, Dec 19 2024
INFO:    spec: 0x1
INFO:    code: 0x88
INFO:    ext 32k is valid
INFO:    ddr: stride-en 4CH
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
INFO:    l3 cache partition cfg-0
INFO:    system boots from cpu-hwid-0
INFO:    disable memory repair
INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
INFO:    dfs DDR fsp_params[0].freq_mhz= 2112MHz
INFO:    dfs DDR fsp_params[1].freq_mhz= 528MHz
INFO:    dfs DDR fsp_params[2].freq_mhz= 1068MHz
INFO:    dfs DDR fsp_params[3].freq_mhz= 1560MHz
INFO:    BL31: Initialising Exception Handling Framework
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 = 0x200000
INFO:    SPSR = 0x3c9
No valid device tree binary found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d 
initcall sequence 00000000002d2af8 failed at call 00000000002c502c (err=-1)
### ERROR ### Please RESET the board ###

if im boot with sdcard in the system and mount /dev/nvm0n1p1 there is the whole system ....
inklusive /boot und boot/dtb .....

what didd I miss ?

Does anyone hav a link to a working tutorial ?

Whats the right kernel / OS for me ?

Wed, 28 May 2025 09:51:04 +0000

Hello all,

I'm also bought an orange pi 5 pro :-)

I have red a little bit in the Forum (after i'm bought) and I'm a little bit confused now 🙂
I'm new in the embedded (arm) world but have some knowledge from the desktop/x86 windows & linux world.

my first expirience with the device was also .... intresting.

I'm installed the official (orangepi.org) debian-booksworm image with the 6.1.xx kernel .... and diddnt get the network interfaces to run, and no nvme device available ...

next try was with debian-booksworm image and the 5.10..xx kernel and the networks just runned and the nvme showed up. But i think for my need this kernel is just old ...

So now im trying armbian (iot version) ..... at the moment with an 6.1.99 vendor kernel.
installed weston seatd & co for running some rudimentary OpenGL ES based tests .... but without success.
glxgears / glxinfo failing EGLInitialize() cannot create context ... rknpuxxxx.so not found.
i think thats the "which /dev/dri device is the right" issue. Have also red that some HW functionally is only available on full blown desktop environments 😞

What do I need:
- i dont want to use the device as a desktop replacement

- i want to use it as development board for tinkering around with OpenGL ES / OpenCL and get some experience with embedded development.
- rudimentary boot2qt functionality based on wayland-egl or eglfs platform (running Qt apps in wayland cage or without window manager)
- good opengl es 3.2 support

- recent compiler support, gcc13(+) / clang 18

- boost / qt 6.7 + should available as devel packages (don't like to build it for my own, but if its necesarry ...)

- opencl support would be nice

- media / audio support (QMultimedia)

- atm i dont need video acceleration, but maybe later ....

So my question:

with which Kernel / System should i start with ?
is the device a good choice ? I bought it mainly because the 2 nics and the available storage options (nvme / emmc) makes it very flexible for another usage (router backup i.e)
Soon or later i have to dig into yocto also maybe ....

Orange Pi 5 Plus multiple "fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing HDMI pull out, return!" errors on boot

Thu, 17 Jul 2025 17:37:22 +0000

After enabling the rk3588-hdmirx overlay in armbian-config device tree overlays, whenever I boot, I am greeted with multiple hdmirx (fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing HDMI pull out, return!) errors on boot.

On a previous install, the hdmirx errors would block the entire boot process and it would just hang forever. I do not know the exact cause, but the issues seemed to arise after I ran this command to disable the X Display Server "systemctl set-default multi-user.target".

The errors could only be resolved if I plugged in the sd card into another device and removed rk3588-hdmirx from overlays in /boot/armbianEnv.txt .

I have since reinstalled Armbian, but the errors still appear during the boot process, however now they do not block the boot process and I am able to successfully boot into Armbian.

Is there any solution to get rid of these errors, or ensure that the "fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing HDMI pull out, return!" error doesn't block the boot process without disabling hdmirx?

These are my current device details:

               ..                     orangepi@orangepi5-plus
            `:]x**j-,'                 -----------------------
       .,+t***********z\<"             OS: Armbian 25.5.1 noble aarch64
       ?******************;            Host: Orange Pi 5 Plus
      '*n` .'`^,;;,^`'. ,cc.           Kernel: Linux 6.1.115-vendor-rk35xx
      -<.                .[l           Uptime: 30 mins
     //     ^^      ^^    \\           Packages: 1822 (dpkg)
     !^         ^^         ":          Shell: bash 5.2.21
    'tt}`     !~]rj_     ")t/.         Display: 3840x2160 @ 60 Hz 
    Itttt?'   ~~]rr]   `{tttt,         DE: KDE Plasma 6.3.90
    \tttttt!""I_]r("""~tttttt1         WM: KWin (Wayland)
  '_tttttttttttt)ftttttttttttti.       WM Theme: Breeze
 \*ztttttttttttttttttttttttttf**[      Theme: Breeze (Dark) [Qt], Yaru [GTK3]
l**c)tttttttttttttttttttttttt(z**,     Icons: breeze-dark [Qt], Yaru [GTK3]
.z*x.`tttttttttttttttttttttttt.`u*n    Font: Noto Sans (10pt) [Qt]
>`   (tttttttttttttttttttttt]   "I     Cursor: breeze (24px)
     ,tttttttttttttttttttttt`          Terminal: konsole 25.4.1
     ./tttttfttttttttfttttt(           CPU: rk3588 (8) @ 2.40 GHz
      'I)))(\()(tt))|\()({;'           GPU: Mesa Mali-G610 (Panfrost)
        .~~~~~~~|)~~~~~~~<             Memory: 4.34 GiB / 15.58 GiB (28%)
        '[)))))1|()))))))?             Swap: 0 B / 7.79 GiB (0%)
          ",,,"    ",,,^               Disk (/): 7.82 GiB /

Here is the dmesg log after boot up, the hdmirx errors appear near the end:

boot_errors.txt

My experiece setting up an Orange Pi 5 Plus, current issues

Fri, 11 Jul 2025 16:20:24 +0000

It's been a while since I used Armbian. I have tons of ARM SBCs from a few years back because I think they're fascinating but they either wind up being too slow or just not worth using it for whatever since x86 "SBC like" boards exist and are pretty cheap. Fast forward to now and I'm doing some touchscreen development and just because of how I have things setup I needed 3 things, I2C, Interrupt capable GPIO and an actual DisplayPort. That combination of things is surprisingly hard to find.

I had a couple of things on hand, (Seeed Odyssey x86, Odroid H2/H3, Rpi's, Nvidia Jetson Nano). I spent way more time than I should have trying to make each of these work, in the end only the Rpi4 worked because the GPIO is good, problem is the HDMI ports are native. That's kind of a thing with ARM SBC's that's opposite from x86 and desktop GPU's...the native display interface is usually DisplayPort of some form on x86. So with the Pi4 I had to use one of the few HDMI->DP adapters I could find (the other way is common, this way is rare) and it worked but it's kind of jank. The other SBCs had various issues with GPIO even though they had displayports.

So I picked up the Orange Pi 5 Plus because it has a typeC/DP which is fine. I think I tried the latest image of Armbian first, and it doesn't boot, there was a post here over a month ago about it so I wound up dropping Armbian cuz that's not a good start. Manjaro Rpi images work well, they have a dev image for the orange Pi but their device tree is missing the typeC displayport connections. Then I tried Orange Pi OS / Arch which looks ugly but the DP works....though the colors are swapped, like the red/green channels are mixed up. I couldn't get I2C2 working either. I saw a post on here about it mentioning the kernel version etc. but I couldn't get it by device wouldn't show up on a scan.

So I came back to Armbian, slightly older image with the vendor kernel. Has pretty much the same issues. After some messing around I found that the I2C4_M3 mux overlay works to put the I2C4 bus into play, this one worked for me. So I was able to compile my driver module against the orange Pi source and get it working but I still have this issue with the DP colors being swapped and slightly shifted. Something is off about the DP configuration. Right now I have enough to do what I need to do but I will have to resolve that. I'm leaning towards the issue being in the DT. If anyone has any ideas about this it'd be much appreciated.

Just figured I'd tell that little story in case some of the Armbian devs are looking for feedback. Think I'll stick with Armbian since it works better than anything else, though I much prefer Arch based distros. As for the Orange Pi itself, this thing is great. It's an actual development board, with enough interfaces to actually develop something, so I think I'll actually use this one.

Chromium Fails to Load

Sun, 18 May 2025 17:39:38 +0000

After installing official Armbian_25.2.1_Orangepi5-plus_bookworm_vendor_6.1.99_xfce_desktop.img to sdcard, then to nvme all is fine, until, I do an apt update & upgrade, after that point chromium fails to run. I explored the logs to see it a failure to load chromium.conf from /etc/chromium.d/chromium.config (failed symbolic link to /etc/armbian/chromium.config).

Is there a known workaround besides utilization of firefox?

How to enable sound on a server version of Armbian

Fri, 17 Jan 2025 06:39:04 +0000

I am running an unmodified Server version of Armbian Linux v6.12 (Ubuntu 24.04) on an Orange Pi 5 Plus.

I need to play sounds using the headphone jack on my SBC. Unfortunately the ES8388 sound chip is not recognized, the aplay -l output is as follows:

**** List of PLAYBACK Hardware Devices ****
card 0: Analog [Analog], device 0: fe470000.i2s-es8328-hifi-analog es8328-hifi-analog-0 [fe470000.i2s-es8328-hifi-analog es8328-hifi-analog-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

The correct output on desktop systems should like this (and it was like this on Desktop Armbian).

What should I do to enable the ES8388 sound chip while staying on a server OS? Change something in the boot environment maybe? Install drivers?

Available frequencies for RK3588 are wrong

Mon, 19 May 2025 14:58:47 +0000

Hi,

The RK3588 supports frequencies as low as 408MHz, but in armbian the minimum is 1008MHz, which makes the cpu run hotter and draw more power even when idle, compared with the OPI ubuntu version.

These are the available frequencies:

$ cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies 
1008000 1200000 1416000 1608000 1800000

$ cat /sys/devices/system/cpu/cpufreq/policy6/scaling_available_frequencies 
1200000 1416000 1608000 1800000 2016000 2208000 2400000

I want to add the missing frequencies, I tried to look in the armbian repo for dts files that contain these frequencies, but I couldn't find anything. Is is possible to do this by loading dti files on boot? or does it need a kernel recompile?

Thanks!

Switch Default Desktop Environment

Fri, 16 May 2025 00:12:28 +0000

How do I change the default desktop environment on Debian 12 startup from cinnamon to xfce4? I have installed xfce4 and it's related "goodies", added a .Xclients file containing "startxfc4" in both root and ~/ folder locations. But the unit sometimes boots back into cinnamon. I do not see anything under armbian-config to control the desktop environment or to switch between cli/gui. I recall such options under orangepi-config (at least the cli/gui switching).

How to install OpenCL on OrangePi 5 Plus

Sat, 04 Jan 2025 17:46:20 +0000

I want to install jellyfin on my OrangePi 5 Plus and need OpenCL to enable HDR-SDR mapping.

I tried to follow the instruction on Jellyfin's official website: Rockchip VPU | Jellyfin

However, I'm stucked on the step of installing OpenCL.

I also tried this: Install OpenCL on Debian and Ubuntu and Armbian for Orange Pi 5 RK3588

But no luck either.

Both instruction led to broken hardware acceleration in chrome and failing to start kernal in Jellyfin.

Logs from ffmpeg:

sudo /usr/lib/jellyfin-ffmpeg/ffmpeg -v debug -init_hw_device rkmpp=rk -init_hw_device opencl=ocl@rk

Applying option init_hw_device (initialise hardware device) with argument opencl=ocl@rk. 
arm_release_ver: g13p0-01eac0, rk_so_ver: 10 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded 
[AVHWDeviceContext @ 0xaaab055f5460] 1 OpenCL platforms found. 
[AVHWDeviceContext @ 0xaaab055f5460] 1 OpenCL devices found on platform "ARM Platform". 
arm_release_ver: g13p0-01eac0, rk_so_ver: 10 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded 
[AVHWDeviceContext @ 0xaaab055f5460] 0.0: ARM Platform / Unknown Device Segmentation fault

Logs from Jellyfin:

Failed creating base context during opening of kernel driver. 
Kernel module may not have been loaded 
Failed creating base context during opening of kernel driver. 
Kernel module may not have been loaded

Logs from clinfo:

arm_release_ver: g13p0-01eac0, rk_so_ver: 10
Failed creating base context during opening of kernel driver.
Kernel module may not have been loaded

I want to know how to correctly enable OpenCL on OrangePi 5 Plus, thank you!

[SOLVED] Armbian 25.2.1 NVMe SPI flash boot issues

Tue, 25 Feb 2025 20:38:11 +0000

EDIT: I tried using ext4 rather than btrfs and.. somehow that solved it? I don't understand how the SSD file system would change how the bootloader is flashed because if properly flashed, the SD card shouldn't work at all, unless something has changed.

Hey all,
I wanted to move to the newest version of armbian (25.2.1) and for whatever reason neither `apt update && apt upgrade` nor `armbian-upgrade` (as a sanity check) worked so I wiped the SPI flash using `mtdtools` as prescribed in the forum post linked on the support page.
1) Booted from SD, installed Armbian and the bootloader.
2) Shut down, removed SD and turned on. Machine hung and never booted from NVMe.
3) Thought somehow I did something wrong or there was an error and used MaskROM mode and `rkdeveloptool` to revert it to boot from SD.
4) Repeated step 2
5) Still won't boot from NVMe but boots from SD (should have tried this first)
6) Tried reinstalling the bootloader to SPI flash, get this message:

Processing blocks: 394/394 (100%)
diff blocks: 0
Done

Which reads like the flash is identical to what would is contained in the installer itself so it isn't overwritten.
Wiped again and tried to install bootloader again. Still won't boot from NVMe but boots from SD card normally.
Also, forgot to include this in my steps: I formatted the NVMe 3 times total and installed/reinstalled Armbian from the `armbian-install` script as a sanity check.

Have had no issues in the past with any of this (I think I was on 24.11 most recently) so my first thought was a bug in the installer but am not seeing anyone else having this issue so figured I would ask here just to be sure.

My questions are:
1) Has anyone else tried to use the installer on 25.2? I can't imagine there were any (much less breaking) changes but I am perplexed at this point.
2) Is the bootloader file available separately so I can flash it from `rkdeveloptools`
Worst case I can image 24.11 on to the SD and try to install the bootloader that way but again, id be surprised if there were major changes.

Thanks in advance!

Intel BE 200 Wi-Fi 7 not working on orange pi 5 plus running Armbian

Sat, 13 Jan 2024 07:32:08 +0000

My setup includes orange pi 5 plus, Samsung NVME SSD M2 4 TB with Armbain os. 256 GB eMMC and Intel BE 200 Wi-Fi. There are no drivers for the intel BE 200 Wi-Fi or any instructions to make it work.

Upgrade Armbian 25.02 to 25.05

Tue, 29 Apr 2025 10:25:26 +0000

I have installed Armbian 25.02 via an official Armbian image for Armbian 25.02 (Debian 12) Vendor Kernel 6.1.xx, is it possible (and sane) to upgrade to Armbian 25.05 (Debian 12) Vendor Kernel 6.1.xx? If so besides downloading the new image and installing fresh what are one's options?

Armbian Build KDE Plasma

Fri, 25 Apr 2025 14:09:34 +0000

I would love to use Armbian Build to construct a Debian 12 Bookworm images with KDE Plasma as the windows manager. I note that KDE Plasma isn't an option in the armbian builder. I have no problem building with XFCE or Cinnamon.

Kernels With EMMC Support

Sun, 06 Apr 2025 05:39:55 +0000

Is there a list of Armbian Kernels that include EMMC support?

I've tried the vendor kernel build 6.1.99, the LTS 6.12.21, and Bleeding Edge 6.14.0 to find they all lack the mmcblk0 under /dev/ , and lack overlays for it under /boot/dtb/rockchip/overlays/. I have wiped SPI and SPNOR without success.

Advice wanted, after todays update OPI 5 plus does not boot from nvme anymore

Wed, 02 Apr 2025 11:47:50 +0000

Hi @ all,

long time reader, but never managed to register.
Now it is time... as I'm not able to solve this myself, kindly asking for help.

I'm stuck, my Orangepi 5 plus stops boot at this:

Loading, please wait...
Starting systemd-udevd version 252.36-1~deb12u1
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... (initramfs)

What happened before?

Last year I bought the Orangepi 5 plus (8GB) and went ahead, testing everything out - having incredible fun with this little box.
But with a way to old/slow sd card which finally failed two or three months ago.

I went ahead and wrote the Armbian based Cinnamon (Kernel 6.1 incl. MESA/VPU) to a new SD Card.
Everything was working flawless, but still ... SD Card.
Therefore I bought a 1TB nvme, installed it and used armbian-install to
install the bootloader on MTD Flash. Afterwards I got everything working from nvme.
Amazing results, it just worked after armbian-install was finished.

I shut down the system, removed SD card and used the nvme install from now on for weeks on a daily basis.
Several apt-get dist-upgrades no problem at all.
The last one done Sunday, if I remember correctly.

Until today.
I had some spare time and decided to apt-get update and apt-get dist-upgrade again.
The commands finished without any error and new updates were done.

But now -I wanted to reboot the device- reboot stalled.
I see a black screen with above mentioned white text.

So, something must have gone wrong I think.
The Orangepi boots fine when I insert the SD Card again, also the nvme is there and can be mounted.
Seemingly all data is still there.

But how to proceed? I'm at a loss.
Can anything be done on my side to solve this? Or is a reinstall to be done?

The apt history logfile on the nvme (/var/logs/apt/history.log) contains both upgrades I mentioned and reads:

Start-Date: 2025-04-01  16:15:10
Commandline: apt-get dist-upgrade
Requested-By: edited (1000)
Upgrade: armbian-config:arm64 (25.5.0-trunk.286.0324.065110, 25.5.0-trunk.325.0401.114753), tzdata:arm64 (2025a-0+deb12u1, 2025b-0+deb12u1), firefox-nightly:arm64 (138.0a1~20250324091950, 139.0a1~20250401094015), ghostscript-x:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), libgs10-common:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), libgs10:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), ghostscript:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), linux-headers-vendor-rk35xx:arm64 (25.2.3, 25.2.3), libgs-common:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7)
End-Date: 2025-04-01  16:15:46

Start-Date: 2025-04-02  09:42:43
Commandline: apt-get dist-upgrade
Requested-By: edited (1000)
Upgrade: linux-image-vendor-rk35xx:arm64 (25.2.3, 25.2.3), firefox-nightly:arm64 (139.0a1~20250401094015, 139.0a1~20250401212749), linux-headers-vendor-rk35xx:arm64 (25.2.3, 25.2.3), armbian-bsp-cli-orangepi5-plus-vendor:arm64 (25.2.2, 25.2.3)
End-Date: 2025-04-02  09:44:34

term.log in this directory shows nothing unusual, too. As far as my limited knowledge reaches ofc:

Log started: 2025-04-01  16:15:10
(Reading database ... 218528 files and directories currently installed.)
Preparing to unpack .../0-tzdata_2025b-0+deb12u1_all.deb ...
Unpacking tzdata (2025b-0+deb12u1) over (2025a-0+deb12u1) ...
Preparing to unpack .../1-armbian-config_25.5.0-trunk.325.0401.114753_all.deb ...
Unpacking armbian-config (25.5.0-trunk.325.0401.114753) over (25.5.0-trunk.286.0324.065110) ...
Preparing to unpack .../2-firefox-nightly_139.0a1~20250401094015_arm64.deb ...
Unpacking firefox-nightly (139.0a1~20250401094015) over (138.0a1~20250324091950) ...
Preparing to unpack .../3-ghostscript-x_10.0.0~dfsg-11+deb12u7_arm64.deb ...
Unpacking ghostscript-x:arm64 (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ...
Preparing to unpack .../4-ghostscript_10.0.0~dfsg-11+deb12u7_arm64.deb ...
Unpacking ghostscript (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ...
Preparing to unpack .../5-libgs10_10.0.0~dfsg-11+deb12u7_arm64.deb ...
Unpacking libgs10:arm64 (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ...
Preparing to unpack .../6-libgs10-common_10.0.0~dfsg-11+deb12u7_all.deb ...
Unpacking libgs10-common (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ...
Preparing to unpack .../7-libgs-common_10.0.0~dfsg-11+deb12u7_all.deb ...
Unpacking libgs-common (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ...
Preparing to unpack .../8-linux-headers-vendor-rk35xx_25.2.3_arm64.deb ...
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' starting.
Cleaning directory /usr/src/linux-headers-6.1.99-vendor-rk35xx ...
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' finishing.
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' starting.
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' finishing.
Unpacking linux-headers-vendor-rk35xx (25.2.3) over (25.2.3) ...
Setting up libgs-common (10.0.0~dfsg-11+deb12u7) ...
Setting up linux-headers-vendor-rk35xx (25.2.3) ...
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' starting.
Configuring kernel-headers (6.1.99-vendor-rk35xx) - please wait ...
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/confdata.o
  HOSTCC  scripts/kconfig/expr.o
  LEX     scripts/kconfig/lexer.lex.c
  YACC    scripts/kconfig/parser.tab.[ch]
  HOSTCC  scripts/kconfig/lexer.lex.o
  HOSTCC  scripts/kconfig/menu.o
  HOSTCC  scripts/kconfig/parser.tab.o
  HOSTCC  scripts/kconfig/preprocess.o
  HOSTCC  scripts/kconfig/symbol.o
  HOSTCC  scripts/kconfig/util.o
  HOSTLD  scripts/kconfig/conf
#
# configuration written to .config
#
Compiling kernel-headers scripts (6.1.99-vendor-rk35xx) using 8 CPUs - please wait ...
  SYNC    include/config/auto.conf.cmd
  HOSTCC  scripts/dtc/flattree.o
  HOSTCC  scripts/dtc/dtc.o
  HOSTCC  scripts/dtc/fstree.o
  HOSTCC  scripts/dtc/data.o
  HOSTCC  scripts/dtc/livetree.o
  HOSTCC  scripts/dtc/treesource.o
  HOSTCC  scripts/dtc/srcpos.o
  HOSTCC  scripts/dtc/checks.o
  HOSTCC  scripts/dtc/util.o
  LEX     scripts/dtc/dtc-lexer.lex.c
  YACC    scripts/dtc/dtc-parser.tab.[ch]
  HOSTCC  scripts/dtc/libfdt/fdt.o
  HOSTCC  scripts/dtc/libfdt/fdt_ro.o
  HOSTCC  scripts/dtc/libfdt/fdt_wip.o
  HOSTCC  scripts/dtc/libfdt/fdt_sw.o
  HOSTCC  scripts/dtc/libfdt/fdt_rw.o
  HOSTCC  scripts/dtc/libfdt/fdt_strerror.o
  HOSTCC  scripts/dtc/libfdt/fdt_empty_tree.o
  HOSTCC  scripts/dtc/libfdt/fdt_addresses.o
  HOSTCC  scripts/dtc/libfdt/fdt_overlay.o
  HOSTCC  scripts/dtc/fdtoverlay.o
  HOSTCC  scripts/dtc/dtc-lexer.lex.o
  HOSTCC  scripts/dtc/dtc-parser.tab.o
  HOSTLD  scripts/dtc/fdtoverlay
  HOSTLD  scripts/dtc/dtc
  HOSTCC  scripts/kallsyms
  HOSTCC  scripts/sorttable
  HOSTCC  scripts/resource_tool
  HOSTCC  scripts/asn1_compiler
  HOSTCC  scripts/genksyms/genksyms.o
  YACC    scripts/genksyms/parse.tab.[ch]
  HOSTCC  scripts/selinux/mdp/mdp
  HOSTCC  scripts/selinux/genheaders/genheaders
  LEX     scripts/genksyms/lex.lex.c
  HOSTCC  scripts/genksyms/parse.tab.o
  HOSTCC  scripts/genksyms/lex.lex.o
  HOSTLD  scripts/genksyms/genksyms
Compiling kernel-headers scripts/mod (6.1.99-vendor-rk35xx) using 8 CPUs - please wait ...
  CC      scripts/mod/empty.o
  HOSTCC  scripts/mod/mk_elfconfig
  CC      scripts/mod/devicetable-offsets.s
  UPD     scripts/mod/devicetable-offsets.h
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/modpost.o
  HOSTCC  scripts/mod/file2alias.o
  HOSTCC  scripts/mod/sumversion.o
  HOSTLD  scripts/mod/modpost
  MODPOST scripts/mod/Module.symvers
Done compiling kernel-headers (6.1.99-vendor-rk35xx).
Done compiling kernel-headers tools (6.1.99-vendor-rk35xx).
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' finishing.
Setting up tzdata (2025b-0+deb12u1) ...

Current default time zone: 'Europe/Berlin'
Local time is now:      Tue Apr  1 16:15:44 CEST 2025.
Universal Time is now:  Tue Apr  1 14:15:44 UTC 2025.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

Setting up armbian-config (25.5.0-trunk.325.0401.114753) ...
Setting up firefox-nightly (139.0a1~20250401094015) ...
Setting up libgs10-common (10.0.0~dfsg-11+deb12u7) ...
Setting up libgs10:arm64 (10.0.0~dfsg-11+deb12u7) ...
Setting up ghostscript (10.0.0~dfsg-11+deb12u7) ...
Setting up ghostscript-x:arm64 (10.0.0~dfsg-11+deb12u7) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.36-9+deb12u10) ...
Processing triggers for man-db (2.11.2-2) ...
Log ended: 2025-04-01  16:15:46

Log started: 2025-04-02  09:42:43
(Reading database ... 218527 files and directories currently installed.)
Preparing to unpack .../armbian-bsp-cli-orangepi5-plus-vendor_25.2.3_arm64.deb ...
Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'preinst' starting.
Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'preinst' finishing.
Unpacking armbian-bsp-cli-orangepi5-plus-vendor (25.2.3) over (25.2.2) ...
Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PC7d0b-Vcff1-H2670-B6e44-R89c9': 'postrm' starting.
Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PC7d0b-Vcff1-H2670-B6e44-R89c9': 'postrm' finishing.
Preparing to unpack .../firefox-nightly_139.0a1~20250401212749_arm64.deb ...
Unpacking firefox-nightly (139.0a1~20250401212749) over (139.0a1~20250401094015) ...
Preparing to unpack .../linux-headers-vendor-rk35xx_25.2.3_arm64.deb ...
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' starting.
Cleaning directory /usr/src/linux-headers-6.1.99-vendor-rk35xx ...
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' finishing.
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' starting.
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' finishing.
Unpacking linux-headers-vendor-rk35xx (25.2.3) over (25.2.3) ...
Preparing to unpack .../linux-image-vendor-rk35xx_25.2.3_arm64.deb ...
Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' starting.
Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' finishing.
Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' starting.
Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' finishing.
Unpacking linux-image-vendor-rk35xx (25.2.3) over (25.2.3) ...
Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postrm' starting.
Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postrm' finishing.
Setting up linux-image-vendor-rk35xx (25.2.3) ...
Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' starting.
dkms: running auto installation service for kernel 6.1.99-vendor-rk35xx.
dkms: autoinstall for kernel: 6.1.99-vendor-rk35xx.
update-initramfs: Generating /boot/initrd.img-6.1.99-vendor-rk35xx
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.99-vendor-rk35xx
Image Name:   uInitrd
Created:      Wed Apr  2 09:43:11 2025
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    17096044 Bytes = 16695.36 KiB = 16.30 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.99-vendor-rk35xx to /boot/uInitrd
'/boot/uInitrd' -> 'uInitrd-6.1.99-vendor-rk35xx'
update-initramfs: Armbian: done.
Armbian: update last-installed kernel symlink to 'Image'...
'/boot/Image' -> 'vmlinuz-6.1.99-vendor-rk35xx'
Armbian: Debian compat: linux-update-symlinks install 6.1.99-vendor-rk35xx boot/vmlinuz-6.1.99-vendor-rk35xx
Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' finishing.
Setting up linux-headers-vendor-rk35xx (25.2.3) ...
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' starting.
Configuring kernel-headers (6.1.99-vendor-rk35xx) - please wait ...
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/confdata.o
  HOSTCC  scripts/kconfig/expr.o
  LEX     scripts/kconfig/lexer.lex.c
  YACC    scripts/kconfig/parser.tab.[ch]
  HOSTCC  scripts/kconfig/lexer.lex.o
  HOSTCC  scripts/kconfig/menu.o
  HOSTCC  scripts/kconfig/parser.tab.o
  HOSTCC  scripts/kconfig/preprocess.o
  HOSTCC  scripts/kconfig/symbol.o
  HOSTCC  scripts/kconfig/util.o
  HOSTLD  scripts/kconfig/conf
#
# configuration written to .config
#
Compiling kernel-headers scripts (6.1.99-vendor-rk35xx) using 8 CPUs - please wait ...
  SYNC    include/config/auto.conf.cmd
  HOSTCC  scripts/dtc/dtc.o
  HOSTCC  scripts/dtc/flattree.o
  HOSTCC  scripts/dtc/fstree.o
  HOSTCC  scripts/dtc/data.o
  HOSTCC  scripts/dtc/livetree.o
  HOSTCC  scripts/dtc/srcpos.o
  HOSTCC  scripts/dtc/treesource.o
  HOSTCC  scripts/dtc/checks.o
  HOSTCC  scripts/dtc/util.o
  LEX     scripts/dtc/dtc-lexer.lex.c
  YACC    scripts/dtc/dtc-parser.tab.[ch]
  HOSTCC  scripts/dtc/libfdt/fdt.o
  HOSTCC  scripts/dtc/libfdt/fdt_ro.o
  HOSTCC  scripts/dtc/libfdt/fdt_wip.o
  HOSTCC  scripts/dtc/libfdt/fdt_sw.o
  HOSTCC  scripts/dtc/libfdt/fdt_rw.o
  HOSTCC  scripts/dtc/libfdt/fdt_strerror.o
  HOSTCC  scripts/dtc/libfdt/fdt_empty_tree.o
  HOSTCC  scripts/dtc/libfdt/fdt_addresses.o
  HOSTCC  scripts/dtc/libfdt/fdt_overlay.o
  HOSTCC  scripts/dtc/fdtoverlay.o
  HOSTCC  scripts/dtc/dtc-lexer.lex.o
  HOSTCC  scripts/dtc/dtc-parser.tab.o
  HOSTLD  scripts/dtc/fdtoverlay
  HOSTLD  scripts/dtc/dtc
  HOSTCC  scripts/kallsyms
  HOSTCC  scripts/resource_tool
  HOSTCC  scripts/sorttable
  HOSTCC  scripts/asn1_compiler
  HOSTCC  scripts/genksyms/genksyms.o
  YACC    scripts/genksyms/parse.tab.[ch]
  HOSTCC  scripts/selinux/genheaders/genheaders
  HOSTCC  scripts/selinux/mdp/mdp
  LEX     scripts/genksyms/lex.lex.c
  HOSTCC  scripts/genksyms/parse.tab.o
  HOSTCC  scripts/genksyms/lex.lex.o
  HOSTLD  scripts/genksyms/genksyms
Compiling kernel-headers scripts/mod (6.1.99-vendor-rk35xx) using 8 CPUs - please wait ...
  CC      scripts/mod/empty.o
  HOSTCC  scripts/mod/mk_elfconfig
  CC      scripts/mod/devicetable-offsets.s
  UPD     scripts/mod/devicetable-offsets.h
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/modpost.o
  HOSTCC  scripts/mod/sumversion.o
  HOSTCC  scripts/mod/file2alias.o
  HOSTLD  scripts/mod/modpost
  MODPOST scripts/mod/Module.symvers
Done compiling kernel-headers (6.1.99-vendor-rk35xx).
Done compiling kernel-headers tools (6.1.99-vendor-rk35xx).
Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' finishing.
Setting up armbian-bsp-cli-orangepi5-plus-vendor (25.2.3) ...
Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'postinst' starting.
Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'postinst' finishing.
Setting up firefox-nightly (139.0a1~20250401212749) ...
Processing triggers for initramfs-tools (0.142+deb12u1) ...
update-initramfs: Generating /boot/initrd.img-6.12.12+bpo-arm64-16k
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8126a-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8126a-2.fw for module r8169
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.12.12+bpo-arm64-16k
Image Name:   uInitrd
Created:      Wed Apr  2 09:44:31 2025
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    57076607 Bytes = 55738.87 KiB = 54.43 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.12.12+bpo-arm64-16k to /boot/uInitrd
'/boot/uInitrd' -> 'uInitrd-6.12.12+bpo-arm64-16k'
update-initramfs: Armbian: done.
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Log ended: 2025-04-02  09:44:34

Any tips how to resolve this and boot from the nvme again?

I know initramfs exists and I can wrap my mind arround it what it does, but in the last years never had to solve anything regarding it.

I do not know where to look or start debugging

nightly system crash: caused by armbian-truncate-logs ?

Tue, 11 Feb 2025 11:12:27 +0000

Since at least one week I find the system every morning with solid red led, waiting for a command in uboot.

When looking at the journal messages, the last messages are always:

Feb 10 23:45:01 etnas2 CRON[5176]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 10 23:45:01 etnas2 CRON[5177]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
Feb 10 23:45:01 etnas2 CRON[5176]: pam_unix(cron:session): session closed for user root
Feb 11 00:00:01 etnas2 CRON[5213]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 11 00:00:01 etnas2 CRON[5212]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 11 00:00:01 etnas2 CRON[5215]: (root) CMD (/usr/lib/armbian/armbian-apt-updates)
Feb 11 00:00:01 etnas2 CRON[5214]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
Feb 11 00:00:01 etnas2 CRON[5212]: pam_unix(cron:session): session closed for user root
Feb 11 00:00:03 etnas2 CRON[5213]: pam_unix(cron:session): session closed for user root
Feb 11 00:00:49 etnas2 systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
Feb 11 00:00:49 etnas2 systemd[1]: Starting logrotate.service - Rotate log files...
Feb 11 00:00:49 etnas2 systemd[1]: dpkg-db-backup.service: Deactivated successfully.
Feb 11 00:00:49 etnas2 systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
Feb 11 00:00:49 etnas2 armbian-ramlog[5278]: Tue Feb 11 12:00:49 AM CET 2025: Syncing logs to storage
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: sending incremental file list
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: ./
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: Xorg.0.log
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: Xorg.0.log.old
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: armbian-hardware-monitor.log
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: auth.log
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: boot.log
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: btmp
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: cron.log
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: kern.log
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: lastlog
Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: syslog
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: user.log
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: wtmp
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: cups/access_log
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/lightdm.log
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/lightdm.log.old
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/seat0-greeter.log
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/seat0-greeter.log.old
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/x-0.log
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/x-0.log.old
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: samba/log.nmbd
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: samba/log.smbd
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: sent 3,469,661 bytes  received 448 bytes  2,313,406.00 bytes/sec
Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: total size is 4,794,812  speedup is 1.38
Feb 11 00:00:50 etnas2 systemd-journald[588]: Time spent on flushing to /var/log/journal/1141762e43884d8b9eb5d35b11be4daa is 55.926ms for 1057 entries.
Feb 11 00:00:50 etnas2 systemd-journald[588]: System Journal (/var/log/journal/1141762e43884d8b9eb5d35b11be4daa) is 17.4M, max 20.0M, 2.5M free.
Feb 11 00:00:50 etnas2 systemd-journald[588]: Received client request to flush runtime journal.
Feb 11 00:00:50 etnas2 systemd-journald[588]: Data hash table of /var/log/journal/1141762e43884d8b9eb5d35b11be4daa/system.journal has a fill level at 122.2 (5561 of 4551 items, 2621440 file size, 471 bytes per hash table item), suggesting rotation.
Feb 11 00:00:50 etnas2 systemd-journald[588]: /var/log/journal/1141762e43884d8b9eb5d35b11be4daa/system.journal: Journal header limits reached or header out-of-date, rotating.

After that no more messages, until the system gets booted again. The issue seems similar to this post. Power supply and system temperatures are fine, the system is running from EMMC memory so issues with SD cards are ruled out. When I boot off e.g. Jonathan Riek's Ubuntu 24.04 using the NVME drive, then all is fine: no nightly crashes. I don't recall this issue when I installed Armbian 24.11.2 back in December, so possibly it came when I upgraded to 24.11.3 using `apt upgrade` (but could be wrong!)

I have added the cron job `*/1 * * * * /usr/bin/dmesg > $HOME/kernel-dmesg.txt` as suggested.

Looking at `/etc/cron.d` and more precisely `armbian-trunctate-log`, I see that `armbian-trunctate-logs` runs every 15 minutes, but it invokes `armbian-ramlog` in practice only just after mignight probably because `/var/log` is over 75% full. Then `/usr/lib/armbian/armbian-truncate-logs` proceeds to synchronize (using `rsysnc`) the logs files in zram (`/var/log`).

After that, the script calls `/usr/sbin/logrotate --force /etc/logrotate.conf` but this rotation takes place on `/var/log.hdd/`.

Somehow that does not sound right... I would have thought it would be the other way around....

Finally, it just truncates the files in `/var/log`. That could be dangerous as processes have these files open... Logrotate sends a signal to processes to let them know they should reopen the log files.

armbianmonitor -u

Thanks in advance for any help.

Orange Pi 5 Plus | rk_hdmirx fdee0000.hdmirx-controller

Fri, 14 Mar 2025 16:51:05 +0000

Hi can anyone advise if they have come accross this issue.
so somehow HDMIRX seems to be the hdmi input controller starts to freak out for no reason
there is nothing plugged into it EVER and will randomly start to outpur this to console
im thinking maybe the HDMIRX is faulty and want to remove it, I have tried removing it

removed the DTB , decompiled and edited and removed it from DTB, tied to blacklist it but with no effect

it does not stop spamming and the device

[ 89.603095] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed!

[ 89.613765] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed!

[ 89.624917] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed!

[ 89.635554] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed!

[ 89.704256] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_controller_init wait timer base lock failed!

not for my last attemt i want to check if anyone has the .config for the kernel and perhaps knows what the driver / module is called

this way I am guaranteed i will not see it again.

Note: I have reinsatlled multiple distros to check and it keeps happening randomly
so any input on this would be great.

Much appreciated and thanks in advance.

Power usage with latest Kernel 6.12 Server Ubuntu build

Tue, 17 Dec 2024 21:47:04 +0000

Hi,

I've come from Joshua's 24.04 Server build. I was concerned that the support was dropping off as he's having a well deserved break.

I've installed the latest Server build from here. https://dl.armbian.com/orangepi5-plus/Noble_current_server-kisak

Works fine, have moved it to EMMC and removed the SD card.

I use a USB power meter to see how much juice it uses.

I noticed this build uses about 20 to 25% more when idle or under load compared to Josh's 6.1 kernel build. I am suspecting 6.12 has enabled more hardware in the OPi5+ and this is the reason.

Is there a way to disable some of the HW to lower the idle power usage?

On average it uses 5w on idle.

Thanks.

Loving the Armbian build.

Armbian Kernels with Functional I2C-2 Module

Sat, 01 Mar 2025 14:44:34 +0000

I have built quite a few Debian12 Desktop images from github.com/armbian/build for a Debian Bookworm/XFCE/Vendor Kernel environment and noticed that recent vendor kernels do not have I2C-2.M0 as a kernel module listed within armbian-config. It appears that only two kernel modules are to be found, one being Panthos, the other involving a change in frequence of some item.

This image does include I2C-2.mo:

Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img

which includes kernel: Linux Atlas 6.1.99-vendor-rk35xx #1 SMP Fri Feb 21 18:11:03 UTC 2025 aarch64 GNU/Linux

But these images do not contain the I2C-2.m0 kernel modules:

Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img (same kernel build as Ambian 25.0.2.0-trunk listed above sans I2C-2-m0)

Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_current_6.12.17_xfce_desktop.img

Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.99_xfce_desktop.img

Is it now necessary to customize the compile options for the kernel and choose that module for compilation when building newer vendor images?

It would make sense (to me at least) to have each build option to have vendor kernels contain the same precompiled kernel modules for simplicity sake.

I'm not even sure if the I2C-2.m0 is available or an option in the later vendor kernels to build.

steps for a working Kodi

Tue, 31 Dec 2024 08:17:31 +0000

I have a new Orange Pi 5 plus 16GB. Seems a pretty cool board and I want to replace my old Rpi 4 for Media center and Home assistant.

I tried several distribution but can't get all my stuff working.

The OPI5+ is attached to an onkio 5.1 receiver and the receiver go to a FHD TV.

What is want to achieve is

in Kodi

1. play video with GPU

2. libCec in Kodi to control Onkio volume

3. Passthrough audio

Is there a working solution?

Thank you

eMMC support & DT overlays

Fri, 30 Aug 2024 22:08:19 +0000

Hello everyone,

This is my 1st post on the forum.

My intention with this post is not to report a specific issue that I am running into, but more because I would like to collect info and suggestions from people with more experience than myself.

I've recently received an Orange Pi 5 Plus and have spent a bit of time exploring operating systems suitable for this system and have settled on the Armbian solution.

I'm a HW designer by trade, and have done some SW work, but I do not consider myself proficient in SW at all. I find my way around things, but that's about as far as it goes....

For the my planned use of the OPi5+, I will need eMMC boot (for the improved OS performance and longevity) and access to the various interfaces (mainly SPI and I2C) on the GPIO header.

What I have discovered so far:
- Version 6.1 of the Armbian built kernel supports the GPIO interfaces quite well (I haven't actually communicated with anything yet, just got the interfaces showing up in /dev), but I could not get it to see the eMMC storage on the board. I tried various different options and flavours of the 6.1 images and I never saw /dev mmcblk0 listed.

- Version 6.10 kernel builds were successful at accessing the eMMC (/dev/mmcblk0 was present) and I have successfully transferred the OS to the eMMC storage on the board. However this version of the kernel has a limited number of device tree overlays (mostly different UART options, and one I2C option).

I'm assuming that the 6.10 kernel is quite a new build and that more support for the board's IO should be available soon.

Did I overlook something on the 6.1 version regarding the eMMC support?

Am I missing something regarding overlays in the 6.10 build?

My thinking is to stay with 6.10 as it supports eMMC and it's the newest kernel version.

Cheers

Volt

Orangepi5B start OK, no HDMI debug message before kernel boot

Thu, 30 Jan 2025 21:26:09 +0000

HI,

On one orangepi5B, it seems not possible to have details from u-boot when starting target. The first messages on HDMI start with the kernel

root@hn-orangepi5b-450:~# dmesg |head
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[ 0.000000] Linux version 6.12.0-current-rockchip-rk3588 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #3 SMP PREEMPT Sun Nov 17 22:15:08 UTC 2024
[ 0.000000] KASLR disabled due to lack of seed
[ 0.000000] Machine model: Xunlong Orange Pi 5
[ 0.000000] efi: UEFI not found.
[ 0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000004ffffffff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x4fdf2d380-0x4fdf300ff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000200000-0x00000000ffffffff]
[ 0.000000] DMA32 empty
root@hn-orangepi5b-450:~#

root@hn-orangepi5b-450:~# cat /boot/armbianEnv.txt
verbosity=7
bootlogo=false
console=both
overlay_prefix=rockchip-rk3588
fdtfile=rockchip/rk3588s-orangepi-5.dtb
rootdev=UUID=dae561f4-e2f2-4686-9748-31eebe9792c9
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
root@hn-orangepi5b-450:~#

Is there one option to change this behaviour ?

Best regards

mesa-vpu extension not being compiled with i3wm

Tue, 28 Jan 2025 17:35:56 +0000

Hi, I've been compiling my own Armbian images since 6.13-rc5, and now 6.13 and I noticed that when I compile i3, youtube videos and webgl tests don't work as great when I compile i3 with mesa-vpu as it does when I compile e.g., cinnamon.

I also noticed that the suffix is not -mesa-desktop, only -desktop.

Is it as per design and i3 doesn't include mesa at all, or is it some kind of bug?

Thanks!

Very slow with OMV image, very fast with Ubuntu image

Mon, 27 Jan 2025 01:18:18 +0000

There's a strange issue with my orange pi 5 plus. When I boot into the ubuntu image, everything is fast, stable and zippy. But when I boot into the openmediavault image, it's incredibly slow. Simple operations like apt upgrade crawl. I noticed the cpu frequency is stuck at 408 MHz in htop in the openmediavault image.

I ran a test. I opened another console and ran yes. Went back to htop and the frequency was still stuck at 408 MHz with one core pegged at 100% from the yes. So I fired up the ubuntu image and did the same thing. The core was at 100% but the frequency was at 2304mhz on that core.

There is something wrong with the openmediavault image. What do I need to do to fix this?

Using the Armbian Build Environment

Tue, 14 Jan 2025 14:21:20 +0000

Hello again,

Based on the recommendations provided in a previous ticket, I have decided to attempt to build a custom image for the Orangepi 5 Plus.

I read the docs provided in the link of that post and noticed that there is no mention of installing the cross complier tool chain for arm in ubuntu 22.04, which I just downloaded for this purpose. Do I need to install those tools or will that be addressed once I clone the git repo and run the compile.sh BOARD=orangepi5-plus ?

Also the instructions mention Multipass and Docker, I have a Debian 12 workstation with virt-manager installed, will that work or will I need a dedicated ubuntu 22.04 host, because in that case I can just build on the host and not in a Multipass VM.

thanks

-ali

Installing 24.11 on Orange Pi 5 Plus

Thu, 09 Jan 2025 03:47:31 +0000

Hello Developers,

I ran into some issues installing the latest release on an Orange Pi 5 Plus.

The images I downloaded are as follows:

Armbian_24.11.2_Orangepi5-plus_noble_current_6.12.0_kde-neon-kisak_desktop.img.xz
Armbian_24.11.2_Orangepi5-plus_noble_vendor_6.1.75_gnome-kisak_desktop.img.xz

The KDE version will install and boot from the 256GB emmc drive, however it only works if there is a 4K HDMI monitor attached to HDMI1, I was not able to get it to display on a 1920x1200 HDMI monitor nor a USB connected or HDMI connected portable display (2560x1440).

The Gnome version will boot with any of those 4 types of displays (4K HDMI, 1920x1200 HDMI and USB C or USB C to HDMI portable display) so in the end I would most likely install the GNOME version and then add KDE or Enlightenment packages to it since I don't like GNOME at all (20 yrs Debian/XFCE4 user).

There is one issue I have with the GNOME version: It does not detect the emmc drive and only the SD card and the 500 GB NVME drives are showing up in gparted and fdisk.

I am looking forward to using Armbian on an Orange Pi 5 Plus as my daily desktop and I hope this can be easily resolved. I am open to using either version as long as I can use a portable USB C or HDMI display with less than 4K resolution.

thanks

-ali

OPI 5+ 16GB random fails with NVMe

Wed, 25 Sep 2024 23:21:55 +0000

Anyone else having problems with NVMe disks on the Orange Pi 5 Plus 16gb? I have a WD Black SN750 and use the original power supply, I have tried with Armbian and Ubuntu Rockchip and with both I have random failures at startup not recognizing the drive.

When fail I do this tests:

08:13:33 cristian@orangepi5-plus ~ → lspci
0000:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01)
0000:01:00.0 Non-Volatile memory controller: Sandisk Corp Device 501e
0002:20:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01)
0002:21:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter
0003:30:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01)
0003:31:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01)
0004:41:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
08:19:56 cristian@orangepi5-plus ~ → lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0          7:0    0     4K  1 loop /snap/bare/5
loop1          7:1    0 164.3M  1 loop /snap/chromium/2906
loop2          7:2    0  69.2M  1 loop /snap/core22/1614
loop3          7:3    0  69.2M  1 loop /snap/core22/1624
loop4          7:4    0  61.2M  1 loop /snap/core24/493
loop5          7:5    0  65.9M  1 loop /snap/cups/1059
loop6          7:6    0 483.3M  1 loop /snap/gnome-42-2204/178
loop7          7:7    0   409M  1 loop /snap/gnome-46-2404/41
loop8          7:8    0 402.2M  1 loop /snap/gnome-46-2404/49
loop9          7:9    0  91.7M  1 loop /snap/gtk-common-themes/1535
loop10         7:10   0  87.3M  1 loop /snap/mesa-2404/142
loop11         7:11   0  33.7M  1 loop /snap/snapd/21761
mtdblock0     31:0    0    16M  0 disk 
mmcblk0      179:0    0   233G  0 disk 
└─mmcblk0p1  179:1    0 230.6G  0 part /var/log.hdd
                                       /
mmcblk0boot0 179:32   0     4M  1 disk 
mmcblk0boot1 179:64   0     4M  1 disk

08:20:07 cristian@orangepi5-plus ~ → dmesg | grep nvme
[   16.331812] nvme nvme0: pci function 0000:01:00.0
[   16.331841] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[   16.765381] nvme nvme0: Removing after probe failure status: -19

Armbian Kernel Features

Wed, 08 Jan 2025 01:30:50 +0000

I somewhat recently used Armbian Build to compile a desktop Bookworm image, which is quite stable and functional except for EMMC support.

Packages: Debian stable (bookworm)
Support: DIY (custom image)
Linux Atlas 6.1.84-vendor-rk35xx #1 SMP Tue Dec 24 13:36:04 UTC 2024 aarch64 GNU/Linux

My question is where can one find the current status of the various kernel versions support for features like I2C, SPI, EMMC, MESA, etc.? I recognize that newer kernels like 6.12.yyy are very much a WIP.

I also would love more information on the the RK3588 kit used with kernels to backport features.

Raspberry TV Hat on OPI5+

Tue, 07 Jan 2025 09:10:17 +0000

Hi.

I have the official raspberry TV hat

https://www.raspberrypi.com/documentation/accessories/tv-hat.html

I'm wondering if I can use it on the Orange Pi.

https://pinout.xyz/pinout/tv_hat

http://www.orangepi.org/orangepiwiki/images/a/ac/Plus5-img302.png

No WiFi on latest image

Wed, 29 May 2024 21:00:34 +0000

I installed latest Armbian_24.5.1_Orangepi5-plus_bookworm_vendor_6.1.43_minimal.img and I can't get wifi to work. The adapter is RTL8852BE. I installed armbian-firmware-full and the adapter is shown in lspci, but there is no wireless interface. armbian-config does not list wifi as an option. armbianmonitor -u

I2C2

Fri, 27 Dec 2024 23:09:16 +0000

I'm using an Orange Pi 5 Plus 16GB SBC, with Armbian image (https://dl.armbian.com/orangepi5-plus/Bookworm_current_cinnamon-backported-mesa) which uses Kernel 6.12. I am trying to get a BME280 I2C sensor attached to the following pins of the 40 pins; 1 (3.3v), 3 (GPIO0C0), 5 (GPIO0B7), and 6 (GND). The BME280 sensor has the VIN wired to 3.3v (pin 1), SDA wired to SDA (pin 3), SCL wired to SCL (pin 5), and GND to GND (pin 6). The device should use address 0x76, but isn't listed under the four I2C buses found in /dev.

This configuration worked fine when using the stock OrangePi 5 Plus Debian Bookworm image, but does not have I2C2 listed as a device under /dev under Armbian image listed above.

My armbianEnv.txt is:

verbosity=1
bootlogo=true
console=both
overlay_prefix=rockchip-rk3588
fdtfile=rockchip/rk3588-orangepi-5-plus.dtb
rootdev=UUID=3cbd3c35-190b-4cc5-8db3-4334fa84ccbd
rootfstype=ext4
overlays=rockchip-rk3588-i2c8-m2
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

I have attached 4 images (screenshots) with the following captions
i2c.png - List of I2C buses and addresses (Armbian Image)

i2c_2.png - List of DTBs (Armbian Image)
i2c_3.png - List of DTBOs aka overlays (Armbian Image)

i2c_opi2.png - List of I2C buses and addresses of I2C2 (Orange Pi Debian 12 Image)

Why isn't I2C2 found in /dev of Armbian image?

New orangepi-5plus_UEFI_Release_v0.12.img

Sat, 28 Dec 2024 14:04:41 +0000

This is a new release of the uefi firmware for Orange Pi 5 Plus which now has mainline kernel support. My thought was that this new release would support armbian uefi builds but so far no love. Does anyone know of an armbian build that would work with this???

The is the one of the tag lines from readme.md found @ https://github.com/edk2-porting/edk2-rk3588

"It delivers a PC-like standardized boot experience, supporting multiple operating systems, such as Windows, Linux, BSD and VMware ESXi."

Desktop images with Armbian Linux v6.12 (Variant Cinnamon)

Sun, 22 Dec 2024 02:02:54 +0000

Desktop images with Armbian Linux v6.12 variant Cinnamon with mesa/vpu support fails to boot from SD card.

The message displayed on screen is "Begin: Running /scripts/init-premount ... (initramfs) _"

SPI was erased, and the minimal install have no issues booting from a sd card.

The SBC is an Orange Pi 5 Plus with 16gb ram

Want to build and compile kernel but what's next?

Tue, 17 Dec 2024 06:26:25 +0000

Not an issue nor a bug nor a trouble abour my Orange pi or Armbian.

I wanted to build my "own" armbian for educational purpose. I mean to raise my knowledge.

I followed this page. https://docs.armbian.com/Developer-Guide_Build-Switches/

however since it's done. I'm looking for about how to make the *.img file or if I can use *.deb located in my ~/build/output/debs

I just miss these informations to finish and trying my failure compilation. I say failure compilation because "first time" is always a fail

By the way, if I posted in the wrong place. Delete my post and please accept my apologies.

NVMe Speed Slow

Fri, 13 Dec 2024 18:06:09 +0000

I have built an Orange Pi 5 Plus systems. I have a 256gb eMMC card which seems to run as speed would expect. Yet when I test the NVMe drive I get slow speeds compared to what is suggested to get. I have seen other people posts that suggest they are getting at least 4gb/s using NVME drives. I have searched for other issues but there is no errors in the logs just can't get the speeds I was expecting.

I have the following which suggests at least 5gb/s

KINGSTON SNV3S500G

I have formatted it using Ext4.

root@orangepi5-plus:/boot# hdparm -Tt /dev/nvme0n1

/dev/nvme0n1:
 Timing cached reads:   2804 MB in  2.00 seconds = 1404.10 MB/sec
 Timing buffered disk reads: 1394 MB in  3.00 seconds = 464.64 MB/sec

32:9 SuperWide Curved Monitor with wrong resolution

Fri, 22 Nov 2024 10:28:01 +0000

I connected a 49" super wide curved monitor (philips 49b2u5900) to opi5+ through HDMI. I would expect to have the possibility to choose between resolutions of 5120x1440 or 3840x1080. Unfortunately I only get 16:9 resolutions.

 v24.8.4 for Orange Pi 5 Plus running Armbian Linux 6.1.75-vendor-rk35xx

 Packages:     Ubuntu stable (noble)

david@orangepi5-plus:~$ xrandr
Screen 0: minimum 16 x 16, current 3840 x 2160, maximum 32767 x 32767
HDMI-1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 1190mm x 340mm
   3840x2160     59.98*+
   2048x1536     59.95
   1920x1440     59.97

How can I configure the proper resolution? I as have little experience with this kind of problems and other similar issues were years ago reported I thought to open a new topic. Thanks for any reply.

Armbian install on Orange Pi 5 Plus - black screen

Tue, 10 Dec 2024 11:56:03 +0000

I followed the provided instructions to install Arbmbian on Orange Pi 5 Plus 16GB, so I downloaded the official Ubuntu image from the Orange Pi website, and when it booted, it

sudo apt update
sudo apt install mtd-utils
sudo flash_eraseall /dev/mtd0

The flash operation was finished successfully. Then I turned off, loaded Armbian Ubuntu 24.04 (Noble) (Desktop images with Armbian Linux v6.12) on SD and started the machine. I have a monitor connected to the machine, but there is no output. My router doesn't show any new network device, so I suppose that Armbian doesn't load. It's exactly the same situation when I tried to install Armbian without /dev/mtd0 erasing.

How to proceed and install Armbian?

Update:

Armbian has been installed successfully. After cleaning bootloader as descried above, I tried to install Joshua Riek's distribution and it loaded. Then I returned back to Armbian downloads and tried Armbian 24.11.2 Noble Gnome with kernel 6.1.75 (the one highlighted) and it worked! And I migrated everything to eMMC by using armbian-config - that was easy.

So to summarize - I'm not sure that /dev/mtd0 cleanup was really required, but I did it. The problem was with the distribution I tried to run. Armbian Ubuntu 24.04 (Noble) (Desktop images with Armbian Linux v6.12) was the wrong choice.

Automatic boot of Orange Pi 5 Plus on Power On

Mon, 09 Dec 2024 17:27:34 +0000

I have Orange Pi 5 Plus that I plan to install in a remote location. To boot Orange Pi, I need to press the physical Power On button. How I can setup the machine to boot automatically once the power is supplied? There is nobody on the remote side to press this button. Or maybe there are other options to boot remotely like WakeOnLAN?

Where it can be configured? In orangepi-config?

HDMI2 - Second HDMI screen not working

Sat, 26 Oct 2024 13:31:10 +0000

I have set up Armbian 24.8.4 bookworm on my 32GB Orange Pi 5 Plus. Most everything works as expected out of the box. The second HDMI port doesn't detect the second screen, and the screen displays No Signal.

I have tested the cables and monitors to ensure they are functioning. I have also ensured I wasn't plugged into the HDMI input by accident.

I was about ready to proclaim it a hardware issue, but on booting the "Official" Orange PiOS Arch image, the dual monitor support worked as expected. I checked the dtb file included with the Arch image, and it has many references to HDMI0 and HDMI1 devices, while the one used by default with the Armbian image only references HDMI0. I'm unsure if that's related, as I'm not entirely sure how those device tree mechanisms work. On a ham-fisted hunch, I tried just copying the dtb file from the Arch install to /boot/dtb/rockchip/ and pointing armbianEnv.txt at that, which resulted in a no-boot condition.

Curious if there's any tips or tricks to getting the second monitor output to work with this device under Armbian.

Attached are copies of the disassembled dtb files, in case they have any relevance.

rk3588-orangepi-5-plus-arch.dts rk3588-orangepi-5-plus-armbian.dts

No network connection after update

Sat, 19 Oct 2024 08:34:56 +0000

Hi, last night a set of updates was installed and I rebooted the Orange Pi 5+ this morning. After the reboot I've seem to have lost the connection to the Orange Pi 5+, it is normally connected without a screen so I access it through SSH and the Open Media Vault web GUI.

I've tried to connect it to a screen and then it seems to boot up just fine. Looking around with the screen connected it seems like the network cards aren't detected. My Linux skills are very limited but "sudo lshw -class network" shows nothing.

One detail is that my router seems to detect it when it's connected and gives it the normal IP address that I've set in the 192.168.0.x range. But when I list network devices logged in to Linux all interfaces seems to have private addresses starting with 172. See the attached image for the output from "ip addr show".

I’m running Armbian Debian Bookworm.

These were the updates that were installed:

armbian-config 24.8.4
armbian-firmware 24.8.4
armbian-zsh 24.8.4
linux-dtb-vendor-rk35xx 24.8.4
linux-image-vendor-rk35xx 24.8.4

Static IP address Orange Pi

Fri, 18 Oct 2024 12:03:04 +0000

Folks,

I've got an Orange pi 5 plus up and running using Armbian, I've used the minimal install and although it's been plain sailing for the main part, no matter what I do I can't work out how to give it a static IP address (dynamic works fine). I've spent an hour trying:

armbian-config, - Network | IP | Static and setting it to what I want - it ignores it and when I go back in it's gone back to 127.0.0.1

This page: https://docs.armbian.com/User-Guide_Networking/

Creates the yaml file with my interface abd required address as here:

 GNU nano 7.2                                                /etc/netplan/20-static-ip.yaml                                                           
network:
 version: 2
 renderer: networkd
 ethernets:
   enP4p65s0: # Change this to your ethernet interface
     addresses:
     - 192.168.5.2/24
     routes:
     - to: default
       via: 192.168.5.1
     nameservers:
      addresses:
        - 9.9.9.9
        - 1.1.1.1

Following this to get rid of the issues with netplan test

Looked high and wide for other tips but can't see anything that would help me. I'm used to Red Hat distros where you just go in and edit an existing config file, but that doesn't seem to be the case with Debian variants?

Anyone able to help me please? Been using Linux for twenty-five years so am no noob, never had a problem like this before setting a fixed IP address!

Thanks

Max resolution limited by 1080p

Sun, 01 Sep 2024 14:51:53 +0000

Hi all ,

Just installed last supported version:

Armbian 24.8.1 Noble Gnome, MESA / VPU, Kernel: 6.1.75, Size: 1.5 GB, Release date: Aug 26, 2024

I have 2 dell monitors : u2515h ultrasharp 1440p, and more modern P3424WE with 3440x1440 max resolution. With both - armbian max resolution in display settings is always 1920x1080.

My previous experience here was with radxa zero D1 and 1440p was working here smoothly out of box on different armbian images.

I also tried Ubuntu 22.04 (Jammy)KDE NeonMESA / VPU https://dl.armbian.com/orangepi5-plus/Jammy_current_kde-neon-kisak with same results: no resolution higher then 1080p

Rdp session to that installations normally propose 2560 and 3440x1440 resolutions available and usable. So I suppose it is some config but not driver/hardware issue.

Rdp installed via:

sudo apt install xrdp xorgxrd

sudo systemctl enable xrdp

The WEB is exploding with tons of guides with dozens of approaches, of course first tried not working...

Can somebody save me from that many hours try and fail circus and guide me on short way to troubleshoot resolution on that new armbian images?

HDMI in OK, what about HDMI-audio-input?

Mon, 14 Oct 2024 16:35:39 +0000

Hi everyone,

I just received an "orange pi 5 plus" and I wanted to use the hdmi-input feature in it.

I installed armbian and added the hdmirx overlay, and now I can use ffmpeg or gstreamer to stream video input. Good.

Alas, I see no alsa hdmi input card. I tried to search for some settings but didn't find any...

The only information I found on this feature are here https://github.com/armbian/linux-rockchip/blob/rk-6.1-rkr3/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts

do you have any pointer to give me on how to enable this feature?

(I know how to compile stuff, using Linux since 1998 )

thanks for any help / pointer you can give me ❤️

BS.

24.11.0-trunk armbian-install failure induced by old partition devices

Fri, 04 Oct 2024 20:38:27 +0000

Hi,

A UEFI-ARM64 install of armbian opi5+ 24.11.0-trunk fails during armbian-install due to incorrect knowledge of partitions:

root@uefi-arm64:/usr/sbin# lsblk -l
NAME      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda         8:0    1  14.4G  0 disk 
sda1        8:1    1   256M  0 part /boot/efi
sda2        8:2    1  14.2G  0 part /var/log.hdd
                                    /
zram0     252:0    0   7.7G  0 disk [SWAP]
zram1     252:1    0    50M  0 disk /var/log
zram2     252:2    0     0B  0 disk 
nvme0n1   259:0    0 953.9G  0 disk 
nvme0n1p2 259:3    0 953.6G  0 part /mnt/armbian-install.NQULbp/rootfs
                                    /mnt/tmp

root@uefi-arm64:/usr/sbin# udevadm settle
root@uefi-arm64:/usr/sbin# lsblk -l
NAME      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda         8:0    1  14.4G  0 disk 
sda1        8:1    1   256M  0 part /boot/efi
sda2        8:2    1  14.2G  0 part /var/log.hdd
                                    /
zram0     252:0    0   7.7G  0 disk [SWAP]
zram1     252:1    0    50M  0 disk /var/log
zram2     252:2    0     0B  0 disk 
nvme0n1   259:0    0 953.9G  0 disk 
nvme0n1p2 259:3    0 953.6G  0 part /mnt/armbian-install.NQULbp/rootfs
                                    /mnt/tmp

root@uefi-arm64:/usr/sbin# ls -l /dev/nvme0n1*
brw-rw---- 1 root disk 259, 0 Oct  5 06:18 /dev/nvme0n1
brw-rw---- 1 root disk 259, 3 Oct  5 06:18 /dev/nvme0n1p2
root@uefi-arm64:/usr/sbin# fdisk /dev/nvme0n1

Welcome to fdisk (util-linux 2.39.3).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

This disk is currently in use - repartitioning is probably a bad idea.
It's recommended to umount all file systems, and swapoff all swap
partitions on this disk.


Command (m for help): p

Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: Fanxiang S501Q 1TB                      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D98AAC78-13E2-42D7-948D-3BD864476713

Device          Start        End    Sectors   Size Type
/dev/nvme0n1p1   2048     526335     524288   256M EFI System
/dev/nvme0n1p2 526336 2000408575 1999882240 953.6G Linux filesystem

Command (m for help): q

although I can hack the install, just curious if there is a cleaner solution other than reboot...

HDMI Schedule

Wed, 09 Oct 2024 08:01:33 +0000

I have a couple Orange Pi's, and the HDMI is broken. I noticed that many believe that it is Armbian, but it is not. Orange Pi's probably won't be where we want them until 2025. I found a couple notes from development teams, one below and one from September. Both say the same thing: essentially it's in the works:

"The RK3588 SoC family integrates the newer Synopsys DesignWare HDMI 2.1 Quad-Pixel (QP) TX controller IP and a HDMI/eDP TX Combo PHY based on a Samsung IP block.

Add just the basic support for now, i.e. RGB output up to 4K@60Hz, without audio, CEC or any of the HDMI 2.1 specific features."

https://patchwork.kernel.org/project/linux-rockchip/patch/20240801-b4-rk3588-bridge-upstream-v2-3-9fa657a4e15b@collabora.com/

Dual boot on orange pi 5 plus

Sat, 09 Sep 2023 14:24:13 +0000

Hello, I would like to have dual boot with a startup menu similar to GRUB on a PC, the idea is to have Android installed on the eMMC and Ubuntu on the NVMe, I am referring to an Orange Pi 5 Plus. Has anyone gotten it or is working on it?
Thank you

Install RTL8821CE on Orange Pi 5 Plus

Fri, 22 Mar 2024 08:39:13 +0000

Hello,

I tried to install the RTL8821CE card on Orange Pi 5 Plus, but only the Bluetooth is on, the wifi not working. Which driver i should use?

I am using Armbian 24.2.1 Jammy with Linux 5.10.160-legacy-rk35xx

here is the dmesg of

admin@orangepi5-plus:~$ nmtui
admin@orangepi5-plus:~$ dmesg | grep 8821
[    5.588211] pci_bus 0003:30: root bus resource [mem 0x9c0000000-0x9ffffffff pref]
[    8.482106] rtw_8821ce 0002:21:00.0: enabling device (0000 -> 0003)
[    8.493940] rtw_8821ce 0002:21:00.0: Firmware version 24.11.0, H2C version 12
[    8.534600] rtw_8821ce 0002:21:00.0: rfe 6 isn't supported
[    8.534719] rtw_8821ce 0002:21:00.0: failed to setup chip efuse info
[    8.534723] rtw_8821ce 0002:21:00.0: failed to setup chip information
[   83.795823] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
[   83.796843] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
[   83.799263] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
admin@orangepi5-plus:~$ lspci
0002:20:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01)
0002:21:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter
0003:30:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01)
0003:31:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01)
0004:41:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
admin@orangepi5-plus:~$ dmesg | grep iwlwifi
admin@orangepi5-plus:~$ dmesg | grep wifi
[    4.419741] wifi_disable: no parameters, enabled
[    4.419802] reg-fixed-voltage wifi-diable-gpio-regulator: wifi_disable supplying 0uV
[    6.159542] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6275p
[    6.159548] [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control.
[    6.159554] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio.
[    6.159620] [WLAN_RFKILL]: wlan_platdata_parse_dt: The ref_wifi_clk not found !
[    6.159633] [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 1
admin@orangepi5-plus:~$

Hardware acceleration by using Docker

Mon, 09 Sep 2024 10:45:11 +0000

I'd like to add hardware acceleration for my Orange PI 5 Plus, i've installed ` apt install -y clinfo` on the host (armbian)


docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -v debug -init_hw_device rkmpp=rk -init_hw_device opencl=ocl@rk
ffmpeg version 6.0.1-Jellyfin Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 12 (Debian 12.2.0-14)
  configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-ptx-compression --disable-static --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto --enable-gpl --enable-version3 --enable-shared --enable-gmp --enable-gnutls --enable-chromaprint --enable-opencl --enable-libdrm --enable-libxml2 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libsvtav1 --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=arm64 --cross-prefix=/usr/bin/aarch64-linux-gnu- --toolchain=hardened --enable-cross-compile --enable-rkmpp --enable-rkrga
  libavutil      58.  2.100 / 58.  2.100
  libavcodec     60.  3.100 / 60.  3.100
  libavformat    60.  3.100 / 60.  3.100
  libavdevice    60.  1.100 / 60.  1.100
  libavfilter     9.  3.100 /  9.  3.100
  libswscale      7.  1.100 /  7.  1.100
  libswresample   4. 10.100 /  4. 10.100
  libpostproc    57.  1.100 / 57.  1.100
Splitting the commandline.
Reading option '-v' ... matched as option 'v' (set logging level) with argument 'debug'.
Reading option '-init_hw_device' ... matched as option 'init_hw_device' (initialise hardware device) with argument 'rkmpp=rk'.
Reading option '-init_hw_device' ... matched as option 'init_hw_device' (initialise hardware device) with argument 'opencl=ocl@rk'.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option v (set logging level) with argument debug.
Applying option init_hw_device (initialise hardware device) with argument rkmpp=rk.
Applying option init_hw_device (initialise hardware device) with argument opencl=ocl@rk.
arm_release_ver: g13p0-01eac0, rk_so_ver: 10
Failed creating base context during opening of kernel driver.
Kernel module may not have been loaded
[AVHWDeviceContext @ 0xaaaadce49f00] 1 OpenCL platforms found.
[AVHWDeviceContext @ 0xaaaadce49f00] 1 OpenCL devices found on platform "ARM Platform".
arm_release_ver: g13p0-01eac0, rk_so_ver: 10
Failed creating base context during opening of kernel driver.
Kernel module may not have been loaded
[AVHWDeviceContext @ 0xaaaadce49f00] 0.0: ARM Platform / Unknown Device

exit code is 139 and device is unknown

Is there any package to install ?

OrangePi 5 Plus with kernel 6.10.x not booting?

Sun, 28 Jul 2024 22:53:35 +0000

Hello! First time poster, long time admirer.

I've been unable to get ANY of the 6.10.x images to boot off SD card (Sandisk Extreme) for the Orange Pi 5 Plus.

Specific images which are not working for me:

Has anybody else had better luck?

eMMC orange pi 5 plus black screen

Mon, 26 Aug 2024 16:02:52 +0000

I'm trying to install https://dl.armbian.com/orangepi5-plus/Bookworm_vendor_minimal in my Orange PI 5 Plus to the emmc but I've got a black screen after removing sd card.

Orange Pi 5 Plus - Dual boot - is possible ?

Tue, 29 Aug 2023 12:58:08 +0000

Hello,

Long time Gentoo and Raspberry Pi user, but I am interested in a more powerful Arm device.

Will buy an Orange Pi 5 plus device if it meets my requirements.

I am interested about dual or multiple boot: let's say Linux and Android or, at least multiple Linux distro - let's say Armbian and Gentoo. It is possible ?

On Raspberry Pi 4 with a larger boot partition I switch content of /boot from boot/debian /boot/gentoo, have multiple partition on SATA SSD connected via USB edit root parameter in /boot/cmdline.txt and that way I choose which distro to boot.

On Orange PI 5 (Plus) I read that SPI chip have to be flashed to choose the boot device from SDCard (default) or NVME disk - I am not sure about eMMC memory, but it is ok to use SD card as boot partition and change root to Gentoo/Armbian/Android partition.

No problem using command line, dd, tar partitioning.

So questions:

1. Is dual boot possible now on Orange Pi 5 Plus ?

2. If yes, is possible to switch between Linux and Android ?

3. Or just between multiple Linux installations ?

I am convinced that Raspberry Pi support is better, I put this question here, because on Orange Pi forum I am not yet able to make a new post.

What to expect from Raxda/Orange ?

I am referring to hardware drivers support like mesa, kernel etc, not questions, community, or simply technical support.

On panfork I see a new package created on 2023-08-16 - https://launchpad.net/~liujianfeng1994/+archive/ubuntu/panfork-mesa , but no commit on git in the last 8 months. Nothing about mesa 23.1, it stay to mesa 20.0 from the beginning.

On the other hand Rock Pi 4 also started from kernel 5.10, but now has support for kernel 6.1 - latest stable one, on Armbian.

Thank you for your support!

Waydroid for rk3588 with armbian edge (Panthor, kernel 6.8)

Sat, 27 Apr 2024 14:14:44 +0000

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

NICs underperforming, ~700Mbps instead of ~1Gbps

Mon, 12 Aug 2024 10:02:27 +0000

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.

OPI5Plus - 32GB version issue

Wed, 13 Mar 2024 23:15:19 +0000

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.. ? ?