You are not logged in.

#1 2023-03-12 22:36:52

edge33
Member
Registered: 2023-01-29
Posts: 37

vdpauinfo on irisXE

Hello guys, I have installed arch and I am exploring the system. I have a t14 lenovo laptop with i5-1145g7 with irisXE graphics, and I installed mesa. intel-media-driver and libva-vdpau-driver-vp9-git as per arch wiki to enable hw video decode.

issuing grep -iE 'vdpau | dri driver' ~/.local/share/xorg/Xorg.0.log, I get:

[    10.129] (II) modeset(0): [DRI2]   DRI driver: iris
[    10.129] (II) modeset(0): [DRI2]   VDPAU driver: va_gl

first question, shouldn't my driver be iHD there? or is iris expected?

also when running vdpauinfo, i get:

display: :0   screen: 0
API version: 1
Information string: OpenGL/VAAPI backend for VDPAU

Video surface:

name   width height types
-------------------------------------------
420     4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16
422     4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16
444     4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16
420_16  4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16
422_16  4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16
444_16  4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16

Decoder capabilities:

name                        level macbs width height
----------------------------------------------------
MPEG1                          --- not supported ---
MPEG2_SIMPLE                   --- not supported ---
MPEG2_MAIN                     --- not supported ---
H264_BASELINE                  51 16384  2048  2048
H264_MAIN                      51 16384  2048  2048
H264_HIGH                      51 16384  2048  2048
VC1_SIMPLE                     --- not supported ---
VC1_MAIN                       --- not supported ---
VC1_ADVANCED                   --- not supported ---
MPEG4_PART2_SP                 --- not supported ---
MPEG4_PART2_ASP                --- not supported ---
DIVX4_QMOBILE                  --- not supported ---
DIVX4_MOBILE                   --- not supported ---
DIVX4_HOME_THEATER             --- not supported ---
DIVX4_HD_1080P                 --- not supported ---
DIVX5_QMOBILE                  --- not supported ---
DIVX5_MOBILE                   --- not supported ---
DIVX5_HOME_THEATER             --- not supported ---
DIVX5_HD_1080P                 --- not supported ---
H264_CONSTRAINED_BASELINE      51 16384  2048  2048
H264_EXTENDED                  --- not supported ---
H264_PROGRESSIVE_HIGH          --- not supported ---
H264_CONSTRAINED_HIGH          --- not supported ---
H264_HIGH_444_PREDICTIVE       --- not supported ---
VP9_PROFILE_0                  --- not supported ---
VP9_PROFILE_1                  --- not supported ---
VP9_PROFILE_2                  --- not supported ---
VP9_PROFILE_3                  --- not supported ---
HEVC_MAIN                      --- not supported ---
HEVC_MAIN_10                   --- not supported ---
HEVC_MAIN_STILL                --- not supported ---
HEVC_MAIN_12                   --- not supported ---
HEVC_MAIN_444                  --- not supported ---
HEVC_MAIN_444_10               --- not supported ---
HEVC_MAIN_444_12               --- not supported ---
AV1_MAIN                       --- not supported ---
AV1_HIGH                       --- not supported ---
AV1_PROFESSIONAL               --- not supported ---

Output surface:

name              width height nat types
----------------------------------------------------
B8G8R8A8         16384 16384    y
R8G8B8A8         16384 16384    y
R10G10B10A2      16384 16384    y
B10G10R10A2      16384 16384    y
A8               16384 16384    y

Bitmap surface:

name              width height
------------------------------
B8G8R8A8         16384 16384
R8G8B8A8         16384 16384
R10G10B10A2      16384 16384
B10G10R10A2      16384 16384
A8               16384 16384

Video mixer:

