Search the Community

I only have options 1,4,5,7 on my nand-sata-install utility and can only boot from a single armbian microsd card but no other. /dev/mtdblock0 shows no files. Everything has been fine till now! Would love some help. Thanks

i am taping in the dark here and in need of some help. i am running openhab on armbian 23.8.1 server and i need to get audio out on 3.5 jack for alerts. openhab has only two options system speaker and web audio. web audio plays on client like browsers using pulse audio. But if i use system speaker nothing comes out. What can i do to get sound on 3.5mm out on opi? is it even possible? i have this but this is also where my knowlege ends so help needed. aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchipdp0 [rockchip-dp0], device 0: rockchip-dp0 spdif-hifi-0 [rockchip-dp0 spdif-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: rockchiphdmi0 [rockchip-hdmi0], device 0: rockchip-hdmi0 i2s-hifi-0 [rockchip-hdmi0 i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: rockchipes8388 [rockchip-es8388], device 0: dailink-multicodecs ES8323.6-0010-0 [dailink-multicodecs ES8323.6-0010-0] Subdevices: 1/1 Subdevice #0: subdevice #0 i am assuming card 2 is 3.5 out but not sure what to do with it. thanks for help!

Hey all, New to Armbian, installed to an Orange Pi 5. Installed XRDP - works fine in root (desktop shows) but if I try to do it as a user I just get a black screen with cursor. From searching I can see posts about already being logged in as a user already, and therefore black for privacy but I've not logged in as the user prior? Cant find anything really conclusive explaining how to resolve this Also even in root if I get logged out of desktop (RDP session still active, i.e. desktop lock screen) my root password doesn't work. Password is clearly not wrong

Good day, I have Opi 5 and bought this display https://www.aliexpress.com/item/1005005641383181.html?src=google&aff_fcid=66031a1404104c2cb62a43359c4edcd8-1705719622481-01990-UneMJZVf&aff_fsk=UneMJZVf&aff_platform=aaf&sk=UneMJZVf&aff_trace_key=66031a1404104c2cb62a43359c4edcd8-1705719622481-01990-UneMJZVf&terminal_id=b834b596955b44a1bf643629f5ba5647&afSmartRedirect=y . It was a blind buy ... And now I can't get it work if its even possible. I'm its my first time trying to get display on these boards usually use them trought Monitor or TV and it works flawlessly. Cant find even config.txt . But now im lost at how to get it work .. I am new to this so I would appreciate any tips or help . Have a good day

and, BTW, this will probably work on any SBC that has pwm and working port of wiringPi (wiringOP is much simpler than the dtbo method, IMO) WHY: I don't like fans that run full speed ALL the time pwm fans are a bit limited on the ground in small size, and expensive The SBC has pwm pins, so why not use them none of the examples I have found are adequate, either gpio off/full or excessive python scripts, 40 lines or more,, the bash script is ~ 10 lines Some of the wiringOP/gpio packages don't work (ubuntu-full desktop) try the commands in rc.local, if they don't work, then,,, dpkg -l |grep wiring; apt remove ..... git clone https://github.com/orangepi-xunlong/wiringOP.git,, also install lm-sensors (you may have to make link, this puts gpio in /usr/local/bin, this is branch next) in rc.local: gpio mode 0 pwm #using wPi pin #'s, from gpio readall sleep 500e-3 #pause needed gpio pwm 0 900 #starts for sure gpio pwm 0 380 #slow to MIN until cron adjusts ----- gpio pwm <pin> NNN ,,,, NNN is what I will call PWR, to get range give a PWR too large, the error will give range If the PWR is too low the the fan won't start, even 800 is only 90% start The fan turns all the time, but not at full speed, at MIN you can almost count the turns (maybe 150 rpm) You have to find the PWR number for MIN for your fan, start at 300, it should run for hours, if not add 20, retest When you get some #, then add 10%. With this number, fan should run forever the script that cron calls every minute or 2 #!/usr/bin/bash TEMP=`sensors|grep bigcore0 -A3 |grep temp1 |tr -s ' '| cut -d ' ' -f 2|cut -c 2-3` #adjust grep as suitable, fails >99 echo $TEMP #TEMP=$1 #for testing, will error if $1 is blank PWR=$(("$TEMP" * 11)) #or any other number you choose echo $PWR if [ "$PWR" -gt 999 ]; then #check to see if PWR is in 'correct' range PWR=999 elif [ "$PWR" -lt 380 ] ; then #if this number is suitable for YOUR fan PWR=380 fi gpio pwm 0 $PWR ----- obviously comment out echo lines when debugging finished And now the wiring, it is stupid simple (arrows are both connections AND current flow) (-ve) <-- E pwm --> R --> B (+ve) --> Fan --> C if R is 1k, not enough drive to turn on transistor, 330 is 'iffy', 220 is OK, I have 180, depends on transistor Oh, BTW, scope told me pulses are +, so transistor is NPN, if you couldn't follow circuit logic (TO92 OK, unless fan huge) ---- and now pwmTone,,, absolutely nothing on web gpio pwmTone <pin> <frequency> ,, sounds good, right. well range likely changes, neutral as long as you know plus: fan starts MUCH better, even 1/2 PWR minus: fan barely slows down even with very low PWR If anyone knows more, please reply..... maybe there should be 5-10k pwm --> (-ve) to ensure pwm turn-off??? ---- I guess if you don't have a scope you could feed a LED + R, see if it dims (? R=100?) as you change PWR PS I would suggest this be pinned, if it is considered suitable --------- And a better debugged script, better than off the top (of my head) paying more attention to the hw side and not forgetting anything ----- #!/usr/bin/bash TEMP=`sensors|grep bigcore0 -A3 |grep temp1 |tr -s ' '| cut -d ' ' -f 2|cut -c 2-3` #adjust grep as suitable, fails >9 echo $TEMP if [ $# -gt 0 ]; then TEMP=$1 #for testing fi PWR=$(($TEMP * 11)) #or any other number you choose if [ "$TEMP" -lt 50 ]; then PWR=$(($TEMP * 8)) elif [ "$TEMP" -lt 60 ]; then PWR=$(($TEMP * 9)) elif [ "$TEMP" -lt 70 ]; then PWR=$(($TEMP * 10)) fi echo $PWR if [ "$PWR" -gt 999 ]; then #check to see if PWR is in 'correct' range PWR=999 elif [ "$PWR" -lt 380 ]; then #if this number is suitable for YOUR fan PWR=380 fi echo $PWR gpio pwm 0 $PWR

pi@opi5:~/AoC-2023-cplusplus$ lscpu --all --extended CPU SOCKET CORE L1d:L1i:L2:L3 ONLINE MAXMHZ MINMHZ MHZ 0 0 0 0:0:0:0 yes 1800.0000 408.0000 1800.0000 1 0 1 1:1:1:0 yes 1800.0000 408.0000 1800.0000 2 0 2 2:2:2:0 yes 1800.0000 408.0000 1800.0000 3 0 3 3:3:3:0 yes 1800.0000 408.0000 1800.0000 4 0 0 4:4:4:0 yes 2256.0000 408.0000 2256.0000 5 0 1 5:5:5:0 yes 2256.0000 408.0000 2256.0000 6 1 2 6:6:6:0 yes 2304.0000 408.0000 2304.0000 7 1 3 7:7:7:0 yes 2304.0000 408.0000 2304.0000 Why the odd cortex a76 MAXMHZ values. pi@opi5:~/AoC-2023-cplusplus$ uname -a Linux opi5 5.10.160-legacy-rk35xx #1 SMP Tue Nov 28 02:45:16 UTC 2023 aarch64 GNU/Linux

Hello people, Happily running Bookworm, because it was the mainstream download for OPI5 a few months ago, I now see that the main download for OPI is back to Jammy. Apart from hardware accceleration, Bookworm runs great for me. In fact HA is not crucial for my server usage, though it would be nice. Question: what is the reason the main OPI5 download is now back to Jammy in stead of Bookworm? And what would be the advantages of going back from Bookworm to Jammy? (Got the aluminium passively cooling case for the OPI5, so far it's been great, 10 minutes of stresstesting all 8 cores doesn't get above 70 degrees celsius. For reference my Meko 3588 box without any cooling reaches over 80 degrees. On that Mekobox I am running Portainer, Docker, HomeAssistant, MosquitoServer, very stable for months and months) Bas Hamstra

Hello, i'm using Armbian 23.11 Jammy-amazingfated Gnome. Kernel 5.10 If to seek a couple of times in h264 1080p BD remux'es it will cause system restart. Any video players are affected. Tried mpv, vlc, kodi and others. Problem affect just h264 1080p remuxes, that typically are 30..40 Gb, smaller h264 or even larger h265 files seem to work fine. I tried fresh install of armbian, where no rkmpp is installed, then h264 files plays/seeks fine, in software mode of course. Once I did sudo update/upgrade, that also installs rkmpp and other rockchip stuff, then videos start to play with rkmpp and problem is back. I've tried disabling hw decoding as workaround , weird, but it seems it's not possible to do in any player. In mpv : hwdec=no , or pressing ctrl+h has no affect, can't get rid of rkmpp decoder. Ive tried all possible commands related to this, from official mpv documentation, but nothing helps to disable rkmpp . This is probably another issue. Disabling buggy h264_rkmpp_decoder could be good workaround, as cpu is easily capable do play 1080p in sw, but can't find a way to do this, no matter i try, pls help. Especially looking for solution for mpv

This https://github.com/Joshua-Riek/ubuntu-rockchip/wiki/Orange-Pi-5 produces nearly 0 dropped frames at 4K 60fps on https://www.youtube.com/watch?v=LXb3EKWsInQ While latest Armbian_23.11.1_Orangepi5_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz and doing immediately after install, only these commands: sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia sudo apt update sudo apt dist-upgrade sudo apt install mali-g610-firmware rockchip-multimedia-config exactly like it says on https://www.armbian.com/orangepi-5/ and sudo reboot produces alot of dropped frames on same youtube 4K 60fps video! What am I missing? Shouldnt there be equal accelerated video performance?

I am using Wifi/BT USB dongle to connect network for Orange Pi 5. But it does not work with Armbian. It works smoothly with Orange Pi's Ubuntu and Debian distros. I just need to insert the dongle into USB 3 to work. Is there anything I can do to use the dongle with Armbian? My dongle is "USB WiFi Bluetooth Adapter Dual Band 2.4/5.8Ghz Wireless RTL8821CU Don-ig"; https://www.ebay.com.au/itm/404244701011

This image works OK, and we now have both a 6.7 kernel AND graphics. Minor issues: EzCast stupid windows Wifi adapter does not plug and play. The vertical USB port does not sense plugging in a device (Wifi) Good work, Gullik

Hello, sorry if this has been answered somewhere else. I was just wondering how i upgrade my Orange Pi 5 running Arbmian 23.11.1 Bookworm w/ Linux 5.10.160-legacy-rk35xx to the latest Kernel. I tried using `sudo armbian-config` and updating via that with kernel upgrades unfrozen but it doesn't seem to work. Is there something I'm missing? Startup splash below: ___ ____ _ ____ / _ \| _ \(_) | ___| | | | | |_) | | |___ \ | |_| | __/| | ___) | \___/|_| |_| |____/ Welcome to Armbian 23.11.1 Bookworm with Linux 5.10.160-legacy-rk35xx System load: 4% Up time: 0 min Memory usage: 8% of 3.83G IP: 192.168.1.69 10.121.215.1 CPU temp: 40°C Usage of /: 6% of 57G RX today: 38.2 MiB

