Posts by chewitt

It indicates the Raspberry Pi wants more current than the PSU can provide. Shorter/better cables or a PSU with a higher Amp rating will make it go away. I think these days 2.5A or 3A is the recommendation.

Before debating drive support check that the disc you are attempting to play has keys in the KEYDB.cfg file. You can also tail the Kodi log and if you see errors about encrypted content .. it's because no key exists to decrypt it.

Kodi must have permission to access the shared content on Win10, which is done by setting access controls on the content. Do you share content using a local machine user/password or what's called a "microsoft ID" account, e.g. [email protected] ?

zip the firmware instead of tgz

Well no.. but you didn't share that nugget before. Is this an LE vs Android comparison or .. ??

"touch /storage/.config/debug_connman" and reboot, then "journalctl -f" to see the live log output of connman while you attempt to enable the tethered hotspot. I forget what the actual error message is but connman output is readable (if very extensive/verbose) and it's a fairly clear message about driver support .. but generally it either works, or the driver doesn't support it.

shut-down-your-windows-pc-remotely-from-linux

^ That might work. We have the samba stuff although we don't compile with all possible options enabled which restricts some functionality. No harm in trying though.

Connman "polls" for new networks and periodically updates the list of visible SSID's in the connections screen. It also has a hard-coded behaviour of preferring Ethernet over Wireless so if you have a wireless connection active and connect Ethernet the latter becomes the primary connection. The wireless connection will remain active but it will lose the ability to route data off-subnet.

Tethering requires a wireless driver that supports AP modes. Not all drivers support it and it is not possible to reliably pre-detect whether a driver supports it so the option shows in the GUI even if the driver doesn't. If it doesn't work, 99.99% the driver doesn't support it.

LMGTFY

Yup, we added some detection in 8.1.2 that looks for the string with v4 (anything older is presumed not based on the v4 template) and if not found we skip the custom config and start Samba with the default template. You were too efficient fixing your config before 8.2.0

It's only Windows that is dumb about multiple partitions on a USB stick. Nearly all other OS manage it fine.

Backup: get free space of selected folder by mglae · Pull Request #82 · LibreELEC/service.libreelec.settings · GitHub will help with this, it will be in 8.2.0

I don't debate theoretical issues. Provide a Kodi debug log .. or there is no problem.

I'll rephrase the question. What computing device/hardware/model are you trying to boot from the USB key?

Kodi running on Android can only use SMB1 and Kodi in current beta versions of LE (and most community created builds) is capable of using SMB3 which brings a considerable performance increase and fewer security issues.

Test the OVPN config from the console first, where messages are more verbose and easier to see. Then when it works you can configure it to be used with Brian's add-on. Last time I tried it (which was admittedly some time ago) it worked fine.

Run "dmesg" or "journalctl -b 0 --no-pager" to show the system log .. errors from RTC are harmless and are probably due to the kernel trying to load it when it doesn't exist on other hardware - if it's an external board or something with HK boards (not sure, never seen one personally).

Fix the template first and then update the 'NAS' box (C2?) so it's using the current beta release. Then use it. We have no interest in theoretical issues that you are concerned about or think might happen. We only care about issues that actually happen. Make sense?

The add-on is stable.

It's been done before. The challenge is getting mac mini's to boot Linux, but Google and you'll find instructions.