Kodi Community Forum
v17 LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: v17 LibreELEC Testbuilds for x86_64 (Kodi 17.0) (/showthread.php?tid=269815)



RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Ichabod Fletchman - 2016-08-02

(2016-08-02, 12:20)_Spook_ Wrote:
(2016-08-02, 12:16)Ichabod Fletchman Wrote:
(2016-08-02, 11:40)_Spook_ Wrote: Hi, I have the same box and have no problems with getting 3840x2160 at 60hz in GUI. Works just fine. So I would guess that it's an issue with AVR or TV. Because this has worked fine for some time for me.

EDIT: And I use the HDMI 2.0 port connected through a Marantz NR1606 AVR to a LG 65E6 TV.

If it is working for you, then I have hopes that I can do something to get it working.
But do you know why Windows 10 works at 3840x2160 60hz and LibreELEC doesn't?
It worked out of the box for me. I moved the SSD from a NUC6i5SYK to the NUC6i7KYK without any problems and the 3840x2160@60Hz was then set up as default.

I will check this a bit more when I get home from work.

I would appreciate that, but at the same time I hope you don't ruin your current setup. It would be tragic if you change a setting and ends up like mine. Big Grin


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - jan-g - 2016-08-02

(2016-08-02, 08:21)FernetMenta Wrote:
(2016-08-01, 23:53)jan-g Wrote: So, this evening I was watching a 12 years old Progressive xvid file.
I have no interlaced files in my library and deinterlacing is set to off and post processing for this file to on.

MediaInfo 0.7.83
Width : 624 pixels
Height : 352 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (23976/1000) fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive

but when I looked at the Player process info, it states:
Deinterlace method: yadif=1:-1:1

this doesn't seem right, the file is clearly progressive and no deinterlacing should be active.
or am I misreading?
using latest #801 build (with nvidia 340.96)

the last :1 means adaptive mode. yadif is always engaged and the filter only deinterlaces if the content is interlaced.

@FernetMenta
thanks for clarifying, and many thanks for your amazing work on kodi.


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Tequilla9 - 2016-08-02

again a noob question :/ Do I have to create the autostart.sh file by myself cause I can't find it. I guess it shoud be in /storage/.config?

this schoud be in the script:

FB_TYPE="$(grep '^0 ' /proc/fb | sed 's/[^[Confusedpace:]] //')"

if [ "$FB_TYPE" == "inteldrmfb" ]; then
OUTPUT=`/usr/bin/xrandr -display :0 -q | sed '/ connected/!d;s/ .*//;q'`
for out in $OUTPUT ; do
# Hack - something is not yet fully right
/usr/bin/xrandr -display :0 --output $out --set "Broadcast RGB" "Full"
/usr/bin/xrandr -display :0 --output $out --set "Broadcast RGB" "Video 16:235 pass-through"
# Seems there is a little race somewhere on some outputs
# Turn the display shortly off and on again
if [ -e "/storage/.config/forcedisplay" ]; then
/usr/bin/xrandr -display :0 --output $out --off ; /usr/bin/xrandr -display :0 --output $out --auto
fi
done
fi


thx for your help ....


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Milhouse - 2016-08-02

(2016-08-02, 11:52)_Spook_ Wrote: @Milhouse just curious, offically Kodi is at alpha3 right? Just wondering since in build #0731 here it was pumped to beta 1. Are there different releasecycles for public and the the on you use here?

The official release version of Kodi has been tagged as Alpha3. Now that Alpha3 is released, the development of Beta1 begins. The code in these builds is from Beta1. You'll notice that these builds were using "Alpha3" source code since #0701.


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Milhouse - 2016-08-02

(2016-08-02, 13:47)Tequilla9 Wrote: again a noob question :/ Do I have to create the autostart.sh file by myself cause I can't find it. I guess it shoud be in /storage/.config?

Yes, you'll need to create it if it doesn't exist. The filename is: /storage/.config/autostart.sh


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - tinzarian - 2016-08-02

(2016-08-01, 00:59)Milhouse Wrote: Thanks.

Kodi segfaulting due to NFS everytime it is shutdown is not good. I'm seeing that here too - will try and work out when that started.

As for your two logs, both systems (one with 4.7.0 kernel, other with 4.4.7) appear to complete the shutdown more or less normally.

Presumably with 4.4.7, the machine is left in a state where it can be woken up (from power off) on receipt of an IR signal, and this isn't happening since 4.6-rc4. This would look like a kernel (and/or BIOS) bug of some sort. Since the machine has been "powered off", I guess you are resuming from the S5 sleep state, which is no longer working since 4.6-rc4.

I guess it's sort of similar to wake on lan, and is a feature on these and maybe other (Zotac) boxes.

