Search the Community

Hello! Can anyone comment whether PCIE Passthrough is even theoretically possible on an Orange Pi 5+? Or should I just cease and desist? #1) The hardware seems to be there #2) IOMMU seems to be working at least for platform/PHP devices #3) VFIO looks to be on #4) no cigar The missing piece looks to be MMU600_PCIE support, as non-platform devices don't seem to be getting assigned iommu groups? --- #1 "There are two MMU600 instances in RK3588, MMU600_PCIE and MMU600_PHP respectively " https://github.com/FanX-Tek/rk3588-TRM-and-Datasheet/blob/master/Rockchip RK3588 TRM V1.0-Part1-20220309.pdf #2 root@oppa:~# dmesg | grep -i iommu [ 4.106039] iommu: Default domain type: Translated [ 4.106116] rk_iommu fdab9000.iommu: version = 2 [ 4.106520] rk_iommu fdb50800.iommu: version = 2 [ 4.106772] rk_iommu fdb60f00.iommu: version = 2 [ 4.106972] rk_iommu fdb70f00.iommu: version = 2 [ 4.107142] rk_iommu fdb90480.iommu: version = 2 [ 4.107330] rk_iommu fdba0800.iommu: version = 2 [ 4.107517] rk_iommu fdba4800.iommu: version = 2 [ 4.107706] rk_iommu fdba8800.iommu: version = 2 [ 4.107893] rk_iommu fdbac800.iommu: version = 2 [ 4.108080] rk_iommu fdbb0800.iommu: version = 2 [ 4.108282] rk_iommu fdbdf000.iommu: version = 2 [ 4.108568] rk_iommu fdbef000.iommu: version = 2 [ 4.108871] rk_iommu fdc38700.iommu: version = 2 [ 4.109162] rk_iommu fdc48700.iommu: version = 2 [ 4.109386] rk_iommu fdcb7f00.iommu: version = 2 [ 4.109567] rk_iommu fdce0800.iommu: version = 2 [ 4.109682] rk_iommu fdd97e00.iommu: version = 2 [ 5.095442] mpp_vdpu2 fdb50400.vdpu: Adding to iommu group 1 [ 5.096226] mpp_vepu2 fdb50000.vepu: Adding to iommu group 1 [ 5.096639] mpp_vepu2 fdba0000.jpege-core: Adding to iommu group 5 [ 5.097143] mpp_vepu2 fdba4000.jpege-core: Adding to iommu group 6 [ 5.097610] mpp_vepu2 fdba8000.jpege-core: Adding to iommu group 7 [ 5.098073] mpp_vepu2 fdbac000.jpege-core: Adding to iommu group 8 [ 5.098725] mpp-iep2 fdbb0000.iep: Adding to iommu group 9 [ 5.099329] mpp_jpgdec fdb90000.jpegd: Adding to iommu group 4 [ 5.100281] mpp_rkvdec2 fdc38100.rkvdec-core: Adding to iommu group 12 [ 5.101031] mpp_rkvdec2 fdc48100.rkvdec-core: Adding to iommu group 13 [ 5.101989] mpp_rkvenc2 fdbd0000.rkvenc-core: Adding to iommu group 10 [ 5.102543] mpp_rkvenc2 fdbe0000.rkvenc-core: Adding to iommu group 11 [ 5.103910] mpp_av1dec av1d-master: av1_iommu_of_xlate,784 [ 5.103927] av1_iommu_probe_device,736, consumer : av1d-master, supplier : fdca0000.iommu [ 5.103934] mpp_av1dec av1d-master: Adding to iommu group 17 [ 5.120930] rockchip-vop2 fdd90000.vop: Adding to iommu group 16 [ 5.578177] rkcifhw fdce0000.rkcif: Adding to iommu group 15 [ 5.579738] rkisp_hw fdcb0000.rkisp: Adding to iommu group 14 [ 5.739969] rga3_core0 fdb60000.rga: Adding to iommu group 2 [ 5.740438] rga3_core1 fdb70000.rga: Adding to iommu group 3 [ 5.741091] rga2_mmu: IOMMU binding successfully, default mapping core[0x1] [ 5.783349] RKNPU fdab0000.npu: Adding to iommu group 0 [ 5.783493] RKNPU fdab0000.npu: RKNPU: rknpu iommu is enabled, using iommu mode for a in /sys/kernel/iommu_groups/*; do find $a -type l; done | sort --version-sort /sys/kernel/iommu_groups/0/devices/fdab0000.npu /sys/kernel/iommu_groups/1/devices/fdb50000.vepu /sys/kernel/iommu_groups/1/devices/fdb50400.vdpu /sys/kernel/iommu_groups/2/devices/fdb60000.rga /sys/kernel/iommu_groups/3/devices/fdb70000.rga /sys/kernel/iommu_groups/4/devices/fdb90000.jpegd /sys/kernel/iommu_groups/5/devices/fdba0000.jpege-core /sys/kernel/iommu_groups/6/devices/fdba4000.jpege-core /sys/kernel/iommu_groups/7/devices/fdba8000.jpege-core /sys/kernel/iommu_groups/8/devices/fdbac000.jpege-core /sys/kernel/iommu_groups/9/devices/fdbb0000.iep /sys/kernel/iommu_groups/10/devices/fdbd0000.rkvenc-core /sys/kernel/iommu_groups/11/devices/fdbe0000.rkvenc-core /sys/kernel/iommu_groups/12/devices/fdc38100.rkvdec-core /sys/kernel/iommu_groups/13/devices/fdc48100.rkvdec-core /sys/kernel/iommu_groups/14/devices/fdcb0000.rkisp /sys/kernel/iommu_groups/15/devices/fdce0000.rkcif /sys/kernel/iommu_groups/16/devices/fdd90000.vop /sys/kernel/iommu_groups/17/devices/av1d-master #3 dmesg | grep -i vfio [ 5.183453] VFIO - User Level meta-driver version: 0.3 root@oppa:~# cat /lib/modules/$(uname -r)/modules.builtin | grep vfio kernel/drivers/vfio/vfio.ko kernel/drivers/vfio/vfio_virqfd.ko kernel/drivers/vfio/vfio_iommu_type1.ko kernel/drivers/vfio/pci/vfio-pci.ko kernel/drivers/vfio/platform/vfio-platform.ko kernel/drivers/vfio/platform/vfio-platform-base.ko kernel/drivers/vfio/mdev/mdev.ko kernel/drivers/vfio/mdev/vfio_mdev.ko #lspci lspci -nn -D | grep -i 79 0002:21:00.0 Network controller [0280]: MEDIATEK Corp. Device [14c3:7961] lspci -vnk -s 0002:21:00.0 0002:21:00.0 0280: 14c3:7961 Subsystem: 1a3b:4680 Flags: fast devsel Memory at 980000000 (64-bit, prefetchable) [disabled] [size=1M] Memory at 980100000 (64-bit, prefetchable) [disabled] [size=16K] Memory at 980104000 (64-bit, prefetchable) [disabled] [size=4K] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?> Capabilities: [108] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [200] Advanced Error Reporting

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 ?

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.

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.

