royk

FYI with the master branch HDR is broken again after this commit https://github.com/xbmc/xbmc/pull/23116/commits/e278e3a4b990d5de7afe9642b6b39c7eeff999bb If you revert this, it will work again, a proper fix seems has to be done in the kernel. So if someone knows how this has to be done...

You did only have to look a few posts further.

The experience I had was that the quotes were needed to make it even boot. But it seems you did it right, perhaps the issue isn't edid related. You could compare the edid with the one when it's working and the one when it doesn't. I thought I saw somewhere in the orange pi os there was a script hdmi/dp related. You could try that image to see if that works, if it does you could copy that script. Another thing you could try as workaround is to use a hdmi dummy, you might need one that imitates a 1080p monitor.

@Straconis To be sure, do you get a result with: lsinitramfs /boot/initrd.img-5.10.110-rockchip-rk3588 | grep btt7.bin

@NiLace I literally gave you the page number, how hard can it be. In case you're not able to find a page number in a manual......

@Straconis what passworder wrote is that if he first plugged his monitor into the HDMI (not the usb-c adapter) then the lcd into the usb-c adapter. If @passworder will compare the edid when it's working with the edid when it's not working you might gonna see what's going wrong. A way to do this: sudo apt install edid-decode cat /sys/class/graphics/fb0/device/drm/card0/card0-HDMI-A-1/edid | edid-decode > edid-working.log cat /sys/class/graphics/fb0/device/drm/card0/card0-HDMI-A-1/edid | edid-decode > edid-not-working.log With the usb-c adapter it will probably be cat /sys/class/graphics/fb0/device/drm/card0/card0-DP-1/edid | edid-decode > edid-working.log cat /sys/class/graphics/fb0/device/drm/card0/card0-DP-1/edid | edid-decode > edid-not-working.log To make loading the edid work, you'll need to add the edid file to your initramfs, to do this: sudo cp /sys/class/graphics/fb0/device/drm/card0/card0-DP-1/edid /usr/lib/firmware/edid/waveshare.bin sudo nano /etc/initramfs-tools/hooks/edid.sh #!/bin/sh # Copy local EDID monitor description data # mkdir -p "${DESTDIR}"/lib/firmware/edid EDID_DATA=/usr/lib/firmware/edid/waveshare.bin if [ -f "${EDID_DATA}" ]; then cp "${EDID_DATA}" "${DESTDIR}"/lib/firmware/edid/ fi exit 0 sudo chmod +x /etc/initramfs-tools/hooks/edid.sh sudo update-initramfs -u sudo nano /boot/armbianEnv.txt extraargs="drm_kms_helper.edid_firmware=edid/waveshare.bin"

@Dbosco Because you've installed the ansible of Martivo, you could try to edit the asound.conf to: /etc/asound.conf <confdir:pcm/dca.conf> defaults.pcm.dca.iec61937 1 Or: <confdir:pcm/dca.conf> defaults.pcm.dca.aes0 0x04 Then: sudo alsa-force-reload && pulseaudio -k pulseaudio -D in pulseaudio you should see a hdmi/dts device. Choose that device. I guess you already have this installed, but you could run: sudo apt install libswresample3 If this doesn't work, you could try to set pulseaudio back to hdmi stereo, then in kodi set the audio output to 2.0 and at passthrough options disable all formats except ac3 and enable ac3 transcoding You could also try these with alsa, so 6 options to try. I don't have other ideas at the moment, but will search further for hbr passthrough.

@Dbosco That will not work You shouldn't had to rm 90-pulseaudio.rules, I hope you only moved it instead of removing. What is in /etc/udev/rules.d/11-rockchip-multimedia.rules Be sure you've got in the file: /usr/share/alsa/cards/HDMI-OUT.conf # configuration for HDMI connection which just expose the # audio out device <confdir:pcm/hdmi.conf> HDMI-OUT.pcm.hdmi.0 { @args [ CARD DEVICE CTLINDEX AES0 AES1 AES2 AES3 ] @args.CARD { type string } @args.DEVICE { type integer } @args.CTLINDEX { type integer } @args.AES0 { type integer } @args.AES1 { type integer } @args.AES2 { type integer } @args.AES3 { type integer } type hw card $CARD } And in /usr/share/alsa/cards/aliases.conf the line: rockchip-hdmi0 cards.HDMI-OUT Then: sudo alsa force-reload && pulseaudio -k && pulseadaudio -D Then open pulseaudio volumecontrol: in "Configuration" only enable hdmi" set this on STEREO, then go to "Output devices" -> advanced and enable the passthrough functions Now you're able to passthrough dts and ac3, but not aac, dts-hd. This is why you could better set pulseaudio at 5.1/7.1 and let kodi the decoding do. Otherwise you could try ALSA, assuming you're running it on GBM: sudo nano /usr/share/wayland-sessions/kodi.desktop And change: Exec=kodi-standalone to: Exec=pasuspender -- env KODI_AE_SINK=ALSA kodi-standalone

@Dbosco This is probably because of the audio device naming rule, I think this is a copied broken fix. Try: sudo rm /etc/udev/rules.d/90-naming-audios.rules What Martivo has should work then. At least for eac3 ac3 and dts. With Alsa some other formats might work. dts-hd could only work with alsa, but it doesn't. I've no idea why yet. Some things I found: Intel had the issue that the channel mapping order was not right, rpi soundchip only accepts one format "IEC958_SUBFRAME_LE". I think for the moment pulseaudio works best because then kodi decodes the non supported passthrough audio and plays it as multichannel, this way you should be able to play all movies with multichannel audio.

