martivo

The SPI fdisk output seems good. From the description I would also recommend to do a fresh trunk installation and also re-install the SPI. If that does not help then find another NVME drive to test with.

Please show also your /dev/mtdblock0 device partitions "fdisk -l /dev/mtdblock0"

I am on a way newer version, I see you are on trunk.0112, maybe try the latest trunk.0232? I also have the 16Gb RAM model and NVME(KingSpec M.2 2242 NVMe PCIe Gen3 x2 SSD, 512GB) without any issues at all. Could you test another model of a nvme drive to see if it could be related to the nvme drive being used? Do you see any pattern with how you reboot the device? Do you use halt/poweroff and then press a button, or do you use reboot command or do you unplug the power? Does it behave the same way regardless of how you do the reboot/restart?

I am also using Wayland and hw acceleration.

@compent you have to replace the values in inventory.yml file with values that are specific to your environment. In this specific case You have to replace "<non root user of your SBC that you created during armbian first boot, ex: martin>" with the normal username that you use for the Pi. In my case I use "martin" there. There are also other fields that you have to replace in the inventory.yml depending on what roles you have activated (most of them have example values too.) The Readme also lists what variables are needed for what roles. Depending weather you execute it locally or remotely as in the Readme, you will have slightly different inventory file. Here is the top part of my inventory.yml that I use: all: hosts: 192.168.0.3: #Replace with your Orange PI IP address ansible_user: martivo #Replace with oyur Orange PI 5 username for SSH vars: normal_user: martivo timezone: Europe/Tallinn hostname: loovsys.eu ... I hope it helps.

I have noy yet played aroud with GPIO on the Banan Pi 5, but for the Banan PI Zero I gave up on trying to use a working Python library and resorted to using the command line tools to get some basic functionality. I ended up calling the commands from Python code. import os stream = os.popen('gpio mode <PIN> input') stream = os.popen('gpio read <PIN>') output = stream.read() print(output) I can see that Banan Pi 5 has also gpiodetect, gpiofind, gpioget, gpioinfo, gpiomon, gpioset commands, so probably something like this might work. root@loovsys:~# gpiodetect gpiochip0 [gpio0] (32 lines) gpiochip1 [gpio1] (32 lines) gpiochip2 [gpio2] (32 lines) gpiochip3 [gpio3] (32 lines) gpiochip4 [gpio4] (32 lines) gpiochip5 [rk806-gpio] (3 lines) root@loovsys:~# gpioget gpiochip0 2 1 root@loovsys:~# gpioget gpiochip0 3 0 I hope this will give some ideas to the direction that you can explore and report back how it goes.

[ 35.994282] ------------[ cut here ]------------ [ 35.994307] WARNING: CPU: 3 PID: 219 at drivers/gpu/drm/rockchip/rockchip_drm_vop2.c:2986 vop2_crtc_load_lut+0x54/0x310 [ 35.994311] Modules linked in: xt_nat veth xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc overlay zstd joydev sch_fq_codel fuse ip_tables ipv6 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod panfrost gpu_sched [ 35.994461] CPU: 3 PID: 219 Comm: kworker/u16:4 Not tainted 5.10.110-rockchip-rk3588 #trunk.0184 [ 35.994465] Hardware name: Orange Pi 5 (DT) [ 35.994476] Workqueue: events_unbound commit_work [ 35.994485] pstate: 40c00009 (nZcv daif +PAN +UAO -TCO BTYPE=--) [ 35.994491] pc : vop2_crtc_load_lut+0x54/0x310 [ 35.994497] lr : vop2_crtc_load_lut+0x4c/0x310 [ 35.994500] sp : ffffffc0162c3bd0 [ 35.994505] x29: ffffffc0162c3bd0 x28: ffffff8145226800 [ 35.994515] x27: ffffffc01113d020 x26: ffffff818d398180 [ 35.994525] x25: ffffff81609cc058 x24: ffffff8105492080 [ 35.994534] x23: 0000000000000400 x22: ffffffc011598cf8 [ 35.994543] x21: ffffff8105490080 x20: ffffff8105490080 [ 35.994553] x19: ffffff81054900f8 x18: 0000000000000000 [ 35.994562] x17: 0000000000000000 x16: 0000000000000000 [ 35.994572] x15: 0000000000000010 x14: 0000000034325258 [ 35.994581] x13: ffffffc0162c3b98 x12: ffffffffffffffff [ 35.994591] x11: 0000000000000040 x10: 00000000fffffffe [ 35.994600] x9 : ffffffc0107e6030 x8 : 0000000000000000 [ 35.994610] x7 : ffffff81054e0080 x6 : 00000000000003ff [ 35.994619] x5 : 0000000000000400 x4 : 00000000000003ff [ 35.994628] x3 : 000000003fffffff x2 : 00000000000003ff [ 35.994638] x1 : ffffffc012d05000 x0 : 0000000000000000 [ 35.994647] Call trace: [ 35.994654] vop2_crtc_load_lut+0x54/0x310 [ 35.994661] vop2_crtc_atomic_flush+0x948/0xc18 [ 35.994667] drm_atomic_helper_commit_planes+0x1c0/0x1c8 [ 35.994675] rockchip_drm_atomic_helper_commit_tail_rpm+0xa4/0x144 [ 35.994681] commit_tail+0x80/0x108 [ 35.994686] commit_work+0x1c/0x28 [ 35.994694] process_one_work+0x1d8/0x290 [ 35.994700] worker_thread+0x1e0/0x270 [ 35.994706] kthread+0xf4/0x104 [ 35.994714] ret_from_fork+0x10/0x30 [ 35.994719] PC: 0xffffffc0107e6038: [ 35.994723] 5e38 910003fd a90153f3 aa0003f4 d2800201 a9025bf5 f0006d96 9133e2d6 a90363f7 ... [ 36.010446] ---[ end trace d5485d5fc9687633 ]--- I also noticed these in my dmesg, but have not had time to look into it. I can confirm that I get them too. root@loovsys:~# uname -a Linux loovsys.eu 5.10.110-rockchip-rk3588 #trunk.0184 SMP Fri Jan 20 18:24:04 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

