Problems with Hardware acceleration environment variables [SOLVED]

freefreeno · 2019-05-31 21:12:45

I have only mesa and the Intel media driver installed with the libva-utils package so I can run the vainfo command. If I set the complete path in /etc/environment like:
LIBVA_DRIVERS_PATH=/usr/lib/dri/iHD_drv_video.so
LIBVA_DRIVER_NAME=iHD

then I get error 1 with vainfo command but if set it either with just the name like
LIBVA_DRIVER_NAME=iHD

or with a partial path like

LIBVA_DRIVERS_PATH=/usr/lib/dri/
LIBVA_DRIVER_NAME=iHD

then I can use the vainfo command but in the output I should be seeing where it says opening the driver file and I do not see that part. I am having problems with hardware decode Vp9 and that is how I found this. It works the same whether I have it like :
LIBVA_DRIVER_NAME=iHD

or
LIBVA_DRIVERS_PATH=/usr/lib/dri/
LIBVA_DRIVER_NAME=iHD

No matter which one of those ways it does not say opening the driver and it is supposed to because every output I have seen on the wiki and everywhere else shows opening the driver. Can someone please advise me to what is going on. Also my Vp9 decode should be working but it does not and maybe this is the reason. I have Kaby lake Intel HD 620 with early kms. I have reported this to github Intel-media-driver and they they say I have it set up correctly and that Arch is the only place they are seeing this so can someone please help me. I have been struggling with this for a couple weeks now.

Last edited by freefreeno (2020-02-11 03:25:31)

V1del · 2019-06-01 10:36:51

Post the verbatim commands and output you are getting in [ code ] [ /code ] tags instead of paraphrasing.

freefreeno · 2019-06-01 23:53:53

With variable set it like this in /etc/environment
LIBVA_DRIVERS_PATH=/usr/lib/dri/
LIBVA_DRIVER_NAME=iHD

  vainfo
vainfo: VA-API version: 1.4 (libva 2.4.1)
vainfo: Driver version: Intel iHD driver - 1.0.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
      VAProfileVP8Version0_3          : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointFEI
      VAProfileHEVCMain10             : VAEntrypointVLD
      VAProfileHEVCMain10             : VAEntrypointEncSlice
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointVLD

Last edited by freefreeno (2019-06-02 00:08:13)

jasonwryan · 2019-06-01 23:57:38

Don't include spaces inside the square brackets for code tags. V1del only did that so you would see how it works...

freefreeno · 2019-06-02 00:04:44

Thank you . I was confused. I used Arch for a couple years but not much on forums of any kind.

V1del · 2019-06-02 11:14:26

That looks like it's supposed to, why do you surmise you have a problem with hardware decoding? Looks like the driver open initial lines has been considered unnecessary and delegated to debug output or something (or they only happen with the older intel-vaapi, or libva1). FWIW I found this strange that anyone would hang themselves up over some line being present in that info output, so digging out your thread/issue on github doesn't show a single person claiming your decoding setup being broken due to some missing output in the info command.

Your actual issue is that you have decoding issues in specifically - and from what I'm seeing, only - chromium, these are known and the reason why the official Arch package got reverted and hardware decoding support removed again. From what I'm seeing you are already looking at all the relevant issues on the intel-media-driver pages where it is confirmed that it is an issue there/the interaction between the media driver and chromium.

CarbonChauvinist · 2019-06-02 15:44:42

Agree with everything in V1del's post -- are you able to download and play VP9 videos HW accelerated using i.e. youtube-dl and/or mpv?

freefreeno · 2019-06-03 07:44:03

First off it does not look like the ones on wiki or anyone else's at intel-media driver at github. It should say opening the driver in the little first section right after the command. Here is what is should say: https://wiki.archlinux.org/index.php/Ha … ing_VA-API
No I can not hardware decode Vp9 at all. It does the exact same thing with intel-vaapi-driver so that is not it either. It should have the slice by Vp9 also and it doesn't and I can't hardware decode Vp9 and I would imagine that is why. Other people reporting this at intel-media driver at github and seems to only reported for Arch. I can not play youtube videos at all unless I use the h264ify extension to convert it over. I have doubled checked all my work and even tripple checked it. There is a problem some where for sure. I don't have a powerful PC but it with the way I have it set up it should at least hardware decode.

Last edited by freefreeno (2019-06-03 07:50:35)

V1del · 2019-06-03 07:59:46

