Make a backup on the RPi2 before you start. Now remove the binary add-ons, take a second backup. Install to the NUC .. no errors because there are no binary add-ons, then go install them from the repo.
Posts by chewitt
-
-
It's an old noobs install.
-
Spring cleaning is never a bad idea. Take a backup, move it off box. Clean install to the RPi3, then manually extract (from the backup) and copy back only the things you need like DB files, sources.xml etc. - do not "restore" the backup as this also restores all the old OE cruft that you want to leave behind in the cleanup.
-
Over time we found some memory fragmentation issues that affect long-uptime systems. Check free RAM, and if that's the issue, start planning an update to 9.0 as that's when it'll be resolved.
-
perhaps install rEFInd as the boot selector, ISTR there's a thread on that in here somewhere
-
There are GUI approaches but I personally find editing /storage/.kodi/userdata/sources.xml directly is a lot easier.
smb://user:pass@server/share/ is the normal format
-
If that's the active smb.conf on the NAS/server "//192.168.1.92/Recordings" is the network path
-
run "journalctl -b 0 --no-pager | paste" after 40 seconds or so and then share the URL
-
No debug log .. no problem
-
No idea about the AMD stuff, I have always avoided their hardware. GeForce 7025 requires an image that contains the old 304.xx nVidia driver, see here: LibreELEC builds with nVidia 304.xx driver
-
Is "Neptune" a build? if so, you can't get any support here
is installed which means "off sod" rearranged into a less polite sequence -
Running "cat /storage/.kodi/temp/kodi.log | paste" will generate a URL to share the log, but you probably need to enable debug logging and demo the problem by navigating the GUI, which will require you to sit in-front of the box.
-
No RK add-ons will be built until RK support is merged into our master branch. Then the repo will get built and populated. The workaround is self-building the add-on(s) you need based on the unmerged code.
-
Code
echo "options usbhid mousepoll=0" > /storage/.config/modprobe.d/usbhid.conf^ run that command over SSH and after rebooting the config will be persistently applied.
-
Search for vpeter's version of 8.2.3 for Cubox with a 3.14 kernel and see if that improves things.
-
There are a myriad of reasons why "streaming providers" will cause issues. Unless you reveal exactly which streams and providers you're talking about and provide Kodi debug logs that demonstrate what issue Kodi is having there is no point in debating the theory of reasons why things don't work. Of course, if those are pirate streams from IPTV services, you (and we) know why quality is sh1t and you don't need to bother replying.
-
/mnt/md1/Users/AlexGilbert/Media/Videos looks like the internal path on the server which is probably not the network visible path. It's technically possible to create a share path like that, but normally an SMB/Samba server would create something like //192.168.1.92/Media/Videos so it looks unusual, and unusual often means wrong.
-
Win10 (which has been updated by MS to disable gues/anon access) is using SMB3 with authenticated access. You need to use LE 8.2.3 and you need to configure Kodi to use a user/pass when connnecting to the WIn10 shares. If you don't authenticate; access is not allowed to the shares. It's a well known problem with people who don't read release notes.
