[Bug 1011158] New: vdpau/vaapi not working
http://bugzilla.suse.com/show_bug.cgi?id=1011158 Bug ID: 1011158 Summary: vdpau/vaapi not working Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: mantel@suse.com QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- Created attachment 702827 --> http://bugzilla.suse.com/attachment.cgi?id=702827&action=edit 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. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c1
--- Comment #1 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c2
--- Comment #2 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c3
--- Comment #3 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c4
--- Comment #4 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c5
--- Comment #5 from Hubert Mantel
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.
Unfortunately xine does not work and vdr is using xineliboutput. So mplayer cannot be used as workaround -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c6
--- Comment #6 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c7
Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c8
--- Comment #8 from Max Staudt
http://bugzilla.suse.com/show_bug.cgi?id=1011158
Max Staudt
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c9
--- Comment #9 from Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c10
--- Comment #10 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c11
--- Comment #11 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c12
--- Comment #12 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c13
--- Comment #13 from Stefan Dirsch
vdr:~ # export DISPLAY=:0 vdr:~ # vainfo 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) vaInitialize failed with error code -1 (unknown libva error),exit
Please set here LIBVA_DRIVER_NAME=i965 as well. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c14
--- Comment #14 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c15
--- Comment #15 from Hubert Mantel
(In reply to Hubert Mantel from comment #10)
vdr:~ # export DISPLAY=:0 vdr:~ # vainfo 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) vaInitialize failed with error code -1 (unknown libva error),exit
Please set here LIBVA_DRIVER_NAME=i965 as well.
vdr:~ # export LIBVA_DRIVER_NAME=i965 vdr:~ # vainfo 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 vainfo: 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) vdr:~ # -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c16
--- Comment #16 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c17
--- Comment #17 from Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c18
--- Comment #18 from Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c19
--- Comment #19 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c20
--- Comment #20 from Max Staudt
I can't understand why mplayer works with vdpau backend. Could it be that it does a fallback to a different backend, after vdpau this fails?
See Comment 8: "Pure output without hardware decoding is pretty much bound to work, as the wrapper implements video output via OpenGL." It doesn't use VA for drawing, just for decoding. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c21
--- Comment #21 from Stefan Dirsch
Trying to run it from remote...
vdr:/video/data/Terra X # l /lib/firmware/i915/ -rw-r--r-- 1 root root 8380 Okt 5 19:30 bxt_dmc_ver1_07.bin lrwxrwxrwx 1 root root 19 Okt 5 19:30 bxt_dmc_ver1.bin -> bxt_dmc_ver1_07.bin
So required firmware does exist.
vdr:/video/data/Terra X # mplayer -vo vdpau 20151224\ 1527\ -\ zdf_neo\ HD\ -\ Terra\ X.ts MPlayer -6 (C) 2000-2015 MPlayer Team mplayer: could not open config files /root/.lircrc and /etc/lirc/lircrc mplayer: No such file or directory Failed to read LIRC config file ~/.lircrc.
Playing 20151224 1527 - zdf_neo HD - Terra X.ts. libavformat version 57.56.100 (external) TS file format detected. VIDEO H264(pid=6310) AUDIO MPA(pid=6321) SUB Teletext(pid=6330) PROGRAM N. 11130 FPS seems to be: 50.000000 Load subtitles in ./ 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)
So it fails exactly the same way as it does with vdpauinfo, vainfo. Some fallback is used I'm pretty sure. At least now we have a consistent picture. ;-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c22
--- Comment #22 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c23
--- Comment #23 from Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c24
--- Comment #24 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c25
--- Comment #25 from Max Staudt
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c26
--- Comment #26 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c27
--- Comment #27 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c28
--- Comment #28 from Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c29
--- Comment #29 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c30
Max Staudt
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c31
Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c32
Max Staudt
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c33
--- Comment #33 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c34
--- Comment #34 from Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c35
--- Comment #35 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c36
--- Comment #36 from Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c37
--- Comment #37 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c38
--- Comment #38 from Max Staudt
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c42
--- Comment #42 from Max Staudt
http://bugzilla.suse.com/show_bug.cgi?id=1011158
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1011158
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c43
--- Comment #43 from Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c44
Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c45
--- Comment #45 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c46
--- Comment #46 from Hubert Mantel
vdr:/video/data/Terra X # l /lib/firmware/i915/ total 428 drwxr-xr-x 2 root root 4096 Nov 21 14:04 ./ drwxr-xr-x 76 root root 12288 Nov 19 17:38 ../ -rw-r--r-- 1 root root 8380 Okt 5 19:30 bxt_dmc_ver1_07.bin lrwxrwxrwx 1 root root 19 Okt 5 19:30 bxt_dmc_ver1.bin -> bxt_dmc_ver1_07.bin
After the new install, ver1_07 does no longer exist: vdr:/lib/firmware/i915 # l bxt* -rw-r--r-- 1 root root 5872 16. Mai 2016 bxt_dmc_ver1_04.bin -rw-r--r-- 1 root root 5872 16. Mai 2016 bxt_dmc_ver1_05.bin -rw-r--r-- 1 root root 8380 16. Mai 2016 bxt_dmc_ver1_06.bin lrwxrwxrwx 1 root root 19 13. Mai 14:41 bxt_dmc_ver1.bin -> bxt_dmc_ver1_06.bin vdr:/lib/firmware/i915 # Maybe this is the problem?? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c47
--- Comment #47 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c48
--- Comment #48 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c49
Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c50
--- Comment #50 from Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c51
Hubert Mantel
I no longer remember the details, but I'm afraid you still set
LIBVA_DRIVER_NAME=i965
as a minimum. Leap 42.2/sle12-sp2 hasn't seen a fundamental graphics stack update (at least no Xserver update). So you may need to do something similar as in comment #30, i.e. at least update xorg-x11-server of X11:XOrg. I don't know which patch Max added. His repo is gone meanwhile and he is on sick leave until begin of July.
I forgot to mention: I tried explicitly setting this environment variable, but it just leads to the core dump as before. But thanks for the hint with the updated X server. Will try this tonight. I tried to use the one from Max's home project, but unfortunately it is gone. But even if this will solve my problem, some questions remain: 1. Why don't we have the most recent firmware version any longer? 2. Why can't the kernel correctly load the firmware? This has worked before and seems to be fixed again in a more recent kernel. Of course using this newer kernel is totally acceptable for me and if the patched X server solved the problem, I'm fine. But there still seems to be something fishy at least in the currently available official kernel then. But I understand this is not a problem of the X guys then :) Thanks a lot for your quick answer! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c52
--- Comment #52 from Hubert Mantel
I no longer remember the details, but I'm afraid you still set
LIBVA_DRIVER_NAME=i965
as a minimum. Leap 42.2/sle12-sp2 hasn't seen a fundamental graphics stack update (at least no Xserver update). So you may need to do something similar as in comment #30, i.e. at least update xorg-x11-server of X11:XOrg. I don't know which patch Max added. His repo is gone meanwhile and he is on sick leave until begin of July.
I just double-checked again (did that already at home) and the X server changelog shows this entry: * Fri Dec 09 2016 mstaudt@suse.com - U_dri2-Sync-i965_pci_ids.h-from-mesa.patch Update Intel PCI IDs for modesetting to include Broxton 2x6. Fixes (boo#1011158). This is addressing this very bug, so are you sure this is the problem? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c53
--- Comment #53 from Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c54
Hubert Mantel
I believe we also updated libva/vaapi-intel-driver at this time. So very likely Tumbleweed or components from TW at this time respectively, were much newer than what we still have in Leap 42.2.
Ok, this would make sense then. Honestly I do not know which exact version I had been using back in december. I was under the impression that it was a beta of 42.2, but it could very well have been tumbleweed as well. Thanks for the hint. I will test with tumbleweed as soon as possible (probably in the weekend) and report back then. So no more action required from you right now :) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c55
--- Comment #55 from Hubert Mantel
Ok, this would make sense then. Honestly I do not know which exact version I had been using back in december. I was under the impression that it was a beta of 42.2, but it could very well have been tumbleweed as well.
Btw, I think you are right and I tested with tumbleweed in december. I just checked the kernel-firmware package and it already has the new version 1.07. Since I never tampered with it, this is a very strong indication that it indeed was not 42.2 I tested before. Was not aware that tumbleweed is that much newer than leap :) I'm quite confident things will work fine with the new version again. Thanks a lot! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c56
--- Comment #56 from Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c57
Hubert Mantel
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c58
--- Comment #58 from Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1011158
http://bugzilla.suse.com/show_bug.cgi?id=1011158#c59
--- Comment #59 from Hubert Mantel
Seems vainfo is now built from libva-utils sources/source package. Looks like this has never been submitted to factory. :-(
Glad to hear this was not intentional. Thanks for fixing! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com