be8b298e9981eaf11bd4ad915c35bfaa7a81508258258d1c4ecf0d71f70dca2e (RPi)8d2e632542a27b9d87642c56fbd90fe8ea2a8de499a3bb610f78021eb373e599 (RPi2)e1fc7a5ed315e95439382f9df89630006c3d62da551dcdc7fac2a404180d4216 (RPi4)text:# uname -a
Linux rpi512 5.4.51 #1 Sat Jul 18 00:02:21 BST 2020 armv6l GNU/Linux
# vcgencmd version
Jul 17 2020 11:05:44
Copyright © 2012 Broadcom
version 21a15cb094f41c7506ad65d2cb9b29c550693057 (clean) (release) (start_x)
# lsb_release
LibreELEC (Milhouse): devel-20200718000045-#0717-g776b589 [Build #0717]
# Kodi version
Starting Kodi (19.0-ALPHA1 (18.9.701) Git:7b97a46). Platform: Linux ARM 32-bit
Quote:Notice: RPi2 users may need to raisegpu_memhigher than 320 if experiencing HEVC playback issues (CMMALPoolerrors, crashes).
It appears the latest kodi with ffmpeg-4.3 is using significantly more GPU memory than previous kodi/ffmpeg-4.2 versions.
Higher resolution artwork may be a contributing factor, as GPU memory is temporarily used when displaying artwork which then isn't available during playback.
I have the following higher-than-standard resolution artwork configured inadvancedsettings.xml:
and some 720p and 1080p HEVC playback fails withtext:
<fanartres>1080</fanartres>
<imageres>720</imageres>
gpu_mem=320and this latest kodi/ffmpeg-4.3 build (works fine with #0626).
As a (hopefully) temporary fix,gpu_mem=380is working OK with this new build (I did trygpu_mem=360but even that isn't enough in every case).
The issue is being investigated (need to determine if this is a kodi, ffmpeg-4.3, or HEVC issue - or some combination).
(2020-07-18, 14:49)graysky Wrote: @Milhouse - I updated on my RPi4 to 0717 from the stock image, the update and reboot was successful, I briefly saw the "rainbow" splash screen but then I get no output on my monitor although it detects an output signal. I can connect via ssh. Log such as it is, here.dmesg and contents of config.txt / cmdline.txt would be useful.
(2020-07-18, 02:40)Milhouse Wrote: New LibreELEC.tv Matrix build #0717: RPi / RPi2 / RPi4
(2020-07-18, 16:34)popcornmix Wrote:(2020-07-18, 14:49)graysky Wrote: @Milhouse - I updated on my RPi4 to 0717 from the stock image, the update and reboot was successful, I briefly saw the "rainbow" splash screen but then I get no output on my monitor although it detects an output signal. I can connect via ssh. Log such as it is, here.dmesg and contents of config.txt / cmdline.txt would be useful.
(2020-07-18, 16:34)popcornmix Wrote:I have the same problem. Started with a 9.2.3 and upgraded to latest.(2020-07-18, 14:49)graysky Wrote: @Milhouse - I updated on my RPi4 to 0717 from the stock image, the update and reboot was successful, I briefly saw the "rainbow" splash screen but then I get no output on my monitor although it detects an output signal. I can connect via ssh. Log such as it is, here.dmesg and contents of config.txt / cmdline.txt would be useful.
(2020-07-18, 17:06)graysky Wrote: dmesg: https://gist.github.com/graysky2/194a9d7...97ed37e07b
config.txt: https://gist.github.com/graysky2/bc8a0c9...7d0e584d6d
cmdline.txt: https://gist.github.com/graysky2/b6610da...d6d5ff2801
(2020-07-18, 21:16)popcornmix Wrote:There is no video output of the boot sequence, what do you think is causing it?(2020-07-18, 17:06)graysky Wrote: dmesg: https://gist.github.com/graysky2/194a9d7...97ed37e07b
config.txt: https://gist.github.com/graysky2/bc8a0c9...7d0e584d6d
cmdline.txt: https://gist.github.com/graysky2/b6610da...d6d5ff2801
gpu_mem=360 is unwanted (and harmful) on Pi4.
You shouldn't need to set it (video decode buffers and 3d textures come from cma).
If it still fails to boot try renaming /storage/.kodi and restarting in case something in there is unsuitable.
(2020-07-18, 21:16)popcornmix Wrote:(2020-07-18, 17:06)graysky Wrote: dmesg: https://gist.github.com/graysky2/194a9d7...97ed37e07b
config.txt: https://gist.github.com/graysky2/bc8a0c9...7d0e584d6d
cmdline.txt: https://gist.github.com/graysky2/b6610da...d6d5ff2801
gpu_mem=360 is unwanted (and harmful) on Pi4.
You shouldn't need to set it (video decode buffers and 3d textures come from cma).
If it still fails to boot try renaming /storage/.kodi and restarting in case something in there is unsuitable.
config.txt was supplied by the tarball or edited by something in LE. I did not edit it. I commented out the gpu_mem=320 lineconfig.txt as well as renamed /storage/.kodi but I am getting the same result. If it helps diagnose, the green light on the RPi4 is blinking rapidly when there is no video output. Happy to try something else.
(2020-07-18, 21:33)graysky Wrote:(2020-07-18, 21:16)popcornmix Wrote:(2020-07-18, 17:06)graysky Wrote: dmesg: https://gist.github.com/graysky2/194a9d7...97ed37e07b
config.txt: https://gist.github.com/graysky2/bc8a0c9...7d0e584d6d
cmdline.txt: https://gist.github.com/graysky2/b6610da...d6d5ff2801
gpu_mem=360 is unwanted (and harmful) on Pi4.
You shouldn't need to set it (video decode buffers and 3d textures come from cma).
If it still fails to boot try renaming /storage/.kodi and restarting in case something in there is unsuitable.
For the record,config.txtwas supplied by the tarball or edited by something in LE. I did not edit it. I commented out thefromCode:gpu_mem=320 lineconfig.txtas well as renamed/storage/.kodibut I am getting the same result. If it helps diagnose, the green light on the RPi4 is blinking rapidly when there is no video output. Happy to try something else.
To recap:
1) Boot, rainbow screen is shown but nothing else
2) Blank screen but system is up and connectable with ssh
Here is a debug log: https://gist.github.com/graysky2/520543e...06ff834685
Quote:2020-03-06 12:38:57.279 T:753 INFO <general>: CAESinkALSA - Unable to open device "default" for playback
2020-03-06 12:38:57.296 T:753 INFO <general>: CAESinkALSA - Unable to open device "sysdefault" for playback
2020-03-06 12:38:57.297 T:753 INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi" for playback
2020-03-06 12:38:57.298 T:753 INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi,DEV=0" for playback
2020-03-06 12:38:57.298 T:753 INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi1" for playback
2020-03-06 12:38:57.300 T:753 INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi1,DEV=0" for playback
(2020-07-18, 16:40)popcornmix Wrote:#0717 Rpi4:(2020-07-18, 02:40)Milhouse Wrote: New LibreELEC.tv Matrix build #0717: RPi / RPi2 / RPi4
On Pi4 this build has an updated hdmi audio driver.
It should support HBR audio (DTS-HD, TrueHD including atmos).
Multichannel PCM is also improved and should map channels to speakers correctly in more circumstances.
If you have a multichannel setup then test with passthrough enabled and disabled and report if audio comes form correct speakers.
