Posts by chewitt

Anything that uses autostart.sh is a dirty hack. Their instructions should be updated for 7.0 builds too, and for the same reasons.

17:44:26 19.334791 T:1963106304 NOTICE: ADDONS: Using repository
no support to users of piracy add-ons and repo's, particularly as the crapware in them frequently causes instability issues. Thanks.

The problem is probably timing. The instructions on the MSL website should be adjusted so the function script is triggered/managed by systemd to fit into the OS startup and shutdown sequence. Adding dependencies on network being up etc. then become simple.

I can't script python either, but I can open the file in a text editor and look for /file/system/paths under /opt and experimentally change them to something under /storage. It's probably not a hard change.

(
sleep 10
amixer -c1 set PCM 100%
)&

autostart.sh runs early in the boot sequence but will background and sleep the command for 10 secs which is normally more than enough time for things to come up.

I looked at Dataplicity Developer Hub probably briefly and if their install python script is similar they are trying to write things to locations under /opt that don't exist on LE so yes, it will fail. Modify the python script to use somewhere on /storage and it should work okay.

p.s. If you are installing a Chromium add-on from the Kodinerds repo, please ask Kodinerds for support.

I removed the build after jcdammers confirmed the fix. The 7.95.1 beta will ship with the fix (soon-ish)

It might be worthwhile looking at the unRAID forums as they have a tweaked LE image used with QEMU in their distro.

Virtual is a developer tool used for basic functional and GUI testing. It supports vmware (we dropped vbox as it breaks with every kernel bump and nobody used it). Virtual has no AMD/Intel/nVidia drivers so you will not be able to do GPU passthrough in ESXi. If you wanted to do that you'd need create something custom that has both vmware things (else the OS won't boot) and the video drivers required.

In a Generic/QEMU combo there should be a console on CTRL+ALT+F3 ..but it's not really a 'supported' configuration in the sense you won't find staff that know anything about running it, although we're aware it can be made to work.

It's something already in the to-do list, although (sorry) not the greatest priority. I'd like to target some settings add-on changes for LE9.0.

The 'update channel' function requires 7.0.3 .. it does not exist in 7.0.2.

Thanks to milhouse the cmake issue has been resolved. Slice will skip the v7.90.010 release; next up will be a v7.95.1 beta based on Kodi 17.0-RC2 (RC1 was rather short lived due to a critical Android bug).

Older NUC's are a bit hit/miss unless the firmware is updated. Early firmware is a bit, err, not good

There are no changes to nvidia drivers in 7.0.3 so you will need to use the current alpha (soon to be beta) release.

systemctl stop kodi.service
mv /storage/.kodi/userdata/guisettings.xml /storage/.kodi/userdata/guisettings.old
systemctl start kodi.service

this will "lose" current Kodi GUI config things but you can always reverse the process. Does this solve the issue? I've tested subtitle positioning in a VM install of LE and it works fine so I'm wondering if things have gotten messed up somewhere.

It would help if you described the problem you are trying to solve and shared the patch you are trying to use (and where it came from)?

PuTTY is an SSH client, not a file transfer client.

If you need the ability to resume transfers use rsync or an SFTP software (FileZilla, WinSCP, Transmit, etc.)