• 1
  • 7
  • 8
  • 9(current)
  • 10
  • 11
  • 128
Linux VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04
Wsnipex has restored the working verions from June. As frodo is not actively developed anymore, we keep that version for now. When gotham gets near final / vpp gets merge, we will update the packages to a gotham version.

Edit: after vpp gets merged, you can just use mainline :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Do you still need logs? Will be happy provide them tomorrow if so ;-)
Nope - we roled back to what was tested within OpenELEC and also will be shipped with 3.2 - Frodo developing is over. We will replace the build with a gotham one as soon as it is in - to start gotham testing.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Looks like I might be seeing this issue too. XBMC is crashing when attempting to play any LiveTV MPEG2 streams.

Do I need to do anything special to revert to the working version?
remove all your xbmc packages (xbmc-bin xbmc) you can find them with dpkg -l |grep xbmc afterwards do sudo apt-get update followed by sudo apt-get clean followed by sudo apt-get install xbmc xbmc-bin

afterwards post: dpkg -l |grep xbmc
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
faster:
sudo apt-get install xbmc=2:12.2~git20130618.1944-vpp-0raring xbmc-bin=2:12.2~git20130618.1944-vpp-0raring

replace raring with your ubuntu version
Thanks! I started with the method suggested by wsnipex (replacing raring with precise) and everything appears to be working.

If the dpkg listing is needed for debugging let me know and I'll post it.

Can't wait to test the gotham build - the Live TV improvements will be helpful.

Thanks again!
Just forked the XBMC git code and merged the vaapi-vpp pull request. Compiles and works fine, I just had to try it on the latest GIT :-)
This is working for me.
Ubuntu 12.04 LTS amd64
Kernel 3.10.7
MSI C847MS-E33 (Celeron 1.1GHz, Sandybridge)

Is this still the prefered way to get deinterlacing with vaapi?
Tell me another one?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
As far as I know, this is the only one.
Are these changes get's into master someday?
The ones from this ppa - never.

But btbn is working on an extended version, that supports MADI, MCDI, BOB and others - it is currently PRd. But needs some final tweaks.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Hi,

I am facing a segfault when using libva-1.2.1 & libva-intel-driver-1.2.1
with xbmc 13.alpha-7f45288 (downloaded from sources.openelec.tv)
which does not occur with libva-1.1.1 & libva-intel-driver-1.0.20.

CPU is a i3-3220T, Linux kernel version is 3.11.0, the system is
uClibc-based, the binaries are cross-compiled using buildroot.

The segfault happens when playing h264 content:
Code:
libva info: VA-API version 0.34.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/va/i965_drv_video.so
[New Thread 0xa49faba0 (LWP 6221)]
libva info: Found init function __vaDriverInit_0_34
libva info: va_openDriver() returns 0

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa49faba0 (LWP 6221)]
vaCreateSurfaces_0_32_0 (dpy=0xd0ec8f8, width=1920, height=800, format=1, num_surfaces=219852252,
    surfaces=0xa) at va_compat.c:40
I fixed the segfault by reverting this patch:
http://cgit.freedesktop.org/libva/patch/...222ff704f9

Unfortunately my knowledge is too low to tell why the
revert fixes the bug, my guess is that the libva compat
layer was introduced later than this xbmc commit:
https://github.com/xbmc/xbmc/commit/da65...1477b1bbab

Reverting the xbmc commit in question and using a patch
similar to this MythTV patch
http://code.mythtv.org/trac/changeset/3b...eb0/mythtv
did not fix the xbmc segfault however.
Kodi 19.5-Matrix/OpenGLES/gbm (+ PR19558 ) - Linux kernel 5.14.21 x86_64 - ffmpeg 4.4-git (+ patch )
Mesa 22.3.7 with iris driver - VA-API version 1.16.0 + Intel iHD driver version 22.6.3 - libdrm 2.4.116 - libcec 6.0.2
Intel i9-11900T - ASRock Z590 Extreme - BIOS version 2.20
Are the kernel changes from the custom kernel here included in the default kernel for Ubuntu 13.10? Alternatively, is it safe to upgrade to 13.10 and re-use the same kernel images?
a) You can use the stock Ubuntu Kernel 13.10.
b) No idea. I won't switch the next weeks.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
  • 1
  • 7
  • 8
  • 9(current)
  • 10
  • 11
  • 128

Logout Mark Read Team Forum Stats Members Help
VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.0416