Posts by HiassofT

stalko can you please test with this build https://test.libreelec.tv/12.0/RPi/RPi5/…-a7e7ad8.img.gz and report back if it fixes the issue?

so long,

Hias

The fix https://github.com/LibreELEC/LibreELEC.tv/pull/9253 has just been merged into the LE12 branch and should be available in LE12 nightly builds in the next few days

so long,

Hias

See post #9. Run the following two commands and then change the driver and device settings in the [lircd] section in lines 11 and 12 of the file

cp /etc/lirc/lirc_options.conf /storage/.config/
nano /storage/.config/lirc_options.conf

The default lirc_options.conf looks like this - don't change anything else, especially not the output setting or it won't work

# These are the default options to lircd, if installed as
# /etc/lirc/lirc_options.conf. See the lircd(8) and lircmd(8)
# manpages for info on the different options.
#
# Some tools including mode2 and irw uses values such as
# driver, device, plugindir and loglevel as fallback values
# in not defined elsewhere.

[lircd]
nodaemon        = False
driver          = default
device          = /dev/lirc0
output          = /run/lirc/lircd.socket
pidfile         = /run/lirc/lircd.pid
plugindir       = /usr/lib/lirc/plugins
permission      = 666
allow-simulate  = No
repeat-max      = 600
#effective-user =
#listen         = [address:]port
#connect        = host[:port]
#loglevel       = 6
#release        = true
#release_suffix = _EVUP

#logfile        = ...

[lircmd]
uinput          = False
nodaemon        = False

# modinit is not supported in LibreELEC

# [modinit]
# code = /usr/sbin/modprobe lirc_serial
# code1 = /usr/bin/setfacl -m g:lirc:rw /dev/uinput
# code2 = ...


# [lircd-uinput]
# add-release-events = False
# release-timeout    = 200
# release-suffix     = _EVUP

so long,

Hias

Your lirc_options.conf file looks wrong, eg output should be /run/lirc/lircd.socket not /var/run/lirc/lircd - did you use some other lirc_options.conf file as a base instead of the /etc/lirc/lirc_options.conf from LibreELEC?

As mentioned in post 4 RE: libreElec on X86 with Crestiv Xfi usb 5.1 copy that to .config

cp  /etc/lirc/lirc_options.conf /storage/.config

and then change the driver and device lines in the file, then it should work.

so long,

Hias

Please post the full contents of the lircd.conf and lirc_options.conf files

pastebinit /storage/.config/lircd.conf
pastebinit /storage/.config/lirc_options.conf

so long,

Hias

Please post the config files you added and a kodi debug logfile - enable debug logging in kodi, reboot, press buttons on your remote and then upload the logfile (either with "pastekodi" on the command line or with the upload logfile option in LibreELEC settings)

so long,

Hias

You can install LE 9.2.6 directly with PINN, just choose "LibreELEC_RPi2_926" in the Media tab - LibreELEC_RPi2 is the current 12.0.0 version

Make sure your PINN is up to date - see here https://forums.raspberrypi.com/viewtopic.php?t=142574

