Search the Community

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

Hi all, so I was trying to map a windows network drive to armbian but something is missing or am i doing something wrong here: I tried smb://10.10.2.101 sftp://10.10.2.101 both are highlighted in red It works fine on Rocky Linux thou.. any ideas ?

Rk3588 boards now share the same linuxfamily as rk3568 and rk3566 boards. It means rockchip-rk3588 kernel won't get update longer. Here is some steps for migration: sudo sed -i 's/LINUXFAMILY=rockchip-rk3588/LINUXFAMILY=rk35xx/g' /etc/armbian-release sudo apt update sudo apt install linux-image-legacy-rk35xx linux-dtb-legacy-rk35xx linux-headers-legacy-rk35xx sudo apt remove linux-image-legacy-rockchip-rk3588 linux-dtb-legacy-rockchip-rk3588 linux-headers-legacy-rockchip-rk3588 NOTE: The steps are currently for beta branch only. Don't try on stable branch.

I have some problem starting Linux image with my OPi 5+. I just got an OPi 5+ 16Gb RAM no eMMC. I flashed official Android image into SD card with SDDiskTool following the instruction in wiki. It worked. Then I do the "Data Reset" in Android Settings. The board doesn't boot anymore. I re-flashed Android into the SD, and it worked again. Then, I want to try Linux. I flashed Joshua Riek ubuntu-22.04.3-preinstalled-desktop-arm64-orangepi-5-plus.img.xz into the same SD with balenaEtcher. It doesn't boot. I tried again with Armbian_24.2.1_Orangepi5_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz and official Ubuntu image as well. None of them managed to boot up. The led just swap between red and blue (or red and green in Armbian case). After about 5 minutes or so, I think I got stuck in a loop because my screen just go from off to black to off to black continuously. I flashed Android again on the SD card, and it magically worked again. I am not very good with hardware, but from what I read around, I think it could be the SPI memory. I find it a bit hard to believe because it is the new board and I did not tamper with it at all. The only thing I touched is the SD card. I am out of options now. I am thinking of clearing / flashing the SPI memory, but I also read a lot of stories about people bricking their OPi after touching that region. I don't want to do something that I might regret later. Does anyone have an idea what could have caused this and should I just try to erase the SPI? I used stock 5V 4A power, and also tried a different HDMI port. Still the same thing.

Hello. The official adapter does not work for my orange pi 5 plus. https://aliexpress.ru/item/1005005956334270.html?spm=a2g2w.orderdetail.0.0.4e224aa6r3APff&sku_id=12000035019805399 The problem is this. Wi-Fi works, you turn on bluetooth, bluetooth doesn’t work initially. After turning on bluetooth, Wi-Fi does not work and bluetooth does not work either. Realtek RTL8852BE-CG BE CPU work in all officials builds. Help me please

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

Orange Pi 5 plus. It seems that in the 'edge' kernels, ssh is disabled by default. Since HDMI doesn't function this is a problem. I used the debugging UART and after setup I got the message "ssh.service is disabled" I enabled the service and all is well. Any reason why ssh would be disabled?

Are there any plans to make a version with the new Rockchip 6.1 kernel available for Orange Pi 5/5+? Joshua Riek seems to have had some success, he even got the Panfork drivers running. I run a headless server though so even without graphics it would be interesting but I use Debian.

