ricardo_brz

Based on the related forum post by @Robert-MX, I was able to resolve the "file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/s>" spamming the journalctl logs after a reboot due to the logs not being cleared properly.
 
The root issue appears to be that /usr/lib/armbian/armbian-truncate-logs has an issue when ran with as #!/bin/sh after a reboot. To get around that it manually with bash instead.
To fix it temporarily until the next reboot then just run 
sudo bash /usr/lib/armbian/armbian-truncate-logs check 'journalctl -f' to see if the rsyslog issues disappear, if so then you'll want to add it to your crontab for every boot
 
To fix it permanently then add the command to your crontab so it runs every time you boot:
switch to root
su - edit your crontab
crontab -e add the line at the bottom so that the log truncate happens after each boot
@reboot bash /usr/lib/armbian/armbian-truncate-logs reboot and check journalctl -f to see if you are still seeing the rsyslog issues
 
 

I Did It! I Got It Working!!
 
ES8388 Analog Audio Output
 
Here's How (this is very easy to do):
It just involves making one simple modification to the devicetree.
 
Note: I did this with the Edge kernel. My guess is that it will also work with the Current kernel. You can also try the Vendor kernel if its devicetree has the same code.
Update: I've addressed the Current and Vendor kernels in this comment below:
https://forum.armbian.com/topic/52118-hdmi-audio-and-analog-audio-do-not-work-on-opi5plus/#findComment-225009
 
 
I manually applied this patch:
https://patchwork.kernel.org/project/linux-rockchip/patch/20250823-orangepi5-v1-1-ae77dd0e06d7@hotmail.com/
 
If you scroll to the bottom where it gives the patch, the GPIO_ACTIVE_LOW needs to be changed to GPIO_ACTIVE_HIGH in the given section of the devicetree.
 
Here's the simple / quick way to fix it, without having to go through any lengthy (re)builds.
Modify the already installed devicetree file (/boot/dtb/rockchip/rk3588-orangepi-5-plus.dtb).
 
1. Install the package: device-tree-compiler
2. Backup the original, and convert to .dts format as follows:
 
# Go to your devicetree directory cd /boot/dtb/rockchip/ # Make a backup of your original devicetree: sudo cp rk3588-orangepi-5-plus.dtb rk3588-orangepi-5-plus.dtb.bak # Use device-tree-compiler to convert the file from the binary .dtb format to source (text) .dts format (ignore the warnings) sudo dtc -I dtb -O dts -o rk3588-orangepi-5-plus.dts rk3588-orangepi-5-plus.dtb # Safety-Check Part 1: Convert right back to .dtb format (another filename), ignore the warnings. sudo dtc -O dtb -I dts -o rk3588-orangepi-5-plus-test.dtb rk3588-orangepi-5-plus.dts # Safety-Check Part 2: Compare the newly converted file with the original. They should be identical (this command should produce no output) cmp -l rk3588-orangepi-5-plus-test.dtb rk3588-orangepi-5-plus.dtb  
3. Using a text editor in sudo mode, edit the source (text) file:
rk3588-orangepi-5-plus.dts
 
Search for this phrase: simple-audio-card,hp-det-gpios
I should appear exactly once in the file.
 
# Here is what that line looks like (for me): simple-audio-card,hp-det-gpios = <0x133 0x1b 0x01>; # This is that same line before original compilation simple-audio-card,hp-det-gpios = <&gpio1 RK_PD3 GPIO_ACTIVE_LOW>;  
4. Notice between the brackets, there are 3  values, separated by spaces. The third value is the value to modify from GPIO_ACTIVE_LOW to GPIO_ACTIVE_HIGH, or for us, from 0x01 to 0x00.
 
5. Convert your modified .dts file to a .dtb file (ignore the warnings):
sudo dtc -O dtb -I dts -o rk3588-orangepi-5-plus-fixed.dtb rk3588-orangepi-5-plus.dts # Optional: Quick Comparison Check (this should output exactly 1 line with 3 numbers: [big number] 0 1) cmp -l rk3588-orangepi-5-plus-fixed.dtb rk3588-orangepi-5-plus.dtb  
6. Copy the new fixed file to (overwriting) your original:
sudo cp rk3588-orangepi-5-plus-fixed.dtb rk3588-orangepi-5-plus.dtb  
7. Reboot (and have ES8388 analog audio out).
 
Note: Whenever you do a kernel change or update, you will need to repeat this process until the Armbian kernel updates catch up with this patch.
 
 
Here's the lengthier explanation (this is repeatable if you want to check it out yourself)
1. I downloaded the source code for version 25.8.1:
https://github.com/armbian/build/releases/tag/v25.8.1
 
2. I extracted the archive and started the building process (./compile.sh) with the edge kernel (and a desktop image).
It would not build because it rejected two of the kernel patches, but it did download everything into the cache.
 
3. I then found the file described in the patch:
./build-25.8.1/cache/sources/linux-kernel-worktree/6.16__rockchip64__arm64/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts
 
4. In that file, I searched for the line indicated in the patch, just prior to the line to modify:
simple-audio-card,aux-devs = <&speaker_amp>, <&headphone_amp>;  
...and found the appropriate section. I confirmed the line that followed matched the original (incorrect) version mentioned in the patch entry.
 
