Posts by chewitt

    Samba 3.6.5 in LE 8.0.2 only speaks SMB1 and Win10 after the creators update only speaks SMB2+ so nothing can be reconfigured to work. Your options are a) updating to a current Milhouse (which is Kodi Leia) or self-build version of the forthcoming LE beta based on our 8.2 (still Krypton) branch, or you wait patiently for the 8.2 beta/release. Those contain Samba 4.6 which supports SMB2+ out of the box.

    Hyperion is in our add-on repo (and Hypercon to match is on the wiki) and should work fine as-is today with most of the frame-grabber based Ambilight kits. Normal "pi" kits that use the GPIO pins won't be compatible as those interfaces aren't on the rear of a Slice box. In theory it's should be possible to drive something from one of the USB ports but that needs some tinkering and (based on previous conversations with Gordon) possibly driver support. I am slowly acquiring the physical parts to investigate and post-vacation I have a working Slice (CM3) box again, but I don't code so wouldn't be able to complete the task unaided, and for various reasons it's currently super-low on my personal priority list.

    Set the Skin to Confluence before updating, then update. The skin will switch to Estuary on update, but it won't throw errors. Now you can install the updated (Krypton compatible) version of Aeon Nox from the Kodi repo (if it doesn't update automatically) and switch back.

    Possible issues:

    a) If you have any pre/release version of the fall/autumn creators update installed this removes SMB1 server support for your Win10 shares and Kodi currently only speaks SMB1. A beta testing release of LE 8.2 with SMB2/3 support in Kodi should be out in the next couple of weeks.

    b) If the server now speaks SMB2+ (no SMB1) even with the LE 8.2 version there will be no network browsing as this requires the network master browser to speak SMB1 protocol. You will have to add sources manually using the full server/share path.

    c) MS is actively discouraging guest/anon access in their security patches and setting a user/pass is becoming mandatory. If you set user/pass it needs to be a local machine user account and not an MS hotmail/outlook ID account (e.g. desktop login ID) as the authentication schemes are completely different and the latter is known to cause some challenges.

    The http 401 refusal is probably due to an outdated version of the TVDB scraper add-on; the API keys used by Kodi in the add-on were revoked recently due to widespread copying/abuse from pirate add-ons. You need to update the scraper so it uses an updated/valid key.

    If the box is not showing add-ons at all try add-on a 10-second "wait for network" boot delay in LibreELEC settings or context click on the Kodi repo and run 'check for updates' to see what it finds.

    Code
    echo "options snd-hda-intel model=imac24" > /storage/.config/modprobe.d/alsa-base
    or 
    echo "options snd-hda-intel model=mb5" > /storage/.config/modprobe.d/alsa-base

    ^ One of those should/might do the trick. You need to reboot to effect the change..

    Remove old drive. Clean install LE to the new drive. Connect old drive to USB cable and plug into HTPC, wait for the drives to mount. Stop Kodi, copy over all the stuff you want from the old drive, restart Kodi and all your old config is there. Disconnect old drive, then in a few weeks when nothing went wrong with the new drive you can reformat the old one and use it for backups or something.

    It's usually faster to copy data in a filesystem than make a block-by-block copy of the entire filesystem.

    It's still not a debug log but there is no apparent attempt to install anything so nothing fails. I can see pvr.hts is present though, so at some point you have successfully installed the TVHeadend client from our repo.

    If the repo's look blank, either force refresh them manually or add a "wait for network" startup delay of 10 seconds in LE settings.

    There are usually some installation challenges (especially on older Mac hardware that sucks at USB booting) but x86_64 compatible Mac hardware should be able to run the Generic image. It is not widely used though (new NUC's are considerably cheaper than new Mac minis) so there are some lingering grey areas on support.