The .tar archive only contains files (nothing to do with ext4) so the only thing you'll need to unpack on Win7 is a tool like WinRAR. If you then try to restore specific Kodi files from a Linux install to Windows you'll have issues with file paths (as Win/Linux use different conventions) and some Linux preferences in guisettings.xml do not exist in Windows. Kodi has never officially supported cross-platform config changes so sometimes it works, and sometimes it doesn't.
Posts by chewitt
-
-
No idea if OpeneELEC is supported.
None of our current add-ons are compatible with legacy OE releases.
-
The CPU in the WP1 is too weak for software decoding of DRM'd content. It's not something we can solve in software.
-
No explanation of the build environment (which distro etc.) so it's hard to comment. Also completely unrelated to the original post (not the same issue).
-
cron expects /full/path/to/binary when executing things so plain 'connmanctl' won't work
-
"systemctl restart kodi" will restart Kodi not the whole box. The fact that the list only updates at boot time is a known issue and something we'll look to address when we rewrite the addon for LE10.
-
Please retest using the current Beta release. We will not fix issues in 8.2.5 even if we can diagnose them, and the Beta has never everything.
-
If that's the case it's a Kodi GUI bug and not something LE specific .. and you need to report to Kodi developers via their GitHub issue tracker.
-
You can add "ssh" to kernel boot params to force SSH service start. On a Raspberry Pi boot params are in cmdline.txt .. we have never (not even back in OE days) supported forced start from a file called 'ssh' in the boot partition.
-
Do I have a question in the build for amlogic s905 * how does it work, using amremote or meson-ir?
LE 9.0 images use meson-ir
-
The forum attracts pharma spam, e.g. f00d suppl3ments and annoying a few users with censored words list is considerably less effort for the forum staff than cleaning up the spam that gets posted without it. Sorry
-
The release images for LE 8.2.x were compiled on Ubuntu 16.04 .. so perhaps use an older VM to build with. We have no real-world interest in maintaining the compilability of older releases on newer platforms.
-
IMHO docker is the right option for people who want to load up on NAS apps (which appears to be the case sometimes) but for a basic home sharing setup where MariaDB is the only server app required I see no harm having it as a native add-on. The only thing that surprises me is that it's taken so long before someone did the work for the add-on
-
Provide a Kodi debug log please.
-
That's a Kodi debug log not the systemd journal log (read post #2) so it doesn't show anything useful. And there's nothing wrong with the certificate on the update server .. but your device has broken NTP so the current datetime is before the validity of the cert starts; hence it throws an error.
-
I'm not expecting the kernel patch sets to be merged quickly as it touches a bunch of code and everyone's aware that it lays the groundwork for how HDR is handled in other SoC/GPU types .. so there's lots of chefs in the kitchen. LE 10.0 is far enough out that it should be a safe 'yes' and LE 9.0 is a definite 'no' but hopefully one of the interim LE 9.x releases we make between them will add support to the K18 codebase.
-
Share the systemd journal again (as in post #3) please.
-
It's technically possible to create two audio paths with some asound.conf magic, but the alsa routing is hardware specific (not generic) and alsa config is one of the Linux "dark arts" so you're unlikely to find a nicely written howto guide for your specific hardware. Should you learn and figure something out on your own you'll also discover that the audio paths through the TV and the AVR result in slightly different timings, and this is something that Kodi cannot adjust for (audio delay can be configured globally not per-output) so there's a high chance you end up with a subtle but annoying reverb effect.
