Hi,
I've succesfully deployed Media SDK 2016 on Centos in the past.
Now I would like to use Media SKD 2017 on ubuntu,
Running the decode_sample provided, I always get:
Return on error: error code -3, MediaServerStudioEssentials2017/MediaSamples_Linux_2017/samples/sample_decode/src/pipeline_decode.cpp 404
Return on error: error code 1, MediaServerStudioEssentials2017/MediaSamples_Linux_2017/samples/sample_decode/src/sample_decode.cpp 646
I didn't patch the default kernel because i915 graphic driver is already installed.
Please could you suggest a solution?
Thanks in advance
Here is my environment:
- MediaServerStudioEssentials2017
- Intel® Core™ i5-5200U CPU, Intel® HD Graphics 5500
- Ubuntu 16.04 64bit, kernel 4.4.0-57-generic
libva info: VA-API version 0.99.0
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
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.99 (libva 1.67.0.pre1)
vainfo: Driver version: 16.5.55964-ubit
lsmod | grep i915
i915 1208320 5
i2c_algo_bit 16384 1 i915
drm_kms_helper 155648 1 i915
drm 364544 6 i915,drm_kms_helper
video 40960 1 i915
Link Copied
Hi,
Regarding use MSS on Ubuntu, you can refer this article:
And patch the patches is important step.
Thanks,
Zachary
Thank you Zachary for your quick answer.
I've already downloaded and implemented the linked document.
The problem is that patching Ubuntu kernel sources returns errors because that kernel is already patched with Intel graphic driver. Installing upstream kernel (from kernel.org) is not an option for me. So I'd rather prefer to make Ubuntu kernel just work. The best would be understand what's happening on my machine. Could you provide any advice?
Thanks in advance
Your Ubuntu kernel already include the patches of MSS, right ? can you double check this ?
Sometime patches merge not correct will cause failure to run media function.
Thanks,
Zachary
Yeah I confirm that.
Please check the first thread post where I reported the vainfo output and the i915 driver loaded by 'original' ubuntu kernel. Those outputs are the same as they were produced by a patched upstream kernel.
Regards
What is the output of command line ?
$ ls -l /dev/dri | grep renderD128 ## if no output, you need do the kernel patch merge.
$ cat /proc/kallsyms | grep userptr ## if no output, you need do the kernel patch merge.
Thank you Zachary,
Below you'll find the outputs. They seem fine:
$ ls -l /dev/dri | grep renderD128
crw-rw----+ 1 root video 226, 128 dic 29 05:36 renderD128
$ cat /proc/kallsyms | grep userptr
0000000000000000 t __i915_gem_userptr_set_active [i915]
0000000000000000 t i915_gem_userptr_put_pages [i915]
0000000000000000 t cancel_userptr [i915]
0000000000000000 t i915_gem_userptr_mn_invalidate_range_start [i915]
0000000000000000 t __i915_gem_userptr_set_pages [i915]
0000000000000000 t i915_gem_userptr_get_pages [i915]
0000000000000000 t __i915_gem_userptr_get_pages_worker [i915]
0000000000000000 t i915_gem_userptr_init__mmu_notifier [i915]
0000000000000000 t __cancel_userptr__worker [i915]
0000000000000000 r i915_gem_userptr_notifier [i915]
0000000000000000 t i915_gem_userptr_dmabuf_export [i915]
0000000000000000 t i915_gem_userptr_release [i915]
0000000000000000 r i915_gem_userptr_ops [i915]
0000000000000000 t i915_gem_init_userptr [i915]
0000000000000000 t i915_gem_userptr_ioctl [i915]
Regards
For more complete information about compiler optimizations, see our Optimization Notice.