Posts by HiassofT

  • HyperHDR suspend not working

    What exactly did you do with the suspend script and what do you mean by "it didn't work"?

    After adding the systemd service file to /storage/.config/system.d you have to adjust it (if you changed the webui port number in hyperhdr) and then use "systemctl enable NAME_OF_THE_SERVICE_FILE" to enable it.

    There are two reasons why I didn't include the suspend script in the addon:

    First of all the addon system doesn't support multiple systemd units/services per addon so only the main one (service.hyperhdr) would ever get enabled automatically.

    Second, the suspend systemd file contains hard-coded port numbers of 8090 which won't work anymore (and could upset any other service running on that port) if you change the port number in the hyperhdr configuration. That's quite a PITA, even if you change it it would get overwritten on every addon upgrade.

    Therefore, just use the manual approach, you only have to do it once after installing and it'll survive addon updates as well.

    PS: I can't help testing / verifying if the suspend systemd service works as I don't have any LE systems that support suspend/resume here.

    so long,

    Hias

  • Slice4s

    Thanks a lot for reporting back, and glad to hear it's working for you, too!

    You can safely ignore (and actually should dtop) the ancient Linux patches, they are no longer needed nowadays.

    The mmc patch dates back long before we switched to reference the flash and system partitions by UUID, when the EMMC/SD card device ordering still mattered - with UUIDs it doesn't matter if the EMMC is /dev/mmc0 or /dev/mmc1.

    The cs4265 patch also predates changes to the upstream cs4265 driver and isn't needed anymore.

    And the alsa card conf was only needed for kodi so it recognises an IEC958/SPDIF capable device to allow AC3/DTS passthrough via Toslink(SPDIF. A few years ago I looked into improving the (incomplete) SPDIF support but realized a lot of important bits were missing in the cs4265 driver to transmit proper channel status information - then gave up and shortly afterwards SPDIF got broken again in the cs4265 driver due to changes in the upstream code. So better use HDMI if you need/want to pass through AC3/DTS/..., receivers with only SPDIF input are also quite rare today.

    so long,

    Hias

  • Slice4s

    Please give this slice-drivers branch a try: https://github.com/HiassofT/slice…/kernel-5.10%2B

    And here's an LE13 branch that pulls in the driver for RPi2 (you'll need to adjust the RPi4 options for your CM4s): https://github.com/HiassofT/LibreELEC.tv/tree/le13-slice

    A few years ago I tried to clean up the slice (soundcard) driver, I dug out the branch again and noticed a couple more fixes are required now and added those today (I also ran into the distorted sound issue).

    The RPi2 LE13 build worked fine on my Slice with CM3 with just dtoverlay=slice added to config.txt (this enables audio, IR and the RTC), analog audio out sounds fine now.

    Note: SPDIF out doesn't work since a change to the cs4265 upstream driver some years ago, I haven't looked at that.

    I also didn't care about the dt-blob.bin files from the slice-firmware repo, using the blobs from old Slice images works fine to get USB/ethernet working - you may need to create your own dt-blob for CM4s.

    so long,

    Hias

  • [RPi] Composite fighting at every turn

    Actually two changes are required, you also need to change cmdline.txt. See the docs in config.txt just before the distroconfig include:

    Code
    # Use distroconfig-composite.txt instead of distroconfig.txt to enable
# composite video output.
# The composite video mode needs to be configured in cmdline.txt:
# For PAL add: video=Composite-1:720x576@50ie
# For NTSC add: video=Composite-1:720x480@60ie

    Note that everything in cmdline.txt must be on a single line, so separate the video=... just with a space from your current content. And don't forget the 'e' at the end of the video mode, otherwise kodi won't be happy.

    so long,

    Hias

  • [RPi5] PCIe to Ethernet not recognised

    The image I provided already includes the Realtek R8169 driver mentioned in the Waveshare docs and according to your log the ethernet adapter was detected just fine as eth1:

    Code
    Sep 03 18:37:19.569160 LibreELEC kernel: r8169 0001:04:00.0: enabling device (0000 -> 0002)
Sep 03 18:37:19.577761 LibreELEC kernel: r8169 0001:04:00.0: can't read MAC address, setting random one
Sep 03 18:37:19.588967 LibreELEC kernel: videodev: Linux video capture interface: v2.00
Sep 03 18:37:19.594613 LibreELEC kernel: r8169 0001:04:00.0 eth1: RTL8168h/8111h, ae:7f:66:a5:82:77, XID 541, IRQ 194
Sep 03 18:37:19.594825 LibreELEC kernel: r8169 0001:04:00.0 eth1: jumbo features [frames: 9194 bytes, tx checksumming: ko]

    So you should have an eth1 interface available (check with "ifconfig eth1"), note though that LE doesn't support multiple network interfaces and you have to configure it manually - you may need to adjust whatever you did to set up you USB ethernet adapter.

    so long,

    Hias

  • [RPi5] Enforcing HDR instead of Dolby Vision

    In case of UHD Blu-Rays it is mandatory that the DV video stream contains a HDR10 core stream - which kodi will pick up and play just fine.

    For streaming content this is not true and a DV video stream contains only DV video - which kodi won't handle as there's no DV support in linux.

    TL;DR: it's expected that your pirated "webdl" file won't play fine if it contains DV.

    so long,

    Hias

  • [RPi4] PRIME breaks system on LE 12.2

    Thanks for the info, I could now reproduce the issue and we'll look into getting that fixed.

    EGL rendering is the culprit, that causes a huge memory leak and when all memory is used up the system comes to a crawl - until eventually the OOM killer kicks in and restarts kodi (that could take a couple of minutes).

    In general I strongly recommend to stick to the default Direct-to-plane rendering method as that has a lot higher performance than EGL (and also supports 10bit / HDR output).

    so long,

    Hias

  • [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