Posts by chewitt

Quote from donbrew

Linux people are obsessed with accounts and passwords for security, they don't understand that most home users don't care about security; Windows has ways to get around that stuff, for now.

Good advice will always be inclusive of users and will push, direct or persuade them towards better security habits. If you want to preach insecure habits we'd prefer you to keep quiet and not offer the advice. Fortunately Microsoft is also (finally) taking security more seriously. Feel free to note their current dislike of anonymous access and general direction towards everything being properly password protected, like Linux.

Sorry I thought this was some internal device, but nothing shows. Rinse/repeat with "lsusb | paste"

Kodi smbclient defaults to SMB3 so if you set minimum it will continue to attempt (and fail) with SMB3. Hence the option allows you to force the maximum protocol versionto be SMB1 which prevents SMB2/3 interfering.

client max protocol = NT1
client use spnego = no
client NTLMv2 auth = no

^ adding those to /storage/.kodi/.smb/user.conf and restarting Kodi (or rebooting) allows me to access an existing share in sources.xml although when browsing pictures in a share the connection seems to die regularly. Browsing photo's has always been partially broken in Krypton for me so I'm not sure if it's also the same with video. I'm actually surprised Apple hasn't done a firmware update to support SMB2/3 on these boxes; time to get a proper NAS!

Quote from donbrew

Add the source by typing the network path then provide user name and password. Samba browser is gone in the new version.

That is in the release notes.

^ that is wrong information for this use case.

mount -t cifs //172.16.40.100/SHARE /storage/tcshare -o user=kodi,password=kodi,sec=ntlm,vers=1.0

^ that works from the console so worst case you can use local mounts to access. I will see whether I can translate that into working smb.conf

I have remembered that my Apple router is in fact a TimeCapsule so I will play about with it and see what I can figure out. They use Apple's own interpretation of SMB protocols not Samba so there is bound to be something unusual required.

Random guess.. OE hasn't been updated since June so won't be using a current version of inputstream.adaptive. LE has a much newer version and the defaults may have changed from HLS to DASH. Go fiddle with YT settings and see swapping between them makes a difference.

I found two sites that list the AzureWave AW-NB136NF module as having a BCM43142 chip, not BCM43231.

Please run "lspci -nn | paste" and share the URL so I can see the actual device IDs.

Nothing has changed between releases and the original Kodi language packs and weather add-ons are found in the Kodi add-on repository, not the kodinerds repo. The only difference is that the Pi0W has maybe a slower loading network driver so the initial repo check fails and thus there appears to be no addons available. As Klojum already said, refreshing the Kodi repo resolves this.

I've no idea about support for data DVDs, but Kodi has no hot-plugging support so it will not detect a DVD drive connected after Kodi starts.

basically.. no

compile [LibreELEC]

fstab uses kernel mounts not smbclient and in Ubuntu 16.04 this is probably SMB1 by default, but it also might not work with SMB3 (depends on what Ubuntu's kernel allows) so try adding vers=2.0, e.g.

mount -t cifs //10.19.64.3/Movies /media/OpenelecMovies -o vers=2.0,user=libreelec,pass=libreelec

Working?

run "lsmod" to list the kernel modules active .. but if is "wl" the older broadcom STA driver, we already ship this:

LibreELEC.tv/package.mk at libreelec-8.2 · LibreELEC/LibreELEC.tv · GitHub

so how it works on Ubuntu and not us is a mystery..

Please read the release notes

And what OS version is the Windows box?

This is a guess, but an educated one: I'm not sure LE 8.2 supports 32-bit boot devices (some CT devices are 64-bit but only support 32-bit boot) but LE 9.0 (development images) do - via grub, which is also what Ubuntu uses. Grab a current milhouse development build from the Kodi forum and use this to install so you have a working bootloader, then downgrade to the normal 8.2.0 release using the manual update function in the LE settings add-on, and then perform a hard reset to remove any stray Milhouse/Leia configuration bits. Make sense?