Search the Community

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

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

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

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

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

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

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

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

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

I lost whole day yesterday to try boot with new images from Armbian download page - kernel 6.1 / kernel 6.8 bookworm/trixi and none boots... If I take Ubuntu or Debian image I have no problem to boot from. Do you have the same?

playing around with armbian-config after switiching to vendor kernel - missing "toogle hardware configuration" Left is on (previous legacy vendor) kernel with "24.5.1 and right is legacy kernel with "24.2.1"" Just curious if anyone know why that is? Perhaps I should have taken other steps when switching to vendor kernel(I have rebooted and confirmed it is running vendor kernel prior to screenshot)

Can you help me with the contents of the file name? I understand edge, vendor, but then there are other suffixes that are not clear to me: are gnome-oibaf_desktop the same "kernel release" as the xfce_desktop or minimal? Or there are patches that are applied only to a specific version? Thanks!

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?

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 ?