Posts by chewitt

  • RPi4 testbuild with HDR support

    Set desktop to 1080p, it will be much faster to navigate in the Kodi GUI and the TV will do a better job of upscaling 1080p to the TV panel native 4K resolution than Kodi can achieve. Use the whitelist so Kodi switches to 4K when needed for playback.

  • Frequency of the NTP queries

    ^ running "journalctl | grep ntp" on an idle Amlogic device in the network here shows a check every 17 mins; more frequent than I would have expected but also nothing too extreme. It's not 20/minute though. Can you corroborate that frequency with journal entries?

  • flash an old 8726 MX box tv with sdcard and USB-SD creator on Mac OS

    Quote from derlinus

    Hey Chewitt, no chance to get my trusty Wetek play1 back on a supported version ?

    Nope. It's a struggle to get people to work on mainline Linux support for the latest Amlogic chips, let alone a chip from 2014 that was slow at the time it was released. There is nobody doing any work on mainline Linux Meson 6 support, so this unlikely to change, so LE 9.0 is (and will remain) the last release for 8726MX devices like WP1.

  • trouble with eMMC on rock Pi4

    LE runs 64-bit kernel and 32-bit userspace (so widevine DRM libs work), so the =arm in the build command is correct, and the aarch64 kernel conf is also correct. The original problem is probably solved by using "boot=LABEL=LIBREELEC disk=LABEL=STORAGE" in extlinux.conf instead of the GUIDs; assuming LIBREELEC/STORAGE are the partition labels.

  • Nightbuild on Mecool KIII Pro

    Someone needs to write a V4L2 demux driver before any work can be done on supporting internal DVB cards (and then there's reworking the demod driver, and the pile of individual tuner drivers). I'm not expecting that work to happen anytime soon.

  • Pi4, hardware acceleration, fast forward freezes

    LE 9.2 reached a point where it worked for the majority of use-cases, and then the focus moved away from legacy MMAL/OMX decoding onto the all-new GBM/V4L2 codebase. The older methods still have rough edges that will never be fixed, so if you have problem media I'd suggest you retest under LE10, because bugs/issues found there are of interest to the developers.

  • LibreELEC (Matrix) 10.0 BETA2

    Quote from eisenb11

    Will in-place upgrades be allowed on the final release? Understand it's not recommended, but I have a massive DB and would rather not rescan everything again.

    No, because add-ons frequently cause problems in any Kodi major version upgrade and the Py2 > Py3 move from K18 > K19 throws up some extra challenges. Nothing impossible for knowledgeable users to figure out, but the other 98% of our userbase will panic and use lots of bad words. We aren't going to stop people from doing it, but the warnings will stay and if people ignore them; users should expect low sympathy when things go wrong.

    That said. I would stop Kodi, move /storage/.kodi to /storage/.kodi-old, download the LE10 image file to /storage/.update/ and then reboot. It will upgrade to an empty Kodi install which sidesteps 99% the issues with outdated Py2 add-ons. Then stop Kodi, and move /storage/.kodi-old/userdata to /storage/.kodi/userdata and restart again. DB files should now auto-upgrade and you have all the existing settings etc. for add-ons (once you reinstall them) and thumb caches. Kodi settings may need to be tweaked if stuff changed. Always take a backup and move it off-box first so if something does go tits-up you can always reinstall LE-old and recover.

  • Yet another SMBv2 issue

    Users frequently try to avoid setting a credential on shares believing "no passwords" to be easier. It is not, and how different OS with different versions of SMB/CIFS software will work gets a bit random. Set a credential and then configure the things that need to access the share to use it. This is how the software has been designed to work. This is how you get a consistent experience over all devices.

  • ReSize LE Image

    Users are frequently obsessed with "backing up the USB stick" using disk imaging tools when what they should be doing is "backing up the content on the USB stick" which is a fraction of the data size (as you noticed). LE provides a backup function in the settings add-on that does that. There is also a Kodi Backup add-on in the Kodi repo that does it too.

  • Make LibreElec 9.2 with RTL8125 driver

    Code
    [    3.211046] r8125: version magic '5.4.0-72-generic SMP mod_unload modversions ' should be '5.1.16 SMP mod_unload'

    ^ the r8125 kernel driver is compiled for Linux 5.4, and:

    Code
    [    0.000000] Linux version 5.1.16 (msv@vm-server) (gcc version 8.3.0 (GCC)) #1 SMP Fri Apr 23 09:46:06 UTC 2021

    ^ LE 9.2 uses Linux 5.1, so the module is not compatible. And:

    Code
    ls: /usr/lib/firmware/rtl_nic: No such file or directory

    ^ means even if you built the right kernel module, you did not put the firmware in the correct directory (because that's the correct one).

    I wasn't able to check the contents of http://80.251.144.40/update/RTL8125B-9.005.01.tar.gz as the file didn't download for me, but my guess is the package contains a pre-built module for Linux 5.4 in addition to sources, and even if you do build the module from sources in the LE build system, the script is copying the wrong .ko into the image; giving you the bad magic message. I would download the sources from the awesometic Git repo as this doesn't contain pre-built modules.

    On the firmware side; again I couldn't download the file to check contents but you're not moving the file to the correct location. I would not call ./install scripts writen for other build systems. Just do simple "cp" to the correct destination. Look at other packages and the format and $VARIABLE names to use for source/destination are simple to follow.