Posts by chewitt

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.)

Sync Playback to Display tells Kodi to use the display clock for sync purposes, but passthrough audio requires VideoPlayer to use media for clock sync (else you are modifying the source, which is not true passthrough) so if you enable SP2D passthrough is automatically disabled. This is different from Jarvis where SP2D is effectively broken but a collection of hacky things kind-of works. Krypton fixes things, so in summary: Krypton != Jarvis.

The forum "search" function is the magnifying glass icon top-right on the screen.

The lack of documentation is bad, but also a good n00b filter. Over the years we noticed those who will be successful in their attempts to create custom builds (and have some dev skills) figure out the build system quickly and get on with things relatively unaided as it works logically and already contains a wealth of prior-art which serves as the instruction manual. Those who have no skills or aptitude for the task will continue to ask in forums/IRC for howto guides. It's fairly easy to spot the first group from the questions asked. Carry on

systemctl stop kodi.service
rm -rf /storage/.kodi/temp
systemctl start kodi.service

That normally frees up a chunk of space. If you need more you're looking to prune thumbnail caches which is a little more advanced.

Create a diff patch of your changes from the root folder of build.LibreELEC-RPi2.arm*/linux-4.9 and place in projects/RPi2/patches/linux/linux-002-mystuff.patch or in packages/linux/patches/ with a suitable sequence number (patches are applied in order) then re-run the build command. The linux package will be cleaned and rebuilt with the patch applied. If this fixes something that others would benefit we'd also encourage you to PR the patch to our git repo so it can be included until it works its way into mainline kernel.

Compile - LibreELEC

Hard to guess what the root issue is but something add-on related would be my guess. If you took a backup in OE before starting it will be quickest to create a new SD card and then selectively restore things of importance. If you didn't and you are only seeing the Jarvis splash screen you can SSH into the box and rename /storage/.kodi to /storage/.kodi-old - then once the system is up you can stop Kodi and selectively restore things as required. If you are seeing the first LE boot splash and the box is fully rebooting that won't be possible and you'll need to remove the SD card and mount the storage partition in Linux to rename .kodi to .kodi-old before doing the same selective restore. You can also try clean install and restoring the backup, but that probably gets you back to the same boot-loop point.