Posts by chewitt

If yours sources.xml file looks like this:

<sources>
    <video>
        <default pathversion="1"></default>
        <source>
            <name>MOVIES</name>
            <path pathversion="1">smb://CAPTAIN/Movies/</path>
            <allowsharing>true</allowsharing>
        </source>
    </video>
</sources>

You need to ensure passwords.xml exists and contains something like:

<passwords>
    <path>
        <from pathversion="1">smb://CAPTAIN/Movies</from>
        <to pathversion="1">smb://username:password@CAPTAIN/Movies/</to>
    </path>
</passwords>

The alternative is adding the username:password credential directly into sources.xml like this

<sources>
    <video>
        <default pathversion="1"></default>
        <source>
            <name>MOVIES</name>
            <path pathversion="1">smb://username:password@CAPTAIN/Movies/</path>
            <allowsharing>true</allowsharing>
        </source>
    </video>
</sources>

It was an extra "cd" on the end of a command. It looked like a simple copy/paste error so I edited the post. If you'd gotten the commands wrong you wouldn't have built an image

There's no harm from running repo-tool but it's not necessary and you're using disk space for packages you won't use, e.g. if you build RPi2 you'll also end up grabbing the kernel sources for 3x Amlogic kernels, 1x Rockchip kernel, and all the hardware specific packages for those build targets. I'd guesstimate it's an extra ~1GB of data.

Quote from Scottford

Would I need to install a Linux distro on my pi.

Yes, but fortunately LE is a Linux distro

have a look at the CIFS mount sample file in /storage/.config/system.d

I answered the question in post #2.

The thing that conclusively proves the SoC type is under the heatsink, but the sticker that's visible indicates S905W.

It all depends on how the original vendor bootloader has been built and configured. It it checks the SD card first, no tricks are required. If it only checks when recovery mode is invoked, then tricks are necessary.

If the USB drive has no problems that prevent mounting it will mount in /mnt/<name of USB drive> (where name is the disk label). NextPVR client can be installed from the LibreELEC add-on repo. We don't provide tools like SABnzdb.

If you are trying to "browse" the Windows network from LE it will not show anything because LE (and Win10) no longer use the SMB1 protocol which supported a network browse service. We now use SMB2 or SMB3 which do not. Microsoft also recently deprecated the homegroup function in the latest creators update.

As someone already said earlier.. You need to go find someone who's more computer literate to help.

The best place to ask for support would be the plugin author's support thread in the Kodi forum. "Connection reset by peer" looks like a network issue; typically something being blocked.

Accessing LibreELEC [LibreELEC.wiki]

Use PuTTY to access the box over SSH, run "nano /storage/.kodi/userdata/sources.xml" and edit the sources to have valid URL's, then save (Ctrl+O) and exit (Ctrl+X) and reboot the box.

Stop using \\ and \ in the servername, don't append \ to the folder name, don't use an IP unless the Win10 box is on a static address (or static DHCP lease).

Kodi normally builds ffmpeg as an internal dependency to control the ffmpeg version and apply specific patches. LE builds its own 'external' ffmpeg but applies the same patches. We also have an 'ffmpegx' package in our build-system because Tvheadend also needs ffmpeg but it needs more features enabled than the quite minimal Kodi version.

I would not invest too much time/effort in the Amlogic 3.14 codebase. It's full of low quality kernel code and unresolvable issues. In the next couple of months we will have a mainline kernel/uboot with V4L2/mem2mem hardware video decode.

The "Kodi" user needs to have a password. Then you need to edit the existing 'sources' in Kodi to use that username/password (credential) when accessing the shares on the Win10 box. That can be done in the GUI (edit source). It can also be done manually by accessing the LE box over SSH and editing /storage/.kodi/userdata/sources.xml in a text editor (nano). As scary as that might sound it's often the quicker and easier way to edit things. The URL's in sources.xml need to be in smb://user:pass@server/path format.

The "git reset --hard" isn't necessary because you already checked-out the repo at a specific tag, and IMAGE_SUFFIX=v825 isn't required as the 8.2.5 version is part of the release image filename. Also be aware that the repo-tool script will download the sources for all packages in the build system; whereas if you allow them to be downloaded at build-time you only download sources for the packages used in the image you create. Apart from that (and one typo, which I corrected) all looks fine.

If you plan to build/rebuild things I'd recommend moving the 'sources' folder somewhere outside the main git folder and then creating a symlink to it. This allows you to nuke the git folders and re-clone (or share sources between multiple git folders) without having to re-download or duplicate all the sources. If you're a git novice it's kind of inevitable that at some point things get screwed up and the easiest way forwards is to nuke/clone again, and downloading sources adds time to the build process. NB: It takes a while to get the hang of git and everyone makes mistakes at first (nobody ever stops learning).

No harm in trying..

If there is no "just scan" option on the TV you can calibrate the screen in Kodi settings > system > display > calibrate. You need to calibrate for each refresh rate that your media requires.

Kodi is written around ffmpeg (some of the Kodi developers are ffmpeg developers, none are gstreamer fans) so anything that forces another player app into the codebase is always going to be an ugly hack that is hard to maintain. It would be long-term better to think about enhancing ffmpeg capabiltiies in Kodi and contributing improvements, not hacking gstreamer support.

Can you point me to your GitHub repo?