feature name                    sup
------------------------------------
DEINTERLACE_TEMPORAL             -
DEINTERLACE_TEMPORAL_SPATIAL     -
INVERSE_TELECINE                 -
NOISE_REDUCTION                  -
SHARPNESS                        -
LUMA_KEY                         -
HIGH QUALITY SCALING - L1        -
HIGH QUALITY SCALING - L2        -
HIGH QUALITY SCALING - L3        -
HIGH QUALITY SCALING - L4        -
HIGH QUALITY SCALING - L5        -
HIGH QUALITY SCALING - L6        -
HIGH QUALITY SCALING - L7        -
HIGH QUALITY SCALING - L8        -
HIGH QUALITY SCALING - L9        -

parameter name                  sup      min      max
-----------------------------------------------------
VIDEO_SURFACE_WIDTH              -
VIDEO_SURFACE_HEIGHT             -
CHROMA_TYPE                      -
LAYERS                           -

attribute name                  sup      min      max
-----------------------------------------------------
BACKGROUND_COLOR                 -
CSC_MATRIX                       -
NOISE_REDUCTION_LEVEL            -
SHARPNESS_LEVEL                  -
LUMA_KEY_MIN_LUMA                -
LUMA_KEY_MAX_LUMA                -


free(): double free detected in tcache 2
[1]    4236 IOT instruction (core dumped)  vdpauinfo


disregarding the double free at the bottom tongue, I see that the list of supported decoder capabilites is short, is this expected on this chip and the drivers I am using? it looks weird to me.

Offline

#2 2023-03-13 11:11:25

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,045

Re: vdpauinfo on irisXE

vdpau is designed by nvidia and works best on nvidia drivers. Intel does nothing with vdpau and uses VA-API .

The libva-vdpau-driver-vp9-git translates va-api calls to VDPAU calls and can be useful if your hardware supports vdpau but your appiication(s) don't .

Post the output of vainfo to verify which capabilities your intel gpu has.
Which application(s) are you trying to run with HW video acceleration ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2023-03-13 18:48:38

edge33
Member
Registered: 2023-01-29
Posts: 37

Re: vdpauinfo on irisXE

Lone_Wolf wrote:

vdpau is designed by nvidia and works best on nvidia drivers. Intel does nothing with vdpau and uses VA-API .

The libva-vdpau-driver-vp9-git translates va-api calls to VDPAU calls and can be useful if your hardware supports vdpau but your appiication(s) don't .

Post the output of vainfo to verify which capabilities your intel gpu has.
Which application(s) are you trying to run with HW video acceleration ?


thanks for the clarification smile
here's the vainfo output

Trying display: wayland
Trying display: x11
vainfo: VA-API version: 1.17 (libva 2.17.1)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 23.1.0 ()
vainfo: Supported profile and entrypoints
      VAProfileNone                   :	VAEntrypointVideoProc
      VAProfileNone                   :	VAEntrypointStats
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Simple            :	VAEntrypointEncSlice
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointFEI
      VAProfileH264Main               :	VAEntrypointEncSliceLP
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointFEI
      VAProfileH264High               :	VAEntrypointEncSliceLP
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointEncPicture
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:	VAEntrypointFEI
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSliceLP
      VAProfileVP8Version0_3          :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointFEI
      VAProfileHEVCMain               :	VAEntrypointEncSliceLP
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileHEVCMain10             :	VAEntrypointEncSlice
      VAProfileHEVCMain10             :	VAEntrypointEncSliceLP
      VAProfileVP9Profile0            :	VAEntrypointVLD
      VAProfileVP9Profile0            :	VAEntrypointEncSliceLP
      VAProfileVP9Profile1            :	VAEntrypointVLD
      VAProfileVP9Profile1            :	VAEntrypointEncSliceLP
      VAProfileVP9Profile2            :	VAEntrypointVLD
      VAProfileVP9Profile2            :	VAEntrypointEncSliceLP
      VAProfileVP9Profile3            :	VAEntrypointVLD
      VAProfileVP9Profile3            :	VAEntrypointEncSliceLP
      VAProfileHEVCMain12             :	VAEntrypointVLD
      VAProfileHEVCMain12             :	VAEntrypointEncSlice
      VAProfileHEVCMain422_10         :	VAEntrypointVLD
      VAProfileHEVCMain422_10         :	VAEntrypointEncSlice
      VAProfileHEVCMain422_12         :	VAEntrypointVLD
      VAProfileHEVCMain422_12         :	VAEntrypointEncSlice
      VAProfileHEVCMain444            :	VAEntrypointVLD
      VAProfileHEVCMain444            :	VAEntrypointEncSliceLP
      VAProfileHEVCMain444_10         :	VAEntrypointVLD
      VAProfileHEVCMain444_10         :	VAEntrypointEncSliceLP
      VAProfileHEVCMain444_12         :	VAEntrypointVLD
      VAProfileHEVCSccMain            :	VAEntrypointVLD
      VAProfileHEVCSccMain            :	VAEntrypointEncSliceLP
      VAProfileHEVCSccMain10          :	VAEntrypointVLD
      VAProfileHEVCSccMain10          :	VAEntrypointEncSliceLP
      VAProfileHEVCSccMain444         :	VAEntrypointVLD
      VAProfileHEVCSccMain444         :	VAEntrypointEncSliceLP
      VAProfileAV1Profile0            :	VAEntrypointVLD
      VAProfileHEVCSccMain444_10      :	VAEntrypointVLD
      VAProfileHEVCSccMain444_10      :	VAEntrypointEncSliceLP

