Posts by ghtester

Are you sure argonremote.zip was created for LibreELEC? Most likely it supports only Python 2.x but LE 10 is already using Python 3 which is not backward compatible. So you should ask vendor for updating the installation scripts to be working with Python 3.

I would say it will need some manual configuration but it will work for sure on LE 10.

Look here: Kodi, Harmony, and Raspberry PI 4 with IR sensor newb guide

Focus on Setup points 10. - 11. Edit the key mapping file in accordance with your Remote Control.

Understood... You are welcome.

Edit - just FYI - 20211012: http://ix.io/3BA2

I have upgraded LE 11 Nightly from 20211005 to 20211007 but Kodi could not start afterwards. Then I tried to reinstall (by putting the image file to .update folder & reboot) with LE 11 Nightly 20211006 with the same result. Even reinstalling with (previously working) 20211005 did not fix the issue. Yestarday I tried to reinstall with 20211010, Kodi also does not start. After several attempts to start Kodi the LE reboots in Safe mode.

Does anybody know how could I easily make it working again please (hopefully I won't need to revert to a bit older LE release & restore configuration from backup)?

http://ix.io/3Bp4

http://ix.io/3BpJ

As there's no HDMI CEC standard in fact and usually it's a nightmare to make it working stable & reliably, I would recommend to configure IR Remote Control on LibreELEC to be independent of your TV.

Look here for more information (you don't need Harmony, any IR RC should be suitable, even the same you are using for your TV - just configure the key mapping accordingly).

Thread

Kodi, Harmony, and Raspberry PI 4 with IR sensor newb guide

Verified working with 10.0.1

Introduction

After 6 years of using cheap boxes I decided to explore other hardware options. I was shocked at the price of Shields and some higher end boxes based on Amlogic S922X chips. After some pondering I ended up getting a Raspberry Pi 4 for it's price to power ratio. I realize that it may not be better or even equivalent to the aforementioned solutions, but it certainly beats my limping 905X based boxes.

Using a RPI4 is definitely not for the plug and play…

Skripo

January 28, 2021 at 1:47 PM

My LE 11 Nightly crashed after upgrade from 20211005 to 20211007 - Kodi was not able to start, then LE rebooted to recovery mode. Reinstall to 20211005 did not help, Kodi did not start anymore so some files were damaged. Did not have time to analyze the issue / recover from earlier backup yet.

Edit - just tried upgrading to LE Nightly 20211010 but Kodi does not start on my RPi 4B / 2GB.

http://ix.io/3Bp4

http://ix.io/3BpJ

Edit2 - as it is a bit off-topic here, I am going to create another thread.

Quote from mglae

The nightmare is that you do accept OOM situations.

I know, you are right but it's only temporary...

Quote from mglae

For research reasons a core dump is generated by default if possible. This can be disabled by

Code echo 0 >/proc/sys/vm/oom_dump_tasks

Great, thanks a lot! That's exactly what I needed to know.

Quote from CvH

that is basically too much

try 2500/800, that should work more reliable

Thank you, I have already reduced those values a bit and started monitoring free RAM online by script. It looks that latest LE releases are a slightly bit more hungry regarding to RAM as I did not have OOM issues with the mentioned settings couple weeks ago.

I believe the thread can be marked as Resolved.

Thank you for feedback / advice.

Yes I can try to decrease a Timeshift Maximum RAM size parameter a bit (currently 3090 MB on RPi 4B/4GB, running Tvheadend 4.2 and 1100 MB on RPi 4B/2GB).

But why the hell the LE is now freezing and generates a huge disk / SD card activity for several minutes when OOM killer is activated?!?

It did not happen in older LE releases (if OOM killer terminated Tvheadend, it was restarted immediately, the Timeshift data were lost but LE was not completely hanged for long time).

So it looks this behaviour was started on in some recent kernel version and it's a nightmare (and also not very good for SD card if there are writes).

Another freeze encountered on RPi 4B / 4G, running LE 11 Nightly 20211002.

As the issue happens too often and it's very annoying, I am afraid I'll have to revert to some earlier LE version as the stability is one of the most important features to me...

If someone have an idea how to prevent LE from freezing even though OOM killer is activated (like before), please let me know. Perhaps I should uncomment the Storage=auto option in /etc/systemd/journald.conf or set it to volatile?

http://ix.io/3AKh

Please note RPi 4B is still a relatively new kind of HW and it always takes some time to be fully adopted by developers community.

There's a lot of work needs to be done on (a new) drivers and it is still in progress.

Keep in mind that the LE community is based on volunteers who develop this software in their spare time and without claim to reward. And although the LE 10 is still not perfect, they do a great job here.

There are many fundamental changes between versions 9 and 10, which is why this transitional step is so challenging, but these changes will accelerate and facilitate the future development of LE. So we (LE users) should be grateful and still a little patient...

Thanks for the reply / advice but the timeshift to RAM is a basic functionality which I can't 'live' without.

It looks that latest freeze on RPi 4B / 4G happened when there're still a plenty of free RAM and there was no obvious reason for OOM killer to be activated (I know such cases were reported on earlier - 32 bit - kernel and should be already fixed now).

But I wanted to point out that now it's a worse case (than earlier) due to several minutes complete freeze after OOM event.

Repeating issue on LE Nightly 20210930.

Also encountered on another RPi 4B / 4G, running LE Nightly 20210928.

It's a very annoying behaviour as it takes several minutes until LE returns to operation and there are intensive (perhaps write) operations with storage. It looks it appears more likely when the TV channel with high bitrate is played.

The same issue after upgrading to LE 11 Nightly 20210928 with Kodi 20.0-ALPHA1 (19.90.101).

I am not able to point out what's the difference but affected channels have no Teletext stream and Kodi with Tvheadend 43 can't use DVB subtitles in this case to display them online (despite it's detected that subtitles are there as they can be turned on/off and they are also recorded properly).

Kodi 20 .0-ALPHA1 (19.90.101) is already released in LE 11 Nightly 20210927, unfortunately this issue still persists.

Observed again today on fresh LE Nightly 20210925.

http://ix.io/3A40

The same issue after upgrading Tvheadend service 4.3 (Alpha) to 10.80.0.102 package (4.3-1979). Hopefully the incompatibility will be fixed in some further Kodi release.

BTW. after upgrade to LE 11 Nightly 20210918 another kind of OOM happened.

http://ix.io/3znU

I have experienced several times a strange issue on current LE 11 Nightlies, installed on RPi 4B / 2GB at external HDD, connected through USB/SATA adapter. TVheadend server 4.3 + TVheadend client used.

It's a more or less random freeze of LE (did not even respond to PING, SSH console was frozen as well, no response to remote control and during that time there was an intensive HDD activity) and it looks it's related to TimeShift function which activated oom-killer.

After some time (up to several minutes) the LE usually starts responding again, even the SSH console starts where it stopped responding (without disconnection).

http://ix.io/3zkn

http://ix.io/3zkq

There are also some random issues with audio - sometimes audio does not start when I switch the channel - it's necessary to switch to another channel and back. Sometimes (usually when the live stream has a temporary corruption due to bad signal) it leads to freeze playing (a percentage circle appears on display and stops somewhere between 0-100%). Using TimeShift to move back or forward is usually possible (even though the TimeShift pointer gets confused and does not work correctly until stopped / started or switch to another channel). When I got back, the stream was playng until the problematic point where it freezed again. Unfortunately I don't have a stream recorded as it's not possible to save the TimeShift data (configured to use RAM only).

This is a part of kernel log, showing the several attempts to shift back before the freeze point:

Yeah, it's not a bug, it's a feature...

In another words:

I can confirm BCM2835 is reported in pure original RPi 4B and perhaps (due to reasonable pricing) it's not very likely there are some fake devices ever but who knows...