Hi, Thank you for maintaining this excellent distribution, I have tried out this evening, via SD card, the new Armbian 23.11 Bookworm CLI Kernel 6.7 and I wanted to share some feedback on it along with some queries please: 1) HDMI works connected to my 4K Samsung TV, although I had to turn off "Input Signal Plus" for it to display the console correctly, otherwise there were all manner of green rectangles and other screen corruption present. Turning off "Input Signal Plus" fixed this straight away. 2) I cannot access either of the SSDs I have connected to my powered USB 3 hub. I tried with the hub connected to the USB-C port on the Orange Pi 5 and I also tried with it connected to the Top USB 3 port on the Orange Pi 5. I installed the full firmware package but this made no difference (not sure if it should). Issuing an lsusb does not show the USB connected SSDs. Is it expected to have these issues with USB 3 or USB-C on Kernel 6.7 ? as I do not have these issues using the legacy 5.10 kernel 3) If I issue a "sudo poweroff" the Orange Pi 5 shuts down all services and reboots rather than shutting down and powering off like the legacy 5.10 kernel does. If I press the power button on the Orange Pi 5 nothing happens, whereas the legacy 5.10 kernel initiates a shutdown and powers the Orange Pi 5 off. Is this expected behaviour on Kernel 6.7 ? Thanks again for all your work on this distribution.

