Posts by chewitt

Just a comment: That nvidia 7 series GPU will be unsupported in LE 8.0 as we bumped the "legacy" driver version to something newer.

The clue is in the im6/xbian name .. the origins of that Kernel are not OE/LE so there will be a few differences. It's trivial to add the module, but does the device also require firmware?

Add the new package to the dependencies in packages/virtual/network/package.mk

What are you adding?

First let's see if those are bits added back. If not, we can look at patches. Most of the LE team aren't fans of the way codec type info has been dumbed down in Estuary. We understand why it's been done, but.

If you're using LE v7.0.x (Jarvis) it should be identical to OE. If you're using LE 8.0 alpha builds (Krypton) Kodi devs removed the overlay screen that shows codec and other bits of info. It wasn't a popular move and should be partially added back before Kryton release.

The build system works by unpacking sources and patching them before compiling. You can make changes in the unpacked sources, but then you need to create a "diff -Naurp" patch of the changes and add that to the package. Any change to the package folder will trigger a clean rebuild of the package where the sources are nuked and re-unpacked. The patches need to follow packagename-version-sequence-name.patch format; look at the existing set of kernel patches for more info.

Make sure "sync playback to display" is not enabled in Kodi config, because in Krypton this automatically disables passthrough.

the long-name in /var/media should change to the new name when you reboot

There will be a change in LE 7.0.3 to (hopefully) fix this:

kodi: fix for saving sking settings on shutdown · LibreELEC/LibreELEC.tv@0cf94ed · GitHub

LE can use the same .img.gz file for new installations *and* updates to existing installations; same process as .tar

LMGTFY

No current plans for official nightly builds. Alpha builds are every few weeks. Milhouse builds are every few days.

It's never been enabled in official builds, so maybe you've updated/upgraded from a custom build. What hardware are you using?

It can be done by fiddling with routing tables and not-routing traffic to the IP ranges used by Auntie's CDN infrastructure. However, as those IP's are not publicly listed anywhere and some are dynamicly allocated (much more than the website needs to be handled) it's not a simple task. You'd be better off using the LE box for TV and a NAS for whatever dubious function requires a permanent VPN to mask your traffic.

Much depends on the GPU drivers. Windows drivers are generally better written (over a wide range of hardware) and can be fiddled with extensively due to the potentially wider range of use cases on a general purpose OS ~ drivers are shipped with a very safe configuration so a major tweaks are needed to get decent performance for Kodi. Hence such packs/add-ons exist. Linux GPU drivers expose dramatically fewer things to fiddle with but tend to run optimised out of the box. However, that's all moot because there is a choice of Kodi VideoPlayer or Kodi VideoPlayer. If you find a better player you need to suggest it to Kodi developers as their app needs to include support before we can bundle anything. Good luck in making the suggestion .. do you have a crash helmet and earplugs?

User donations fund some VPS for web/forums. The project is happy to receive "no strings" donations and support, but we prefer to be independent of "sponsor" obligations (another lesson learned). It might change in the future, but seems to be working for now

We've been sort of hoping/wishing that GitHub improves the Issues function; they've hinted changes are coming. At the moment it's deliberately turned off as OE experience shows an open tracker attracts a lot of "my wireless doesn't work" noise, and users get confused on where to report issues (we'd prefer the forums, and GitHub requires another registration). If we could restrict GitHub issues to prior contributors or a list of known people it would be ideal. We'd pass on the offer of using your server; the gesture is appreciated but as a result of our OE experience the team mandates that infrastructure and apps must not being dependent on any single person .. once bitten, twice as shy!

Boot from the debian USB, create an MBR partition scheme on the HDD with two partitions labelled BOOT (512MB) and STORAGE (the remainder of the space). Format both as ext4 and install syslinux bootloader to BOOT. Copy the SYSTEM, KERNEL and extlinux.conf files to BOOT; edit extlinux.conf to use BOOT=LABEL=BOOT and DISK=LABEL=STORAGE .. and then reboot. Installing LE manually takes ~10 mins.