Kodi debug log please - preferably via the built-in paste function so we don't have to waste time downloading attached log files
Posts by chewitt
-
-
You have media piracy repo's and add-ons installed. This forum will provide no support until you provide log files showing they are removed.
-
No log = no problem
-
As a general rule Linux is more efficient and achieves better performance than Android.
wrxtasy .. you had a Mi Box for testing a while back if memory serves?
-
You've stated it cannot connect to anything outside your network AND that TMDB is working .. which is outside your network. There is no description of your network or what said IP settings supposedly are, and no log evidence which might clarify which statement is true. It'll be hard to help you.
-
a WeTek Play 2 as it also has S/PDIF output for the ancient (but nice sounding) Marantz AVR that I use.
-
This is the first time I hear of NUC's having crackly audio over HDMI and there are quite a few NUC users among the team. The issue with HD audio is still present (as Intel still didn't get their sh1t together and fix their driver) but this sounds [sic] like something more basic. Next release will have updated Kernel (and thus drivers) but since this kind of thing isn't a known issue there is no guarantee anything will be fixed. You could try using a Milhouse (Leia) build to test that; LE 8.2 isn't quite ready for public testing yet.
-
The connection manager (connman) supports EAP but nobody has ever written the GUI bits to configure it; because nobody among the project staff or regular contributors has ever had access to the necessary infrastructure (and in 5-6 years EAP support has been asked-for the same number of times). If you find a normal Linux distro that also uses connman and configure it there you should be able to transfer the service config files over to LE in /storage/.cache/connman/ and have it work. If some keen and capable volunteer submits the required changes to support EAP on github we'll review and hopefully merge them. I suspect the 7th-ever enquiry for EAP (in a year or so) will see me repeat this answer though.
-
Hope all that makes sense
Nope. We like debug logfiles. They explain more than humans.
-
If you can import from OVA there is a vmware image: Mirror List
If not.. I doubt there's an option as ISO is an optical media format and all our boot/run things are designed for disk media.
-
I have been using "adjust refresh rate to match video" on LE/OE systems since ~2010. It requires advanced/expert mode to be visible.
-
SSH to the IP address of the box Accessing LibreELEC - LibreELEC
-
There is an Emby GUI add-on in the Kodi repo. Never used it so can't speak of how good/bad/ugly it is.. but it's there.
-
Share files from Ubuntu over SMB or NFS and configure the shares in Kodi .. it's not hard. Look in the Kodi wiki for instructions if you need them.
-
Contact pimoroni and ask if they have spares. Have a look at the OSMC remote if an original Slice one isn't available. It's pretty similar in size and layout and you can steal the remote.conf from OSMC's github repo.
-
Your box does not technically violate our forum rules (yet) but the intent is clear and I have no interest in assisting users with the installation of pirate crapware that damages the name of Kodi and our project.
-
The replacement main board and PSU was handed over in Spain and it all works again. It's lost its spot as the family main box, but at least I can test stuff before publishing now.
-
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.
