Posts by chewitt

I looked at updating the cacert.pem bundle we embed which is obtained from here: curl - Extract CA Certs from Mozilla but the update doesn't make any changes to Symantec/Verisign certs and the bundle doesn't need to contain intermediate CA details; in broad terms the signing chain will be followed through live queries until you reach a trusted or revoked certificate; and if neither is reached the process fails.

It's possible this is just another indeterminate LibreSSL problem - we've seen some random/unexplainable issues and it's the reason we switched back to OpenSSL in preparation for LE 8.2/9.0. If you can test a current milhouse Leia build (Generic and Pi hardwar) on a spare USB/SD card that would confirm if that solves the issue.

I can see lots "unable to connect to server" messages. I cannot see any references to .so not loading. We have no real expertise in the add-on; we simply build whatever upstream developers publish so it's probably best to start with the support thread in the Kodi forums.

The certs are baked into the system image so updating them requires the image to be rebuilt. It's something we can look at for 8.2 release, which should be in beta test soon-ish.

We got the overlayfs stuff needed for Docker working for the 3.14 kernel used in WP2 but the 3.10 kernel in WP1 is too old.

inputstream.adaptive for Krypton is being updated up with backports from master in prep for the 17.4-RC1 release. The k17_2 branch in peak3d's github repo is (or will become) the production repo for it. Current git HEAD fixed a bunch of issues that I was seeing - we did some joint debug and test last night.

Kodi debug log please.

It's not required for YouTube.

You can also uUse our USB/SD creator app (or Win32 disk imager, rufus, etc.) and restore bootsector.img to the USB. If the USB is not defected/damaged it should show in Windows as unformatted; and you can re-format.

Debug Kodi log from the RPI3 please.

MrChromebox.tech

The pi tools add-on has several options for python-based GPIO control that something could be built around. If you're only interested in the end-result and not the learning process a Pi case with good passive cooling (and no noisy fans) would be an easier option. The Kodi 'flirc' case is metal with a conductive heat-sink for the main processor as part of the design.

I'll add their name to the list of rip-off merchants who sell an incompetently built version of our great £0 software for profit. As there are no sources for their images visibly published anywhere they can also join the list of GPLv2 violators too. We officially disown anything they provide.

Or try restoring bootsector.img to the card first, then eject and reconnect.

That's just "how it is" in Kodi Krypton. Kodi Leia contains some improvements so depending on what hardware you're using you could always try a milhouse nightly release.

The tethered hotspot function is a tethered hotspot function not a WIFI router function. It is not designed to (and cannot) be changed. You'd need to self-build an LE image after patching a different default IP range into connman source code. It would appear the routing function is also on the basic side if /etc/hosts isn't being checked. In summary: It's working as designed (and it's a über simple design) so if you need/want a proper router you'll need to go buy a proper router, or use a more conventional Linux distro where greater configuration options are possible.

The update function in LE settings checks official servers for official LE images. We have never released an image for generic Android boxes so you must be running something community created; hence nothing is listed when you check for updates. Some of the community image creators also take liberties with version numbers and content, which explains why 8.0.2 on your box does not have Kodi 17.3 like our official 8.0.2 release.

I've moved the thread to the Amlogic section of the forum where the offending community creators hang out

You can make LED patterns in gimp. It's not a web-app but it does the job.

It sounds like a routing issue; either the router is not routing between Ethernet and WAN interfaces when in wireless bridge mode or the DHCP server isn't providing a gateway so you can only ping things within the local subnet. If LE works when the router configuration is rather points the finger at the router being the issue is (which isn't our domain of expertise) not LE.

My personal preference has always been to aim for the least number of boxes vs. trying to eek out value in old purchases. I'd get the new expensive single-box VDSL+ router and eBay the old one to partially offset the cost.