Posts by chewitt

    LE v7.0.x and OE 6.95.x have diverged in how the OS is built (OE's creator decided to rework half of the build-system in the week before releasing his beta) but the end result is largely the same; no major differences.

    I'd like to see us extend the capabilities of the LE settings addon to include more pi config things. The need for overclock settings has died out now that pi2 and pi3 have more RAM and higher clock speeds, but things like codec licenses and some other basics should be possible. @gda is correct stating that these are things you only need to set once in the life of a pi, but as pi devices represent ~65% of our userbase I think we can do more.

    NB: A RasPlex style installer is already being worked on. We've used their code as the base and improved it a little :) .. but this won't help you configure a pi because the installer only downloads the image and writes the SD card. There are not config tools in it.

    FYI, one of the primary reasons we forked from OE was stability. The guy that runs/ran OE felt it was acceptable to add 300+ untested commits (mostly package bumps) to the project codebase 24 hours before releasing a major beta. He did that kind of thing regularly. He did that kind of thing even when we expressly asked (and then begged) him not to. It pissed off a large number of people in and around the project. If OE was stable for individuals like yourself it was the result of luck more than design, because he was gambling with code.

    Your experience is not normal and bad performance is usually the result of bad hardware (e.g. dying SD cards or shitty network devices) or plugins (esp. the less than legal ones out there). As Klojum has said, a Kodi debug log is the best way to start.

    #1: In my experience there is ION, and then there are all the nVidia boards that people call ION that are actually something else. Tell us the actual nVidia GPU number by running "lspci" and we can confirm whether the board is supported or not.

    #2: It is possible to capture the EDID from the TV when it's connected to an edid.bin file and then use a custom xorg.conf that references the edid.bin file to ensure Xorg always thinks the TV is connected. Read: Config EDID nvidia - OpenELEC

    #3: Ignore my colleague Klojum, he's confused; config.txt is a pi thing :)

    The LE/OE build-system is relatively simple to figure out (very logical) and full of "prior art" to crib and learn the process of extending the core OS and creating add-ons from. There have never been nicely written guides or tutorials because creating packages/add-ons requires developer skills, and people with the skills to succeed tend to poke about and ask a few specific questions, while those who do not have the skills (self included, I'm no developer) need to ask for tutorials and guides. Unfortunately, to package an entire Linux distro in two files requires greater up-front complexity in the creation process compared to a more conventional distro, and it raises the entry-bar on tinkering.

    The file you downloaded was in .img.gz format. If Safari (or other browser) does not automatically unzip the file to be in .img format it will still be in .img.gz format and thus when you run a dd command against the .img (not .img.gz) filename the file (correctly) does not exist.

    "gunzip LibreELEC-Generic.x86_64-7.0.0.img.gz"

    NB: Make sure you download and use v7.0.2 as it corrects some occasional errors in the installer.