Bug 1011164

Summary: vdpau/vaapi not working
Product: [openSUSE] openSUSE Tumbleweed Reporter: Hubert Mantel <mantel>
Component: X.OrgAssignee: E-mail List <xorg-maintainer-bugs>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: Linux   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: lspci of affected machine

Description Hubert Mantel 2016-11-20 13:41:48 UTC
Created attachment 702828 [details]
lspci of affected machine

Trying to use vaapi on the following hardware does not work:

http://www.asrock.com/mb/Intel/J3355B-ITX/index.de.asp

I'm getting the following error:

vdr:~ # vdpauinfo
display: :0   screen: 0
libva info: VA-API version 0.39.3
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
API version: 1
Information string: OpenGL/VAAPI backend for VDPAU

When trying to explicitly select the i965 driver:

vdr:~ # export LIBVA_DRIVER_NAME=i965
vdr:~ # vdpauinfo
display: :0   screen: 0
libva info: VA-API version 0.39.3
libva info: va_getDriverName() returns -1
libva info: User requested driver 'i965'
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
vdpauinfo: intel_driver.c:100: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
Abgebrochen (core dumped)

The funny thing is that mplayer seems to work just fine when giving the option "-vo vdpau". According to its output it is indeed using vdpau.

According to the Intel documentation this graphics hardware is fully supported under Linux.

Since I have a test setup, I'm more than willing to test any updates.
Comment 1 Hubert Mantel 2016-11-20 13:56:19 UTC
dup

*** This bug has been marked as a duplicate of bug 1011158 ***