• 1
  • 112
  • 113
  • 114(current)
  • 115
  • 116
  • 342
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
Fix your switch / cable. The device has absolutely no problem running at gigabit if the infrastructure is setup correctly.

Concerning the intermittant black screens: No Debug Log no problem
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Hi!

I just tested OpenELEC-Generic.x86_64-6.0-devel-20151016183920-r21488-g163fae9.tar but it did not work well (Kodi does not start) since the kernel is too old (integrated intel skylake i5-6500 with HD Graphics 530).

With a nvidia gtx950 kodi is starting but at 2160p, interface and videos are stuttering - even without any framedrops. It seems to be fine for 24p source videos but not so for 25fps source videos. kodi switches back to 50hz in a 25hz video even if i set the system refresh rate to 25hz.

Anyway i just tested this release: OpenELEC-Generic.x86_64-6.0-devel-20151016183920-r21488-g163fae9.tar

Would it be possible to compile it with 4.3-rc6 or at least 4.2 so that i can test my skylake hardware? With the current 4.1 kernel and the i915 kernel boot "hack" i don't get more than 30fps on hdmi 2.0 - and yes - my mainboard has hdmi 2.0 (at least it should)

PS: it is actually not kodi that fails with skylake but x11 - thats also the reason why i don't have any kodi logs.
Reply
Use the experimental build from one page back. Also latest build from Jarvis folder has 4.3. Official upcoming Openelec final 6.0 won't work on your hw anyways.

Quote:With a nvidia gtx950 kodi is starting but at 2160p, interface and videos are stuttering - even without any framedrops. It seems to be fine for 24p source videos but not so for 25fps source videos. kodi switches back to 50hz in a 25hz video even if i set the system refresh rate to 25hz.

This has been answered many times. We play the video at the maximum refreshrate r_i for which r_i % fps == lowest value and 2160p is the resolution your display tells us as "default mode". Furthermore all my "Isengard" backport builds are only meant for Intel only. At this time of the EGL patches no nvidia debugging was done. For nvidia choose the Millhouse builds or the Jarvis version.

The version which should run on your intel hw is: http://fritsch.fruehberger.net/experimental/ <- again Isengard is old and outdated from dev point of view - Jarvis is the future.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Thank you.

Seems i messed up the builds. I will test it asap.

Thank you again.
Reply
This version:
(Is this Jarvis folder version?)
http://fritsch.fruehberger.net/experimen...1801a4.tar

Does work, has a 4.3-rc5 kernel (4.3-rc6 was released on the 18th ...) but i cannot use 2160p. It switches to the resolution but my tv says "no signal" and a few seconds later kodi switches back. It is the same for 1080p 24fps and 29.xx fps and all 2160p x XXXfps.

1080p 25fps,30fps and 60 fps do work.


I deleted all logs, rebooted and tried to switch to 2160p - kodi switched back.

The log:
http://xbmclogs.com/p5wxvnq0c
Reply
you log says xrandr doesn't report any modes >1080p

edit: scrap that, I'm just blind

it tries to switch to UHD, but apparently fails
Code:
13:55:57 T:140301553141632    INFO: XRANDR: /usr/lib/kodi/kodi-xrandr --screen 0 --output DP2 --mode 0xc6
13:55:57 T:140301553125120   DEBUG: CALSAHControlMonitor - Monitored ALSA hctl value changed
13:55:57 T:140301542590208   DEBUG: CActiveAE - device change event
13:55:57 T:140301553125120   DEBUG: CALSAHControlMonitor - Monitored ALSA hctl value changed
13:55:57 T:140301553141632    INFO: GL: Maximum texture width: 8192
13:55:57 T:140301553141632   DEBUG: ------ Window Init (DialogYesNo.xml) ------
13:55:57 T:140301553141632    INFO: Loading skin file: DialogYesNo.xml, load type: KEEP_IN_MEMORY
13:55:57 T:140301553141632   DEBUG: NotifyXRREvent - notify display reset event
13:55:57 T:140301553141632   DEBUG: RecreateWindow - current output: DP2, mode: 0xc6, refresh: 30.000
13:55:57 T:140301553141632   DEBUG: OnLostDevice - notify display change event
13:55:57 T:140301542590208    INFO: CAESinkALSA - Unable to open device "surround21:CARD=PCH,DEV=0" for playback
13:55:57 T:140301542590208   DEBUG: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=0" may be unconnected (no ELD data)
13:55:57 T:140301542590208   DEBUG: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=1" may be unconnected (no ELD data)
Reply
Try manually: xrandr --output DP2 --mode 0xc8

and see what is happening, please and post dmesg | pastebinit after it. I don't see kodi switching at all in your log.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Short explanation:

As you can see i am using the internally called DP2 port. My board (http://www.asrock.com/mb/Intel/Fatal1ty%...ing-ITXac/) uses alpine ridge to convert the displayport signal to all full flavourd hdmi 2.0 signal. But randx does not report 2160p 60hz. If i try to use the other hdmi port (the board has two) it reports to use internally called "hdmi3" port and i get no signal at all.
Reply
(2015-10-20, 14:09)fritsch Wrote: Try manually: xrandr --output DP2 --mode 0xc8

and see what is happening, please and post dmesg | pastebinit after it. I don't see kodi switching at all in your log.

I don't get a signal after manually switching. Had to manually switch back to 4a.

dmesg:

http://xbmclogs.com/pjpnc5av7
Reply
I was about to ask, how you convert from DP to HDMI. The place to file this bug is: bugs.freedesktop.org in DRM/intel section - I wish you luck - cause I think the oss driver kernel / xserver has no code yet for this alpine ridge at all.

As wsnipex points out kodi does the right job and switches.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Thank you.

One last question - is there a binary firmware which i could load?

[ 0.218007] i915 0000:00:02.0: Direct firmware load for i915/skl_dmc_ver1.bin failed with error -2
[ 0.218011] [drm:i915_firmware_load_error_print] *ERROR* failed to load firmware i915/skl_dmc_ver1.bin (0)
[ 0.218071] [drm:finish_csr_load] *ERROR* The driver is built-in, so to load the firmware you need to
[ 0.218071] include it either in the kernel (see CONFIG_EXTRA_FIRMWARE) or
[ 0.218071] in your initrd/initramfs image.
Reply
Yes skl needs firmware oe kernel needs to include it. That's the pain of early adapters :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2015-10-17, 10:57)fritsch Wrote: For those upgrading to Ubuntu Wily:

Sadly they package a broken libva / libva-driver-intel for Braswell chips which cannot decode 4K HEVC. I felt free to open a bug: https://bugs.launchpad.net/ubuntu/+sourc...ug/1507112
Hopefully wsnipex will also build libva and i965-va-driver for upcoming Wily.


Once again it's a single package that makes this EGL / VAAPI work _not_ work out of the box :-( I should have filed that earlier.
I've helped a little bit by confirming this bug. We'll see if it helps, but probably no way for Wily :-(
Reply
As long as we have wsnipex - that won't be a problem for us :-) Add one ppa and be done ... sadly the kernel is also not up2date enough - upcoming 4.3 will solve the remaining issues.

So:
Kernel 4.3
Mesa 11.0.3
libva 1.6.1

^^ this is what we need and all is fine.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
So everything will be OK for 16.04 LTS. Until this wsnipex ppa (with custom kernel).
Reply
  • 1
  • 112
  • 113
  • 114(current)
  • 115
  • 116
  • 342

Logout Mark Read Team Forum Stats Members Help
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server18