[HiassofT]

In LE 9.2.4 we reverted the RPi0-3 firmware back to an older version (predating the common firmware change, which caused issues in LE 9.2.3), and as this firmware change affects internal clocking behaviour it could well be that this makes the difference in your case.

so long,

Hias

[abga]

Thanks for the hint. It's not the firmware, because it was the first thing I tried in my investigation, copied over the firmware files from LE 9.2.4 and booted my own system with them, didn't help.
However, I'll keep and use them from now on on my Kodi systems, given the details (issues) you provided.
I didn't try using the LE 9.2.4 kernel, instead I'm using the latest Raspberry official 5.4.51 and the latest userland (/opt/vc) which I git cloned and built something about a week ago.

It bothers me that the LE 9.2.4 Kodi 18.8 links against the generic mesa libs in /usr/lib and not the Raspberry provided ones in /opt/vc. That's if LE 9.2.4 didn't just copy over the libs from /opt/vc into /usr/lib....
Will need to try this out.

Frankly, I'm starting to consider using LE instead of my own compilation (it's becoming a big PITA), it has pretty much what I need now - able to configure a firewall, VPN support & co.
The only thing I'm missing and I might be able to hack, is the use of Kodi as an actual media player/center and not as a simple application, but this is a fundamental design problem with Kodi I already raised in some of my older posts here in the forum.
I mean, what's the point to shutdown a media system? Especially if the system is a Raspberry. You need to unplug/plug back the power to bring it back to life and that's really dumb.
I'm resolving this issue by using lircd - irexec and starting Kodi with a script - also bringing the monitor/TV in suspend mode (turning it off), while the system (Linux) remains permanently running:

Code:

/opt/vc/bin/vcgencmd display_power 1
/usr/bin/kodi
/opt/vc/bin/vcgencmd display_power 0

And there's another issue with the shutdown timer, which is fundamental in any media center. Kodi has it too, but the user needs to be able to shutdown the system in order to have the menu displayed, and that needs special definitions in polkit and we come back to the first issue - why on earth would you want to shutdown a media system - especially a Raspberry.
For resolving this, I'll need to hack (butcher would be more appropriate) Kodi's PowerManager.cpp and set the shutdown validations on true, even if the kodi user doesn't have the ShutDown rights.

These are the main reasons why I'm building my own Kodi. The first lircd - irexec launch method I might be able to implement in LE, not sure about how to fool Kodi that the user - in LE it's root! - doesn't actually have the right to shutdown the system and to exit Kodi instead.

[abga]

OK, so basically LE 9.2.x copies over the userland libs in /usr/lib and that explains why I noticed Kodi 18.8 linking to /usr/lib instead of /opt/vc

Code:

LibreELEC:/ # ls -al /opt/vc/lib
lrwxrwxrwx    1 root     root             8 Jul 29 23:34 /opt/vc/lib -> /usr/lib

And the script installing and moving the libs around:
https://github.com/LibreELEC/LibreELEC.t...package.mk
I have no clue which version is being used ... PKG_VERSION="2b76cfc6f57d4943144b9ceb5b57d3d455d6a8fd" & PKG_SITE="http://www.broadcom.com"

And mesa wasn't touched since 2019:
https://github.com/LibreELEC/LibreELEC.t...package.mk

I'm out of ideas. Will maybe start hackig LE and adapting it to my media center needs

[popcornmix]

And the script installing and moving the libs around:
https://github.com/LibreELEC/LibreELEC.t...package.mk
I have no clue which version is being used ... PKG_VERSION="2b76cfc6f57d4943144b9ceb5b57d3d455d6a8fd" & PKG_SITE="http://www.broadcom.com"

That would be https://github.com/raspberrypi/firmware/...d455d6a8fd

[abga]

And the script installing and moving the libs around:
https://github.com/LibreELEC/LibreELEC.t...package.mk
I have no clue which version is being used ... PKG_VERSION="2b76cfc6f57d4943144b9ceb5b57d3d455d6a8fd" & PKG_SITE="http://www.broadcom.com"

That would be https://github.com/raspberrypi/firmware/...d455d6a8fd

Thanks, I thought it's the userland, bot the actual firmware.

[abga]

Will start a new thread on the LE 2.4.9 replication. Thank you all so far for the inputs & help!

[popcornmix]

I'm resolving this issue by using lircd - irexec and starting Kodi with a script - also bringing the monitor/TV in suspend mode (turning it off), while the system (Linux) remains permanently running:

Code:

/opt/vc/bin/vcgencmd display_power 1
/usr/bin/kodi
/opt/vc/bin/vcgencmd display_power 0

https://github.com/asavah/script.pidisplaypower is alternative way of suspending TV.

[abga]

I'm resolving this issue by using lircd - irexec and starting Kodi with a script - also bringing the monitor/TV in suspend mode (turning it off), while the system (Linux) remains permanently running:

Code:

/opt/vc/bin/vcgencmd display_power 1
/usr/bin/kodi
/opt/vc/bin/vcgencmd display_power 0

https://github.com/asavah/script.pidisplaypower is alternative way of suspending TV.

Thanks! I'm already aware that there are also Kodi screensavers available making use of vcgencmd. Tried some and wasn't happy with the usage. I need a proper shutdown timer that would also stop the playback (exit Kodi's current activity). It would be nice to have an Exit Timer as alternative and the timer menu access location should be in the current playback menu (bottom part - context menu) and not in the Shutdown Button menu. I remember suggesting these in some of my older posts and apparently nobody cared. Well, Kodi is a player application, not a  Media Center, still, I like it very much.