You are not logged in.

#1 2021-08-22 03:09:45

origamisith
Member
Registered: 2020-07-13
Posts: 31

Need sudo for vainfo; Chromium doesn't include support for VP9

I have been trying to play Stadia in 4k. My monitor and connection are adequate, but when I look in chrome://gpu I don't see the VP9 flag that is neccessary to run Stadia in 4k. So, I go looking to make sure everything is up to standard based on https://wiki.archlinux.org/title/Hardwa … celeration. I have an Intel i7-1065G7, so I make sure that intel-media-driver and linux-firmware are installed, and that LIBVA_DRIVER_NAME=iHD. Next, I try running "mpv --hwdec=auto aVideoIHave.mp4", and although it runs, I get this output:

 (+) Video --vid=1 (*) (h264 360x360 30.000fps)
 (+) Audio --aid=1 (*) (aac 2ch 48000Hz)
Cannot load libcuda.so.1
[ffmpeg] AVHWDeviceContext: Cannot load libcuda.so.1
[ffmpeg] AVHWDeviceContext: Could not dynamically load CUDA
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
[ffmpeg/video] h264_v4l2m2m: Could not find a valid device
[ffmpeg/video] h264_v4l2m2m: can't configure decoder
Could not open codec.

When I try to run intel_gpu_top (which requires sudo) while playing a 4k video with Chromium or mpv, I see no activity from the Video or VideoEnhance categories (although Render/3D and Blitter show activity).
When I try to run vainfo, it returns with "vaInitialize failed with error code -1 (unknown libva error),exit".
However, when I run sudo vainfo, it returns with

 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
      VAProfileVP8Version0_3          :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointFEI
      VAProfileHEVCMain               :	VAEntrypointEncSliceLP
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileHEVCMain10             :	VAEntrypointEncSlice
      VAProfileHEVCMain10             :	VAEntrypointEncSliceLP
      VAProfileVP9Profile0            :	VAEntrypointVLD
      VAProfileVP9Profile1            :	VAEntrypointVLD
      VAProfileVP9Profile2            :	VAEntrypointVLD
      VAProfileVP9Profile3            :	VAEntrypointVLD
      VAProfileHEVCMain422_10         :	VAEntrypointVLD
      VAProfileHEVCMain422_10         :	VAEntrypointEncSlice
      VAProfileHEVCMain444            :	VAEntrypointVLD
      VAProfileHEVCMain444            :	VAEntrypointEncSliceLP
      VAProfileHEVCMain444_10         :	VAEntrypointVLD
      VAProfileHEVCMain444_10         :	VAEntrypointEncSliceLP

And when I run the mpv test with sudo, I see activity in the Video category

Why aren't any of these checks working without sudo? My ultimate goal is to be able to play Stadia in 4k with the VP9 feature in Chromium, but Chromium doesn't work with sudo so I need these to work for my current user. Also, I tried making a brand new user and it suffers from the same issues as my current one.

Last edited by origamisith (2021-08-22 03:18:36)

Offline

#2 2021-08-22 10:01:35

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 23,950

Re: Need sudo for vainfo; Chromium doesn't include support for VP9

It rather looks like you've set LIBVA_DRIVER_NAME=vdpau somewhere. Double check your environment, and where exactly did you set that?

Offline

#3 2021-08-23 21:25:31

origamisith
Member
Registered: 2020-07-13
Posts: 31

Re: Need sudo for vainfo; Chromium doesn't include support for VP9

I set LIBVA_DRIVER_NAME in my .bashrc, and when I run

 echo $LIBVA_DRIVER_NAME 

it returns 'iHD'. I followed all suggestions at https://unix.stackexchange.com/question … -came-from to try and find any other place that LIBVA_DRIVER_NAME could have been set, but have come up empty. I even set LIBVA_DRIVER_NAME=iHD in /etc/environment, but the result is the same.

UPDATE: I'm not sure what happened, but somewhere along the way Chromium decided it would support VP9 encoding, even though I still need sudo for vainfo. So I guess somewhere along the way something worked out.

Last edited by origamisith (2021-08-24 02:00:32)

Offline

Board footer

Powered by FluxBB