EDIT: I am using the Armbian 23.5.5 Orange Pi 5 Plus Jammy Legacy 5.10.160 Gnome Desktop image Let me preface this with I am a Linux noob and this is one step below black magic voodoo to me. For some reason my Orange Pi 5 Plus USB 3.0 ports are no longer functioning. I setup my OPi at my testing station and everything was working fine (except I couldn't get my WiFi dongle to work but that's a different post) After I turned off my Orange Pi 5 Plus, disconnected it and set it back up where it was going to be staged now the USB 3.0 ports no longer function. Putting in the "lsusb" command shows all my ports, including the non-functional USB 3.0 ports, but I can't get the 3.0 ports to work. The USB 2.0 ports are completely fine and functional. Does anyone know why the USB 3.0 ports stopped working and how to get them functioning again?

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 ?

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

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!

I recently purchased an Orange Pi 5 Plus and installed Armbian. It shuts down about every ten minutes. Strangely, when it is streaming video over HDMI it does not shutdown. So it can stream movies for up to three hours without shutting down. But if I am not streaming, for example if I am SSH into the device, it will shutdown after about ten minutes and I get booted out. I disabled system suspend in `settings > Power settings` but this did not help. I also just replaced the power supply with a 4 amp power supply (up from 3.5 amp) but this did not help at all. I also looked around 'armbian-config' but I did not notice any settings that could be the issue. I do not see any services or anything in the system log related to this. I tried to install caffeine as a workaround, which is supposed to prevent the computer from sleep, however, this did not help. I installed caffeine and made sure it was running but again it didn't help: ```bash ps aux | grep caffeine pi 2356 0.0 0.2 364892 45416 ? Ssl 13:53 0:00 /usr/bin/python3 /usr/bin/caffeine pi 2517 0.0 0.2 364896 45000 ? Sl 13:53 0:00 /usr/bin/python3 /usr/bin/caffeine ``` I would like help to debug this problem. Please give me some tips to track down the issue. Thanks!

