Posts by HiassofT

  • LE on SD Card vs USB

    It'll depend a lot on the exact model you use, most of the 32-128GB USB sticks I have are a lot slower than the 32/64GB SD cards I use (Sandisk Extreme Pro), especially when it comes to writes and random access.

    As a rule of thumb: if the manufacturer didn's spec write speed it'll be slow. For SD cards also make sure you get one with A1 or A2 application class and, as always, stay away from no-name brands.

    You'd need to look for USB SSDs (not USB sticks / thumb drives), they should be fast - but they are quite expensive.

    so long,

    Hias

  • PINN releases

    Take your time, we're not in a rush.

    I had planned to rework our noobs/pinn build a bit in the next weeks or so (as time permits) and it'd be nice to have that finished when we ship LE12.0.0. As we haven't started with LE12 betas yet I'd guess that won't be before March, so there's plenty of time (and it's also no huge deal if we do it some time later, then you/we can just do a manual os_list update).

    so long,

    Hias

  • PINN releases

    Thanks for adding/updating the os list!

    I think moving to sha checksums of the downloaded tarballs etc is a good idea, then we can drop the manual md5 sum creation and checks in partition_setup.sh.

    Do you have some pointers how to use/add the pinn sha512 checksums?

    In general I'm very open to all improvements and suggestions how to simplify stuff, just speak up :)

    so long,

    Hias

  • ext HDs not mounted after 11.01 update

    Please test with the latest LibreELEC 12 nightly builds, I recently noticed and fixed an issue which may have led to filesystem writes (updating last file/directory access timestamps) even if you only read from NTFS partitions

    NTFS filesystems are mounted with incorrect options · Issue #8474 · LibreELEC/LibreELEC.tv
    Automounting NTFS drives via udevil should mount NTFS filesystems with nosuid,noexec,nodev,noatime,fmask=0133,uid=0,gid=0 according to udevil.conf but on LE12…
    github.com

    In addition to that you can now configure LE to mount NTFS partitions read-only by default which should further help with accidential filesystem corruption in case of unclean shutdown, powerloss etc. If you want to change files eg via SMB share or shell just remount it read-write, eg via mount -o remount,rw /var/media/YOUR-NTFS-DRIVE and remount it again read-only after changing stuff via mount -o remount,ro ...:

    Copy /etc/udevil/udevil.conf to /storage/.config/udevil.conf and change the default_options_ntfs line of /storage/.config/udevil.conf to contain the ro option. i.e. add , ro at the end of it:

    Code
    LibreELEC:~ # cp /etc/udevil/udevil.conf /storage/.config/udevil.conf
LibreELEC:~ # nano /storage/.config/udevil.conf
    Code
    ...
default_options_ntfs      = nosuid, noexec, nodev, noatime, fmask=0133, uid=$UID, gid=$GID, ro
...

    so long,

    Hias

  • PINN releases

    procount currently we only have the latest version available, via https://releases.libreelec.tv/noobs/..., but that does seem to cause issues with the mirrors so we are discussing if we should provide versioned directories.

    9.2.6 was our last release for RPi1, RPi2 (also used for RPi3), RPi4 and RPi5 releases are at 11.0.5 now - which was just released today and the mirrors don't seem to have picked up the new noobs files yet.

    eg https://ftp.halifax.rwth-aachen.de/libreelec/noobs/ doesn't have RPi5 yet but it's available directly from our release server - eg https://releases.libreelec.tv/noobs/LibreELEC_RPi5/os.json, RPi2 is at 11.0.4 (the previous release) and RPi4 at 11.0.3 (I broke RPi4 and RPi5 noobs builds in 11.0.4 so that was our previous RPi4 noobs release as well).

    The easiest solution would be if you could pull a json with the latest noobs image metadata from our server, like RPi imager does - then we can automatically update it when we do a new release.

    Regarding image metadata: do you have some info which settings should be in the os/os_list.json files`? Currently we fill in lots of very deprecated fields like supported_hex_revisions which IIRC got dropped ages ago and may be missing some other now required fields.

    so long,

    Hias

  • Anything better than a Pi4 currently?

    Quote from yamcenutzer

    All these cases that are not FLUSH with hdmi connector will cause problems.

    This is indeed a problem with a lot of the cases as that won't allow you to full insert the HDMI plug into the socket, causing all sorts of (intermittent or also permanent) contact problems.

    Fortunately though there's an easy workaround: take out your X-Acto knife and trim off 0.5-1mm of the plastic on the front of the HDMI plug. BTDT a couple of times and it fixed my issues.

    Issues with bad solder joints of HDMI adapter PCB boards, like inside the Argon cases, are a lot more troublesome to solve though.

    so long,

    Hias

  • Raspberry Pi Tools - GPIOZERO - LE12 Issues

    Mario77 thanks, I could finally reproduce the issue:

    The underlying lggpio library tries to create a pipe in the current working directory - when starting the python script via a systemd service or autostart.sh that will be the root directory which is read-only in LE so everything goes south. Running the script from the console will also fail if you "cd /" before...

    I'd say this is a major design flaw in gpiozero / lg-gpio (it shouldn't write anything to the current directory in the first place) but fortunately there's an easy workaround:

    Change the working directory to a directory where you have write permissions - eg /tmp

    In the service file just add a WorkingDirectory setting, in autostart do a cd /tmp before starting the python script.

    so long,

    Hias

  • Raspberry 5 cooling fan control

    The fan has a 4-pin connector (5V, GND, PWM, RPM/pulse sense input) - like standard PC fans.

    DT params to adjust the fan temp/speed curve have just been added to the RPi kernel, I'll update the kernel in LE soon so it'll be available in nightlies - hopefully in the next few days.

    so long,

    Hias

  • edid firmware load attempted before firmware overlay

    You can find some - rather outdated, somewhat incorrect and PC specific - background info in the wiki here: https://wiki.libreelec.tv/configuration/edid

    Long story short: remove all the stuff you manually added, connect the RPi to your TV and reboot, then run getedid create via ssh and you are done.

    That will dump the edid of your TV to .config/firmware/edid, create the necessary edid.cpio initrd so that the edid is also available in very early boot stage - before the .config/firmware overlay is enabled and everything will be fine - no need to manually fiddle around with duming edids, adjusting config.txt and cmdline.txt etc

    so long,

    Hias

  • Anything better than a Pi4 currently?

    wyup refresh rate switching is essential if you want (micro-)stutter-free, smooth video playback. Cinema stuff/Blu-Rays are usually at 23.97/24 Hz, TV broadcasts at 50 or 59.94 Hz, PC videos often at 60Hz - if your video output mode doesn't match the video's framerate it'll look juddery.

    Regarding DV: UHD Blu-Rays have a mandatory HDR10 base layer, so DV on these disc is an additional layer on top and RPi4/5 will output the HDR10 layer just fine - tested that here with 4k (DV) Blu-Ray rips I did on my own with makemkv.

    Streaming services with "pure DV content" (without the HDR10 base layer) is another thing, and RPi4/5 certainly wouldn't have the grunt to process that - direct-to-plane rendering works fine for 4kp60 but GL/EGL rendering doesn't - it's too slow, even without shaders having to do tonemapping (RPi's graphics "chip" isn't anywhere near an Nvidia RTX).

    so long,

    Hias