I am using brave, hwacceleration is active in brave, I can see that in about://gpu, but I cannot hardware decode vp9 videos, let say youtube. I am reading the thread about hwAccel in chromium here on the forum, it looks like it has quirks.

Offline

#4 2023-03-14 12:44:35

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,045

Re: vdpauinfo on irisXE

edge33 wrote:

issuing grep -iE 'vdpau | dri driver' ~/.local/share/xorg/Xorg.0.log, I get:

[    10.129] (II) modeset(0): [DRI2]   DRI driver: iris
[    10.129] (II) modeset(0): [DRI2]   VDPAU driver: va_gl

first question, shouldn't my driver be iHD there? or is iris expected?

(Forgot to answer) .
The IHD functions on a different levle and would be shown as libva driver .
Iris is the most used intel mesa dri driver atm, older intel video uses crocus  .



Your procesor i5-1145g7 is from the Tiger Lake family which is mentioned on https://en.wikipedia.org/wiki/VP9#Hardw … mentations .
So there is hardware support for vp9 on your system , the problem lies in software support.

The vainfo does list VAProfileAV1Profile0 and AV1 is the successor of vp9 . (vp10 was never releaxsed, but it's functionality was added to av1 )
Does youtube support AV1 ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#5 2023-03-20 09:09:22

edge33
Member
Registered: 2023-01-29
Posts: 37

Re: vdpauinfo on irisXE

Lone_Wolf wrote:
edge33 wrote:

issuing grep -iE 'vdpau | dri driver' ~/.local/share/xorg/Xorg.0.log, I get:

[    10.129] (II) modeset(0): [DRI2]   DRI driver: iris
[    10.129] (II) modeset(0): [DRI2]   VDPAU driver: va_gl

first question, shouldn't my driver be iHD there? or is iris expected?

(Forgot to answer) .
The IHD functions on a different levle and would be shown as libva driver .
Iris is the most used intel mesa dri driver atm, older intel video uses crocus  .



Your procesor i5-1145g7 is from the Tiger Lake family which is mentioned on https://en.wikipedia.org/wiki/VP9#Hardw … mentations .
So there is hardware support for vp9 on your system , the problem lies in software support.

The vainfo does list VAProfileAV1Profile0 and AV1 is the successor of vp9 . (vp10 was never releaxsed, but it's functionality was added to av1 )
Does youtube support AV1 ?

I am not sure about the support for av1 on yt haven't checked. but I am seeing that chromium hw accell is pretty much hit or miss these days

Offline

Board footer

Powered by FluxBB