Posts by milhouse

    schumi2004 you're triggering a memory leak that results in kodi.bin being killed by the out of memory process killer, do you know the steps to reproduce this? Are you able top reproduce with my latest test build (although these builds have a separate bug - introducd in build #0806 and not in 7.90.004 - that triggers OOM when seeking in ts files)

    Following works for me with FreeNAS:

    1. NFSOPTS=nfsvers=3,rw,intr,noatime,rsize=32768,wsize=32768,nolock,async,proto=udp
    2. [ ! -d /storage/freenas ] && mkdir /storage/freenas
    3. [ ! -d /storage/data ] && mkdir /storage/data
    4. mount -t nfs /storage/freenas -o $NFSOPTS
    5. mount -t nfs /storage/data -o $NFSOPTS

    Something is messed up. Run the following:

    1. cat /storage/.kodi/userdata/sources.xml | pastebinit

    and paste the link.

    Note that the libnfs library used by Kodi to access NFS filesystems does not support NFSv4 so you'll need to ensure you have an NFSv3 server, otherwise you'll have to use OS NFS mounts in LibreELEC.

    What lrusak is saying is that the LE build doesn't support what you are trying to achieve. You'll need to patch the various systemd scripts for kodi, connmand etc. to deploy your files to /storage from within your image. You don't want to copy a folder called "/storage" to your image as that will be very confusing (as LE already mounts a /storage partition), but you could put your own files in a folder called /usr/storage which should then be copied to your image, and then deploy your files from /usr/storage.

    However, it's probably a solution that will break at some point when other updates are applied to master, and it might be easier to deploy your static files from a tar file. Presumably you're creating a custom image for more than just these WiFi credentials, as that's a lot of work for something that's fairly trivial.


    Why don't you use as it says in the Wiki?

    I'm not sure if will work - what that says to me (and it's only used in a comment) is a network 192.168.1.* configured with mask - not that you should configure the export in that way. I could be wrong, so someone else may have to advise.

    And if you want a read-only export, change "rw" to "ro".

    and when i search for a nfs share i don't see any, when i put to try it, i don't see any....

    Not all NFS servers advertise their shares in a way that is compatible with Kodi, unfortunately. My ReadyNAS NFS server would advertise it's shares (I think because it runs a Rendezvous service) but my FreeNAS NFS server does not, so when setting up my FreeNAS NFS shares I simply typed them in and didn't bother trying to navigate using the folders when adding the source in the GUI.

    Also, you did restart your NFS server after adding the new share? Some servers/services may need this.

    This is how my FreeNAS NFS source looks to me in Kodi:

    Once the source is added it's possible to navigate the NFS share in Files, or scan the library (in my example above, all sub-folders/directories below the media folder are accessible to Kodi).

    Read only is possible, just configure the NFS export with the "ro" setting. Based on your configuration, the problem is most likely that you've granted access to the wrong IP address.

    If you continue to have problems, post your /etc/exports file, and a link to your full Kodi debug log (use a pastebin site for the debug log, then paste a link).

    ... and here's a crashlog from last Monday ...
    based on Milhouse : LibreELEC devel-20160724223031-#0724-geb89f33


    The reason for that crash is due to a patch included in the #0724 build (and since removed). Please don't confuse this thread with details from my builds - they are quite different to Crashes or problems with my builds should only be reported in the relevant Kodi forum test builds thread.

    Are you sure you meant to restrict access to - that's likely to be an unusual IP address for a LibreELEC client (more likely to be the IP address of your router/gateway). Or did you mean to grant access to the entire subnet, ie. in which case you're missed off "/24".

    Does the user on your Fedora system have id 1000? What user owns the files in the share, and when logged in as this user on Fedora what is the output of the "id" command?