Kodi Community Forum

Full Version: Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
i used root account only to get logs.
i currently run:
$ kodi --version
16.1 Git:c327c53 Media Center Kodi
Please open your own thread as this is off topic.
(2016-08-07, 18:27)fritsch Wrote: [ -> ]Please open your own thread as this is off topic.

You ment my post?

I use the setup provided by this thread so i thought here is the correct place to ask if something breaka after an upgrade.
Nope - that was @maurer. In your case most likely the "inputstream" addon causes this issue, which no requires a not yet packaged up2date version.
(2016-08-07, 20:07)fritsch Wrote: [ -> ]Nope - that was @maurer. In your case most likely the "inputstream" addon causes this issue, which no requires a not yet packaged up2date version.

So for now I will downgrade to
17.0~git20160726.0200-2b8e204-0xenial_amd64.deb (lying around in apt cache) which works with current inputstream version.

Now I have to wait on which package to get updated? kodi-inputstream-mpd or kodi itself?
Where could I find more information when I can go upstream again?

thanks in advance
No further information, no timeline yet. Please wait and keep the cached file.
I just installed Ubuntu server 16.04.1 and Kodi (nightly) with the instructions of the first post, also installed Intel drivers 1.7.1.

But I have a problem: screen goes blank in random times, even when idle in the main screen.

Looks like refresh rate is quicly changed and then changed back again. Same also happens when I go to settings screen of resolution and refresh rate, there screen goes blank and Kodi asks if I want to keep the change even before I do anything,

Cables are OK, I have no problems with earlier install of Ubuntu server 14.04 and Kodi (nightly).
Mainboard has Intel H87 chipset with Haswell processor, using HDMI connection.

So what is going on? Is there some known kernel/driver bug that causes this?
Post all the Logfiles, please. Including dmesg after it happens.
(2016-08-09, 13:46)fritsch Wrote: [ -> ]Post all the Logfiles, please. Including dmesg after it happens.

kodi@Kodi:~$ dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/22801170/
kodi@Kodi:~$ DISPLAY=:0 vainfo | pastebinit
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
http://paste.ubuntu.com/22801190/
kodi@Kodi:~$ cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/22801213/
kodi@Kodi:~$ dmesg | pastebinit
http://paste.ubuntu.com/22801221/
kodi@Kodi:~$ id | pastebinit
http://paste.ubuntu.com/22801240/
kodi@Kodi:~$ amixer | pastebinit
http://paste.ubuntu.com/22801252/
Same with 4.7 Kernel?
I noticed these in kodi.log
ERROR: Window Translator: Can't find window musiclibrary
ERROR: Window Translator: Can't find window musicfiles
ERROR: Window Translator: Can't find window videolibrary
ERROR: Window Translator: Can't find window librarysettings

I was using Confluence skin (tried with addons download and also via Github download) , now with stock Estuary skin looks like the problem is gone. But why Kodi tries to change display frequency if a skin element is missing?
I'll try again later when Confluence is synced with latest changes.
Hi Fritsch, I read in Milhouse's Libreelec thread that EGL has been removed from the later builds in krypton, is this the same for nightly/fernetmenta repo's as well? Apologies if I've got this wrong.
Bullshit!
I got it wrong then, thanks!
EGL was merged long ago into the v17 codebase ... Milhouse removed the automatic setting of the proper xrandr mode and the related kodi setting, that's all.

So, just add the relevant command manually like posted in the forum thread in Milhouse's thread and switch use Limited Range on -> done.