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.

Installing Media SDK 2016

Bob_Kirnum
Beginner
429 Views

Got a new GPU system and attempted to install the Media SDK.  Not sure it went well . . . 

[root@sut-1339 x86_64]# rpm -Uvh kernel-3.10.0-229.1.2.47109.MSSr1.el7.centos.x86_64.rpm
Preparing...                          ################################# [100%]
Updating / installing...
   1:kernel-3.10.0-229.1.2.47109.MSSr1################################# [ 50%]
Cleaning up / removing...
   2:kernel-3.10.0-229.el7            warning: file /lib/modules/3.10.0-229.el7.x86_64/weak-updates: remove failed: No such file or directory
warning: file /lib/modules/3.10.0-229.el7.x86_64/modules.softdep: remove failed: No such file or directory
warning: file /lib/modules/3.10.0-229.el7.x86_64/modules.devname: remove failed: No such file or directory
################################# [100%]

Am I missing something?  Should I reboot?  Try installing again?

System info . . . 

[root@sut-1339 ~]# cat /etc/*release*
CentOS Linux release 7.1.1503 (Core)
Derived from Red Hat Enterprise Linux 7.1 (Source)

[root@sut-1339 ~]# cat /proc/cpuinfo

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 94
model name      : Intel(R) Xeon(R) CPU E3-1275 v5 @ 3.60GHz
stepping        : 3
microcode       : 0x6a
cpu MHz         : 3600.048
cache size      : 8192 KB
physical id     : 0
siblings        : 8
core id         : 0
cpu cores       : 4
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 22
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap
bogomips        : 7200.09
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

 

 

0 Kudos
4 Replies
Bob_Kirnum
Beginner
429 Views

More info . . . 

[root@sut-1339 x86_64]# ls -altr /opt/intel/mediasdk/
total 4
drwxr-xr-x 2 root root  123 Mar 13 21:39 lib64
drwxr-xr-x 2 root root   78 Mar 13 21:39 plugins
drwxr-xr-x 5 root root   47 Mar 13 21:39 ..
drwxr-xr-x 9 root root   95 Mar 13 21:39 .
drwxr-xr-x 2 root root  108 Mar 13 21:39 doc
drwxr-xr-x 3 root root   20 Mar 13 21:39 lib
drwxr-xr-x 2 root root 4096 Mar 13 21:39 include
drwxr-xr-x 6 root root   98 Mar 13 21:39 opensource
drwxr-xr-x 5 root root   57 Mar 13 21:39 tools

 

[root@sut-1339 x86_64]# find / -mount -name 'libdrm.so.*' -print
/usr/lib/libdrm.so.2
/usr/lib/libdrm.so.2.4.0
/usr/lib64/libdrm.so.2.4.0
/usr/lib64/libdrm.so.2

[root@sut-1339 x86_64]# find / -mount -name 'libva.so.*' -print
/usr/lib64/libva.so.1
/usr/lib64/libva.so.1.9900.0

 

0 Kudos
Jeffrey_M_Intel1
Employee
429 Views

It looks like you're very close on your install.  From the getting started guide, these are the steps in a nutshell:

(as root)
# ./install_sdk_UMD_CentOS.sh
# mkdir /MSS
# chown {regular user}:{regular group} /MSS

(as regular user)
$ cp build_kernel_rpm_CentOS.sh /MSS
$ cd /MSS
$ ./build_kernel_rpm*.sh 

(as root)
# cd /MSS/rpmbuild/RPMS/x86_64
# rpm -Uvh kernel-3.10.*.rpm
# reboot

First, install the user-mode components with "install_sdk_UMD_CentOS.sh", then build the kernel RPM with "build_kernel_rpm_CentOS.sh".  Install the kernel and reboot.

More detailed checks/diagnostics are described in this paper:

http://www.intel.com/content/dam/www/public/us/en/documents/white-papers/quicksync-video-ffmpeg-install-valid.pdf

While the title says it's about FFmpeg, the majority of the diagnostics are for Media Server Studio.

0 Kudos
Bob_Kirnum
Beginner
429 Views

Thanks for the response Jeff.  I do realize I am very close, I am up to the last step, reboot.  I have installed this SDk (and the 2015) several times on another system.  I am unsure about the results of the second to last step, installing the rpm . . . 

[root@sut-1339 x86_64]# rpm -Uvh kernel-3.10.0-229.1.2.47109.MSSr1.el7.centos.x86_64.rpm
Preparing...                          ################################# [100%]
Updating / installing...
   1:kernel-3.10.0-229.1.2.47109.MSSr1################################# [ 50%]
Cleaning up / removing...
   2:kernel-3.10.0-229.el7            warning: file /lib/modules/3.10.0-229.el7.x86_64/weak-updates: remove failed: No such file or directory
warning: file /lib/modules/3.10.0-229.el7.x86_64/modules.softdep: remove failed: No such file or directory
warning: file /lib/modules/3.10.0-229.el7.x86_64/modules.devname: remove failed: No such file or directory
################################# [100%]

Are the warnings some indication that the SDK is not properly installed?  None of this is detailed in the document you provided.

Thanks - Bob

0 Kudos
Jeffrey_M_Intel1
Employee
429 Views

As I'm reading the warnings, they are harmless.  They are from the "clean" stage of the RPM install, reporting that a file rpm is attempting to remove isn't there to remove. The directory affected is for the previous kernel's modules, not the kernel modules you're installing, so it doesn't necessarily indicate something is missing from the MSS kernel rpm package.  Of course the real proof is to reboot to the new kernel -- if something is missing it should be obvious.  Thanks for the documentation suggestion -- seems like a good addition to the install documentation.

0 Kudos
Reply