I purchased the wifi + bt module. It is RTL8852BE. my armbian: Linux orangepi5-plus 5.10.160-legacy-rk35xx #1 SMP Fri Feb 2 07:51:33 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux My Bluetooth never works. It cannot be listed under hciconfig: vnc@orangepi5-plus:~$ hciconfig -a vnc@orangepi5-plus:~$ rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth bt_default blocked unblocked 1 wlan phy0 unblocked unblocked vnc@orangepi5-plus:/$ sudo cat /var/log/dmesg | grep "\(luetooth\|RFKILL\)" [sudo] password for vnc: [ 4.299662] kernel: Bluetooth: Core ver 2.22 [ 4.299678] kernel: Bluetooth: HCI device and connection manager initialized [ 4.299682] kernel: Bluetooth: HCI socket layer initialized [ 4.299685] kernel: Bluetooth: L2CAP socket layer initialized [ 4.299691] kernel: Bluetooth: SCO socket layer initialized [ 5.822591] kernel: [BT_RFKILL]: Enter rfkill_rk_init [ 5.822597] kernel: [WLAN_RFKILL]: Enter rfkill_wlan_init [ 5.823354] kernel: [WLAN_RFKILL]: Enter rfkill_wlan_probe [ 5.823394] kernel: [WLAN_RFKILL]: can't find rockchip,grf property [ 5.823401] kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6275p [ 5.823406] kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control. [ 5.823412] kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio. [ 5.823458] kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: WIFI,host_wake_irq = 8, flags = 0. [ 5.823468] kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: The ref_wifi_clk not found ! [ 5.823473] kernel: [WLAN_RFKILL]: rfkill_wlan_probe: init gpio [ 5.823480] kernel: [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 1 [ 5.823485] kernel: [WLAN_RFKILL]: Exit rfkill_wlan_probe [ 5.824968] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 148. [ 5.825045] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 21. [ 5.825063] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 150. [ 5.825081] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 0. [ 5.825187] kernel: [BT_RFKILL]: Request irq for bt wakeup host [ 5.825276] kernel: [BT_RFKILL]: ** disable irq [ 5.825419] kernel: [BT_RFKILL]: bt_default device registered. [ 8.815604] kernel: [BT_RFKILL]: bt shut off power I tried rfkill to unblock the device. It can be listed under hciconfig: vnc@orangepi5-plus:~$ sudo rfkill unblock 0 vnc@orangepi5-plus:~$ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:21 acl:0 sco:0 events:2 errors:0 TX bytes:6 acl:0 sco:0 commands:2 errors:0 Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Packet type: DM1 DH1 HV1 Link policy: Link mode: PERIPHERAL ACCEPT After rebooting the dmesg shows the firmware is not found. Please advise: vnc@orangepi5-plus:/$ sudo cat /var/log/dmesg | grep "\(luetooth\|RFKILL\)" [sudo] password for vnc: [ 4.304042] kernel: Bluetooth: Core ver 2.22 [ 4.304063] kernel: Bluetooth: HCI device and connection manager initialized [ 4.304067] kernel: Bluetooth: HCI socket layer initialized [ 4.304070] kernel: Bluetooth: L2CAP socket layer initialized [ 4.304076] kernel: Bluetooth: SCO socket layer initialized [ 5.796021] kernel: [BT_RFKILL]: Enter rfkill_rk_init [ 5.796026] kernel: [WLAN_RFKILL]: Enter rfkill_wlan_init [ 5.796715] kernel: [WLAN_RFKILL]: Enter rfkill_wlan_probe [ 5.796743] kernel: [WLAN_RFKILL]: can't find rockchip,grf property [ 5.796749] kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6275p [ 5.796754] kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control. [ 5.796758] kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio. [ 5.796795] kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: WIFI,host_wake_irq = 8, flags = 0. [ 5.796801] kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: The ref_wifi_clk not found ! [ 5.796804] kernel: [WLAN_RFKILL]: rfkill_wlan_probe: init gpio [ 5.796809] kernel: [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 1 [ 5.796813] kernel: [WLAN_RFKILL]: Exit rfkill_wlan_probe [ 5.797654] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 148. [ 5.797698] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 21. [ 5.797709] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 150. [ 5.797720] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 0. [ 5.797785] kernel: [BT_RFKILL]: Request irq for bt wakeup host [ 5.797840] kernel: [BT_RFKILL]: ** disable irq [ 5.797942] kernel: [BT_RFKILL]: bt_default device registered. [ 8.790808] kernel: [BT_RFKILL]: rfkill_rk_set_power: set bt wake_host high! [ 8.842572] kernel: [BT_RFKILL]: rfkill_rk_set_power: set bt wake_host input! [ 8.842598] kernel: [BT_RFKILL]: ENABLE UART_RTS [ 8.952573] kernel: [BT_RFKILL]: DISABLE UART_RTS [ 8.952634] kernel: [BT_RFKILL]: bt turn on power [ 8.952658] kernel: [BT_RFKILL]: Request irq for bt wakeup host [ 8.952693] kernel: [BT_RFKILL]: ** disable irq [ 9.253728] kernel: usb 5-1.1: Product: Bluetooth Radio [ 9.312606] kernel: Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852 [ 9.313357] kernel: rtk_btusb: Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432 [ 9.313592] kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 9.313600] kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin [ 9.315321] kernel: bluetooth hci0: Direct firmware load for rtl_bt/rtl8852bu_fw.bin failed with error -2 [ 9.315330] kernel: Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852bu_fw.bin not found [ 11.338412] kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.338421] kernel: Bluetooth: BNEP filters: protocol multicast [ 11.338434] kernel: Bluetooth: BNEP socket layer initialized

