Posts by chewitt

  • Work with Libreelec like a PLEX SERVER..

    I store media on a NAS box in the network. The NAS shares files over SMB and has an SQL database so that I can start any LE client device in the network and see the same DB content. It also runs a Plex server because I spend lots of time in Hotels and Plex nicely handles transcode of media to different resolutions or quality levels to suit the sometimes limited bandwidths available. Plex also allows kids to play media from the native Plex app on a moderately-smart TV in their bedroom. The Kodi and Plex DBs are separate (not sync'd) because that's not important to me, but it's possible to use LE/Kodi as a pure player device for Plex using the Plex client add-on. There is also an add-on that syncs the Plex DB to Kodi so you have a native Kodi database but referencing the Plex-stored media.

    It's technically possible to convert an RPi board to be the NAS, but my advice would be "If you want a NAS, get a NAS" as at some point the effort involved and better performance and reliability of a proper NAS outweighs the savings of using an RPi board.

  • Odroid C2 update from CoreELEC to LibreELEC is it possible ?

    Direct updates are not supported. You need to follow a backup > clean install > partial restore process.

    Take a backup of essential things: sources.xml, advancedsettings.xml, add-on settings and DB files from Kodi. Download the latest nightly from https://test.libreelec.tv/11.0/Amlogic/odroid-c2/ then create a new SD card or reimage the emmc module. Then boot, stop Kodi, move the essential things you backed-up to where they need to be. Restart Kodi and start reinstalling add-ons.

  • Unable to install, "no devices", x86-64

    I'm not sure why it's failing when the system was booting from the same SSD before. If the APPEND line in syslinux.cfg (on the SSD) shows boot=LABEL=LIBREELEC or boot=GUID=<long-guid-string> perhaps edit it to use boot=/dev/sda1 disk=/dev/sda2 instead. You can also try booting from an Ubuntu USB and using that to write the LE installer image directly to the SSD, then boot and run from itself (prob. called run from USB or such - it's years since I booted/installed Generic so I forget).

  • Unable to install, "no devices", x86-64

    Code
    cd /storage/.update
wget https://releases.libreelec.tv/LibreELEC-Generic.x86_64-10.0.3.tar
cd /storage
systemctl stop kodi
mv /storage/.kodi /storage/.kodi-old
reboot

    If the current install boots/runs fine check the size of the boot partition. If it is ~230MB it's too small for a direct update to LE10 and you will need to figure out the install issue; hint, if you see the installer it's not a BIOS/EFI issue as it booted the installer. If it is ~512MB size the boot folder is large enough for a direct update. The commands above ^ download the LE 10.0.03 update file to the right place in preparation for a direct update. Then you stop Kodi, move the existing install files out of the way, and reboot to start the update. Once the update completes you will have a clean Kodi instance. You can then stop Kodi, copy essential bits of the old install from /storage/.kodi-old to /storage/.kodi (sources.xml, specific add-on settings, etc.) then restart Kodi to continue with setup. Rinse/repeat until things are as you need them again.

    NB: Instructions saying you need to clean install for LE10 are not quite true. The OS and Kodi update with zero issues, but add-ons can cause major issues due to the Python 2 > Python 3 change. The process above avoids that by moving the old (and potentially problem) Kodi data including add-ons out of the way.

  • Can I change my graphics card without re-installing?

    The "Generic" image should auto-detect the correct GPU, but audio card names will change so you'll need to revisit settings in Kodi to ensure things are selected again. I would not recommend an nVidia card unless your requirements are quite basic. Our mid-term plan is still to kill off the X11 image to focus on GBM and that still means no nVidia support (and under X11 there is no HDR).

  • 24/7 TV shuffler with mini pcs?

    The TVs in the video are old devices without HDMI connections. The config.txt file on the RPi is only being used to force NTSC vs. PAL output on the Composite video output. That kind of modification in config.txt is supported only on RPi boards and only in LE 9.2 and older. In LE10 and up (LE11 is coming soon) video modes are forced with "video=" kernel boot parameters (params).

    On a Raspberry Pi these are set in cmdline.txt, and you would append one of the following:

    video=Composite-1:720x576@50ie <= PAL

    video=Composite-1:720x480@60ie <= NTSC

    Code
    RPi4:~ # cat /flash/cmdline.txt 
boot=UUID=0602-0454 disk=UUID=a7ecf32f-d897-4f8e-b760-03d219e31c88 quiet video=Composite-1:720x480@60ie

    On x86_64 hardware devices you append it to the APPEND line in the syslinux.cfg file in /flash:

    Code
    NUC:~ # cat /flash/syslinux.cfg
DEFAULT linux
PROMPT 0

LABEL linux
 KERNEL /KERNEL
 APPEND boot=LABEL=System disk=LABEL=Storage quiet video=Composite-1:720x480@60ie

    If you are creating something with an HDMI equipped device and you already have video output there is nothing to do - there is no need to force NTSC vs PAL (the concept doesn't exist with HDMI) and you only need to implement the autoexec.py part of the tutorial.