Posts by ieure

    Thanks. I enabled persistent logs, and it stayed up a few days. Found it crashed again this morning. Nothing interesting in the logs.

    Here's when it last booted:

    Code
    Mar 28 09:48:46 LibreELEC kernel: Linux version 6.16.12 (docker@c7f39856707b) (x86_64-libreelec-linux-gnu-gcc-13.2.0 (GCC) 13.2.0, GNU ld (GNU Binutils) 2.41) #1 SMP Sat Nov  1 07:12:40 UTC 2025

    And the last message in the logs is:

    Code
    Mar 29 15:14:21 baryon connmand[537]: ntp: adjust (slew): -0.000993 sec


    Last seven hours of logs are NTP messages and this temp file cleanup:

    Code
    Mar 29 10:04:58 baryon systemd[1]: Starting systemd-tmpfiles-clean.service...
    Mar 29 10:04:58 baryon systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
    Mar 29 10:04:58 baryon systemd[1]: Finished systemd-tmpfiles-clean.service.


    These four messages are the only ones that look like something that might be off:

    Code
    Mar 28 15:31:01 baryon kernel: perf: interrupt took too long (2525 > 2500), lowering kernel.perf_event_max_sample_rate to 79200
    Mar 28 19:07:47 baryon kernel: perf: interrupt took too long (3162 > 3156), lowering kernel.perf_event_max_sample_rate to 63000
    Mar 29 00:35:16 baryon kernel: perf: interrupt took too long (3972 > 3952), lowering kernel.perf_event_max_sample_rate to 50100
    Mar 29 08:44:23 baryon kernel: perf: interrupt took too long (4974 > 4965), lowering kernel.perf_event_max_sample_rate to 40200


    From what I see, these typically happen when the CPU frequency scales up or down, which doesn't sound like a problem.

    Any other ideas?

    I was unhappy with the performance of my Raspberry Pi 4 running LibreELEC, so I switched my HTPC to a ThinkCentre M720q. While the performance is much improved, it will crash overnight if left alone.

    The setup is: Computer (with USB CEC dongle) -> Marantz NR1604 receiver -> Sharp Aquos 4T-C70BK2UD TV. LibreELEC 12.2.1.

    Symptoms: No video output, no response to the keyboard, not connected to the network (it's on WiFi). When I turn the TV on, it calls the input "CEC Adapter" instead of Kodi.

    The crash seems to be time-based. I typically watch stuff in the evenings, if I turn it off around 9pm, then try turning it on the next day around 6-7pm, it will always be non-responsive. As an experiment, I turned the TV on the next morning; it was fine.

    I left a SSH session logged into it and tailing the logs the last time it crashed, but there was nothing helpful. It seems like it was only application logs, is there some way to get kernel logs out of this thing?

    Did you backup the RPi4 and restore to the ThinkCentre? or make a clean install on the ThinkCentre?

    I installed LibreELEC on the ThinkCentre, then copied the Kodi configuration from the Pi.

    The "rPI's poor WiFi" it's easy to handle with a USB-Wifi adapter, or better with a wifi-ethernet adapter (if you have no chance to use wired network there). The "tendency to hang and need a reboot" could be related to the wifi issue... So, if you still have the RPi4 and could try with wired network or have a cheap USB-wifi, it worth to try it... I'm using few RPi-LE, and with "normal" use (without too much "fancy" addons), it's very stable. Even the one with wifi connection (not the "standard built in wifi"), it's stable.

    I have other gripes about the pi, like its lack of support for VP9. WiFi and locking up seem like different/unrelated problems to me. The WiFi will sometimes drop and not reconnect, but the system doesn't lock up. Other times, it's completely unresponsive and has to be rebooted.

    Had similar issues with the 3B and 4.

    I switched back to the Pi4, but I don't like it.

    You could try to check the sound options in the BIOS. Maybe it's something to set the default sound output to HDMI. Or disable the built in speaker.

    Already checked, there's nothing like that. It doesn't really know about things at the level of what's connected to the outputs. If I disable audio in the BIOS, I can only select Bluetooth as the audio output in Kodi -- the built-in audio controller handles HDMI audio as well as the speaker/headphone.

    If I disable the speaker, but leave the controller enabled, it boots up to no audio at all. It still shows the output as HDMI, and switching to another output / back to HDMI restores audio.

    Another thing, even if these developed for continuous use, it could be benefic to be rebooted time to time. For this I'm using a cron job, to reboot the LE every day at early morning (like am 3:00).

    Since the problem occurs only when the system is re/booted, this would exacerbate the issue.

    I have another issue with the ThinkCentre, which is that it freezes whenever I turn my TV off. Sigh...

    Hi folks, long-time user, first-time caller. I recently replaced a Raspberry Pi 4 which was running Kodi with a ThinkCentre; I got tired of the rPI's poor WiFi and tendency to hang and need a reboot.

    The new setup isn't working as well as I hoped. Every time I reboot the machine, it plays audio through the (terrible) internal speaker, instead of over HDMI into my receiver. if I go into settings->system settings->audio, the audio output device is set correctly ("ALSA: HDA INTEL PCH, MJI MARANTZ-AVR ON HDMI #0"), though it isn't actually used. Fixing this requires changing the output device to something else, then back to the receiver, after every reboot.

    Seems like a bug to me, but is this known / is there some kind of workaround?


    Using LibreELEC 12.2.1 generic.x86_64, hardware is a ThinkCentre M720q (i5-8400T w/ 8gb RAM).