Posts by HiassofT

  • 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

  • Video freezing with audio continuing

    I'm no expert in kodi caching details but quite likely it had cached more audio data than video so audio could continue for a while.

    As for the USB drive: might be worth to just ditch the case, there are tons of reports of cheap USB-SATA/NVMe adapters/cases being crap.

    so long,

    Hias

  • Video freezing with audio continuing

    The log shows that your USB (SSD?) drive frequently stops responding and the kernel needs to reset it (after the 30 second timeout elapsed) so no wonders you have issues playing media from it.

    Code
    May 07 07:49:49.601266 RPi4 kernel: usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
May 07 07:49:49.617935 RPi4 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s
May 07 07:49:49.618535 RPi4 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 3b 5d e2 00 01 00 00
May 07 07:49:49.618913 RPi4 kernel: I/O error, dev sda, sector 54222306 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 2

    Insufficient power and broken cables/connectors/... are very often causing such errors, so first try to look into that and connect via a powered USB3 hub.

    Lots of USB devices, especially the cheap no-name ones, have broken USB implementations and sometimes it's possible to work around those with usb-storage.quirks - in your case it's not the rather frequent UAS issue though, it's already using the usb-storage driver.

    Quick search for the USB IDs (idVendor=13fd, idProduct=3456) didn't show up anything useful, searching for "sage 3639S" did neither so not sure what device you actually have.

    so long,

    Hias

  • LE 11.0.1: Unable to mount /storage to a BTRFS partition

    Using a btrfs filesystem as /storage is not supported, the btrfs kernel driver is built as a module (so not available during initramfs stage) and also the initramfs doesn't contain fsck.btrfs - this is only available via the btrfs-progs addon (so in case anything goes wrong you won't be able to fix the issue on LE).

    Stick to ext4 for /storage - you can use btrfs on additional drives though.

    so long,

    Hias