Hi, The release notes for Armbian 23.11 state, under Key Improvements in This Release, "Mainline Kernel for RK3588 with experimental HDMI support." I am currently running the default 5.10.160-legacy-rk35xx kernel If I wanted to switch to and try out the mainline kernel for RK3588 with experimental HDMI support, would I do something like this: sudo apt install linux-image-collabora-rockchip-rk3588 After testing, If I want to rollback to the default legacy kernel, what are the steps involved? Apologies if there are instructions elsewhere that cover this. Thanks in advance for any guidance.

Have an incident where I tried installing a newer kernel in an nvme working setup and the device wont post. My original installation flash card is working but is giving me problems. So I got 2 others and attempted to boot new version of the image and Im getting no post. I was able to solve my original problem by installing a legacy version in flash and copying /boot over to nvme. I also attempted rebuilding the mme partitions with no success. But it seems that there is something not working right with kernel 6.7.

On Armbian Orange Pi 5b webpage, one can download the latest image with kernel 6.7 Rrc1, not stable. Once the kernel (6.7) is stable, will there be a way to upgrade without reinstalling? Thanks.

Hello folks, I happily run Armbian Jammy XFCE on my much beloved Meko box (with at least SOME hardware accel) and Bookworm on Orange Pi 5. Both run excellent, but Jammy/xfce is a bit more snappy. probably because of partly harware accell. On the Meko R3588 4Gb box I installed Docker, Portainer, MQTT server container, Home Assistant container. All is well. I operate my boxes via RealVNC, so that it also will work seemlessly when VPN is active. The containers are so extremely light that they hardly take a few percent CPU. Home Assistant container takes 0,5Gig or so, MQTT server takes 0.1Gig. My first encounter with docker is very positive! Next I will try to add open VPN and SABNZB containers if possible. So...these containers got me thinking...can we run QEMU on Armbian? Probably not, but I have to ask: would it be possible to: have QEMU working on RK3588 Armbian Run for example a windows VM in QEMU? Even if it would be slow? Just playing and experimenting...never used XFCE before, it grows on me, very snappy and no-nonsense...! And with dark themes these UI's look a lot cooler in the first place IMO. PS: I don't get that my plastic Meko box doesn't get hot, without ANY active cooling. I did a stresstest for 4 minutes, all 8 cores maxed, and sensor temps reach eventually over 80 degrees. Where does the heat go? The box never gets really hot and when the stresstest ends sensor temps go straight back to 60/50s almost instantly. I quite LIKE it's completely silent and without moving parts. It's got an EXCELLENT built-in wifi adapter too! So good that I don't even bother to plug the ethernet cable in, that says it all. Maybe I'll start loving my 8Gig Opi5 more when I get a passively cooled aluminium case for it. But currently it has moving parts and NO built-in wifi and an ugly transparent case 😉 Bas

