no time yet to finish, sadly its a mess so nothing you can do quickly in the evening 
Posts by CvH
-
-
hmm looks strange, pls try to force a add-on repository update and try again
-
pls try also a image from test.libreelec.tv, they include a much more recent kernel (5.15 at this time)
likewise they ninja changed the the chips at the board at some time
Luckily its a Hauppauge Card so the support should be doable at some point.
If it still does not work with the 5.15 kernel try to report it to https://github.com/b-rad-NDi/Ubun…-kernel-builder, he is the driver dev that does the upstreaming to the kernel for Hauppauge/WinTV
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
SMB1 was disabled by default for LE10/K19.
You have a 7 year old low end NAS that was not up to date at release date - so the chances are high, that it just supports SMB1 at all.
Try allowing SMB1 at the Kodi settings, this should work already.
Not sure if there is a additional NAS update that maybe fixes anything for you
-
Opened a PR to "fix" it.
[nfs] change connection timeout to 15sec by CvH · Pull Request #20475 · xbmc/xbmcDescription Change the connection timeout of the nfs client to 15 sec. Motivation and context Since #15686 kodi fails to playback files from a nfs share if the…github.com -
Your NAS is likely horrible outdated (software wise) so it can only handle SMB1 connections.
You should really not use SMB1 anyway, besides the security problems it also includes a lot problems connected with kodi.
You can switch Kodi to allow SMB1 connections or the better fix is to switch you shares to NFS. You NAS should allow that and you can enable SMB + NFS at the same time so you have no additional problems.
-
if anyone is wondering how it works
/storage/.kodi/userdata/advancedsettings.xml
XML<?xml version="1.0" encoding="utf-8"?> <advancedsettings version="1.0"> <network> <nfstimeout>15</nfstimeout> </network> </advancedsettings> -
try to refresh the repository
-
I use a 6TB drive in a setup too for LE+Media (no NAS etc).
I already lost my data because I needed to redo something so the data was lost too
I would really avoid such setups, better add a USB Stick or something.
-
can you try if it works with yatse ?
-
it is easily possible that some random problem is created by that, no fix for that
if you don't need the "latest dvb drivers" don't activate them !
-
WARNING: Manual update with settings addon from 10.0.0 to 10.0.1 just lead to "factory reset" to 10.0.0 here with lots of garbage in
That is very likely due a file system corruption, most likely your SD Cards is dead. Ofc could be the result of a weak power supply and whatnot too.
-
PS: Freezers seem to be a known issue on Intel N3700: Click!
this should be fixed in more recent kernels (we already ship)
But the issue sounds like this I think.
Not sure what might be the solution here, maybe try an LE 11 test version if it works there ?
-
Quote
Up until v19, NFS access was "wait forever" but this sometimes causes UI deadlocks. Hence this was changed to a 5s wait by default, and a property added to advancedsettings.xml to allow the user to configure it. See https://github.com/xbmc/xbmc/pull/15686. On my system 5s is way too short, hence I have restored the previous wait forever with the following entry in advancedsettings.xml
-
I never tried this option but perhaps it'll work for you, via the advancedsettings.xml : https://kodi.wiki/view/Wake_on_lan
the server is already woken up and is reachable so WOL won`t help here
The NAS is active 24/7
what brand of NAS do you have ?
-
Would it help to mount the device from the fstab?
https://wiki.libreelec.tv/how-to/mount_network_share#smb-shares
-
I try to assemble an image with a more recent version of the TBS driver maybe this helps. Sadly this is all clusterfuck and every time you bump the drivers something else is broken. That's sadly the pain with drivers that are not at the linux kernel. Very likely a situation that get never fixed.
I let you know when I have assembled a new image.
