Kodi uses the smbclient from Samba which defaults to SMB2, so if you enable min SMB1 and max SMB2 it will use SMB2 and you will not be able to access your SMB1 share. To force SMB1 you need to set min/max to SMB1. You may also need to enable the legacy security option; depending on how ancient the SMB code is in the router.
Posts by chewitt
-
-
Yes, Intel are arseholes for requiring Windows to update firmware. Yes I said firmware. AFAIK the BIOS/firmware are the same thing on a NUC.
-
Yes it is possible to multi-boot an x86_64 device with LE as one of the OS. It's not something we support in our installer though, so you'll need to do a manual install and figure out the sequencing and bootloader bits yourself.
-
Update the NUC firmware. Update the Marantz firmware. Update to the current LE beta. Make sure "sync playback to display" is off.
-
Clean install the current beta. If necessary do a selective (manual) restore of DB files from a previous install .. but you need to lose all the addon cruft that OE added else all we can see in logs is the entire Kodi language addons set updating. I'm sure there's some vide playback in the log somewhere, but I gave up looking for it.
Once you have a clean install .. retest and if necessary run "cat /storage/kodi/temp/kodi.log | paste" and share the URLs
-
udev rules are cummulative so you can add a rule to /storage/.config/udev.rules.d/ that matches on label/uuid and runs fsck on the drive. This will then be a persistent behaviour that is done on each boot.
I'm not sure what the match criterial look like in a rule so you'll need to Google a bit, but the following commit shows a similar rule that matches on HFS+ filesystems and fsck's them so the rest of the rule will look similar:
-
I didn't look (and have no plan to either) but I doubt it's wildly different. Despite all manufacturers claiming their product is unique it's in their own interests (for software support) to not diverge far from the reference designs.
-
s/branch/kernel ..
-
Use the default AM8-AUDIO? device which outputs on HDMI and S/PDIF at the same time - and don't necro-bump old posts.
-
-
I haven't built 3.14 branch for some time, but you need a version of this commit for whatever libmali is being used:
add support for EGL_KHR_debug · chewitt/libmali@9143da0 · GitHub
-
There are paid-for solutions to mounting EXT4 partitions under Windows but it's not worth the effort.
Copy the tar file to the new device and learn how to unpack a tar file from the SSH console. As the saying goes .. it's not rocket sc1ence.
-
Assuming you pass the "understanding the build system" test and can create a working "Generic" image the main issue you'll have with older hardware is GPU drivers. We tend to support current and recent hardware not old hardware; if we still have the drivers it'll work. If not.. more creativity in the build-system is required.
Linux SBC's are pickier with USB/SD when they run shitty/ancient kernels. Run a modern kernel and those issues generally go away.
-
No .. contact the manufacturer. And don't double-post the same irrelevant question.
-
-
If you have more than one output and the BIOS supports display mirroring then it can work; Kodi still outputs to one screen but the underlying hardware will send that one output to both. I doubt NUC's do that though - it's normally a laptop feature.
-
^ that's a good start to the year, although these things usually take a few iterations before being accepted.
-
If all you plan to do is overwrite stuff .. why make the process complicated by manually unpacking the tarball on a Windows box. Just use the restore function in the settings add-on.