Posts by chewitt

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.

WP/WC alpha builds should start with v7.90.004

The lack of fix is not due to a lack of effort. I'm told that it's not been forgotten, and continues to be invesigated..

AML changes for 23.976 on S805/S905 are not relevant to the AML8726MX SoC in the WP box. It's a different device. It needs a different solution.

LE has a strong "community" focus and is structured as a collective of people with a common interest. Although a number of us regard ourselves as "on the team" none of the people working/collaborating with the project have ever been asked to declare a formal affiliation to the project. Contributors are not asked to pick sides and are free to contribute to either project as they like. Establishing a legal entity for the project in the future may require us to formally distinguish between voting and non-voting members, thus creating a team, but that's in the future. Today there is no formal team, so it's not appropriate to publish lists of names. Our GitHub commit history provides the best guide to our regular contributors.

Post back when you've got a working dev build.

We have no plan to go into more detail as any attempt at explaining ends up reading like an attack on OE's founder, which would be inappropriate and broadly misunderstood. The fork was no betrayal or coup, and although the main reasons are "about a person and their actions" (or mostly their lack of actions) they were never personal.

LE's git codebase fully respects our origins in OE, and there is nothing to stop OE continuing as a successful distro. In all communications with Stephan before, during, and since the fork we have always clearly stated our desire for both projects to coexist respectfully. So there is no "LE vs. OE" situation and we would ask that nobody attempts to frame one. In the long-term the differences between projects can speak for themselves.

releases.json .. the spec is not final yet, and may change again before we reach beta

Not supported.

no debug log, no problem

Compile - LibreELEC <= Get a working development build first, then support for the RAID card is a case of making a one line change to the kernel config to enable Linux Kernel Driver DataBase: CONFIG_BLK_DEV_SIIMAGE: Silicon Image chipset support and then rebuild.

The URL path that you configure needs to include a correctly structured releases.json file containing details of the files available. The feature does not work by scraping webserver directory listings. It's probably easier just to scp files to /storage/.udpate/

LE (and OE before) have a long-standing policy of refusing to add RAID support to the OS to avoid "the death of a thousand cuts" ..because if we add one RAID driver then we're obliged to add a long list of others, then all the filesystem management tools needed for RAID, and more. We have always been a "client" focussed distro; all the fancy RAID stuff belongs in a NAS/server device.

PCMCIA is off the list too. You're maybe the second or third person that asked for PCMCIA support in the last 4-5 years. It's niche and there is no new hardware coming so we wouldn't add it. We are generally a forwards (not backwards) looking distro when it comes to hardware support.

The external display adapter is also unlikely. Kodi is designed to use a single display so supporting additional screens (aside from laptops and modern interfaces like Thunderbolt) isn't a big requirement for our target audience. USB devices are likely only needed on old hardware (which is not something we're aiming at) and probably doesn't deliver good performance.

NB: LibreELEC's sources are in public github and it's not hard to create a custom image with personal changes. If you really want to use this collection of bits, that would be the best option.

The main point of a NAS device running OMV is to store media and have it always available and the main point of a media client device running LE would be to access media on the NAS. So i'm not sure dual-booting LE/OMV makes any real sense? .. but on a technical level "it's not rocket science" to use a bootloader like grub that supports multiple entries that you can select from at boot time.

thanks for confirming .. the patch will be included in v7.90.004

In recent Kodi versions the developers migrated a lot of things out of the core binary into add-ons to improve ease of maintenance. Unless you track the changes it can give the appearance of Kodi having a ton of extras installed, but really the out of box defaults are including the standard stuff needed for an average user. I personally prefer to watch movies instead of hunting around the add-on screens every day looking at what's installed. The default skin in Krypton is changed to focus on video/music add-ons so the infrastructural stuff is more hidden.

Weather requires you to install an add-on (e.g. Yahoo weather) and configure locations (and home-screen display) in the Skin. If you don't bother with any of those Kodi won't check for weather udpates.

If you create LibreELEC builds and share them with other users the GPLv2 license obliges you to publish the changes you make. This also helps others attempting to build for the same hardware and encourages people to collaborate.