Media (Intel® oneAPI Video Processing Library, Intel Media SDK)
Access community support with transcoding, decoding, and encoding in applications using media tools from Intel. This includes Intel® oneAPI Video Processing Library and Intel® Media SDK.
Announcements
Welcome to the Intel Community. If you get an answer you like, please mark it as an Accepted Solution to help others. Thank you!

I cannot find Intel gfx driver

SHara
Novice
496 Views

Hi,

 

I'd like to decode RTP H.264 video stream with Media SDK.

But installation of Media SDK is failed. 

 

Download libva, libva-utils, Gmmlib, media-driver and MediaSDK from github.

Build and install with gcc 8.3.1(devtoolset-8).

         libva: https://github.com/intel/libva/releases/tag/2.7.0

         libva-utils: https://github.com/intel/libva-utils/releases/tag/2.7.1

         Gmmlib: https://github.com/intel/gmmlib/releases/tag/intel-gmmlib-20.1.1

         Driver: https://github.com/intel/media-driver/releases/tag/intel-media-20.1.1

         Media SDK and Samples: https://github.com/Intel-Media-SDK/MediaSDK/releases/tag/intel-mediasdk-20.1.0

 

Run vainfo.

    # vainfo
               error: XDG_RUNTIME_DIR not set in the environment.
               error: can't connect to X server!
               libva info: VA-API version 1.7.0
               libva info: User environment variable requested driver 'iHD'
               libva info: Trying to open /usr/local/lib/dri/iHD_drv_video.so
               libva info: Found init function __vaDriverInit_1_7
               DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
              Assuming 131072kB available aperture size.
              May lead to reduced performance or incorrect rendering.
              get chip id failed: -1 [22]
              param: 4, val: 0
              libva error: /usr/local/lib/dri/iHD_drv_video.so init failed
              libva info: va_openDriver() returns 18
              vaInitialize failed with error code 18 (invalid parameter),exit

 

Run vainfo with option "--display drm --device /dev/dri/renderD129" for all of /dev/dri/*.

As a result, it was same error message.

 

I made following code to initialize.

But device files are not found.

 

          int open_intel_adapter()
          {
                     std::string adapterPath = "/dev/dri/renderD";

           char driverName[5] = {};
           mfxU32 nodeIndex = 128;

 

           for (mfxU32 i = 0; i < 16; ++i) {
                          std::string curAdapterPath = adapterPath + std::to_string(nodeIndex + i);

   

                          int fd = open(curAdapterPath.c_str(), O_RDWR);
                          if (fd < 0) continue;

                          drm_version_t version = {};
                                          version.name_len = 32;
                                          version.name = driverName;
                                          ioctl(fd, DRM_IOWR(0, drm_version), &version);
                                          if(!strcmp(driverName, "i915")) return fd;
                        close(fd);
                    }
                   return -1;
          }

 

 

My Environment is;

OS
           CentOS Linux release 7.6.1810
CPU
           Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz
GPU
           NVIDIA GeForce GTX 1080
                  NVIDIA gfx driver is installed.
                          NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020
                 NVIDIA gfx driver is disabled as follows.
                            # sudo mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
                             # sudo dracut --force --omit-drivers nouveau /boot/initramfs-$(uname -r).img $(uname -r)
                             # echo "blacklist nouveau" | sudo tee /etc/modprobe.d/modprobe.conf
                             # echo "blacklist nouveau" | sudo tee /etc/modprobe.d/nouveau-blacklist.conf
DRI
                  # ls /dev/dri
                              card0 card1 renderD128 renderD129
                  # cat /sys/kernel/debug/dri/*/name
                              nvidia-drm dev=0000:03:00.0 unique=0000:03:00.0
                              nvidia-drm dev=0000:03:00.0 unique=0000:03:00.0
                              nvidia-drm dev=0000:04:00.0 unique=0000:04:00.0
                              nvidia-drm dev=0000:04:00.0 unique=0000:04:00.0

 

Could you tell me why intel gfx driver is not found?

 

I plan to try another PC.  CPU of that PC is Intel(R) Xeon(R) W-2133 CPU @ 3.60GHz.

Does Media SDK support Xeon W-2133?

Labels (1)
0 Kudos
1 Solution
JaideepK_Intel
Moderator
333 Views

Hi,


Xeon Processors:

For Media SDK, we must make sure “Quick Sync” is included in the integrated GPU. So Xeon W-2133 will not work. We only include GPU in Xeon E3.


i7-6800K should be ok but if Nvidia's GPU takes the primary position, the integrated GPU might not be accessible. Please go through below links:

  1. https://github.com/Intel-Media-SDK/MediaSDK/issues/167
  2. https://github.com/Intel-Media-SDK/MediaSDK/issues/1067
  3. https://github.com/Intel-Media-SDK/MediaSDK/issues/2477


Thanks,

Jaideep



View solution in original post

4 Replies
JaideepK_Intel
Moderator
410 Views

Hi,

Thank you for posting in Intel Communities.

We are investigating your issue at our end and we will get back to you soon.


Thanks,

Jaideep


JaideepK_Intel
Moderator
334 Views

Hi,


Xeon Processors:

For Media SDK, we must make sure “Quick Sync” is included in the integrated GPU. So Xeon W-2133 will not work. We only include GPU in Xeon E3.


i7-6800K should be ok but if Nvidia's GPU takes the primary position, the integrated GPU might not be accessible. Please go through below links:

  1. https://github.com/Intel-Media-SDK/MediaSDK/issues/167
  2. https://github.com/Intel-Media-SDK/MediaSDK/issues/1067
  3. https://github.com/Intel-Media-SDK/MediaSDK/issues/2477


Thanks,

Jaideep



View solution in original post

SHara
Novice
289 Views

Hi,

 

Thank you for your reply.

Please close this.

JaideepK_Intel
Moderator
264 Views

Hi,


Glad to know that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.


Thanks,

Jaideep


Reply