Posts by chewitt

  • Thinking about switching to LibreELEC instead of customing my own Ubuntu KODI but have a few questions.

    5. We don't embed a listing of packages in each image but GitHub - LibreELEC/LibreELEC.tv: Just enough OS for KODI has tagged sources for all our releases.

    6. We use syslinux (extlinux) by default and plymouth light. We provide no choice in our images but it's Linux so there is nothing to stop you from using Grub if you wanted to configure it yourself. You're stuck with plymouth light though as this is embedded into the image files. There are probably posts in here for doing it but there is no formal project documentation.

  • Updating from Kodi 17.3 to 18 on a Nexbox a95x

    Quote from ghtester

    I believe the upgrade from LE 8.0.2a should work to LE 9.2.6 stable but test at your own risk. ;)

    Don't forget to make a backup of your current installation first.

    Then read here: Updating - LibreELEC.wiki

    Use the proper file path to upgrade (file which is appropriate for your device).

    ^ There is no LE 9.2.6 update for Amlogic hardware, we abandoned the Amlogic BSP kernel at LE 9.0 and shifted focus to mainline kernel support. CE have images equivalent-ish to LE 9.2.6 but I believe they have announced their next release will no longer support S905 (GXBB) since the new vendor kernel they are bumping to no longer excludes it. A95X has an upstream device-tree, so you can/should be able to use the AMLGX test images here: Index of / as well. Support is a little rough around the edges, but slowly improving.

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

    LE no longer supports Amlogic 8726MX (Meson6) hardware and even when we did, our support was limited to one specific device. So if booting from the WP1 SD card image didn't work there are no further options to explore with us. There is almost zero modern kernel support for this generation of Amlogic hardware and nobody anywhere working to change that (some efforts at the next generation, Meson8, but not Meson6 = 8276MX).

  • 32-Bit libreELEC (NEED HELP)

    Support for i386 hardware was dropped between OpenELEC v5 and v6 in 2015 and the first LibreELEC release was v7 in 2016. It is probably possible to create a 32-bit Generic image as a large percentage of the build-system is still used with 32-bit ARM devices, but there are no instructions to follow, probably no willing volunteers stepping forwards, and even if you managed to jump through a lot of hoops to get a working image, running it on ageing hardware (10-15 years old?) usually isn't great - a Raspberry Pi Zero is probably better.

  • mpv and btrfs mount

    Quote from atohmdiy

    For a linux's user point of view, it's strange to have no package manager or a clear way to have a shell. I had to use a nightly build because the ethernet of the h2+ wasn't working, except that no problem whatsoever but i have two question. First as you figure it out, how can i install mpv, i don't find it anywhere. I guess it's not in the plugin repositary, so my only hope is to find a .zip package ?

    Another question, my ssd with my data seems to be auto mounted by libreelec, i use btrfs with two option (autodefrag and compress=zstd). How can i make libreelec to mount my ssd with these options ?

    There is no MPV in LE and no package to add (and no package manager) and we don't support alternative players like Desktop oriented distros. It is technically possible to force a local console to exist but the idea is the HTPC is connected to the TV and you're sat at another device with SSH access to the HTPC box. You can put custom udev rules in /storage/.config/udev.rules.d/ that override the embedded rules with different mount options. We are probably not the distro you are looking for.

  • Thinking about switching to LibreELEC instead of customing my own Ubuntu KODI but have a few questions.

    1. LE builds with Alsa and Pulse; the latter is only used for BT audio (streaming to LE from a phone or other BT device) and Alsa is used for Kodi. As pulse is included in the image you can always go fiddle with it to enable pulse output in Kodi .. but sounds like this is not desirable.

    2. It would depend on the capabilities of the enclosures/firmware being used in them. Most drives will power down when not used. Some drives have shitty firmware that needs manual forcing so there's no single answer. If you need to force it with a script in other distros it may need to be forced in LE as well.

    3. No. LE is built to run Kodi only, there is no "Desktop" environment. You also cannot tinker with drivers from within LE itself (there are no build tools) but you can create your own custom LE image with changes using our very simple to learn build-system (on GitHub).

    4. We run a newer <everything> code stack than other distros which sometimes brings improvements (due to newer code) but otherwise no idea.

  • Official LE11 Test Images for Amlogic (Kodi-20)

    CEC is not working at the moment (so I'm told, I never use/test it myself) - kenel maintainers are aware. The process for configuring a remote has changed since legacy kernels; it is now the same as all the other modern kernel devices that we support, see Infra-Red Remotes - LibreELEC.wiki for more info.

    NB: If people share working remote confs for specific boxes that have upstream device-trees I will create (and then upstream) drivers for them to the kernel and then directly enable the IR keymap in the device-tree for better out-of-box experience. If people don't share them .. the OOB experience will remain the same.

  • Milhouse?

    After 8+ years of building nightly images he had enough and resigned from the keyboard. From the occasional comment that's come in he's alive and well, but we're not expecting him to return or resume. Official images (less experimental but still nightly) can be found here: Index of /

  • [unoffical] LE-9.2/9.80-Images for RK3229/RK3228

    Create /storage/.config/system.d/wlanmac.service with ^ this content then enable it, and remove any other .service files and udev rules you have set in the system. The main difference is that I take the interface down before setting the MAC, then bring it up again.