5. I then scrolled to the top of the .dts file and looked at the files #included, to find where the GPIO_ACTIVE_LOW macro was defined. I figured dt-bindings/gpio/gpio.h was a reasonable place to look first. I found it here:
./build-25.8.1/cache/sources/linux-kernel-worktree/6.16__rockchip64__arm64/include/dt-bindings/gpio/gpio.h
 
Near the top of the file were these #defines:
/* Bit 0 express polarity */ #define GPIO_ACTIVE_HIGH 0 #define GPIO_ACTIVE_LOW 1  
6.  See the simple fix above for the rest.
 
Tags:
@Werner, @Igor, @laibsch
@dimaxus, @EricaLina, @ricardo_brz, @eselarm

This fixed the issue with Chromium. I simply created a file /etc/armbian/cromium.conf with the contents you provided and chromium opened perfectly.

Just thought I'd add that this appears to be fixed in the latest "stable" release with edge kernel (6.8.10). Connecting to WiFi networks works out of the box, and creating a hotspot works if you install armbian-firmware-full.

how exactly are you writing to the SD card? I just did it today with Gnome Image Writer and it worked without any issue. The image I used was https://mirror-us-stl1.armbian.airframes.io/dl/orangepi5-plus/archive/Armbian_24.5.1_Orangepi5-plus_noble_vendor_6.1.43_gnome-oibaf_desktop.img.xz
 
There is no need to unpack. Right click -> open with Image Writer -> select destination (SD card) -> wait until the process finishes -> boot with SD card -> setup Armbian -> start using.

I'd like to congratulate you for a great release (24.2.1) with KDE! I was looking for a guide to install KDE in a minimum version, but I could not trim it down enough, and this release solved my issues.
 
Everything is working smoothly, video acceleration is there, Wi-Fi (AX210) is there, bluetooth is there! A real pleasure to use.
 
Best, team!

I had one OPi5 setup and working properly with one of my TVs.  I was running Kodi and using the remote from my TV to control Kodi using HDMI-CEC.  I went to setup a second one on another TV but this time the TV remote did not work properly.  Through elimination I came to determine the HDMI cable was the issue.  I ordered another HDMI cable that had the Ferrite at each side of the cable.  Now it worked properly.  Thought this might be useful for others.  This is the cable I ordered:  https://www.amazon.ca/dp/B003PDHJ6M
 
Conclusion:  In order to make HDMI-CEC work properly, make sure the HDMI cable is of sufficient quality.  I think ones with the Ferrite may be best to remove any electrical interference.

Needed/wanted to add Bluetooth to my OPi5 and also needed WiFi at the same time.  Did not want to use 2 USB ports so I tried the T2UB.  Working well.  Bluetooth appeared on my Armbian Ubuntu Jammy setup and I plugged in the dongle.  It saw a few of my bluetooth devices.  Reason I wanted bluetooth is to use a controller for some games/emulators.  I'll make another post for that.  My PS4 Dualshock controller is not showing up in the list of devices.  My version is an older version, Armbian 23.06.420 Jammy with Linux 5.10.160-rk35xx  No end-user support: built from trunk
 
Conclusion:  TPLink T2UB should work properly on Armbian Ubuntu desktop.

I am using a Rock5a with an RK3588s, and it won't even work on the Edge version. I think the adapter is bound with Intel chipsets, AMD users also complained about this on Windows 

Key is not deprecated, method is. On Noble / Sid and future.
 
sudo wget https://apt.armbian.com/armbian.key -O key sudo gpg --dearmor < key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null sudo chmod go+r /usr/share/keyrings/armbian.gpg sudo echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com $(lsb_release -cs) main $(lsb_release -cs)-utils $(lsb_release -cs)-desktop" | sudo tee /etc/apt/sources.list.d/armbian.list apt update  

Some inspiration: https://github.com/awesome-selfhosted/awesome-selfhosted

did you also check the power supply?
 
Another thing I noticed was that among your trial you used:
 
Maybe you have installed this at some point and it kinda breaks the process and you need to reinstall the "plus" one again to fix it?

I use 154! I understand it will use C.UTF-8 as locale. That's what I've been using forever, and it just works... 

Recover OrangePi 5 Plus
Download:
https://drive.google.com/drive/folders/19SMZHj1Y8l_Vvr6_SMDHYdJHi41hMgsI
Press and hold the MASKROM button, then plug in USB power and release the MASKROM button
Open a terminal in Linux and install "rkdeveloptool"
*Note, I saved all the files in that URL to /home/$USER/opi5plus then "cd opi5plus" | use "sudo rkdeveloptool ld" to see if your device can be seen (plug in USB cable from PC to the USB-C connector opposite the power).
opi5plus$ sudo rkdeveloptool db MiniLoaderAll.bin
Downloading bootloader succeeded.
opi5plus$ sudo rkdeveloptool ul MiniLoaderAll.bin
Upgrading loader succeeded.
opi5plus$ sudo rkdeveloptool td
Test Device OK.
opi5plus$ sudo rkdeveloptool rd
Reset Device OK.
Make sure you have a freshly baked SD card installed with your Linux flavor of choice then power off, install the SD card and boot up!