My first suspect would also be the external USB drive. Also if you still have an SD card in it, try removing it too and see if it changes anything. If possible you could also try to change the power supply to see if it has any effect. Just to rule out these.

@Tony3 I personally would start from scrach (back up your personal/important data first). Install latest trunk release and follow this guide again + pin the repos.

@compent I would recommend to get the trunk release instead rather than the stable. "3. At the login screen, there is no option to select “kodi” anywhere, just the user profile I initially created. So Kodi is run manually." You have to first press on the username and only when you are at the password promt the selection is displayed in the bottom right (it is only a tiny gear icon). If you run Kodi from desktop you will not get it to work right as far as I know and possibly other issues are also related to it. @Tony3 Possibly the repo priorities are not set and some packages are later taken from default repo? Check this thread.

Some of them could (and are like setting the hostname), but I am guessing there is a reason why these hardware acceleration things are not yet packaged with Orange pi 5 Armbian by default? Hopefully someone who knows more can shed some light on what the downsides of using those repos is or what the future plan is. I like to think that once this is more mature then users would only need to run "sudo apt install chrome" or "apt install kodi" and get all the correct things. For now I am trying to collect, automate the How-To of Orange Pi 5 HTPC + Home Server setup into the Ansible roles to make it easy to apply setups without error....following forum instructions can be prone to error and sometimes tedious.

I use "htop" it shows each core separately and is a more modern view than top. Though if you really want to see it all then prometheus + node-exporter + grafana

Thanks, seems like a good idea. Added this functionality to orange pi 5 ansible role collection into "orangepi5-hdmi" role.

With AC3 I am able to send 5.1 audio throught the TV! Also content from the TV is played properly and ARC works. No need to change any audio sources. I have created an ansible role that will setup DTS and AC3 ALSA devices on Orange PI 5 so any audio that you play is sent with compression over HDMI/DP. Pulseaudio will show them as sinks. So if anyone else wan'ts to use an older receiver without 4K resolution support but has a new 4K tv then either of these could solve that issue. Both of these methods also work with a HDMI audio extractor.

@roykYes, I did get that to work(kind of), but not thanks to pulse-audio options(I really tried all of them in different combinations), I resorted to using dacenc for that(I refuse to have to check or know if my media file has the needed formats already with it in order to use it or if I want to play a game on the OPI5). My Receiver is rather old(2012 Yamaha RX-V567) and it supports only DolbyDigital or DTS(with most of their sub types. I will try out AC3 later to see if it works ). Seems LG has a beef with DTS, even though my TV(LG 60UF776V ~2016) lists support for it. I am having a suspicion that they have disabled passthrough for it in a later firmware update or it never supported passthrough like that - reading in many multimedia formus people are pissed at LG that buying a an expensive LG tv even in 2020 does not support DTS passthrough(and other brands do). I did try forcing PCM in TV with hopes that it will just pass it to the receiver and force the receiver to DTS without any luck. I really treied all of the combinations. I have a 4k HDMI splitter/audio extractor and yesterday I managed to get the 5.1 sound to the receiver using compressed DTS over SPDIF from it and 4k/60Hz to the TV at the same time[when using "Audio only" HDMI in the splitter to the receiver the TV picture got screwed up thats why I used SPDIF - ill investigate later]. So the remaining problem is the TV passthrough. I am still hoping to get the passthrough to work using a service menu configuration or maybe the TV will manage AC3. I want to get the TV passthrough to work so I would not have to switch sources when the source of the sound is the TV or the OPI5. Ill create the relevant ansible roles for that setup too in case someone finds it useful. #Start rant# At least now I understand what all those fancy words in user manuals mean...I never thought as a consumer I need to know all of that..."just plug in the ARC and have only one cable that does it all - it's Magic!" The good old times when we only had 1080p and everything worked perfectly no matter in what order you connect things up. We have open source processors, printable guns, but some companies are still playing licencing games over 6 channel audio as if it's some high tech future feature. #End rant#