Is it possible to use the onboard microphone of Orange Pi 5 on Armbian? It does not seem to turn on

I am currently facing a challenge with my Orange Pi 5 running Armbian 23.8.1 Jammy. I'm trying to get an exFAT formatted USB drive to work with this setup. I cannot mount an exFAT filesystem, despite having exfat-fuse and exfat-utils installed. The system fails to recognize the exFAT filesystem, displaying the message: "unknown filesystem type 'exfat'". I tried to install this module: https://github.com/arter97/exfat-linux. But I'm getting an error, that states that the driver already should be included on this version of the kernel: root@orangepi5:~/exfat-linux# make make -C /lib/modules/5.10.110-rockchip-rk3588/build M=/root/exfat-linux modules make[1]: Entering directory '/usr/src/linux-headers-5.10.110-rockchip-rk3588' CC [M] /root/exfat-linux/inode.o In file included from /root/exfat-linux/exfat_fs.h:14, from /root/exfat-linux/inode.c:16: /root/exfat-linux/compat.h:12:2: error: #error "This driver doesn't support v5.8+, " "please use the included driver from your kernel" 12 | #error "This driver doesn't support v5.8+, " \ | ^~~~~ /root/exfat-linux/inode.c: In function 'exfat_readpages': /root/exfat-linux/inode.c:367:16: error: implicit declaration of function 'mpage_readpages'; did you mean 'mpage_readpage'? [-Werror=implicit-function-declaration] 367 | return mpage_readpages(mapping, pages, nr_pages, exfat_get_block); | ^~~~~~~~~~~~~~~ | mpage_readpage cc1: some warnings being treated as errors make[2]: *** [scripts/Makefile.build:273: /root/exfat-linux/inode.o] Error 1 make[1]: *** [Makefile:1920: /root/exfat-linux] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.10.110-rockchip-rk3588' make: *** [Makefile:24: all] Error 2 I'm lost, where should I look then for the driver for my kernel version? In armbian-config, I can only install kernel with version 4.19.193, But I'm not sure if downgrading the major version is a viable option.

