NFS is marginally more efficient but not natively supported on Windows. I've used SMB for years without issues .. if it has problems the issue is configuration or inadequate bandwidth.
Posts by chewitt
-
-
a) Poking /sys will work if you figure out the right command (not very helpful advice I know)
b) Multi-channel audio is in the to-do list, but not the highest priority at the moment
c) Not at the moment .. the V4L2/GBM code will need to evolve support for VNC
d) Most likely the TVH add-on currently in the repo doesn't match the minimum version for the Kodi nightly; once 9.0.1 is out this should get resolved
-
If it's a BT device? it can be un-paired in LE settings.
-
1. No
2. It's possible but normally impossible to pin down to a specific thing. SMB2/3 will give faster throughput (an incentive to update)
3. Our testing showed a positive improvement. All testing is subjective to environments.. YMMV.
4. Honestly no idea how Windows handles version negotiation. Kodi on Windows uses the native SMB capabilities of the OS whereas on other OS (Linux/Android/macOS etc.) we use smbclient (part of Samba).
-
Code
05:13:36.005 T:1567286128 ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://USERNAME:PASSWORD@SYNOLOGY/root/Videos/Movies/The%20Fly%20(1986)' unix_err:'16' error : 'Invalid argument'^ are you connecting with a valid username/password?
-
We cannot use Python3 because Kodi has a hard dependency on Python2. Team Kodi will switch to Python3 for v19 to ensure the change happens before the end of Python2 support in 2020.
-
Run "journalctl -b 0 --no-pager | paste" to share the systemd journal .. the Kodi log won't show anything about the OS or the time period before Kodi starts which is where any delays/issues are.
-
Not supported, and no plans to support. Sorry..
-
LibreELEC Downloads – LibreELEC <= has .img files that can be restored to SD card, the .tar (update) file cannot be used for installs. If you want to install via noobs; just boot via noobs lite and LE should be one of the available install options.
-
You can use a bind mount (in autostart.sh) to make it appear in /usr/bin/rsync
-
^ currently on the 16th revision of the patch series, so probably a few revisions to go yet
-
Definitely not going to return.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Go read about "WannaCry" ..
-
No idea what the issue is, but the backup is just a tar archive so it can be extracted to a local folder and you can manually move back the important bits instead of the whole file.
-
RK3399 can work with panfrost but needs a mainline kernel .. so you hit some issues:
a) There's only partially working video drivers for mainline RK at the moment
b) Device-trees are for the mali blob and panfrost requires some changes
b) There are plenty of bugs (as with S912) that impact stability
So it works, but, YMMV
-
See http://opensource.rock-chips.com/wiki_status_matrix for the list of RK chips we can support. RK3228 is not on the list.
-
Our definition of a working driver is "doesn't need another out of tree realtek driver to be added" .. and since we plan to drop support for all wifi devices that don't have in-kernel drivers in LE 10.0 we're aren't in a rush to add more of them now.