Have you actually tried? Again, according to that output everything is loaded correctly, the wiki output is with an older version of libva, where that additional output might've been added by default. Whether or not it is present, your posted output confirms that the driver is loaded correctly and VP9 Decoding available.

Stop hanging yourself up on this, your hardware accel is set up correctly to use intel-media-driver.

Acquire a vp9 video, run it with

mpv --hwdec=vaapi

post the terminal output.

freefreeno · 2019-06-03 14:06:03

But the thing is Vp9 does not work in chromium vaapi. All others do just fine. That command doesn't work on my setup.

Last edited by freefreeno (2019-06-03 14:14:22)

seth · 2019-06-03 14:43:52

https://bbs.archlinux.org/viewtopic.php?id=244031

V1del · 2019-06-03 14:47:14

Yes, and we and as shown from the various bug reports you yourself commented on, know that this is a specific interaction issue with chromium-vaapi which is a known bug. It doesn't work for anyone with the current stable versions from what I'm gathering. Your original question stated issues with the environment variables. We have established that these work correctly and are not actually an issue.

You should use that command (install the mpv package) to test whether you actually have an issue decoding VP9 or whether this is limited to the well known issues with chromium. If you can hardware decode a vp9 video with another player, then your original question is resolved and you should follow the relevant bug reports to get information on whether and/or when the chromium compatibility is fixed.

freefreeno · 2019-06-03 20:56:18

Can you explain why Arch is the only one that doesn't say " Trying to open /usr/lib/dri/i965_drv_video.so" after the vainfo command. Everyone's vainfo command brings back this result but not in Arch. This is for both intel-media-driver and the libva-intel-driver

$ vainfo
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.39 (libva 1.7.3)
vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 1.7.3
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Simple            :	VAEntrypointEncSlice
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSliceLP
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointEncSliceLP
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointEncSliceLP
      VAProfileH264MultiviewHigh      :	VAEntrypointVLD
      VAProfileH264MultiviewHigh      :	VAEntrypointEncSlice
      VAProfileH264StereoHigh         :	VAEntrypointVLD
      VAProfileH264StereoHigh         :	VAEntrypointEncSlice
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointEncPicture
      VAProfileVP8Version0_3          :	VAEntrypointVLD
      VAProfileVP8Version0_3          :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice

I know it is not relevant to you but I would like to know. And while I am here. Can the old xf86-video-intel be used in conjunction with the intel-media-driver or should I only use mesa. Reason I ask is because both the libva-intel-driver and the intel-media-driver say we need guc and huc loaded but on the wiki intel-graphics page it says that without xf86-video-intel guc and huc is basically useless. So in other words this has me thinking I need the old intel driver but from other sources like the driver github pages they say only mesa and whichever hardware acceleration driver you are using needs to be present. If huc and guc is no good with mesa then why does both drivers say it needs to be loaded. And thanks for the help.

Last edited by freefreeno (2019-06-03 23:54:34)

seth · 2019-06-03 21:19:39

I've no idea why arch is the only whatever to not say some paraphrased stuff (and I don't have VA capable HW), but I guess it relates to the LIBVA_MESSAGING_LEVEL=1 in /etc/libva.conf

sabroad · 2019-06-04 11:49:17

freefreeno wrote:

Can you explain why Arch is the only one that doesn't say " Trying to open /usr/lib/dri/i965_drv_video.so" after the vainfo command.

The libva package has LIBVA_MESSAGING_LEVEL=1 (ie. no INFO, only ERROR) in /etc/libva.conf . This has nothing to do with your problem though with chromium playback of VP9.

Did you check chrome://gpu for VP9 HW decoding info?

Last edited by sabroad (2019-06-04 11:50:36)

sabroad · 2019-06-04 12:13:05

freefreeno wrote:

VLC does work fine. It is only Chromium giving me fits

As you well know, VP9 videos on Intel don't play since [chromium] v73.

Last edited by sabroad (2019-06-04 12:18:23)

freefreeno · 2019-06-04 15:39:11

Thanks for the help. The post never started for the reason of why my hardware acceleration in Chromium wasn't working. It started for the reason of not getting all the info back from the vainfo command. Thanks for those of you that have helped. There is not another Distro or post I have ever seen that does not have the Trying to open /usr/lib/dri/i965_drv_video.so and I wanted to know why we are different. But people will be people and some of you think you can speak to people any way you want and you do this forum so much injustice it is pathetic. I do not post here and I hope this is my last but to those that helped I am in gratitude.

