Posts by chewitt

The two issues are kernel age and volume of devices. In dog/internet/linux years the 3.10 kernel is prehistoric and because it's missing so many now-fundamental structures it's too challenging to backport things. The 3.14 kernel is marginally easier, and unlike 3.10 there are a ton of devices using it, so community developers have made the effort.

NB: The second we have mainline kernel support for Amlogic devices, anything that cannot run mainline will have official support discontinued. The full scope of affected devices is not clear, but WP1 with the 8726MX chipset will definitely be dropped. Current ETA is post-Leia, so it should survive until the LE 9.0 release, although no promises.

1.) No, we have no clue what proprietary shitty SMB code runs in an ASUS router for their "share disk" feature (or whatever it is).

2.) SMB1 is considered a security risk. By forcing Kodi to continue using SMB1 you are still at risk. Disabling NTLMv2 auth over SMB1 (which is what those two lined do) degrades the already crap security level to something worse than plain normal SMB1. At the end of the day you are at no greater risk than you were six months ago. The only change is you (and many other users) are now marginally less ignorant of that risk, even if you don't understand it.

3.) The active SMB conf is documented clearly in the release notes that nobody bothers to read.

It's not possible to preconfigure networking and we have no plans to change anything to make it possible. CEC should work, as long as the micro to normal HDMI convertor doesn't do something to interfere. Plan C is to invest in a cheap micro USB to normal USB adapter.

I prefer AquariusELEC to LibraELEC

The 3.10 and 3.14 kernels used in current official releases for Amlogic devices (all releases since forever) do not contain the driver for the Xbox tuner so this will not work. I have updated the 8.2.0 release notes to make this clear. Community images provided by kszaq have media_build support and contain the driver, but I am not sure if he (or others) release anything for MX chipset devices. As a general rule the 3.10 kernel is simply too old for simple backporting of drivers so most community builders don't make the effort.

pastebin a Kodi debug log please

LE is a dedicated mediacentre OS. If you want the Pi Desktop please use Raspbian. If you want both OS on the same SD card use noobs to install both OS and make boot time selections.

No such plugin exists.

Read the 8.2.0 release notes.

On our Generic x86 image the available resolutions in Kodi are determined by the EDID response from the monitor. If it does not advertise 24Hz and 23.976Hz modes via EDID then Kodi will not show them as options. On many Android devices the list of available resolutions is often hard-coded (forced) so you see resolutions that the monitor/screen/tv does not claim to support. Audio works in a similar way. If the device does not advertise support for HD formats over EDID, Kodi will not offer them as selectable options. So connect to a proper AVR that supports those formats, not a monitor, and the missing items will (or should) magically appear.

FYI.. 8.2.0 is the current official release, not 8.2.1 (which doesn't exit) or 8.2.0.1 (which is pi hardware only)

Until we publish an official release there is no end-user support for those code branches. This is still early stage work and things are in a fluid state of development. If people want to self-build and experiment that's fine, but expect zero assistance with things that don't work. It's not that we don't care; but time devoted to supporting broken and unreleased code is time not spent on creating stable and released code.

unzip <name of file> unpacks to current directory

put files in /storage/.config/firmware/brcm/ and they are superimposed on /lib/firmware/brcm on reboot

[Unit]
Description=TimeCapsule Mount Script
Requires=network-online.service
After=network-online.service
Before=kodi.service

[Mount]
What=//172.16.40.100/TIMECAPSULE
Where=/storage/timecapsule
Options=username=kodi,password=kodi,sec=ntlm,vers=1.0
Type=cifs

[Install]
WantedBy=multi-user.target

Save that ^ as /storage/.config/system.d/storage.timecapsule.mount then "systemctl enable /storage/.config/system.d/storage.timecapsule.mount" and reboot, and the local mount to the device should be available to add as a new source in Kodi. It appears to be stable for me over a period of several hours. If 'mount' works the issue appears to be in smbclient or how Kodi interacts with smbclient.

Fenderman You will need to rescrape content to the library as all paths to content will change, but at least it works. It is technically possible to update the DB paths but that requires some sqlite SQL skills and I never bothered to learn those. I'm sure there's a howto somewhere.

dmesg shows no signs of an optical device being attached .. bad USB ports or cable?

wrxtasy fancy making a "droid-tools" add-on with the HK version of wiring pi ?

Yes

I've not seen issues with accessing the TC from another device (masOS sierra laptop) using SMB (not AFP) at the same time things in Kodi die and restarting Kodi from the console immediately allowed Kodi to work again for another 30 seconds so I'm not convinced it's a TC problem. I also did some experiments with longer Samba connection timeout values in advancesettings.xml but it made no difference. I might put smb debugging on in Kodi, although that mostly generates a ton of verbose crap that I don't understand so I wouldn't expect a eureka moment. I'll also play about with kernel level mounts to see if the same problem exhibits there.