TLDR; The HDMI 5.1 output works fine with OPI5, except the channels can be mixed up, fix here. The issues I have are not related to Orange PI or Armbian. @roykThank you for your help! After a ton of testing I can conclude that the issue is within my TV. I also tried connecting the TV and receiver with Optical cables and tried different passthrough settings and configurations. When connecting OPI5 straight to receiver then 5.1 works. It works when I play things from the TV itself (Using for example DLNA) over HDMI or SPDIF/Optical. The problem is that the TV I have will not pass anything from inputs except 2 channels PCM. The issue is same as described here. I don't want to connect the OPI5 to the receiver because the receiver is limited to 1080p/60Hz resolutions - but the TV is 4k. I don't feel like replacing a perfectly good 7.1 Yamaha receiver to get a better video resolution. Ill get my hands on a service remote soon and try this hack.

@snowI have not gotten green screen like the yt clip you provided, could you link to a specific video file that I could test and report back?

@royk Ill do some more testing with these options and get back with results. I did try to only connect it to the TV and see if I can hear all the channels(without actual surround of course), but only front-left and front-right were there from that test clip. Yes I am installing the entire image - few reasons...firstly I can reset all the configuations/nonsense that I have tried and start with a clean setup and secondly to be sure that I am exactly where everyone else is by installing image from trunk. Can someone confirm that HDMI 5.1 works for them correctly? so I can conclude that it is an issue with my TV/Rceiver setup and not an issue with Armbian/OPI5? @adr3nal1n27 I was frustrated too by the limits, but seems pay-to-play here if you are in a hurry - I bought the subscription for 5€ and can edit and post normally now.

@royk Yes it is pulse audio. I had now more time to test. I used the ChID-BLITS-EBU.mp4 file. Only front-left and front-right speaker work when I select Digital Surround 5.1 (HDMI) Output and the sound comes from the correct speakers. When I switch front-left and front-right in /usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf then they are switched (front left speaker says "front right"). When I switch front-left and front-center, then I can hear from the left speaker "front-center". I also tried your suggestion but it did not change anything, I also tried some other combinations, but seems only physical front left and front right speaker do anything. I tested it with Kodi(gdm3 directly starts Kodi) and with mpv(In Ubuntu desktop with Wayland) - same behaviour. Test were done with kernel 5.10.110-rockchip-rk3588 #trunk.0184 SMP Fri Jan 20 18:24:04 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux My old setup works with an Intel motheboard and Ubuntu Linux, I am trying to replace it with this Orange Pi 5. I am using ARC (From Orange Pi 5 HDMI to TV and ARC from TV to receiver), maybe that is somehow affecting it. I am now using the same HDMI port on the TV too, so only thing changed is the HDMI source(The Orange Pi 5). I also tried to reduce the resolution to 1080p@30Hz in case it might be a bandwidth issue(HDMI 1.4). About Wayland and KDE I would not bee too hopefull yet, it is "tech-preview state". https://community.kde.org/KWin/Wayland Since the armbian image updates require re-installation I have created a set of Ansible roles that can do what the guide describes in steps 3 to 5. I used ubuntu-desktop-minimal to avoid installing libre office etc. This made testing different stuff a lot faster and easy to go back to an original state. There are some other roles too but they are not related to this Guide. https://github.com/martivo/armbian-orange-pi-5-ansible readme provided for How-to use it. To do the same as the original guide activate the following roles in site.yml: --- - hosts: all become: yes roles: - role: orangepi5-hdmi - role: ubuntu-desktop-minimal - role: gdm-enable-wayland - role: kodi - role: gdm-auto-login #optional

Thanks for the instructions! For me stereo HDMI Audio works good in this setup. I am using Armbian_23.02.0-trunk.0179_Orangepi5_jammy_legacy_5.10.110_minimal.img.xz. Is anyone else having 5.1 channel audio issues over HDMI? When I switch to 5.1 then I do get some sound, but seems like only side channels are actually playing or the channels are mixed up somehow (movies have sound but can't hear people talk).