@Dbosco Perhaps you didn't uninstall the version with support for RPI. Try to install libcec again with: cmake -DCMAKE_INSTALL_LIBDIR:PATH='lib/aarch64-linux-gnu' -DCMAKE_INSTALL_PREFIX:PATH='/usr' -DHAVE_LINUX_API=1 .. make -j8 && sudo make install For Kodi run "make clean" and your cmake command first before you run make again, otherwise it will make the config it made before

@Dbosco I guess by first compiling and install libcec without support for RPI.

@passworder I think you need to force it to load the correct edid. You could try to copy the edid at the moment it's working to /lib/firmware/edid/ then add the boot arg and hope it works. So that should look something like: sudo cp /sys/class/graphics/fb0/device/drm/card0/card0-HDMI-A-1/edid /lib/firmware/waveshare.bin sudo nano /boot/armbianEnv.txt Then add a new line: extraargs="drm_kms_helper.edid_firmware=edid/waveshare.bin"

@Kuu Tirronen Nice found that hack, but I'm questioning if you've followed the right steps, so which steps did you follow? Wayland will probably give better results, for hardware video decoding you'll need software that will make use of mpp. Amazingfate made a repo for jammy with panfork mesa and a repo with software build with rkmpp hw acceleration there are a few topics about this, also don't forget to install malirun from his repo, this will set the udev rules that's needed for hw acceleration. For Panfrost this option should be disabled: cat /boot/config* | grep CONFIG_DRM_IGNORE_IOTCL_PERMIT For mali blob you'll need the right driver and is not compatible with panfork mesa and not every driver supports X11.

@NiLace Check the UART output, page 96 in the manual.

@dkg It seems like your cec-client is missing the linux cec framework api, but with what do you want to use it? If it's with kodi you'll need to configure this before you compile it. If you want to use cec-client outside of kodi, you could try to compile a new one. First remove the installed version. apt-get update apt-get install cmake libudev-dev libxrandr-dev python-dev swig git clone https://github.com/Pulse-Eight/libcec.git mkdir libcec/build cd libcec/build cmake -DHAVE_LINUX_API=1 .. make -j8 sudo make install sudo ldconfig

@dkg Can't test it at the moment, but it did work. Don't you have a /dev/cec0 device? How did you test, which version, dtb?

@PajPaj You could try: https://github.com/philn/glide

The bootloader does work, but I can't boot into X. After the kernel is loaded it's repeating messages on the screen with "Failed to start network manager", "failed to start D-bus system message bus", "Failed to start User login management", "Failed to start system logging service" I did a manual install, removed all partitions on the nvme, created one ext4 partition, then mounted your "image for mtd install with gnome". cp -ra /location/image/* /location/nvme/ Changed the UUID in extlinux and fstab, then wrote the bootloader /usr/lib/linux-u-boot-current-orangepi5_23.02.3_arm64/rkspi_loader.img to mtdblock0. Oops I think I'd to check the disk first: " re-mounted 715e6119-a664-4ffb-8e5f-1ef95ca8a651. Quota mode: none." Ok wrote the image to usb and this booted correctly, then I installed it to the nvme with "armbian-install" and now it boots from nvme, so everything is working correctly.

Thanks, nice to see having more options. AFAIK the MTD bootloader of opi-5 doesn't support ext4, so the boot manager has to be on an ext2 or fat partition.

@amazingfate HDR problem is solved by https://github.com/JeffyCN/FFmpeg/commit/2e578b9ce6f46c4e2ab7f5bc3e066a7be1d586bc

@ZBGB That sucks, are you sure that you've the right settings and the adapter support these? I assume you know the adapter has to be at 3.3v and rx from the adapter has to be connected to tx on the board?

@vandyman Ok tnx, to be able to watch hdr at the moment it's only possible from gbm with gles rendering, I'm almost certain it doesn't work. I think that ffmpeg needs some adjustments due to changes in mpp. @amazingfate Found something, in ./mpp/codec/dec/h265/h265d_refs.c there is a line "s->h265dctx->pix_fmt |= MPP_FRAME_HDR;" when I change that to "s->h265dctx->pix_fmt |= MPP_FMT_YUV420SP_10BIT:" it plays HDR again. I assume a proper way to fix this is to add "MPP_FRAME_HDR" to ffmpeg?

@vandyman And does that one play HDR videos? @amazingfate and @luizkun I haven't found the exact problem yet, but luckily found a backup. With this backup it does play HDR videos again, but with the HDR Vision the colors don't match. After compiling a new version of mpp the same problem occured as before. So the problem should be in mpp or the combi of the new version with ..... The file I've uploaded is the working one for HDR10, is from date 2022-11-16 librockchip_mpp.so.0

@ZBGB That's what I thought when mine didn't boot whatever I tried. The voltage you read could be a bit lower because it's connected but since the pin should be pulled low to reset it doesn't matter anyway.

@ZBGB Did you look at the serial output? Perhaps that will make it a bit easier to find out what's going wrong. And how do you write the image to the SD card and which image?