Jump to content

Going mental over Ryzen 2400G / Vega vaapi


xantios

Recommended Posts

Hi,

 

Trying to get this up and running

 

I have Ryzen 2400G which has the integrated video chip, for what i know that should be able to play along nicely with Emby ? 

now. i do have a additional GPU which is passed through to a VM for gaming.

 

So my idea was to run games on my "big" GPU and run Emby transcoding on the integrated GPU.

struggling along for almost 3 days now im kinda going insane so maybe someone can help out?

 

Things i tried to do:

- Added the emby user to the usergroup video

- Updated everything, even instaleld the beta version of Emby

- Tried to define the environment variables to point Emby to the GPU i wanted to use

- Googled a lot

 

Now, to save you all some time asking for logs:

here is what i have

vainfo 
libva info: VA-API version 1.4.0
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
vainfo --display drm
libva info: VA-API version 1.4.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.4 (libva 2.4.0)
vainfo: Driver version: Mesa Gallium driver 19.0.1 for AMD RAVEN (DRM 3.27.0, 5.0.0-8-generic, LLVM 8.0.0)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileVP9Profile0            :	VAEntrypointVLD
      VAProfileVP9Profile2            :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc

Also attechted the hardware logging json file.

 

There the both GPU's show up, but it doenst seem to "skip" the first GPU, forget about it and go on... 

 

 

Any clues on how i can get this running with hardware transcoding?

 

Thanks ! 

emby.json.txt

Link to post
Share on other sites

Yes. multiple times.

 

Update: reinstalled the entire box. still no bal. 

 

the hardware detection:

"Error": {
   "Number": -1,
   "Message": "Failed to initialize VA /dev/dri/renderD128. Error -1"
}

however vainfo still seems to fine with it. 
 

Edited by xantios
Link to post
Share on other sites

What OS/Version is this?

 

I tried Ubuntu 19.04 beta and Ubuntu 18.10

regarding Emby they don't seem to differ

 

 

We'll look into this, thanks.

 

Would be great :) Anything i can do to help?

(Although i'm a web-developer, so i don't know if that helps?)

Link to post
Share on other sites
  • 3 weeks later...
bigverm23

using a Ryzen 2200G here and there is no option for mine either under Hardware Acceleration...

 

libva info: VA-API version 1.4.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.4 (libva 2.4.0)
vainfo: Driver version: Mesa Gallium driver 19.0.2 for AMD RAVEN (DRM 3.27.0, 5.0.0-13-generic, LLVM 8.0.0)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :    VAEntrypointVLD
      VAProfileMPEG2Main              :    VAEntrypointVLD
      VAProfileVC1Simple              :    VAEntrypointVLD
      VAProfileVC1Main                :    VAEntrypointVLD
      VAProfileVC1Advanced            :    VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:    VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:    VAEntrypointEncSlice
      VAProfileH264Main               :    VAEntrypointVLD
      VAProfileH264Main               :    VAEntrypointEncSlice
      VAProfileH264High               :    VAEntrypointVLD
      VAProfileH264High               :    VAEntrypointEncSlice
      VAProfileHEVCMain               :    VAEntrypointVLD
      VAProfileHEVCMain               :    VAEntrypointEncSlice
      VAProfileHEVCMain10             :    VAEntrypointVLD
      VAProfileJPEGBaseline           :    VAEntrypointVLD
      VAProfileVP9Profile0            :    VAEntrypointVLD
      VAProfileVP9Profile2            :    VAEntrypointVLD
      VAProfileNone                   :    VAEntrypointVideoProc

 

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org (0x1002)
    Device: AMD RAVEN (DRM 3.27.0, 5.0.0-13-generic, LLVM 8.0.0) (0x15dd)
    Version: 19.0.2
    Accelerated: yes
    Video memory: 256MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 4.5
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 9 MB, largest block: 9 MB
    VBO free aux. memory - total: 2924 MB, largest block: 2924 MB
    Texture free memory - total: 9 MB, largest block: 9 MB
    Texture free aux. memory - total: 2924 MB, largest block: 2924 MB
    Renderbuffer free memory - total: 9 MB, largest block: 9 MB
    Renderbuffer free aux. memory - total: 2924 MB, largest block: 2924 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 256 MB
    Total available memory: 3328 MB
    Currently available dedicated video memory: 9 MB