So what now, what's next to get to the bottom of this and get it fixed?

And in the meantime, how do do I make LE build with kernel 4.4.7? I've been looking through the git but couldn't find an obvious setting.


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - _Spook_ - 2016-08-02

(2016-08-02, 14:21)Milhouse Wrote:
(2016-08-02, 11:52)_Spook_ Wrote: @Milhouse just curious, offically Kodi is at alpha3 right? Just wondering since in build #0731 here it was pumped to beta 1. Are there different releasecycles for public and the the on you use here?

The official release version of Kodi has been tagged as Alpha3. Now that Alpha3 is released, the development of Beta1 begins. The code in these builds is from Beta1. You'll notice that these builds were using "Alpha3" source code since #0701.

Ofcourse Confusedlapintheface:


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - _Spook_ - 2016-08-02

(2016-08-02, 12:25)Ichabod Fletchman Wrote:
(2016-08-02, 12:20)_Spook_ Wrote:
(2016-08-02, 12:16)Ichabod Fletchman Wrote: If it is working for you, then I have hopes that I can do something to get it working.
But do you know why Windows 10 works at 3840x2160 60hz and LibreELEC doesn't?
It worked out of the box for me. I moved the SSD from a NUC6i5SYK to the NUC6i7KYK without any problems and the 3840x2160@60Hz was then set up as default.

I will check this a bit more when I get home from work.

I would appreciate that, but at the same time I hope you don't ruin your current setup. It would be tragic if you change a setting and ends up like mine. Big Grin

No chance of that. But there is nothing special with my setup as I can see.

Have you implemented this: https://downloadcenter.intel.com/download/26061/HDMI-2-0-Firmware-Update-Tool


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Ichabod Fletchman - 2016-08-02

(2016-08-02, 15:23)_Spook_ Wrote:
(2016-08-02, 12:25)Ichabod Fletchman Wrote:
(2016-08-02, 12:20)_Spook_ Wrote: It worked out of the box for me. I moved the SSD from a NUC6i5SYK to the NUC6i7KYK without any problems and the 3840x2160@60Hz was then set up as default.

I will check this a bit more when I get home from work.

I would appreciate that, but at the same time I hope you don't ruin your current setup. It would be tragic if you change a setting and ends up like mine. Big Grin

No chance of that. But there is nothing special with my setup as I can see.

Have you implemented this: https://downloadcenter.intel.com/download/26061/HDMI-2-0-Firmware-Update-Tool

Yes I have already installed that. I tested my MacBook with HDMI into the TV a few minutes ago and I got 2160 60hz. So it is just the NUC I'm having the problem with.
Maybe it is a BIOS setting/s? I have changed various settings in the BIOS to no avail, but it may be something I missed.


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - _Spook_ - 2016-08-02

(2016-08-02, 15:27)Ichabod Fletchman Wrote:
(2016-08-02, 15:23)_Spook_ Wrote:
(2016-08-02, 12:25)Ichabod Fletchman Wrote: I would appreciate that, but at the same time I hope you don't ruin your current setup. It would be tragic if you change a setting and ends up like mine. Big Grin

No chance of that. But there is nothing special with my setup as I can see.

Have you implemented this: https://downloadcenter.intel.com/download/26061/HDMI-2-0-Firmware-Update-Tool

Yes I have already installed that. I tested my MacBook with HDMI into the TV a few minutes ago and I got 2160 60hz. So it is just the NUC I'm having the problem with.
Maybe it is a BIOS setting/s? I have changed various settings in the BIOS to no avail, but it may be something I missed.
Is it connected directly to TV? Tried differen cable?

Can't think of any BIOS settings that should affect the setup of video output. How much memory do you have in the NUC? Try dedicating more memory to display from the BIOS settings.

Hmm...can't think of anything else.


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Ichabod Fletchman - 2016-08-02

(2016-08-02, 15:32)_Spook_ Wrote:
(2016-08-02, 15:27)Ichabod Fletchman Wrote:
(2016-08-02, 15:23)_Spook_ Wrote: No chance of that. But there is nothing special with my setup as I can see.

Have you implemented this: https://downloadcenter.intel.com/download/26061/HDMI-2-0-Firmware-Update-Tool

Yes I have already installed that. I tested my MacBook with HDMI into the TV a few minutes ago and I got 2160 60hz. So it is just the NUC I'm having the problem with.
Maybe it is a BIOS setting/s? I have changed various settings in the BIOS to no avail, but it may be something I missed.
Is it connected directly to TV? Tried differen cable?

Can't think of any BIOS settings that should affect the setup of video output. How much memory do you have in the NUC? Try dedicating more memory to display from the BIOS settings.

Hmm...can't think of anything else.

