Posts by chewitt

RPi3 wireless (both BT and WIFI) sullies the repuation of an otherwise great product. You already discovered the solution.

The OS boots into RAM if there is >=1GB so it's possible to remove boot media and the system will continue to run, but this will make the persistent /storage area unavailable and when it reappears after unclean dismount the kernel will consider the partition to be dirty and remounts it read-only to prevent data corruption issues. This prevents Emby from making ad-hoc saves, and Kodi (Jarvis) only saves it's settings on shutdown, so when you reboot to solve the issue any changes since previous boot are lost.

If it was 1/2 boxes I'd guess dodgy USB ports or USB sticks, but if it's 2/2 and you've already swapped the USB sticks it's either something in hardware like a BIOS or PSU issue that results in interrupted power to the USB ports, or it's software. If it's something in software, it's some kind of kernel level bug that probably doesn't leave much trace: "journalctl --no-pager -b -1" will show the previous boot journal including the diconnect/reconnect, but i'd be surprised if anything is revealed; and I'd be surprised if really was a software issue.

As general advice: I worked for several companies who released products that boot from USB/SD media and a myriad of issues have been miraculously resolved the second they reverted to using old-fashioned spinning rust or SSD's. We don't advocate long-term use of removable media, as while it can be done, the underlying media is not designed for it. I personally consider all USB/SD installations to be temporary. It's never about if things will go wrong, only a matter of when it takes place.

If the folder name starts with . the folders will be hidden and you need to enable "show hidden files and directories" to see them. This is probably a PEBKAC issue but it's hard to say without literally 'seeing' screenshots of things.

There are changes in Kodi Krypton to save settings as you change things rather than on "everything saved on shutdown" which has been seen to cause problems on multiple OS platforms, it's not LE specific. If you have repeated issues you can access via SSH and "systemctl restart kodi.service" to ensure settings are saved outside of the normal shutdown process, or you can update to the current Alpha builds, which despite the "Alpha" name are solid on x86 kit; I've been running them for months (albeit on an nVidia GPU box).

Quote from sakos

Does anything happen with the registered bug reports here?

They languish unloved until sometime replies

I've no idea what the issue is but the first step is updating to the current Alpha release. If the problem still exists it can be investigated, while all development on our Jarvis/7.0 build ceased months ago.

ute it shouldn't block anyone who already registered with an @yahoo.com address from accessing the forum. I'm hoping this is a temporary change while we figure out something that will prevent bots registering with yahoo accounts.

Have you tried copying the binaries from a recent Ubuntu install?

The root cause has been identifed (changes in diskutil info output) and will be corrected in the next update to the app. It also looks like macOS sierra has a bad user experience with the app due to the more restrictive enforcement of gatekeeper, but that's a separate issue.

Try an alpha build on a spare SD card - let us know

giannis1711 - the dmesg log shows a fully working card *but* you have enabled the local wireless hotspot feature. This means your card is acting as an access point; hence you cannot use it to connect to other networks.

You can get decent Pi starter kits from people like The Pi Hut. The kit will ship with a "noobs" SD card that might contain OpenELEC as the pre-loaded mediacentre OS unless they finally exhausted the stock of OE imaged cards, but 30 seconds with our USB-SD creator app will correct that

Other sources of kits are pimoroni.com and modmypi.com .. and since yesterday the official Raspberry Pi - Teach, Learn, and Make with Raspberry Pi shop although that kit has stuff you don't need for a mediacentre and is more expensive. Still, all of them kick back a percentage to the Pi foundation and it's a great cause.

Or you remove the USB drive from the Pi and connect it to the computer you're reading the forum on and format things there.

Connman simply routes traffic from the private 192.168 tethering subnet to the internet connection (e.g. eth0) so the answer should be "Yes" as long as you configure proxy details on the client devices that access the tethered access point. The tethering config that you can set in Kodi only applies to Kodi itself not the whole OS. If it doesn't work you can do "touch /storage/.config/debug.connman" then reboot and tail the journal to look at what connman is doing (output is very verbose but somewhat human readable) in case there's an error, but I suspect there isn't anything. If it really doesn't work, it's probably not designed to work that way. The connman tethering feature is originally created for a mobile phone OS to create a simple mobile hotspot. It's not something that will ever be enhanced so if it doesn't work the solution is to get a proper wireless router..

Streaming to an LE box over BT is not supported. Only streaming from the LE box to BT speakers.

escalade: Sounds like slow-loading drivers and fast starting Kodi. Ye olde "wait for network" setting should prevent that.

crx73: I don't care what SSH client you use .. run the commands

"dmesg | paste" and "lspci -nn | paste" and share the URLs here

And with v7.90.005? .. there was a fix for an OOM issue in Kodo 17b1 (but no guarantee it's the same issue).