Posts by chewitt

If you reach the point where you releasing something based on our codebase you have a GPL obligation to provide sources for your changes, and the easiest way to fulfil the obligation is pushing changes to an online repo, ideally github. If you want people to review work you need to make your work review-able. The easiest way of doing that is pushing changes to an online repo, ideally github. Spot the theme?

Git can be tricky at first, but everyone started out as a novice user and everyone remembers that. If you need help to make the leap, ask.

Changing a single patch to remove the colon would be accepted if PR'd, but if you do that from a Windows filesystem git will (or should) also pick-up a change from 644 to 777 permissions which would grounds for rejecting the PR (or sending it back for rework).

Connect the box to Ethernet in the hotel room and then use the wireless hotspot function to connect a laptop or mobile phone to the LE box. You can now use a browser on the laptop/mobile to provide the login details or voucher code to activate the internet connection. Once authenticated you need to keep using Ethernet as the hotel systems recognise the MAC address of the connected device; i.e. If you authenticate over Ethernet and then switch to a wireless connection you'd need to re-auth the connection against the wireless MAC address. It's possible to connect the other way and connect via wireless (to the open Hotel wifi network) and then share the connection over Ethernet, but our GUI doesn't support that so it can only be done using connmanctl via the SSH console.

I carry an older Apple A1rport express in my hotel kit. I connect that to the Ethernet connection in the room and auth once so it's MAC is registered, and then I can join as many devices as I need to my private network which is always in range and more reliable than the hotel wifi.

I'd ask that you solve the old-school problem sooner than later. Get code in a git repo so changes are under version control and the differences between your codebase and ours can be easily seen and understood. We will be quite happy to provide guidance and assistance, but only if we can comprehend how things work. Nobody will make the effort to review a collection of patch files in a mega share.

Not much change. Current generations of NUC are still the best 'performance' option but HDR support in the Intel GPU drivers is still under active development. Current Amlogic S905X/D devices have sort-of HDR support, but there are some lurking issues in the 3.14 kernel that will never be resolved and although mainline kernel is progressing nicely we are still some way from having full HDMI 2.0 support; and HDR support there will ultimately depend on some of the same "work in progress" kernel bits that the Intel GPU drivers need.

I have no doubt that both Intel, Amlogic, Rockchip etc. will have proper HDR support in the future, but I wouldn't want to guess timescales

Use the example NFS mount service in /storage/.config/system.d/ to mount the NFS shares. Use path substitution to tweak paths to match the DB entries if needed. You don't need to configure sources in the LE instance of Kodi unless you want to update/scrape sources from LE. If you only want to watch DB content sources.xml entries are not required.

CSylvain do you have sources in a public git/code repo?

It's not possible to run LibreELEC on these devices.

Others might have tried but their labours would have been in vain. You'll need to clone LE to a case-sensitive Linux filesystem like ext4 to build a fully working LE image else the permissions of numerous critical system files in the image (if you even get that far) will be trashed and either the image won't boot or important services won't start. You'll need to use a Linux VM or container to build images; both of which should shield colons from the host OS. For the record, our 8.2 branch is no longer open to changes; only bumps to existing addons will be accepted.

LibreELEC is not based on buildroot so their packages will not translate directly. We loosely follow the recipe principles from Welcome to Linux From Scratch! but the main source of instruction is "prior art" in the current buildsystem.

The LED light ring should work "out of the box" in the LE 8.2.3 image. The only reasons I can think of for it not working are /flash/config.txt has been edited (or restored) to disable the slice overlay, or hardware was damaged while making the CM > CM3 upgrade.

C2's run best with the eMMC board.

Settings > Media > General > Allow file renaming and deletion

^ make sure that option is enabled.

Android device trees are not compatible with LibreELEC releases.

It's the correct product (there is only one kind of CM3 card) but you cannot upgrade using the Slice3 .tar file. CM3 requires a new install of LE 8.2.3 using the .img.gz file (mount the Slice storage on Windows or Linux and then use our USB/SD creator app to write the image) because the internal emmc storage is on the CM3 card; i.e. when you remove the CM(1) card you also remove the storage. It's not a big issue, just make a backup before you upgrade and then restore afterwards.

Your solution is a bit "wagging the dogs tail to make the head move" and it's years since I encountered a non-caching DNS server in a router so IMHO the correct solution is to disable logging in pi-hole so it doesn't fill the ramdisk, or change the location to somewhere with more space.

Probably not. Note that you will need approx. 2.5x the size of the backup file as free space on the SD card to restore successfully as the tar file and unpacked tart file will coexist at the same time; plus some working space. If that's not the case you can unpack on something else with more free space and then stop kodi and move files back to where they need to be. Doing things manually isn't so hard.

Start by pushing your changes and commits into a GitHub repo so that the changes you've made can be seen and inspected.