Yes it is a direct run from TV to NUC and Yes, I have tried a different cable (both 'High Speed' HDMI 2.0).
I have 8GB RAM, and I have already tried different memory settings for graphics in BIOS.
I presumed this couldn't be done with the current linux kernel and was about to give up for a while. But since you have it working, I guess I'm going to keep at it knowing that it is possible.


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - _Spook_ - 2016-08-02

It is definelty possible. Just for fun I tried a clean install and it also works out of the box. So don't give up.


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Ichabod Fletchman - 2016-08-02

(2016-08-02, 15:44)_Spook_ Wrote: It is definelty possible. Just for fun I tried a clean install and it also works out of the box. So don't give up.

Wow, well tomorrow I will do some more tests and hopefully find an answer. Thanks for the help.


RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - Milhouse - 2016-08-03

New LibreELEC.tv Krypton build #0802b: Generic
(Supercedes previous build)

Code:
# uname -a
Linux NUC 4.7.0 #1 SMP Tue Aug 2 22:32:27 BST 2016 x86_64 GNU/Linux

# lsb_release
LibreELEC (Milhouse) - Version: devel-20160802223029-#0802b-gfb39931 [Build #0802b]

Based on tip of LibreELEC.tv master (fb39931f, changelog) and tip of XBMC master (f5f9dc51, changelog) with the following modifications: Build Highlights:
  1. More libcec updates
  2. inputstream.mpd and inputstream.smoothstream updates
  3. #0802b: PR:10217: [linux] fix datadir (KODI_HOME) detection
Build Details:
  1. LibreELEC.tv:
    • kodi: update to 17.0-alpha3-fc46cf2 (PR:592, 5 commits, 28 files changed)
    • RPi: Fix Kodi build failure due to aetempo commits (PR:595, 1 commit, 1 file changed)
    • projects/imx6: update kodi patch for 17.0-alpha3-fc46cf2 (PR:596, 1 commit, 1 file changed)
  2. XBMC:
    • VideoPlayer: fix pixel format for ffmpeg based hw decoders (PR:10213, 1 commit, 1 file changed)
    • [xbmc][improvement] Fix detection of KODI_HOME (PR:10180, 2 commits, 5 files changed)
    • [PVR][json-rpc] Added field PVR.Fields.Channel.isrecording (PR:10179, 1 commit, 3 files changed)
    • [xbmc/fix] Fix crash on shutdown (PR:10204, 1 commit, 3 files changed)
    • [xbmc[[cleanup] Add a variadic overload to AddFileToFolder to simplify usage (PR:10012, 2 commits, 21 files changed)
    • [settings] restore input devices to system, and move json-rpc app set… (PR:10201, 1 commit, 5 files changed)
    • fix listprovider updating (PR:10203, 3 commits, 2 files changed)
  3. libcec:
    • added: enduring events (long press) in eventghost. fixes #188 (240b195c)
    • Merge branch 'pr192' into v4 (44a3d14c)
    • added: TransmitSystemAudioModeRequest() (1157d109)
    • fixed: send a <system audio mode request> when an avr is found and the source is activated (73546ee1)
    • Merge branch 'pr208' into v4 (4c75c4de)
    • Fix TDA995x check, part 2 (2bd62826)
    • TDA995x: Add missing std:: namespace (85709f47)
    • Merge branch 'pr214' into v4 (511163e7)
    • Fall back to look for libudev.pc if udev.pc is not usable (298e62bd)
    • Merge branch 'pr231' into v4 (66deb68d)
    • Merge branch 'v4' (0f2be44e)
    • added: EnableAudio() API command (f7551592)
    • added: udev rule to prevent modemmanager and mtp from probing the CEC adapter, which prevents it from working right after it gets plugged in (71dbfcdc)
    • fixed: missing param check in TransmitSystemAudioModeRequest() in 1157d1095ac5e406b4163d3950d77b716990ec23 (62b8520c)
  4. inputstream.mpd:
  5. inputstream.smoothstream:
  6. pvr.stalker:
    • session manager (PR:71, 4 commits, 15 files changed)
  7. xbmc/master (FernetMenta):
    • Commits no longer in build:
      • VideoPlayer: fix handling of progressive content in RenderManager (37bdf1b7)
  8. Additional commits/pull requests/changes not yet merged upstream:



RE: LibreELEC Testbuilds for x86_64 (Kodi 17.0) - axbmcuser - 2016-08-03

@Milhouse
I saw that your first (unposted) uploaded version of #0802 seemed to be broken (black screen, cursor at top left - looks like KODI itself does not start up after LibreELEC boot).
I guess you did some fixing. I have the same problem with my own updated compile of LibreELEC just now - any hints what caused the problem so i can fix it?