Media (Intel® Video Processing Library, Intel Media SDK)
Access community support with transcoding, decoding, and encoding in applications using media tools like Intel® oneAPI Video Processing Library and Intel® Media SDK
Announcements
The Intel Media SDK project is no longer active. For continued support and access to new features, Intel Media SDK users are encouraged to read the transition guide on upgrading from Intel® Media SDK to Intel® Video Processing Library (VPL), and to move to VPL as soon as possible.
For more information, see the VPL website.
3061 Discussions

libva error after installing Media Server Studio 2017 on Centos 7

yair_s_
Beginner
444 Views

I am trying to install the Intel MSS 2017 on my Centos 7.2.1511

When I type the command: "cat lspci -nn -s 0:02.0" this is the output:

00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07)

meaning I have the appropriate hardware to run it, but after I finished running the installation scripts, I tried to check whether the installation went correctly, so I typed the command vainfo and got this in return:

libva info: VA-API version 0.39.3
libva info: va_getDriverName() returns 0
libva info: User requested driver 'iHD'
libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so
libva info: Found init function __vaDriverInit_0_32
Segmentation fault (core dumped)

this is the ouptut of running gdb vainfo:

Reading symbols from /usr/local/bin/vainfo...done.
(gdb) run
Starting program: /usr/local/bin/vainfo
libva info: VA-API version 0.39.3
libva info: va_getDriverName() returns 0
libva info: User requested driver 'iHD'
libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
libva info: Found init function __vaDriverInit_0_32

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff4618b5f in __vaDriverInit_0_32 ()
   from /opt/intel/mediasdk/lib64/iHD_drv_video.so
Missing separate debuginfos, use: debuginfo-install glibc-2.17-106.el7_2.6.x86_64 libX11-1.6.3-2.el7.x86_64 libXau-1.0.8-2.1.el7.x86_64 libXext-1.3.3-3.el7.x86_64 libXfixes-5.0.1-2.1.el7.x86_64 libgcc-4.8.5-4.el7.x86_64 libpciaccess-0.13.4-2.el7.x86_64 libstdc++-4.8.5-4.el7.x86_64 libxcb-1.11-4.el7.x86_64
(gdb) bt
#0  0x00007ffff4618b5f in __vaDriverInit_0_32 ()
   from /opt/intel/mediasdk/lib64/iHD_drv_video.so
#1  0x00007ffff7bbe0c8 in va_openDriver (dpy=dpy@entry=0x611310,
    driver_name=<optimized out>) at va.c:301
#2  0x00007ffff7bbef8b in vaInitialize (dpy=dpy@entry=0x611310,
    major_version=major_version@entry=0x7fffffffdd30,
    minor_version=minor_version@entry=0x7fffffffdd34) at va.c:563
#3  0x0000000000400fe0 in main (argc=1, argv=0x7fffffffde88) at vainfo.c:120
(gdb)

Any help would be much appreciated. Thanks!

 

 

 

0 Kudos
2 Replies
gy__ln
Beginner
444 Views

hi yair.s

    I use libva directly ,and i use  libva-intel-driver , so when I use "vainfo", it open i965_drv_video.so , it's correct. 

    iHD_drv_video is a closed source,and libva-intel-driver is open source, do you know the diffience between these two driver?? 

Best regard

 

0 Kudos
Mark_L_Intel1
Moderator
444 Views

Hi yair.s

This looks like an installation error, from your error message, I can see iHD driver is called correctly from libVA so it might caused by KMD installation error, for the closed i915 driver, we do a kernel patch in the installation process. unfortunately our script doesn't show error message in a good way. If you go back to check the process when it does the kernel patch.

To gy, although both drivers uses hardware QSV functions, the difference is: the "closed driver"(i915) has the original/strong support from Intel graphic driver team. And you are partly wrong about "closed driver", it is open source now. You can find it in following URL:

https://github.com/Intel/media-driver

We also have an open source media project and you can build whole media stack based on following instructions:

https://software.intel.com/en-us/articles/build-and-debug-open-source-media-stack

I am not going to discuss more about the driver issue since this is yair's issue, please open a new post if you want to continue the discussion.

Mark

0 Kudos
Reply