My Orange Pi 5 appears to be completely dead. No lights turn on when the power is connected and the SD card is freshly imaged as well. This started happening when I connected a USB-C multi-port dongle with a connected PD power supply to it. Is it possible to revive this?

I couldn't ping the pi anymore so i hook it up to HDMI. There i see the initramfs prompt What's up with that guys?? When i type df i only see /dev /run Broken m.2 sata?

*UPDATED - The issue is the powered USB3 hub which is actually NOT USB3 as advertised and is instead USB2. Sorry to have wasted your time* Hi, I have a 1TB SATA SSD in a USB3 enclosure (that supports UASP) connected to a USB3 powered hub, which in turn connects to the Top USB3 port of an Orange Pi 5 4GB. Armbian (Debian Bookworm) is installed and running from a 128GB NVME drive plugged into the M2 slot of the Orange Pi 5. If I do an "lsusb -t" I get the output shown below. The SSD is Bus 02, Port 3, Dev 5 and is using the uas driver but is showing USB2 speed of 480M rather than USB3 speed of 5000M. I have also tried plugging the powered USB3 hub with SATA SSD USB3 enclosure plugged into the USB C data port but I have the same limitation. I have plugged the SATA SSD USB3 enclosure into my intel file server running Debian Bookworm and it uses the uas driver at 5000M with no issues. Am I doing something wrong? Do I need to disable the USB C port or dual hdmi display output for this to work? (I only use the HDMI port for video output) and have nothing connected to the USB C data port. Thanks in advance for any help and guidance on this. /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=xpad, 12M |__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 4, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 4, If 3, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 4, If 4, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 5, If 0, Class=Mass Storage, Driver=uas, 480M |__ Port 4: Dev 6, If 3, Class=Application Specific Interface, Driver=, 12M |__ Port 4: Dev 6, If 1, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 4: Dev 6, If 2, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 4: Dev 6, If 0, Class=Vendor Specific Class, Driver=btusb, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M

Hi all, this is my first post here on the forum. I'm getting ready to wrap up for the night, but I recently purchased an Orange Pi 5 (non-B) to do some tinkering with. I downloaded the Bookworm XFCE variant as I am somewhat familiar with XFCE already. Anyway, upon initial testing, I thought my power supply wasn't good enough for the board. I wasn't getting any HDMI output. When I removed the micro-SD card and tried to boot it that way, an orange pi splash screen would show on the attached display, so I think the port actually works (?) I have a spare USB to TTL Serial adapter so I was able to verify the board was successfully booting into Armbian, but xrandr didn't show any connections. I tried a USB-C to HDMI cable that I had handy, and that actually worked. I then stumbled across a forum thread on a similar issue with someone's Orange Pi 5B, and a comment said they fixed it by enabling the HDMI port in armbian-config. I tried that and it still didn't work. I also noticed a few debug messages that would come over the UART interface, something with an error -22. I'll try to replicate it tomorrow and add a comment with the exact error. I don't have it handy, but googling the text didn't really help. Anyway, like I mentioned earlier, I'm wrapping it up for the night so I'll try any suggestions tomorrow after my college classes. Any insights are appreciated.

Hi everyone, Has anyone been able to get gpu hardware acceleration to do encoding/decoding on Jellyfin on the orange pi 5? Thank you

I'm trying to use an SPI driven TFT display on the orange pi 5, but I'm stuck on enabling SPI in the first place. Looking at the pinout of the orange pi 5 in its manual, it appears that SPI4...M0 is the only bus broken out to the pins. However, enabling "rk3588-spi4-m0-cs1-spidev" in the armbian-config menu does not seem to do anything, as no /dev/spi device exists after a reboot. Enabling any of the other spi hardware functions seems to work just fine, creating a /dev/spi device as expected, but none of the other spi busses are accessible through the pin header. I'm on Armbian 23.8.1 (image: Armbian_23.8.1_Orangepi5_bookworm_legacy_5.10.160.img). Has anyone used SPI on the Orange Pi 5 before?