seth · 2019-06-04 15:44:03

Still nice to see that you replaced the paraphrased w/ the actual output *after* my post…

V1del · 2019-06-05 10:55:46

If you now believe us that you do not have a problem with the environment variables and understand the reason for why that output is omitted, can you please mark the thread as [SOLVED] by editing the title in your first post

Last edited by V1del (2019-06-05 11:22:01)

Lone_Wolf · 2019-06-05 12:32:28

freefreeno wrote:

There is not another Distro or post I have ever seen that does not have the Trying to open /usr/lib/dri/i965_drv_video.so and I wanted to know why we are different.

Archlinux vainfo used to show that also.
It looks like a change was made wrt messaging in libva 2.3.0-2 . see https://git.archlinux.org/svntogit/pack … 116b0ebe4a

The output with "trying to load" you posted was from libva version 1.7.3 .
Have you seen any vainfo output from libva 2.3.0+ with such lines ?

freefreeno · 2020-02-11 03:25:07

Everything works as it is supposed to by just adding:
LIBVA_DRIVER_NAME=i965

or if using the intel-media-driver which I prefer for newer hardware then it is:

LIBVA_DRIVER_NAME=iHD

also for intel-media-driver you may want to read the readme and enable guc and huc. I believe it just enables huc though but it uses guc to load huc if I have read correct info. Right now though my i7 9750H with intel UHD 630 seems to be less buggy with libva-intel-driver without the xf86-video-intel and just use modesetting as default plus libva-intel and I have no freezes in kernel 5.5-1. Kernel 5.4 was terrible though. I am marking thread as solved.

Sant0s · 2020-04-05 18:31:31

Any updates on this? I tested running mpv and confirmed that VP9 decoding works. Sadly, I cannot get brave browser to hardware decode VP9 (h.264 works without any trouble).

I assume error comes from the browser but I cannot test if it is brave specifically or chromium in general (the chromium-vaapi binaries were just recently pulled from the AUR).

I would appreciate any tips :)

Arch Linux

#1 2019-05-31 21:12:45

Problems with Hardware acceleration environment variables [SOLVED]

#2 2019-06-01 10:36:51

Re: Problems with Hardware acceleration environment variables [SOLVED]

#3 2019-06-01 23:53:53

Re: Problems with Hardware acceleration environment variables [SOLVED]

#4 2019-06-01 23:57:38

Re: Problems with Hardware acceleration environment variables [SOLVED]

#5 2019-06-02 00:04:44

Re: Problems with Hardware acceleration environment variables [SOLVED]

#6 2019-06-02 11:14:26

Re: Problems with Hardware acceleration environment variables [SOLVED]

#7 2019-06-02 15:44:42

Re: Problems with Hardware acceleration environment variables [SOLVED]

#8 2019-06-03 07:44:03

Re: Problems with Hardware acceleration environment variables [SOLVED]

#9 2019-06-03 07:59:46

Re: Problems with Hardware acceleration environment variables [SOLVED]

#10 2019-06-03 14:06:03

Re: Problems with Hardware acceleration environment variables [SOLVED]

#11 2019-06-03 14:43:52

Re: Problems with Hardware acceleration environment variables [SOLVED]

#12 2019-06-03 14:47:14

Re: Problems with Hardware acceleration environment variables [SOLVED]

#13 2019-06-03 20:56:18

Re: Problems with Hardware acceleration environment variables [SOLVED]

#14 2019-06-03 21:19:39

Re: Problems with Hardware acceleration environment variables [SOLVED]

#15 2019-06-04 11:49:17

Re: Problems with Hardware acceleration environment variables [SOLVED]

#16 2019-06-04 12:13:05

Re: Problems with Hardware acceleration environment variables [SOLVED]

#17 2019-06-04 15:39:11

Re: Problems with Hardware acceleration environment variables [SOLVED]

#18 2019-06-04 15:44:03

Re: Problems with Hardware acceleration environment variables [SOLVED]

#19 2019-06-05 10:55:46

Re: Problems with Hardware acceleration environment variables [SOLVED]

#20 2019-06-05 12:32:28

Re: Problems with Hardware acceleration environment variables [SOLVED]

#21 2020-02-11 03:25:07

Re: Problems with Hardware acceleration environment variables [SOLVED]

#22 2020-04-05 18:31:31

Re: Problems with Hardware acceleration environment variables [SOLVED]

Board footer