OpenGL vendor string: X.Org
OpenGL renderer string: AMD RAVEN (DRM 3.27.0, 5.0.0-13-generic, LLVM 8.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.2
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.0.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20


 

hardwaredetection.txt

Edited by bigverm23
Link to post
Share on other sites
Gerrit507

I currently use a G4600 with Ubuntu 18.04 and docker and it's working fine so far but I want little more CPU power because I have quite a lot of containers running. That's why I wanted to upgrade to a 2400G. Did you guys have any luck to get this working?

 

Have you installed the libva-mesa-driver package?

 

https://wiki.archlinux.org/index.php/Hardware_video_acceleration#ATI/AMD

 

This is also a helpful guide (in german though):

 

https://wiki.ubuntuusers.de/Video-Dekodierung_beschleunigen/

Edited by Gerrit507
Link to post
Share on other sites
softworkz

using a Ryzen 2200G here and there is no option for mine either under Hardware Acceleration...

 

libva info: VA-API version 1.4.0

libva info: va_getDriverName() returns 0

libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so

libva info: Found init function __vaDriverInit_1_4

libva info: va_openDriver() returns 0

vainfo: VA-API version: 1.4 (libva 2.4.0)

vainfo: Driver version: Mesa Gallium driver 19.0.2 for AMD RAVEN (DRM 3.27.0, 5.0.0-13-generic, LLVM 8.0.0)

vainfo: Supported profile and entrypoints

      VAProfileMPEG2Simple            :    VAEntrypointVLD

      VAProfileMPEG2Main              :    VAEntrypointVLD

      VAProfileVC1Simple              :    VAEntrypointVLD

      VAProfileVC1Main                :    VAEntrypointVLD

      VAProfileVC1Advanced            :    VAEntrypointVLD

      VAProfileH264ConstrainedBaseline:    VAEntrypointVLD

      VAProfileH264ConstrainedBaseline:    VAEntrypointEncSlice

      VAProfileH264Main               :    VAEntrypointVLD

      VAProfileH264Main               :    VAEntrypointEncSlice

      VAProfileH264High               :    VAEntrypointVLD

      VAProfileH264High               :    VAEntrypointEncSlice

      VAProfileHEVCMain               :    VAEntrypointVLD

      VAProfileHEVCMain               :    VAEntrypointEncSlice

      VAProfileHEVCMain10             :    VAEntrypointVLD

      VAProfileJPEGBaseline           :    VAEntrypointVLD

      VAProfileVP9Profile0            :    VAEntrypointVLD

      VAProfileVP9Profile2            :    VAEntrypointVLD

      VAProfileNone                   :    VAEntrypointVideoProc

 

name of display: :0

display: :0  screen: 0

direct rendering: Yes

Extended renderer info (GLX_MESA_query_renderer):

    Vendor: X.Org (0x1002)

    Device: AMD RAVEN (DRM 3.27.0, 5.0.0-13-generic, LLVM 8.0.0) (0x15dd)

    Version: 19.0.2

    Accelerated: yes

    Video memory: 256MB

    Unified memory: no

    Preferred profile: core (0x1)

    Max core profile version: 4.5

    Max compat profile version: 4.5

    Max GLES1 profile version: 1.1

    Max GLES[23] profile version: 3.2

Memory info (GL_ATI_meminfo):

    VBO free memory - total: 9 MB, largest block: 9 MB

    VBO free aux. memory - total: 2924 MB, largest block: 2924 MB

    Texture free memory - total: 9 MB, largest block: 9 MB

    Texture free aux. memory - total: 2924 MB, largest block: 2924 MB

    Renderbuffer free memory - total: 9 MB, largest block: 9 MB

    Renderbuffer free aux. memory - total: 2924 MB, largest block: 2924 MB

Memory info (GL_NVX_gpu_memory_info):

    Dedicated video memory: 256 MB

    Total available memory: 3328 MB

    Currently available dedicated video memory: 9 MB

OpenGL vendor string: X.Org

OpenGL renderer string: AMD RAVEN (DRM 3.27.0, 5.0.0-13-generic, LLVM 8.0.0)

OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.2

OpenGL core profile shading language version string: 4.50

OpenGL core profile context flags: (none)

OpenGL core profile profile mask: core profile

 

OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.2

OpenGL shading language version string: 4.50

OpenGL context flags: (none)

OpenGL profile mask: compatibility profile

 

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.0.2

OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

 

 

 

 

@@Luke @@alucryd - It seems that ffdetect is unable to initialize libva for the AMD adapter. Any ideas?

Link to post
Share on other sites

@@xantios @@bigverm23 Could you please try the following and post the output here?

APP_DIR=/opt/emby-server
export LD_LIBRARY_PATH=$APP_DIR/lib:$APP_DIR/lib/samba
export LIBVA_DRIVERS_PATH=$APP_DIR/lib/dri:/usr/lib/x86_64-linux-gnu/dri:/usr/lib64/dri:/usr/lib/dri
vainfo
Edited by alucryd
Link to post
Share on other sites
bigverm23

 

@@xantios @@bigverm23 Could you please try the following and post the output here?

APP_DIR=/opt/emby-server
export LD_LIBRARY_PATH=$APP_DIR/lib:$APP_DIR/lib/samba
export LIBVA_DRIVERS_PATH=$APP_DIR/lib/dri:/usr/lib/x86_64-linux-gnu/dri:/usr/lib64/dri:/usr/lib/dri
vainfo

 

where am I trying this exactly?

Link to post
Share on other sites

 

@@xantios @@bigverm23 Could you please try the following and post the output here?

APP_DIR=/opt/emby-server
export LD_LIBRARY_PATH=$APP_DIR/lib:$APP_DIR/lib/samba
export LIBVA_DRIVERS_PATH=$APP_DIR/lib/dri:/usr/lib/x86_64-linux-gnu/dri:/usr/lib64/dri:/usr/lib/dri
vainfo
APP_DIR=/opt/emby-server                                                                   
export LD_LIBRARY_PATH=$APP_DIR/lib:$APP_DIR/lib/samba
export LIBVA_DRIVERS_PATH=$APP_DIR/lib/dri:/usr/lib/x86_64-linux-gnu/dri:/usr/lib64/dri:/usr/lib/dri
vainfo
error: can't connect to X server!
libva info: VA-API version 1.4.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /opt/emby-server/lib/dri/radeonsi_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.4 (libva 2.4.0)
vainfo: Driver version: Mesa Gallium driver 19.0.2 for AMD RAVEN (DRM 3.27.0, 5.0.0-13-generic, LLVM 8.0.0)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileVP9Profile0            :	VAEntrypointVLD
      VAProfileVP9Profile2            :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc

I currently use a G4600 with Ubuntu 18.04 and docker and it's working fine so far but I want little more CPU power because I have quite a lot of containers running. That's why I wanted to upgrade to a 2400G. Did you guys have any luck to get this working?

 

Have you installed the libva-mesa-driver package?

 

https://wiki.archlinux.org/index.php/Hardware_video_acceleration#ATI/AMD

 

This is also a helpful guide (in german though):

 

https://wiki.ubuntuusers.de/Video-Dekodierung_beschleunigen/

 

 

As a native Dutch speaker my German is rather rusty, but the language is similar enough to get a sense of what the guide is saying.

I did install the libva-mesa-driver package already, currently trying to install the new release.

 

edit: In the meanwhile updated to the latest Emby version. in the UI I still don't see any options when I switch to the "advanced" mode.

 

Also checked the hardware detection log and there is no change as far as I can see (as a web-dev, im kinda used to read JSON files)

 

Could it be (just a 'lucky guess') that Emby is probing the first device (index 0) instead of looping through them? because I have my primary GPU mapped to a VM (which is currently also running emby because I can't use my iGPU).

 

If so; can I tell emby to dont be clever and just point it to a device?

 

 

Edit 2:

 

After updating I get the following output:

APP_DIR=/opt/emby-server                                                                   
export LD_LIBRARY_PATH=$APP_DIR/lib:$APP_DIR/lib/samba
export LIBVA_DRIVERS_PATH=$APP_DIR/lib/dri:/usr/lib/x86_64-linux-gnu/dri:/usr/lib64/dri:/usr/lib/dri
vainfo
error: can't connect to X server!
libva info: VA-API version 1.3.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /opt/emby-server/lib/dri/radeonsi_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva error: dlopen of /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so failed: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so: undefined symbol: amdgpu_bo_list_create_raw
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Trying to open /usr/lib/dri/radeonsi_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
Edited by xantios
Link to post
Share on other sites
bigverm23

 

@@xantios @@bigverm23 Could you please try the following and post the output here?

APP_DIR=/opt/emby-server
export LD_LIBRARY_PATH=$APP_DIR/lib:$APP_DIR/lib/samba
export LIBVA_DRIVERS_PATH=$APP_DIR/lib/dri:/usr/lib/x86_64-linux-gnu/dri:/usr/lib64/dri:/usr/lib/dri
vainfo
libva info: VA-API version 1.3.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /opt/emby-server/lib/dri/radeonsi_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva error: dlopen of /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so failed: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so: undefined symbol: amdgpu_bo_list_create_raw
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Trying to open /usr/lib/dri/radeonsi_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
 
Link to post
Share on other sites
softworkz

Could it be (just a 'lucky guess') that Emby is probing the first device (index 0) instead of looping through them? because I have my primary GPU mapped to a VM (which is currently also running emby because I can't use my iGPU).

 

If so; can I tell emby to dont be clever and just point it to a device?

 

Why would that be 'clever'? I'd say, that would be incredibly stupid...

 

Look at the VAAPI section of the detection log that you posted. There you can see that it tries to open both devices.

 

 

I would suggest to try to install this directly to the host machine instead of inside a VM.

 

If you do, also disable the other VM(s)...

Edited by softworkz
Link to post
Share on other sites
alucryd

Thanks guys, I may be able to get it working. Looks like Ubuntu finally ships a somewhat recent libva version, I'll update ours to the same version, it will ship with the next beta.

Link to post
Share on other sites
xantios

Why would that be 'clever'? I'd say, that would be incredibly stupid...

 

Look at the VAAPI section of the detection log that you posted. There you can see that it tries to open both devices.

 

 

I would suggest to try to install this directly to the host machine instead of inside a VM.

 

If you do, also disable the other VM(s)...

 

 

Admittedly, i might phrased that a bit weird. What i meant to say was: The detection log tells me its probing multiple devices, but maybe it doesn't know it can't use the Nvidia card so it fails? 

 

for debugging purposes it might be nice if I could tell Emby "Dont try, just use this specific device" 

Which is just a train of thought off course (Im obviously not familiar with the internal workings of Emby)

 

Regarding my VM (singular):

 

I'm running Emby on the host. (Ubuntu) the host has the Ryzen iGPU dedicated to it. the Nvidia GPU is passed to a VM (so it is not usable by the host) (using VFIO, KVM/Qemu)  I'd say Emby would be fine ignoring the entire existence of the device. which if I interpreted your post(s) correctly it should?

 

Thanks for the support by the way :) 

Link to post
Share on other sites
softworkz

Admittedly, i might phrased that a bit weird. What i meant to say was: The detection log tells me its probing multiple devices, but maybe it doesn't know it can't use the Nvidia card so it fails? 

 

for debugging purposes it might be nice if I could tell Emby "Dont try, just use this specific device" 

 

The detection process is accessing hardware devices in the exact same way as our included ffmpeg does. 

If it cannot be accessed during detection it won't work for transcoding. 

 

It might be a library mismatch problem though, as @@alucryd has stated above.

 

I think your best bet might be to wait for the next beta and try again then.

Link to post
Share on other sites
  • 2 weeks later...
  • 2 weeks later...

@@xantios can you try the beta server and let me know how that compares? thanks !

 

I just screamed right to my monitor something that would translate to: "I lived to see this happen" ( Dat ik het nog mee mag maken!) 

Luke, SoftWorkz you guys made my day!! 

Link to post
Share on other sites
  • 11 months later...
rutgerputter

Hi, I would like to jump on this thread for some help with my AMD 3200G APU.

 

This is also a RAVEN GPU (Vega 8) like the 2400G and I got it to work with Jellyfin, but I want to use Emby as it is much better dealing with Live TV, DVR and transcoding media.

 

I use a docker container based on Ubuntu Bionic 18.04 (linuxserverio). In this container I installed the vainfo and mesa-va-drivers to enable the GPU drivers. Kernel support is already there.

 

But emby hardware detection still doesn't want to use the AMD GPU:

"Devices": [
{
"DeviceIndex": 0,
"DeviceInfo": {
"VendorId": 4098,
"DeviceId": 5592,
"SubsytemVendorId": 4098,
"SubsytemDeviceId": 5592,
"DevPath": "/sys/bus/pci/devices/0000:0e:00.0",
"DrmCard": "/dev/dri/card0",
"DrmRender": "/dev/dri/renderD128",
"IsEnabled": 1,
"IsBootVga": 1,
"Error": {
"Number": -1,
"Message": "Failed to initialize VA /dev/dri/renderD128. Error -1"
}
 
 
The strange thing is that ffdetect in the emby folder can detect my vaenc and vadec  devices just fine.
I'm on the latest beta but Stable also doesn't work.
 
Could you help shed some light on what I'm doing wrong?
 
Rutger
 
PS: my wainfo output:
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.1 (libva 2.1.0)
vainfo: Driver version: Mesa Gallium driver 19.2.8 for AMD RAVEN (DRM 3.36.0, 5.5.8-Unraid, LLVM 9.0.0)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice
      VAProfileHEVCMain10             : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc

 

 

 

hardware_detection-63724305675.txt

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...