I just did a quick test, installed PINN 3.9.2 with rpi-imager (it's in the Misc Utils section) to a separate SD card, booted it on my RPi 3B+, installed LibreELEC_RPi2_926 via PINN and had a working LE 9.2.6 within 2 minutes.

so long,

Hias

In LibreELEC all config files are in /storage/.config

Copy /etc/lirc/lirc_options.conf to /storage/.config and change the driver and device lines

Then create a file /storage/.config/lircd.conf with the remote key config (the stuff that's stored in RM-850.lircd.conf in the tutorial).

Then reboot and hopefully it'll work.

If something went wrong (eg wrong device name - not sure where that hw:551 in the tutorial comes from) check with systemctl status lircd (or journalctl -u lircd) for errors.

Change the files, then restart lircd with systemctl restart lircd, look for errors again.

If no errors show up you can check the button/key mapping with irw /run/lirc/lircd.socket

If that looks fine, reboot and the remote should work in kodi too

so long,

Hias

I haven't used lircd for ages but I think it should still work, just create lircd.conf and lircd_options.conf files in /storage/.config

See also the info in the wiki https://wiki.libreelec.tv/configuration/…es#lirc-support
and eg in this thread How do I configure LIRC with changing lirc_option file?

Note that you no longer need to enable lirc in the settings (as the Wiki states), just creating the files and rebooting will automatically enable it.

As I never used the alsa_usb driver or the soundcard/remote you mentioned I can't help with that though.

so long,

Hias

Yes, I got the summary fine here on RPi4 with the build I linked above.

No idea why you don't get it, maybe the output is too large or taking too long but then I'd expect some systemd message in the journal (systemd sending a SIGKILL if kodi didn't stop within 30 seconds after SIGTERM) which wasn't there.

Honestly no idea why it's not present in your logs.

so long,

Hias

Quote from olze

Not sure about that. Why one-by-one? Do i have to wait after disabling one?

If you want to know which of the addons is causing the issue so you can report it to the addon dev, then yes.

Alternative: do a clean installation without any addons, see if that works. then start addon back the addons one-by-one and see if kodi starts to crash.

As no one else has been experiencing this issue it's really impossible to tell what's going wrong on your system. It literally could be anything, some addon, some kodi setting, maybe something in kodi or something else.

so long,

Hias

There's nothing obvious in the log, it's cut off (probably you forgot to enable persistent logfiles) and still no summary printed - no idea why.

I guess it's time for plan B: try to disable all the addons one-by-one, also your cron script which downloads epg, let kodi run for a while and if it runs out of memory disable the next addon and see try again.

so long,

Hias

This is weird, I just tested here on my RPi4 (with memory limited to 1GB) and after stopping kodi with "systemctl stop kodi" I'm seeing the SUMMARY line in the status output (the exit code / status 23 is normal, that's reported when there was leaked memory).

Can you please post your full journal after stopping kodi?

run "journalctl -b | pastebinit"

so long,

Hias

Ah, damn, the sanitizers aren't compatible with the default RPi4 kernel config.

Could you please test with this RPi4 build?
https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.aarch64-12.0-devel-20240817121729-5f26845.tar

so long,

Hias

First stop kodi (using systemctl stop kodi), then navigate to /storage/.kodi/userdata/Database/ and delete all MyVideosXXX.db / MyMusicXXX.db, ... files with newer versions than the one from LE11 / Kodi Nexus - you may also delete the older database versions and only keep the Nexus ones to save some space.

You can find a list of the database version numbers here: https://kodi.wiki/view/Databases

So keep MyVideos121.db, MyMusic82.db (those are the LE11/Nexus versions), then after the next reboot kodi will migrate those to the newer Kodi Omega versions and you get your state before the LE12 update back.

BTW: It's always a good idea to backup / copy the files somewhere else before permanently deleting them in case you make a mistake

so long,

Hias

How did you format the ext4 drive? By default mkfs.ext4 will reserve 5% of the space for the root user (that can be adjusted with the -m option) - which about matches your observation.

You can check the current setting with eg tune2fs -l /dev/sda1 (look for "Reserved block count" and "Block count") and if needed set it to 0% with eg tune2fs -m 0 /dev/sda1

(replace /dev/sda1 with the correct device node of your drive as shown eg in mount output)

so long,

Hias

You can simply download the tar to the /storage/.update/ folder and reboot - but testing remotely could be tricky if something goes south...

so long,

Hias

Forgot to add: if you test with above builds then it's best to enable "Persistent Logs" in Settings->LibreELEC->System (30 MB size should hopefully be enough) - don't forget to reboot after changing this.

Then you can grab the full sanitizer output, including alloc stacktraces, with journalctl -u kodi -b > your-alloc-info.txt - best do this after each kodi stop and reboot afterwards so each boot contains only one kodi start/stop cycle.

so long,

Hias