Posts by chewitt

It shows a TLS handshake time-out, so maybe NordVPN have a network issue or you're using a config that talks to incorrect servers - but ultimately that's a guess as I have no clue about that add-on. I suggest you contact the add-on creator for help; it's not one of ours.

No debug logs. No problem

Yes in theory you can take the patches and various kernel bits but there is no nicely written wiki article to explain the entire process so in reality it's one of those "If you have to ask how it's done, you're not going to succeed at the task" cases. I don't mean to be arrogant in saying that, it's just that I have a load of experience with people trying to fiddle with the logical and well structured LE build-system, and that's how it plays out.

In some devices the region coding is embedded in device firmware so selection is handled automatically by the kernel. In other devices the default is a world region code. This is in theory what RPi3 has, only the wireless driver has some caveats on auto-detection and only sees channels 1-11 unless you force the region code (which has nothing to do with Kodi). We don't ask for the region code because a) we have no way of asking it currently, b) no other driver needs this, c) out of tens of thousands of installed systems only about 10 people have complained.

No it would not. Setting the region in Kodi has nothing to do with wireless region in the OS layer.

There are no PDFs but

The drive will auto-mount under /var/media .. as long as there is no issue mounting. If it never appears in Kodi log-in over SSH and run "dmesg | paste" and share the URL generated here so we can see the kernel log which will have clues on the reason it doesn't mount.

There's no attachment. If you can't share here post it to imgur.com.

Use "ethtool" to check the port speeds. It can also force the port to a higher speed (instead of auto-detecting) although it's unusual for auto-detect to not get things right. Do the usual things like trying a different Ethernet cable too..

Aside from testing the current Alpha (or Milhouse) builds which will have newer drivers, the best thing to do is capture a couple of mins of the offending channel to a file that can be shared (along with a debug log) with Kodi developers.

LibreELEC.tv/linux.aarch64.conf at master · LibreELEC/LibreELEC.tv · GitHub

support for the kernel module is compiled in. If it needs more than that, someone will need to tell us what.

Please take a photo of the stack trace on screen; close up and steady enough that we (or someone who understands it) can see all the text clearly.

echo "cfg80211 ieee80211_regdom=US" > /etc/modprobe.d/cfg80211.conf
reboot

do that, it will be persistent over reboots.

If you want performance use EXT4. If you want compatibility with Windows use NTFS. If you want compatibility with Win+Mac use exFAT. There is no filesystem that gives performance AND compatibility but all are "good enough" for use in a mediacentre box. Best practice is "plug it in and it just works" as there is no need to muck about with mount points or anything else.

You can permanently disable gatekeeper using the Terminal command. You can also temporarily disable it by control-clicking (or right-clicking) the app icon and clicking open on the menu that appears. This will ask you to confirm whether you really wanted to open it, etc. as per the older behaviour, which is not so bad - I need to update the release notes on the main website. We are still going to investigate what's required to be a known developer, but confirming that behaviour knocks it down the priority list a little

You probably want to set "ieee80211_regdom=US"

Sort of yes/no. The core OS will downgrade that easily but our add-ons are numerically numbered higher than OE's so the best thing is to take a full backup of OE before and then clean install OE and restore the backup to fully revert. That would be a last ditch action though

Why send PM (which I rarely read on principle) .. what is secret?