Yes, as it contains the contents of /storage/.cache .config and .kodi .. and autostart.sh lives in .config
Posts by chewitt
-
-
kowalmisiek you need to provide a Kodi debug log so we understand what kind of device you are using .. and can see what the issue is
-
I can't speak for a few days ago, but right now 2.3.15.0 is present.
-
In short, no. If there's a reasonable use-case to extend the capabilities of the ffmpeg-tools add-on, a pull-request with changes is welcomed.
-
The x86_64 image has "boot" and "run" options in addition to the default "installer" mode. I forget which is which, but one is a persistent "Live USB" mode and the other is the same but non-persistent. Hit tab at the syslinux prompt (instruction text is on-screen, but not for long before the installer starts).
-
The 4.9 kernel is the same badly written Amlogic 3.14 codebase forward ported to a marginally newer (December 2016) kernel. I've even heard some rumours of a 4.19 version being worked on. I wish everyone the best of luck using them once amcodec is removed
-
Hi Guys.. Was mentioned there was a sky go addon someone had working? Is this a UK version as assume the german one is only for those with German sky? If so where do I find it.
SkyGo is for German users only. There is currently no equivalent for UK users.
-
There are balbes150 test images available in this forum if you want to have a play with 5.0 kernel images. For 1080p/8-bit/2.0 video things are super stable but 4k/10-bit and multi-channel audio development is still work in progress.
-
To manually install LE .. create two EXT4 partitions on a disk; 1GB for "BOOT" and remaining space for "STORAGE" then install any bootloader that works on that hardware and configure it for boot=LABEL=BOOT and disk=LABEL=STORAGE .. and ensure KERNEL/SYSTEM live in the boot partition (and mark it active). That's all our installer does. We use syslinux but GRUB and others are fine. We don't touch boot ever after install.
NB: Team Kodi gave up on maintaining an entire distro (Kodibuntu) but the stable/unstable PPA's are still maintained for use with current Ubuntu.
-
LE requires two partitions and (once you create the installer USB using our USB/SD Creator app) the install process is designed for single-use HTPC devices and it does not support dual/multi boot arrangements. In other words, if you keep pressing "okay" to get past the multiple "this will erase the contents of your disk" warning messages; it will nuke your Windows install. We have no desire to support dual-boot or single partition installs.
-
Current version in the LE 9.0 repo is 2.3.15.0 and we maintain a single repo (it's not mirrored like the Kodi repo) so there's no other source.
-
I'm unable to reproduce on Fusion 11.0.2, the 9.0.1 ova just works as normal/expected.
-
Code
rm /storage/.kodi/userdata/profiles.xml && systemctl restart kodi^ that should work. I've seen the same issue but it's unclear what causes it.
-
Panfrost is making serious progress. It now passes almost 100% of GLES 2.0 tests and Rob Herring + Tomeu Viscuso are making good headway on a proper kernel driver (Rob brings the kernel DRM/DRI knowledge lacking among the core panfrost developers). If the current pace of change continues I'm expecting to switch from the ARM kbase driver to a native one in the next month.
-
If you have fixes for anything please upstream them to the kernel, or at least as far as @Kwiboo's repo where things can be validated and aggregated with other changes we accumulate and prove over time.
-
Kodi forums would be the best place to ask for skin development advice; it's where all the skin designers hang out.
-
-
As long as the wireless chips use the standard (correct) device ID's it shouldn't be an issue as the mainline kernel has reasonably intelligent sourcing of the firmware and nvram files (detecting the ID's and using a lookup table). Current VIM1 does not use the correct ID so once we start condensing images we'll need to hack a solution together (and it being hacky, it probably won't be upstreamable) .. but I have some ideas.
