Posts by chewitt

master according to the build dirs (wrong kernel for 7.0) but make sure it's a full clean build and clear ccache

Are you turning on the TV before the HTPC?

Kodi has no Linux support for Rockchip so LE is not available. There was an OE fork with tentative support at some point but it was a one-man effort that died when Kodi refused the patches for code quality reasons.

I'd ask you report the problem to OpenELEC's developer then; his codebase is no longer our problem

Amlogic support in Kodi is/was massively impacted by the VideoPlayer changes in Krypton and it's not far off a ground-up rewrite. It is improving but still quite a bit of effort to be made. It is likely that Generic/Pi devices enter LE beta and maybe even release while Amlogic things continue in Alpha for a while longer and follow their own sub-schedule. The good thing is we have a bunch of people starting to collaborate on Amlogic support instead of the historic situation where WeTek devs do 95% of the effort and others do the remaining 3-4% in isolation from each other. It's all a bit entangled and progress is slow, but we're making progress

LE team are familiar with Lakka and it's main developer is part of our extended collaboration team. Lakka is originally derived from OpenELEC but has emphasis on support for older hardware (e.g. 32-bit x86). The GPU/graphics needs for retroplayer are much lower than Kodi which allows Lakka to run on a wider range of low-cost maker-board devices.

Could be crap firmware in the USB>SATA bridge used by the drive. Could be unclean mounting from Windows. Have a look at "dmesg" output for error messages. If nothing obvious run "dmesg | paste" and share the URL generated.

I had to close and clean up the PR's (one is enough, no need for three) but support has been merged and will be in v7.90.005

Have a look at the example service file in /storage/.config/system.d/ for a persistent and reliable method of locally mounting remote volumes so they are accessible from the filesystem. If you need written instructions look at Mounting network shares - OpenELEC

For asking .. what make/model of TV is it?

I've seen an IRC chat recently where a user updated from Eden to Jarvis without issues so Isengard to Krypton is not a problem

You should be able to use the installer USB stick to install to another USB stick (it's dumb, don't ask) so you don't disturb the 7.0.2 install. You need to copy the default xorg-nvidia.conf from /etc/X11 to /storage/.config/xorg.conf and edit to set modedebug=true, then reboot and the now-debug and lengthy logfile will be in /var/log/Xorg.0.log.

Unless you tell Kodi that a receiver supports DTS/AC3 etc. it will resample content to multichannel PCM with the number of channels determined by the default Kodi channel config which is 2.0 (stereo). If you enable DTS/AC3 pass-through, it will do it.

en-us

According to nVidia release notes the 367.35 driver we use in v7.90.004 should support the GTX1060. If it's not too late I'd be interested in seeing some debug Xorg log output from the card.

Quote from marv_el

libreelec krypton seems to have problems with two gfx cards. i had the same issue, because i have an onboard nvidia 8800 and a amd radeon 4xxx in my htpc.
after installing krypton i also got the xorg failed to start error (never had this on previous versions), researched and tried for hours. like 1 out of 10 reboots it booted into kodi.
i created a udev rule for the nvidia onboard gfx card like in this thread claimed and it works for me:
LibreELEC

If you wanted to use multiple GPU's in an LE box you'd need identical GPU devices or at least two cards that use the same GPU driver as the Xorg start process doesn't handle multiple active drivers. Even then you'd only get duplicate output as Kodi only outputs video to one display; there's no split screen modes available.

CvH is based in Germany so anything to do with ATSC will be challenging for him to test. If things need to change in the TVH packaging to better support ATSC it's best if you suggest the code changes in PR

If you change the setting via xrandr Kodi responds to the Xorg forced change but does not save it. To save it you'll have to force the change to 0xe4 and then go into Kodi settings and set the same 30.00 setting there. It should then be saved; do "systemctl restart kodi.service" and Kodi should start up in 1080p/30 on reboot.

The kodi-xrandr output looks like a listing of all possible HDMI modes rather than a normal (more limited) EDID based listing of the actual modes supported by the connected TV. Do you have the NUC connected to the TV via an AVR or any kind of video switching device?

BTRFS has some nice features, but 99.999% of our users would have no clue why they're nice or how to use them, and attempting to expose them in a noob-friendly way requires complexity that we don't need for our "fairly dumb Kodi client" use-case. LE (and OE before) have a long-history of applying the Star Trek principle of "the needs of the many outweigh the needs of the few" when it comes to adding niche things.

NB: I think we bumped the kernel and other plumbing things several times since the things in @lrusaks repo were compiled, so that's probably why the add-on in his repo stopped working. If you know how to self-build an LE image it should be "PROJECT=Blah ARCH=Blah scripts/create_addon nameofaddon" to create an up-to-date version.