Posts by chewitt

Unless your network is dysfunctional SMB is perfectly fine for sharing.

Add "tty" or "debugging" to kernel boot params in extlinux.conf (in the first partition on the boot disk) and a console will be available on CTRL+ALT+F3. The first just gives the console. The second also puts various subsystems into extra (and persistent) logging mode; as well as having the console.

I ignore zip files attached to forum posts. If someone else wants to review the above they're welcome. Otherwise i'll wait until our log posting guidelines are followed and a sprunge.us or pastebin.com URL link is provided.

There's a paste function in LE 8.0 settings add-on that sends logs to sprunge.us and shows the URL on-screen, but that doesn't address the OP's requirement of sending to a syslog server.

You can install the rsyslog add-on from the LE add-on repo.

Your log shows piracy add-ons installed so support stops here. You'll probably find removing them solves the problem - we see regular issues with pirate crapware accessing the DB at startup to self-enable, install more crap, and deliberately break 'competing' add-ons.

echo "options cfg80211 ieee80211_regdom=DE" > /storage/.config/modprobe.d/cfg80211.conf

RPi3 defaults to a safe "global" wireless regulatory domain, but this only sees channels 1-11 and may not be fully compatible with the radio properties of some access points that are using a local-country regdomain. The above sets the regdomain for Germany (DE) and other locations generally follow the normal ISO country codes; GB, RU, CN, US, etc.

Have a look at MusicBrainz 'Pickard' .. it's much (much) more than a tag editor, but if you want to cure a whole bunch of other tagging related things that you're probably unaware of in your library and ensure your media scrapes correctly it's the best option.

It's something we already do in Generic/x86_64 with Chromium. The main use-case we've seen is access to services like Netflix or Amazon which also need flash or widevine support. It's probably not too hard to create/package netsurf as an add-on, but would it support those services?

In Kodi Jarvis favourites is a buried item with a star shortcut on the Kodi home screen. In Krypton favourites has been promoted to a top-level item on the home screen (if you have it exposed in skin settings) so there is no need for the star shortcut. In other skins the decision to show anything is up to the skin author.

add "dtoverlay=pi3-disable-wifi" to /flash/config.txt and reboot

Quote from vpeter

Time to add SHA256 checksums in our build system. Who will start on that (I have free time)?

I think it's time we did this. Let's chat.

Did you migrate/restore anything (i.e. config) from the WP1 install? .. I'm using a WP2 with the stock remote as my current 'daily driver' and there's no repeat issues in the default image.

At this stage it's too early to say what the future holds for 32-bit Amlogic devices. Kodi needs to clean-up Linux support similar to how the Krypton move to "mediacodec" simplified Android support. In the long term Kodi wants a V4L2 based Linux video architecture, and that almost certainly requires Linux platforms like Amlogic (and Raspberry Pi) to be running a current/mainline Linux kernel with V4L2 video drivers. Older 32-bit S802/805/S812 devices are stuck on an ancient 3.10 kernel that falls wildly short of that requirement. If code clean-up progresses quickly it is quite possible that a 64-bit Amlogic device will be required for Kodi v18 support on Linux.

It depends on the Kodi v18 schedule. If Kodi decide to do a shorter sprint for v18 that results in an autumn-ish release then your 4.11+ fix will arrive in the next series of alpha/beta builds as we move towards that release. If it looks like v18 will run longer (end of year-ish) then we'll organise a mid-year 8.2 release with a newer kernel/mesa to pick up improved Intel hardware support, and we'll probably throw in a switch back to openssl for some bonus credit. So nothing firm yet, but we have Kodi DevCon over the next few days and that might firm ideas.

That can probably be solved by tweaking openvpn configurations to set appropriate routes. Or you go shop and get a proper router, because the hotspot feature in LE is not and never will be a proper wireless router.

OE's update process has no protection against "wrong image" updates (unlike LE which does) so it's blindly applied the RPi2 .tar file to the boot partition and this has overwritten the SYSTEM file. The box still half-boots because RPi devices use a kernel.img file not 'KERNEL' so the original KERNEL file is still present and being used. Half-booting doesn't help though

If you took a backup (and moved it off-box) before updating the fastest option is to create a new installer USB using our USB/SD creator app and then clean install LE on the box. Once it's up/running you can restore the backup.

If you did not take a backup you need to boot the box from an LE install USB or Ubuntu "Live" USB; both can be run in Live mode. LE boots/runs and can give SSH console access to run some terminal commands. Ubuntu gives you a full desktop environment. Basically you need to mount the first partition on the internal HDD and overwrite the KERNEL and SYSTEM files there with new ones extracted from the LE 8.0.1 update .tar file, then reboot and you should be running LE.

NB: On the download page there is a drop list (above the pi logo) and if you click this, you'll see an option for Generic x86_64 hardware. Click that and the page links change to show the Generic image update files. If you don't click it.. you're looking at RPi2 links.

Ideally this is fixed by setting the TV to "just scan" or it's equivalent. Plan B, use calibration in Kodi. Zoom is wrong.