Hey everyone. New to Armbian and Orange Pi, but no stranger to everything I ever try do do being a major hassle! So here's the deal. Installed Armbian jammy 5.1 for orange pi plus. Working nicely. Except some of you might remember me from earlier today when I was struggling to get my ax210ngw working correctly (thanks by the way. Fixed that)! So I follow the process to switch from SD card to my Samsung 980 pro 1tb nvme. Bit of confusion getting it to show as an option in armbian-install, but I got it. Formatted in ext4 with a partition via gparted--now every time I try to run the install script, no matter which option I choose, it either freezes or crashes while transferring rootfs to /dev/nvme0n1 . So I thought why not try creating a smaller boot partition (as I've more than once had an issue modding consoles that this has fixed). So I create a 64gb partition. Great. Nvme0n1p1. Exact same problem. I've let it sit for 45 minutes twice now and didn't help. Tends to get hung up between 25 and 50% if that means anything. PLEASE HELP! Also I've been selecting ext4 as the format but just chose btrfs and the same issue persisted.

Since I am interested in the connection ability, I figured the info we gather should go into ONE thread. I have tried to build new kernels, but can only see USB controllers and devices two ports. I have seen a lot of work by Sebasitian Reichel @ Collabora, and his patches, but these do not seem to have the desired result on my test board. Orange PI 5. There seems to be an issue with the port mux, FUSB302, that either connects the last USB to the "vertical" port or to the "USB C" connector. I will comment my findings and attempts to correct this in this thread, and think we could find out where we are if you add your findings, successes and failures, rather than cluttering everywhere Regards, Gullik

Hi all, I'm using a UEFI based edge ubuntu 24.04 image which reported a kernel stack trace (system still seems functional and no ongoing issue/messages) - [ 22.382942] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 5-.... } 6 jiffies s: 381 root: 0x20/. [ 22.382966] rcu: blocking rcu_node structures (internal RCU debug): [ 22.382972] Sending NMI from CPU 7 to CPUs 5: [ 22.382983] NMI backtrace for cpu 5 [ 22.382995] CPU: 5 PID: 92 Comm: kworker/u16:2 Tainted: G W 6.8.5-edge-arm64 #2 [ 22.383004] Hardware name: Orange Pi Orange Pi 5 Plus/Orange Pi 5 Plus, BIOS v0.9.1 10/12/2023 [ 22.383009] Workqueue: writeback wb_workfn (flush-252:1) [ 22.383024] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 22.383032] pc : FSE_buildCTable_wksp+0x1ac/0x340 [ 22.383041] lr : 0xffff80008847c0ee [ 22.383047] sp : ffff80008309b0e0 [ 22.383051] x29: ffff80008309b0e0 x28: ffff00010117424b x27: 0000000000000006 [ 22.383061] x26: ffff80008309b2f8 x25: 0000000000000007 x24: ffff00010117424b [ 22.383069] x23: 0000000000001db5 x22: ffff8000885b4ad8 x21: ffff800088479ed4 [ 22.383077] x20: 000000000000002c x19: 0101010101010101 x18: 0000000000000080 [ 22.383086] x17: 0000000000000080 x16: ffff80008847c0ee x15: 0000000000000080 [ 22.383094] x14: 0000000000000104 x13: ffff800088479ed4 x12: ffff80008847c094 [ 22.383103] x11: 000000000000002c x10: 0000000000000007 x9 : ffff80008847c100 [ 22.383111] x8 : 000000000000002c x7 : 000000000000002c x6 : ffff80008847c15c [ 22.383119] x5 : 0000000000000004 x4 : 0000000000000023 x3 : 00000000000000ee [ 22.383127] x2 : 0000000000000006 x1 : 0000000000000048 x0 : 000000000000006f [ 22.383135] Call trace: [ 22.383139] FSE_buildCTable_wksp+0x1ac/0x340 [ 22.383145] ZSTD_buildCTable+0x1d0/0x1e8 [ 22.383155] ZSTD_buildSequencesStatistics+0x31c/0x3b8 [ 22.383164] ZSTD_entropyCompressSeqStore_internal.constprop.0+0x170/0x2c0 [ 22.383172] ZSTD_compressBlock_internal+0x8c/0x200 [ 22.383180] ZSTD_compressContinue_internal+0x1e0/0xa88 [ 22.383187] ZSTD_compressEnd+0x34/0x1a0 [ 22.383195] ZSTD_compressStream2+0x514/0x600 [ 22.383203] ZSTD_compress2+0x68/0xb8 [ 22.383211] zstd_compress_cctx+0xa0/0xc0 [ 22.383216] __zstd_compress+0x70/0xc8 [zstd] [ 22.383232] zstd_compress+0x30/0x48 [zstd] [ 22.383245] crypto_comp_compress+0x20/0x38 [ 22.383251] zcomp_compress+0x2c/0x40 [zram] [ 22.383267] zram_submit_bio+0x3dc/0x9a0 [zram] [ 22.383280] __submit_bio+0xb4/0x148 [ 22.383290] submit_bio_noacct_nocheck+0x10c/0x2e8 [ 22.383299] submit_bio_noacct+0x184/0x530 [ 22.383308] submit_bio+0xa4/0x118 [ 22.383317] ext4_io_submit+0x38/0x68 [ 22.383324] ext4_do_writepages+0x568/0xb48 [ 22.383332] ext4_writepages+0xa4/0x138 [ 22.383340] do_writepages+0x90/0x210 [ 22.383346] __writeback_single_inode+0x48/0x400 [ 22.383352] writeback_sb_inodes+0x234/0x5e8 [ 22.383356] __writeback_inodes_wb+0x68/0x150 [ 22.383361] wb_writeback+0x294/0x3a0 [ 22.383366] wb_workfn+0x32c/0x5d0 [ 22.383371] process_one_work+0x164/0x360 [ 22.383378] worker_thread+0x2b8/0x510 [ 22.383384] kthread+0xec/0xf8 [ 22.383389] ret_from_fork+0x10/0x20 Details from armbianmonitor -u at https://paste.armbian.com/tuxuroyunu cheers Andrew

