• 1
  • 282
  • 283
  • 284(current)
  • 285
  • 286
  • 342
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
The new vaapi / libva packages are now in the ppa. Thanks to wsnipex.

Btw. Those only add kabilake / Apollo Lake support - this won't make kodi v17 magically decode hevc-10 bit. So for most users: no change at all.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2017-01-03, 19:55)fritsch Wrote: The new vaapi / libva packages are now in the ppa. Thanks to wsnipex.

Btw. Those only add kabilake / Apollo Lake support - this won't make kodi v17 magically decode hevc-10 bit. So for most users: no change at all.

I upgraded today on j3455(Apollo Lake). kodi v17 can't decode hevc-10 bit.

The command I ran was: apt-get install --only-upgrade i965-va-driver libcec4 libflac8 libva-drm1 libva-wayland1 libva-x11-1 libva1 vainfo

Because there is a problem with grub upgrade.(apt-get dist-upgrade)
Reply
Quote:I upgraded today on j3455(Apollo Lake). kodi v17 can't decode hevc-10 bit.

Nothing new. It's already implemented and will come into v18. If you want it now, you need to compile it from source, including kernel + mesa.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Hello,

I am not sure whether where to report this.

I have a Kodibuntu box with Haswell i3. After upgrading Jarvis to Krypton RC, HD videos would not start or crash Kodi. Looking around I found that both VAAPI and VDPAU was enabled. Disabling this solved the crash.
I have no idea how VAAPI and VDPAU got enabled. I cannot recall if I had such setting in Jarvis or not.

The question is, do we have a problem migrating Jarvis settings to Krypton? In my case, I seem to got bad defaults.

I had another setting-related issue: video post-processing got turned on, causing stuttering when playing ISO DVD images. Disabling it solved the problem.

I have no logs of the upgrade process. I can get logs now, if you would like to have a look, but I am afraid it is too late.
Reply
Please read the first post, we cannot help you without the relevant logfiles.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2017-01-07, 13:46)fritsch Wrote: Please read the first post, we cannot help you without the relevant logfiles.

Sorry, logs are below.
http://paste.ubuntu.com/23749022/
http://paste.ubuntu.com/23749023/
http://paste.ubuntu.com/23749033/
http://paste.ubuntu.com/23749037/
http://paste.ubuntu.com/23749038/
Reply
You don't seem to run this howto. I see Ubuntu 14.04 and a very old kernel / drivers, including vaapi 1.3.0
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Well yes - I installed latest Kodibuntu back then, and I keep updating since then, last time just before the upgrade. So this is anyone gets how keeps a Kodibuntu install running for some time..
Anyway, if I understand correctly, the issue is that Haswell will NEVER work with VAAPI, right? I don't miss that, actually. I only wonder if others might get the same problem when upgrading to Krypton.
Reply
Not sure where you got that from ... we are all running Haswell happily with VAAPI and the original howto in here was written for HSW hardware.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2017-01-07, 14:10)fritsch Wrote: Not sure where you got that from ... we are all running Haswell happily with VAAPI and the original howto in here was written for HSW hardware.

Aha - that explains it. Due to my extremely limited knowledge, I misunderstood the whole thing.

Anyway, back to the original question - so I already had VAAPI enabled back in Jarvis too, but after the upgrade, it stopped working because my kernel/drivers are out of date?
So upgrading to latest Kodibuntu (15 or 16) would probably fix this and let me enable VAAPI?
Reply
We need 0.39.2 of vaapi which 14.04 does not have. You can try wsnipex vaapi ppa.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Checked just now, Kodibuntu is no longer supported. It seems I need to look for some other distro.
Thanks for the help.
Reply
If you'd check the first post - you'd find an easy to do howto for 16.04
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2017-01-07, 15:14)fritsch Wrote: If you'd check the first post - you'd find an easy to do howto for 16.04

I will do exactly that. I realized that the best for me will be a minimal Ubuntu server with standalone Kodi from xbmc ppa. So I no longer get outdated.
Thanks a lot for the help.
Reply
where find hybrid_drv_video.so?

libva info: VA-API version 0.39.4
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
failed to open /usr/lib/x86_64-linux-gnu/dri/hybrid_drv_video.so
Failed to wrapper hybrid_drv_video.so


http://paste.ubuntu.com/23782303/
Reply
  • 1
  • 282
  • 283
  • 284(current)
  • 285
  • 286
  • 342

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