Error received: Permission denied (publickey,keyboard-interactive).Does it mean my remote machine (OSX) does not recognise the public key?
It means you are attempting to authenticate with a password, which is not a valid authentication method. If you allowed passwords the methods available would be "publickey,password,keyboard-interactive".
Can wait to test these changes in
Lakka. Do you know if S912 will be supported too?
The Kernel work Baylibre are doing will fully support S912 hardware but Amlogic have no plans that I'm aware of to license fbdev drivers for Linux so you're stuck with the libhybris Android driver hack to make S912 work.
You can, if you self-build from sources, and right now it would probably cause you a load of problems due to recent upstream content merges that are still being fixed upstream (and on our side). Also consider that 64-bit Amlogic devices will hopefully jump from Linux 3.14 > 4.13 kernel and will end up with a completely new graphics architecture in Leia if things go to plan. I run a WP2 as the family daily driver and I won't be entertaining the idea of Leia code on it for 2-3 months yet. Leia is roughly targeting a year-end release.
First observation is that you're building from the master branch not 8.0 (see LibreELEC-RPi2.arm-9.0 visible in paths) and due to upstream doing some major merges in the last week you'll probably find things a little broken at the moment. We're deliberately waiting for things to stabilise before we fix up our master branch. If you want to build 8.0 run "git checkout libreelec-8.0" before building.
LE works with QEMU and for 8.0 there's a dedicated image for vmware (Virtual) but I'm not sure anyone has tested KVM. If it works, great. If it doesn't work, it's up to you to fix it 
Check cables. Use different HDMI ports.
configure the LE box for key-based auth then you can send commands via SSH, e.g. "ssh [email protected] poweroff"
This is a known issue that affects Amlogic 64-bit devices; i'm not sure about 32-bit. It's something that we have a few ideas about but it is unlikely to ever be fixed in Krypton as the Kodi development focus is now firmly on Leia.
In that case the answer is no, there is no Chromium browser for Pi devices (unless you use Raspbian)
linux-amlogic/dm9601.c at amlogic-3.10.y · LibreELEC/linux-amlogic · GitHub
device is already supported in the kernel's used on S805 devices.
Several pirate add-on repo's are installed. Support stops here.
Connect the NUC to the TV and dump the EDID using the embedded "getedid" script that configures Xorg so it believes the TV is always connected. If you're lucky that overrides whatever the Pioneer AVR is screwing up.
Enable BT under services or system, then go back to the BT devices screen. It's something that needs to be relocated for 9.0
nickr I'm not aware of any and the community efforts are still quite focussed on Krypton, which is probably a good idea considering the amount of plumbing that will radically change before Leia release; new modern kernel and graphics architecture, all the vpupdate stuff etc. in Kodi.
That kind of feature request belongs in the Kodi forum, it's not something we (an OS that runs Kodi) can or would implement.
I'm sure it can be made to work; in the past I created an experimental MT7601U package for OpenELEC that worked and the drivers are similar, but "working" and "supportable" are different things. The driver requires configuration via a user-editable file, which is not how things are done in any modern Linux and certainly not in an embedded distro. Mediatek drivers make Realtek ones look polished so I will reject any attempt to add their current drivers to our images. You're welcome to make your own custom image though.
If you end up with a working/reliable add-on, please consider submitting it to our repo.
"journalctl -b 0 --no-pager | paste" and share the URL generated after a clean boot where the wireless is not on