Hello everyone, and Happy New Year. One question about Orange Pi 5 Plus: i have installed a wifi module (supported than what the official Orange documentation reports) AX210NGW in my Orange Pi 5 Plus main board with Operating System: Armbian 23.11.1 bookworm and Kernel: Linux 5.10.160-legacy-rk35xx. I copied in /lib/firmware the firmware of the module (https://intel.ly/3S0QZrA). if from the terminal I run: lspci I see the device but in "Armbian-config" in hardware section don't see the wifi module, and I can't activate the module to surf the Internet or the local network in wifi. The question is: am I forgetting any steps to setup the wifi module correctly?

I've found information on how to use your own IR remote controller from this site: https://forum.odroid.com/viewtopic.php?f=215&t=44671 In short: 1. Enable logging from the IR kernel module, enter in a terminal: sudo -i echo 1 > /sys/module/rockchip_pwm_remotectl/parameters/code_print dmesg -w 2. Check if your remote is supported by pressing the keys on your remote. It should give you info like: [ 3485.342354] USERCODE=0xfb04 [ 3485.369309] RMC_GETDATA=fd 3. Download the overlay file below and edit the usercode and the code for each key. So for like with the key above it'll be 0xfd 4. Place the header file "rk-input.h" in the same directory as the overlay file. In my case the location is "/usr/src/linux-headers-6.1.43-vendor-rk35xx/include/dt-bindings/input/rk-input.h" 5. Compile and install with: cpp -nostdinc remote.dts remote-precompiled.dts sudo armbian-add-overlay remote-precompiled.dts remote.dts

Hi all! I have a problem with Armbian images on kernel 5.10.160 (jammy & bookworm Armbian_23.11.1_Orangepi5-plus_***_5.10.160.img) When starting from the SD card the nvme device is not visible root@orangepi5-plus:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk1 179:0 0 58G 0 disk ├─mmcblk1p1 179:1 0 256M 0 part /boot └─mmcblk1p2 179:2 0 57.1G 0 part /var/log.hdd / mmcblk0 179:32 0 233G 0 disk mmcblk0boot0 179:64 0 4M 1 disk mmcblk0boot1 179:96 0 4M 1 disk zram0 254:0 0 7.7G 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log but some other distros for opi5+ see nvme fine (official img, from Joshua-Riek, etc..) After playing with different distros, I noticed that the latest builds of the 5.10.160 kernel do not see it, but early kernel builds work quite well with nvme. I still haven’t been able to get the board to start from nvme on any distribution. The SPI is flashed correctly. I can start only from SD or eMMC Has anyone encountered a similar problem on opi5+/16GB ?

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.

Hi, I was just trying to test locally build image with edge kernel (Armbian_23.11.0-trunk_Orangepi5-plus_bookworm_edge_6.6.0-rc1.img) by flashing it on SD card and then trying to boot off it in my Orange Pi 5+. The board just sits there with the LED blinking and that's it. The legacy kernel image (Armbian_23.11.0-trunk_Orangepi5-plus_bookworm_legacy_5.10.160.img) boots fine. Do I have to carry out some extra step(s) to test the edge kernel? It's not a show-stopper for me as I have legacy image booting of EMMC nicely (and I am running jellyfin in docker happily there). It's just I thought I might test out some bleeding-edge stuff. Thanks in advance.

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:~$

Hello, I am using Armbian 23.8.2 Jammy for Orange Pi 5 PLus and it cannot diplay 4K via HDMI. How to enable/switch this on?

Hello I have installed Armbian 24.2.3 Bookworm with Linux 5.10.160-legacy-rk35xx on Orange Pi 5 plus with 32 Gb ram and mounted a heatsink with a fan on the CPU (this model: http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Cooling-Fan.html) I need help configuring the fan to turn on when the CPU temperature reaches 60°C and turn off when it reaches 50°C. Can you provide instructions on how to do this? Thanks for help or support

I built armbian using the branch 23.11 with legacy-kernel 5.10.160 for use as a Nextcloud server. Version: Armbian-unofficial 23.11.0-trunk Bullseye \l . 5.10.160-legacy-rk35xx After running sudo apt upgrade there were a few packages which were being upgraded successfully from 23.11.0-trunk to 23.11.1. Unfortunately the package armbian-bsp-cli-orangepi5-plus-legacy cannot be upgraded to 23.11.1 due to the base-files still being on 23.11.0-trunk. The system is running fine though. $ sudo apt update && sudo apt list --upgradable Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://deb.debian.org/debian bullseye-backports InRelease Hit:5 http://security.debian.org bullseye-security InRelease Hit:6 https://packages.sury.org/php bullseye InRelease Hit:1 http://mirrors.dotsrc.org/armbian-apt bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. Listing... Done armbian-bsp-cli-orangepi5-plus-legacy/bullseye 23.11.1 arm64 [upgradable from: 23.11.0-trunk] $ sudo apt install --only-upgrade armbian-bsp-cli-orangepi5-plus-legacy Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: armbian-bsp-cli-orangepi5-plus-legacy : Depends: base-files (>= 23.11.1) but 23.11.0-trunk-11.1+deb11u8-bullseye is to be installed E: Unable to correct problems, you have held broken packages. $ apt-cache policy base-files base-files: Installed: 23.11.0-trunk-11.1+deb11u8-bullseye Candidate: 23.11.0-trunk-11.1+deb11u8-bullseye Version table: *** 23.11.0-trunk-11.1+deb11u8-bullseye 100 100 /var/lib/dpkg/status 23.8.1-bullseye 500 500 http://apt.armbian.com bullseye/main arm64 Packages 11.1+deb11u9 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages How do I fix this issue? Is there a safe way to upgrade the base-files to 23.11.1? I cannot rebuild the system! Any help is appreciated:)

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

I just installed with the latest KDE image, but I'm able to reproduce this with any of the images available. After going through the initial configuration, wifi works great. I updated apt and upgraded everything. Then I installed the armbian-firmware-full package. After rebooting wifi still works. Then I setup Bluetooth for my mouse and keyboard. They work correctly. After rebooting I no longer see any networks to connect to for wifi. If I disable Bluetooth and reboot wifi works again and so does Bluetooth. Is this an issue of daemons or drivers loading in the wrong order?

I just installed with the latest KDE image, but I'm able to reproduce this with any of the images available. After going through the initial configuration, wifi works great. I updated apt and upgraded everything. Then I installed the armbian-firmware-full package. After rebooting wifi still works. Then I setup Bluetooth for my mouse and keyboard. They work correctly. After rebooting I no longer see any networks to connect to for wifi. If I disable Bluetooth and reboot wifi works again and so does Bluetooth. Is this an issue of daemons or drivers loading in the wrong order?

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!