Posts by HiassofT

  • Add support for sony cxd2880 tuner to kernel for official RPI DVB tv hat

    Test with just the TV hat installed, if you have another (audio) hat installed, it'll easy to create a clash (eg on the HAT EEPROM / autodetect pins) and something won't work.

    Bent pins, damaged header or TV hat hardware are all possibilities - and from the linked threads it seemed replacing the HAT solved the issues.

    If you have a RPi2/3/4 you just need to plug in the TV hat, no need for soldering, and it will just work, both on LE and RPiOS.

    so long,

    Hias

  • Add support for sony cxd2880 tuner to kernel for official RPI DVB tv hat

    This sounds a lot like you have a connection issue, a hardware problem or some configuration issue, especially as it's also failing on RPi OS.

    I did a quick test on RPi4 with latest LE12 build and it detected the TV hat just fine - without adding anything to config.txt (it's plug-and-play)

    Code
    LibreELEC:~ # dmesg | grep -i cx
[   14.786410] dvbdev: DVB: registering new adapter (CXD2880)
[   14.834939] cxd2880: cxd2880_attach: CXD2880 driver version: Ver 1.4.1 - 1.0.5
[   14.834957] cxd2880 spi0.0: DVB: registering adapter 0 frontend 0 (Sony CXD2880)...
[   14.835403] cxd2880_spi: cxd2880_spi_probe: Sony CXD2880 has successfully attached.

    so long,

    Hias

  • Are RPi4 12.0 nightly builds recommended for general use?

    LE12 on RPi4 switched from 32bit to 64bit builds, and when trying to update from LE11 to LE12 you'll get an error message shown on screen because the compatibility check failed.

    You can disable the check by creating a .nocompat file in the .update folder

    Code
    touch /storage/.update/.nocompat

    Note though that you could run into issues with addons because of the 32->64bit switch (updating them should fix this).

    Also note that switching back from LE12 to LE11 is not supported.

    so long,

    Hias

  • Are RPi4 12.0 nightly builds recommended for general use?

    I'd recommend using either LE11 official or LE11 nightly builds.

    LE11 updates are very conservative, mainly bugfixes, and LE11 nightlies have a low risk of breaking stuff (but might contain fixes you'd like to have since the latest official release).

    LE12 is OTOH is rather experimental, gets regular major updates which could break stuff and uses kodi Omega alpha versions. Only use that if you are prepared to fix stuff yourself when something breaks.

    so long,

    Hias

  • RPi 4 vs 3200g performance wise

    A good, fast SD card is certainly a key point in getting good performance on RPi (and all other SBCs that use SD as storage). Random write speed is also important, especially if you use PVR which regularly updates the EPG database.

    Personally I use Sandisk Extreme Pro 32GB micro SD cards and I'm quite satisfied with overall performance on RPi.

    Another point is to stay away from "heavy" skins. The stock Estuary skin and eg Confluence are fine but others that use tons of effects, lot of huge textures etc won't be fun on RPi - it's GPU isn't exactly high end.

    If you already have the RPi I'd also recommend to just invest the ~10 bucks for a good SD card, make sure you have a quality HDMI cable (the official RPi one will be fine for 4kp60) and give it a try,

    My recommendation would be to use the latest LE11 nightly build as it contains a couple of important fixes since the latest official LE11 release. Get it from here:

    https://test.libreelec.tv/11.0/RPi/RPi4/

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    Quote from bborredon

    The last nightly build that works is : LibreELEC-RPi2.arm-11.0-nightly-20230201-a144326.img.gz and then, it's KO for LibreELEC-RPi2.arm-11.0-nightly-20230204-7beffea.img.gz. I see there is a size change between these 2 builds : 126.8M for the first one and 127M for the second.

    add dtoverlay=cma,cma-256 to /flash/config.txt - otherwise devices with 512MB RAM won't boot.

    so long,

    Hias

  • Skipping/Stuttering on SD IPTV with 11.0.1

    ApexDE we got a first fix from jc, could you please give this build a try?

    https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.arm-11.0-devel-20230604194334-43f444f.tar

    Your sample played fine with this build but please keep an eye on other videos as well and report back if something that worked before got broken (this is tricky code and the fix has the potential to break other previously working stuff).

    so long,

    Hias

  • Possible SSD issues using as a PVR

    In general it's a bad idea to trim on each block free (i.e. using the discard mount option) as that leads to write amplification and will wear out SSDs quickly.

    It's better to regularly run "fstrim -a", typically once a week, via a systemd timer.

    LE doesn't ship fstrim.service/fstrim.timer systemd files but you can easily add them to /storage/.config/systemd/ and then enable it with "systemctl enable fstrim.timer".

    Untested as I don't have any SSDs on my LE devices here, but these should work:

    fstrim.service

    Code
    [Unit]
Description=Discard unused blocks on filesystems

[Service]
Type=oneshot
ExecStart=/usr/sbin/fstrim --all --verbose --quiet-unsupported

    fstrim.timer:

    so long,

    Hias

  • Volume Control Via Remote

    What's the exact model of your remote and receiver?

    IR remotes using the standard MCE (RC6) protocol will give you repeated button presses so you can just hold the button (eg to change volume up/down or to scroll through a list).

    There are lots of other remotes though which are commonly (but somewhat incorrecrtly) referred to as "MCE" remotes which use proprietary protocols and receivers. A very common one is the Gmyle / Ortek / Hama VRC-1100 - and guess what, it only sends repeats with up/down/left/right buttons (and maybe a few others) but not volume up/down.

    So if you have one of these there's not much you can do.

    so long,

    Hias

  • loss of UDP protocol support in MOUNT post Leia?

    NFS over UDP is disabled in LE (like in most other distributions as well), so just use TCP instead.

    See the kernel config for background info why UDP isn't supported anymore:

    linux/Kconfig at master · torvalds/linux
    Linux kernel source tree. Contribute to torvalds/linux development by creating an account on GitHub.
    github.com
    Code
       default y
   help
     Choose Y here to disable the use of NFS over UDP. NFS over UDP
     on modern networks (1Gb+) can lead to data corruption caused by
     fragmentation during high loads.

    so long,

    Hias