Posts by HiassofT

  • [RPi4] PRIME breaks system on LE 12.2

    Quote from snoopytfr

    Hello,
    I think the problem occurs with all H264 videos.
    But I downloaded a free video from the internet. Here's the link: https://lafibre.info/videos/test/20…p_h264-main.mp4

    I can confirm that the video is causing my rpi4 to crash with the DRM_PRIME option enabled.

    I'm uploading the full video log with the DRM_PRIME option disabled.

    here is the link : https://paste.libreelec.tv/sharing-midge.log

    Thanks, I tried that sample on my RPi4 and it played fine.

    But I noticed in your log that you have hyperion and drm-capture services installed and they are in a crash loop:

    Code
    Jun 26 10:44:38.189005 TEST-KODI systemd[1]: [email protected]: Scheduled restart job, restart counter is at 1.
Jun 26 10:44:38.224208 TEST-KODI systemd[1]: Started [email protected].
Jun 26 10:44:38.225830 TEST-KODI systemd[1]: [email protected]: Main process exited, code=exited, status=203/EXEC
Jun 26 10:44:38.226180 TEST-KODI systemd[1]: [email protected]: Failed with result 'exit-code'.
Jun 26 10:44:40.103767 TEST-KODI systemd[1]: Started drm-capture.service.
Jun 26 10:44:40.109901 TEST-KODI systemd[1]: drm-capture.service: Main process exited, code=exited, status=203/EXEC
Jun 26 10:44:40.110624 TEST-KODI systemd[1]: drm-capture.service: Failed with result 'exit-code'.

    Please remove both of them and test again with DRMPRIME enabled.

    If that hangs as well, ssh in before playing a video and then try to run "pastekodi" just after kodi became unresponsive.

    so long,

    Hias

  • [RPi4] PRIME breaks system on LE 12.2

    If you can't provide a log from the problematic video then please upload a (short) sample file that exhibits the problem and a debug log from playing that file without DRMPRIME.

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. Generate a log URL (do not post/upload logs to the forum)

    use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

    so long,

    Hias

  • Nightly Builds

    It looks like you picked the generic image instead of the generic-legacy one.

    Running https://test.libreelec.tv/13.0/Generic/G…-25445eb.img.gz here I see a kernel build time of Sat Aug 16 00:55:40 UTC 2025 but your log shows Fri Aug 15 23:00:17 UTC 2025:

    Code
    Aug 17 12:26:04.292047 LibreELEC kernel: Linux version 6.16.0 (ubuntu@a766510b163f) (x86_64-libreelec-linux-gnu-gcc-15.2.0 (GCC) 15.2.0, GNU ld (GNU Binutils) 2.44) #1 SMP Fri Aug 15 23:00:17 UTC 2025

    Missing xorg.service start messages in journal are also a strong indication of wrong image - check /etc/os-release, it should look like this:

    so long,

    Hias

  • Nightly Builds

    Try adding systemd.unit=graphical.target to the end of the APPEND line in /flash/syslinux.cfg. This will prevent kodi from starting (and thus the reboot loop) and get you to a point where you can ssh in and create logs.

    so long,

    Hias

  • Nightly Builds

    First double-check that the rtx3070 still works with your old system using the latest nightly build - the nvidia driver was updated a few days ago so it'd be good to know if that has some play in it.

    To prevent LE from rebooting if kodi doesn't start run touch /storage/.config/safemode.disable - then you can simply ssh in and run pastekodi to create logs.

    so long,

    Hias

  • Nightly Builds

    Quote from palle_c

    Tried latest legacy nightly and it stalls on starting xorg/kodi (ive tried my rtx3070 that works in my z590 system and my new rtx5070 plus ive tried an old gtx1080) also tested to put the 5070 in my old system but that fails because even though latest nightly has the latest nvidia drivers (do you unflag newer nvidia cards when building your images?

    Nvidia drivers are quite a mess.

    The current driver comes with two flavors of kernel modules, the "classic" one which supports a wide range of video cards up to the RTX4000 series, and the new "open" one which supports only very recent cards (IIRC starting with the RTX2000 series or so).

    We can't easily include both modules so we decided to stick to the "classic" kernel module as it supports way more cards - but doesn't support the RTX5000 series (or newer ones in the future).

    tl;dr: it's expected that it LE won't work with your RTX5070 and it's quite unlikely that'll change in the future.

    so long,

    Hias

  • Nightly pi5 high cpu usage on 4k

    small correction to the above post: SDRAM_BANKLOW=3 needs to go into the bootloader / rpi-eeprom config, not into config.txt.

    Run rpi-eeprom-config -e and add SDRAM_BANKLOW=3 to the end of the file, then reboot.

    With this change a 4k H264 file played fine on my RPi5.

    BTW: no need to test older builds.

    so long,

    Hias

  • (RPi4) LibreELEC Nightly Updates broken with RPi4

    We need logs and more info.

    Is just the screen black (and you can still ping/ssh in/.. the system) or does it not boot ad all?

    Are you booting from SD or USB?

    What does the diagnostics screen show you when you boot with your SD/USB boot cards/devices removed?

    I just reconfrmed toady, wrote the linked image to a Sandisk Extreme Pro 32GB SD card and my RPi4 4GB booted fine.

    so long,

    Hias

  • [x86-64] USB HDD always spin down after few minutes

    Quote from myksto

    I could check support pages yes but I tried with 3 different HDD: WD-RED 12TB, SEAGATE BARRACUDA 8TB, HITACHI DESKTAR 3 TB and all of them have the same "problem": when I pause a movie from LibreElec HDD spins down after few minutes.

    These are all internal, not external drives.

    Which enclosure are you using? Check with the manufacturer of the enclosure, very often (and in your case very likely) it'll be the USB-SATA controller in the enclosure that's responsible for the spindown.

    so long,

    Hias

  • [x86-64] USB HDD always spin down after few minutes

    Check the support pages of your drive manufacturer. eg with external WD drives you have to use WD Drive Utilities on Windows to configure the sleep timer.

    I'm have connected a 14TB WD MyBook and a 4TB WD MyPassport here on my RPi5 and both power down after half an hour of inactivity (that's the default sleep timer config of those drives).

    If the drives don't shut down after shutdown check your BIOS settings and see if you can find an option to cut power to the USB ports after shutdown (disabling wake-on-USB might help, too).

    I've also seen some USB hubs to interfere with spindown after shutdown, so if you use one also try with the drive connected directly to your PC.

    so long,

    Hias