Hi, I went to see if there were any updates to the OPi5+ images and saw the OPi5 had updates. I clicked on the link on the main download page. https://www.armbian.com/orangepi-5/ https://redirect.armbian.com/orangepi5-plus/archive/ I've come back and now it has desktop images but no server images.

Hi, I've been running Armbian legacy server on my 5+ for a month now. I had trouble initially with my EMMC not booting, but I discovered, I had to wipe the SPI Nor then using Armbian config to flash it, then write to EMMC. When a new version of Armbian comes out for the 5+ and it may be a 6.8 kernel build, will I need to re-flash the SPI before I can install the newer version of Armbian (or another image from that's not Armbian?) before updating the EMMC. I found the steps on the Radxa site insightful for a general overview of SPI Nor and flashing (I understand it not an OPi5 x board), but it's not clear to me if a different OS will need the SPI updated due to different bootloader etc ..... https://docs.radxa.com/en/rock5/lowlevel-development/bootloader_spi_flash

I want to share some information about an issue that I see on my OPi5+. Since I got it I am messing around with it and everything works great so far with the edge 6.7 kernel. One thing I noticed though was, that right after installation with nothing connected and when idle, there was one kernel process that was constantly consuming around 10% CPU time and the load stays at 1. The process was irq/136-hym8563. The number varies of course after each boot. Kernel driver is rtc_hym8563. Since it is build into the kernel I was not able to unload it as a first test. Side node, the issue is not seen on the Rock5b, so it seems OPi5+ hardware specific. Even if both are relative similar. I have not found anything useful so far on the internet. Don't know if it is just my device or if others are seeing a similar thing on their OPi5+ with the 6.7 edge kernel. IRQs going up like crazy for a few interrupts, compared to when driver rtc-hym8563 is not there. arch_timer rk_timer fec80000.i2c hym8563 Here are some debugging information. top output. root@orangepi5-plus ~# top -b -n 4 -p (pgrep hym) top - 16:30:43 up 3 min, 1 user, load average: 1.08, 0.63, 0.27 Tasks: 1 total, 0 running, 1 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 1.2 sy, 0.0 ni, 97.6 id, 0.0 wa, 1.2 hi, 0.0 si, 0.0 st MiB Mem : 15718.1 total, 15299.5 free, 422.6 used, 212.1 buff/cache MiB Swap: 7859.0 total, 7859.0 free, 0.0 used. 15295.5 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 438 root -51 0 0 0 0 D 0.0 0.0 0:16.90 irq/136-hym8563 top - 16:30:46 up 3 min, 1 user, load average: 1.08, 0.63, 0.27 Tasks: 1 total, 1 running, 0 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.7 sy, 0.0 ni, 97.9 id, 0.0 wa, 1.3 hi, 0.0 si, 0.0 st MiB Mem : 15718.1 total, 15299.5 free, 422.6 used, 212.1 buff/cache MiB Swap: 7859.0 total, 7859.0 free, 0.0 used. 15295.5 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 438 root -51 0 0 0 0 R 7.7 0.0 0:17.13 irq/136-hym8563 top - 16:30:49 up 3 min, 1 user, load average: 1.07, 0.63, 0.27 Tasks: 1 total, 0 running, 1 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.7 sy, 0.0 ni, 97.9 id, 0.0 wa, 1.3 hi, 0.0 si, 0.0 st MiB Mem : 15718.1 total, 15299.5 free, 422.6 used, 212.1 buff/cache MiB Swap: 7859.0 total, 7859.0 free, 0.0 used. 15295.5 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 438 root -51 0 0 0 0 D 8.0 0.0 0:17.37 irq/136-hym8563 top - 16:30:52 up 4 min, 1 user, load average: 0.99, 0.62, 0.27 Tasks: 1 total, 0 running, 1 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.8 sy, 0.0 ni, 97.9 id, 0.0 wa, 1.3 hi, 0.0 si, 0.0 st MiB Mem : 15718.1 total, 15299.5 free, 422.6 used, 212.1 buff/cache MiB Swap: 7859.0 total, 7859.0 free, 0.0 used. 15295.5 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 438 root -51 0 0 0 0 D 8.0 0.0 0:17.61 irq/136-hym8563 Interrupt increase over 1 minute. 100k for hym8563 and 1million for fec8000.i2c root@orangepi5-plus ~# uptime && date && cat /proc/interrupts | grep -iE "(hym|fec80000|_timer)" && sleep 60 && date && cat /proc/interrupts | grep -iE "(hym|fec80000|_timer)" 17:28:15 up 35 min, 1 user, load average: 1.01, 1.07, 1.00 Mon Jan 22 05:28:15 PM CET 2024 19: 26038 125123 73155 438814 46260 13649 3574 299665 GICv3 26 Level arch_timer 25: 22900 83767 54823 279426 36468 15155 10963 9513 GICv3 321 Level rk_timer 48: 0 0 0 0 0 0 0 30250774 GICv3 355 Level fec80000.i2c 136: 0 0 0 0 0 0 0 5041747 rockchip_gpio_irq 8 Level hym8563 Mon Jan 22 05:29:15 PM CET 2024 19: 26366 125128 91142 438815 46849 13652 3574 307458 GICv3 26 Level arch_timer 25: 23366 84133 67225 279722 37149 15171 10976 9752 GICv3 321 Level rk_timer 48: 0 0 0 0 0 0 0 31073437 GICv3 355 Level fec80000.i2c 136: 0 0 0 0 0 0 0 5178856 rockchip_gpio_irq 8 Level hym8563 irq cpu time is also visible in mpstat root@orangepi5-plus ~# mpstat -P ALL Linux 6.7.1-edge-rockchip-rk3588 (orangepi5-plus) 01/22/2024 _aarch64_ (8 CPU) 07:43:50 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle 07:43:50 PM all 0.13 0.00 0.68 0.01 1.33 0.03 0.00 0.00 0.00 97.82 07:43:50 PM 0 0.03 0.00 1.30 0.01 0.98 0.08 0.00 0.00 0.00 97.61 07:43:50 PM 1 0.03 0.00 0.26 0.01 0.18 0.02 0.00 0.00 0.00 99.51 07:43:50 PM 2 0.03 0.00 3.06 0.01 2.46 0.07 0.00 0.00 0.00 94.37 07:43:50 PM 3 0.02 0.00 0.77 0.01 0.58 0.02 0.00 0.00 0.00 98.60 07:43:50 PM 4 0.59 0.00 0.11 0.01 0.03 0.02 0.00 0.00 0.00 99.24 07:43:50 PM 5 0.22 0.00 0.05 0.01 0.01 0.01 0.00 0.00 0.00 99.70 07:43:50 PM 6 0.06 0.00 0.01 0.01 0.01 0.00 0.00 0.00 0.00 99.91 07:43:50 PM 7 0.04 0.00 0.02 0.01 6.49 0.03 0.00 0.00 0.00 93.42 procinfo output shows as well the high number for irq 136 and 48. root@orangepi5-plus ~# procinfo Memory: Total Used Free Buffers RAM: 16095284 585248 15510036 22584 Swap: 8047640 0 8047640 Bootup: Mon Jan 22 16:53:14 2024 Load average: 1.29 1.09 1.02 1/231 9335 user : 00:01:51.76 0.1% page in : 238872 nice : 00:00:00.03 0.0% page out: 118633 system: 00:09:19.33 0.7% page act: 59088 IOwait: 00:00:09.19 0.0% page dea: 0 hw irq: 00:18:07.58 1.3% page flt: 1335085 sw irq: 00:00:24.98 0.0% swap in : 0 idle : 22:09:57.44 97.8% swap out: 0 uptime: 02:51:46.79 context : 142704160 irq 18: 0 irq 66: 0 427819017 Edge ae irq 19: 4672570 irq 77: 0 570425352 Edge PC irq 20: 0 irq 78: 0 570425353 Edge ae irq 23: 0 irq 89: 0 285212680 Edge PC irq 25: 2504720 irq 90: 0 285212681 Edge ae irq 31: 0 irq 91: 2 irq 32: 15 irq 92: 0 irq 33: 1 irq 93: 32 irq 34: 0 irq 94: 0 irq 35: 0 irq 95: 75881 428343296 Edge en irq 36: 0 irq 96: 0 570949632 Edge en irq 37: 0 irq 97: 0 irq 38: 0 irq 98: 0 irq 39: 0 irq 99: 0 irq 40: 0 irq 100: 0 irq 41: 2 irq 101: 514 irq 43: 653459 irq 102: 0 irq 44: 2278 irq 119: 0 irq 45: 1346 irq 130: 0 8 Edge PCIe PME irq 46: 203 irq 131: 0 9 Edge aerdrv irq 47: 41964 irq 132: 99660 irq 48: 141047548 irq 133: 56265 irq 49: 108 irq 135: 0 irq 50: 0 irq 136: 23507838 irq 51: 0 irq 137: 324 irq 52: 2 irq 138: 0 irq 53: 0 irq 139: 0 irq 54: 0 irq 140: 0 irq 65: 0 427819016 Edge PC Since I do not need the RTC on my system, my idea was to create an own custom image, where rtc_hym8563 is build as a module. Where I can disable the module in the hope the process is gone and nothing is consuming cpu time when idle. It turns out that worked for me and I am running it like this for now. Here are my steps. Change kernel config in the build system. # config/kernel/linux-rockchip-rk3588-edge.config CONFIG_RTC_DRV_HYM8563=y After new image is installed and booted, it is indeed now a module. root@orangepi5-plus ~# zcat /proc/config.gz | grep -i hym CONFIG_RTC_DRV_HYM8563=m Disabling the rtc_hym8563 driver echo "blacklist rtc_hym8563" > /etc/modprobe.d/blacklist-rtc.conf update-initramfs -u reboot I just wanted to share this information in case someone else see this. For now I will live with my workaround and keep an eye on the kernel development to see, if there will be a change. In case there is some hardware expert and has some other tips, please feel free to share. Cheers, Marco

I've got Orange Pi 5 Plus board with 16 Gb of RAM, 256 Gb of eMMC, Realtek RTL8852BE-CG wireless module. SD card is Samsung EVO Plus 32Gb. I tried to run Armbian images on this board (from the SD-card I've mentioned before) but it was absolutely failed. I tried 5 images: Armbian_23.11.1_Orangepi5-plus_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz Armbian_23.11.1_Orangepi5-plus_bookworm_legacy_5.10.160.img.xz Armbian_23.11.1_Orangepi5_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz Armbian_23.11.1_Orangepi5-plus_bookworm_edge_6.7.0-rc1.img.xz Armbian_23.11.1_Orangepi5-plus_jammy_edge_6.7.0-rc1.img.xz which I downloaded from your website but the result the same: tons of errors, a lot of dumps, no even chance to see a desktop. Also I should say the official images of Ubuntu and Debian works fine so I guess it's not a hardware issue. There is UART log when I tried to start Armbian_23.11.1_Orangepi5-plus_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz image putty.log Could anyone tell me what the problem is?

Hi gals & guys, Came over to this forum from the OPI forums which seem.. rather low on real-user activity. I am quite new to the SBC Arm64 platform and have many questions. I am an experienced sysadmin on x86/amd64 and still figuring out the differences. I bought a Orange Pi 5 Plus 32G of RAM and i am running of the 256G emmc. I am able to run different OS's (OPI-Ubuntu, OPI-debian, plain Ubuntu and Armbian). As i intend to use the board as server i didn't look into Android and the like.. My plan is running (OMV) from the emmc and attaching ZFS storage by means of a nvme-to-sata adapter and providing iscsi storage from there to my home-lab with my VM's and containers + shared storage and backup. Teamed NIC's for the network, for later. With that out of the way, here is my question... My OPI5plus is running fine from emmc and i am able to handle most normal issues. My main problem is that i cannot get my storage or even my nvme-to-sata adapter detected. I don't really know how to go about it and how to use overlays to configure my system. Beside the fact that the OPI5plus has no native sata and only 1 sata2 overlay, i have a basic lack of understanding of the overlay concept, i guess. I've seen very little information online on "OPI5plus NAS/SATA" and was wondering if someone here could help me out ? Config: Armbian_Bookworm_legacy 5.10.160 on Emmc rkspi_loader.img flashed, else no boot. Tried: rkspi_loader_sata.img for OPI5pro, but then no boot overlay rk3588_sata2, but then no NIC's My nvme-to-sata adapter is an M.2 nvme pcie3 to 6 port sata3.0 with ASM1166 chipset. At boot time the leds on it flicker, then go out. In lspci there is no mention of it neither in lshw (not even as unclaimed or unidentified device) in dmesg there is: rk-pcie fe170000.pcie: PCIe Link Up rk-pcie fe180000.pcie: PCIe Link Up rk-pcie fe190000.pcie: PCIe Link Up (Are these the pcie bridges or the lan & wlan NIC's ?) rk-pcie fe150000.pcie: PCIe Link Failed (But i can't decrypt why) armbianmonitor: https://paste.armbian.com/ovicanekan Thanx for all your work helping others! Hope i can join you soon..