With LIBVA_DRIVER_NAME=iHD variable set in /etc/enviroment only the h 264 works and Vp9 works only if you remove the variable #621
Comments
freefreeno
changed the title
|
@freefreeno After remove LIBVA_DRIVER_NAME=iHD, chrome browser should fall back to SW decoding. For VP9, I can see VpxVideoDecoder from your screenshot of chrome://media-internals. I am not sure which commit of iHD driver is used. Could you please try the latest commit? Recently, some VP9 profile patches are merged. Thanks. |
|
I am using from Arch AUR and it is the 19.1.0-1 so i think it is the latest.
|
|
Chromium is not using the software rendering after the variable is removed I dont't think. As you can see my videos are playing h264 and Vp9 videos WITH the variable removed but with the variable set in /etc/environment I can only play h 264. I don't even understand how the h 264 and Vp9 videos are being played after the variable is removed. Also I believe people with a little less knowledge would benefit from instructions on the variable because it took me a while to figure that part out myself and now once I have it all figured out it is not working. Maybe a little more info on where to set variable and such and how to check it with the vainfo and also the installing of the libva utils package. If you set the variable like this the vainfo command still shows error. These are your directions . Of course my path is correct. I just copied your directions. export LIBVA_DRIVERS_PATH=<path-contains-iHD_drv_video.so> BUT if you only set the variable like this then the vainfo command works and shows the info like I showed you up top but the Vp9 videos do not play. How am I able to play the Vp9 and the H264 videos without the variable set?? If you set my variables like they should which is like this. THEN THE vainfo command shows IF YOU REMOVE THE FIRST LINE WHICH IS THE PATH THEN vainfo SHOWS THE CORRECT INFO BUT MY VP9 VIDEOS DO NOT PLAY. WITH THE PATH REMOVED I GET THIS WHEN vainfo command is ran. "BUT NO Vp9" Same results when you set the exports in the bash.rc and reboot. video_codec_name | vp9 |
|
@freefreeno I mean software decoder not software rendering. VpxVideoDecoder from your chrome://media-internals should be software decoder. And MojoVideoDecoder is GPU accelerated which will use iHD driver. You can check chromium code to confirm it. |
|
I would Like to show you something. Just to see if it would change things I removed the driver and installed the older libva-intel and when I type the vainfo command I see that now I have the slice next to Vp9 and with you alls intel-media-driver I did not have that but the thing is that it still does not play the Vp9 so the libva-intel driver is doing the same thing besides it actually shows like I should be able to play the Vp9 videos.
Ok so what needs to happen is the software decoder should pick up what the driver can't decode but that is not what is happening. If I set the variable yes I can hardware decode everything but Vp9 but the software decoder does not pick up the slack. The software decoder does not work at all if you set the variable. It is either hardware decoded or the video does not play at all. But you will see above that the regular libva driver shows I can decode Vp9 but the same thing happens and the Vp9 hardware decoded videos fail to even play at all with i965 variable set. The intel-media-driver does not even show that it will decode the Vp9 for Intel HD 620 on i57200u but the libva-intel-driver does show it should work but it does not. It does the same thing as your driver and works for everything BUT Vp9 with mojo |
|
|
I compiled this driver yesterday and the same problem is still there. Mesa has been updated this morning. The hardware decoded Vp9 videos do not work on the old libva-intel and your intel-medi-driver. It did work a couple weeks back. Your driver doesn't even show to be capable to run Vp9 hardware decode on my system and it did a week or so ago. I have done everything possible including building and installing. it just doesn't work on my Intel HD 620 and what really sucks is once you set that variable then when a video fails to hardware decode well it just doesn't play AT ALL so I have to go remove the variable and then it works with software. Plain and simple it should fall back to software decode if hardware fails. Everything works but Vp9 with hardware accel but it doesn't automatically fall back to software decoder. IF YOU UNSET THE VARIABLE THEN IT WILL FALL BACK TO THE SOFTWARE DECODER WHEN IT IS NEEDED BUT IF YOU FOLLOW ALL THE GUIDE THEN THAT IS NOT THE CASE. THE GUIDES NEED TO BE CLEARED UP OR SOMETHING NEED TO BE FIXED. WITH VARIABLE SET I CAN PLAY H264 NETFLIX WITH MOJO DECODER AND A YOUTUBE VIDEO AT THE SAME TIME AND THAT MEANS THAT I AM USING HARDWARE AND SOFTWARE AT THE SAME TIME. |
|
@freefreeno Do you try it on Ubuntu/Fedora with the chromium upstream? Ubuntu/Fedora may be easier to debug and locate this issue. Thanks. |
|
Uh NO. How would an operating system that I have never used be easier to debug. I have everything set just like every wiki and everyone says and there is more than then environment variable going on. Me and everyone you see listed above says there Vp9 does not play any longer and that goes for intel-vaapi or intel-media driver. I can remove all the variables with the same results. I just wanted to know why I can not set the path variable and it work as it is supposed to. I can put the variable name in /etc/environment but not the path because when I do all the hardware acceleration stops working. |
|
@freefreeno I have not ArchLinux + Chromium browser to test currently. And I cannot find this issue on Ubuntu/Fedora. |
|
@freefreeno maybe you can enable libva trace and upload the logs also try debug version media driver to tell us the root cause |
|
Just an overview. I have all the latest packages from Arch Linux. When I did a clean install about two weeks ago I went thru everything again. Enabled early kms. Enabled huc and guc and can confirm kms and huc and guc is loaded. I have intel-media-driver, xf86-video-fbdev and libva-utils installed. I can set the variable for the name like so-LIBVA_DRIVER_NAME=iHD |
|
@freefreeno I am not sure if there is also i965 media driver at your platform. If yes, could you please remove it fully? Thanks. |
|
Yes we have the intel-vaapi driver in ther AUR. It is called libva-intel-driver and I have never installed it since I did my clean install 2 weeks back. I did try it and IT DID JUST LIKE THE INTEL MEDIA DRIVER. Same exact thing. I could set the name variable but not the path. Makes me wonder if it isn't a Arch Linux problem or not a problem but maybe something they are doing differently. I just want my stuff to work and I may not be the smartest person in the world but I am doing everything that is supposed to be done. I have also never had xf86-video-intel installed on this setup either so there has been nothing but mesa and I am on version 19.0.5-1. |
|
hi @freefreeno , 1. should set LIBVA_DRIVERS_PATH=/usr/lib/dri/, this variable should only include the path name exclude the driver so filename , vainfo should works with LIBVA_DRIVER_NAME=iHD & LIBVA_DRIVERS_PATH=/usr/lib/dri/ . 2. I still prefer to get the libva log or media driver log. simply export LIBVA_TRACE=folder name. you can get the libva traces. we can help check the call sequence. thanks. |
|
I have had it set this way the entire time. LIBVA_DRIVERS_PATH=/usr/lib/dri/ I did not think it was relevant because it is not the full path and it works the same way with or without the partial path set. Exactly the same. Either way I can not set the full path because error 1 and with the partial path set it works the same way as if I had it set with just the name. I can hardware decode everything but Vp9 and the vainfo command does not show opening driver I guess because the full path can not be set. It make no difference whether I set it like: or if I set it like LIBVA_DRIVER_NAME=iHD Both give the same results. Now can the intel media driver and the xf86-video-intel driver be ran in conjunction with each other or should you use only mesa with the intel-media-driver. If I can use the intel driver and the intel-media driver together then maybe I should try it because I have tried everything and I believe it has something to do with this environment variable. It surely has never once said opening the driver when I run the vainfo command. I would just like to get the most use from my PC and performance and I can't stand to have a problem that I can't solve so I am trying to solve this for myself and if I can solve it I will update the Arch wiki to reflect whatever is going on here. All the info I have placed here has been with the variable set just like you said. |
|
@freefreeno using ALL CAPS is generally viewed/interpreted as SHOUTING. If you need to emphasize something, please use other means like, bold, italics, etc... Thanks. |
|
I am not shouting but ok. lol |
No worries. It's just a netiquette thing and wouldn't want your posts to be taken the wrong way ;-) |
Sorry. If anything I am aggravated. I have posted to Arch site this week with no help there yet. Can someone please tell me if the old intel driver can be ran with the intel-media-driver?? I found some info on Arch wiki that says that if you want to take advantage of huc and guc and other things as well like fbc then that requires the old regular intel driver. I did not know that and I am not reading in between the lines to come up with that because it plainly say it in either the intel graphics section or the hardware acceleration section.Can someone to confirm or not confirm if the intel-media-driver can ran with xf86-video-intel? Exact words from wiki "Also, the modesetting driver will not be benefited by Intel GuC/HuC/DMC firmware" |
|
I also have same issue using arch linux and intel HD 630, it used to work few months before |
|
@alfinbi I have still not been able to resolve my issues and now I don't even think I can play any videos. I believe the issues is with the new chromium's. If you will install version 74.0.3729.169-2-x86_64 then I believe you will start back working then. Go to the aur and look at the comments there. It is known that the new versions break or hardware accel on Intel graphics but they are leaving it up to us to block the new updates. |
|
I have a similar issue. Use Archlinux as well. No crash here. Just unable to play VP9 or VP8 with hw-acceleration enabled in epiphany browser. What I've noticed is that the problem only seems to happen for me in applications that use gstreamer. I've installed gstreamer-vaapi and when I set LIBVA_DRIVER_NAME=iHD along with GST_VAAPI_ALL_DRIVERS=1 (because gstreamer won't actually use iHD if this isn't set. see: https://wiki.archlinux.org/index.php/GStreamer#Hardware_video_acceleration) When using mpv which uses ffmpeg as backend vaapi works as expected for both VP8 and VP9. |
|
I've also started experiencing this issue on debian with the iHD 20.1.1 driver version. we're working on shipping HW acceleration in chrome by default for linux here: https://chromium-review.googlesource.com/c/chromium/src/+/2288633 you'll notice that we used a workaround to ask chrome to switch to the i965 driver, if available. Obviously, we'd like to not have this workaround, but it seems that unless the crash goes away, we're stuck with it. I believe we are getting the same crash as described in issue #818 by calling VaPutSurface. |
|
also, as a note to @freefreeno DecryptingVideoDecoder is using widevine, which can punt the decoding issue off to software or hardware, depending on the license restriction from the video hosting service. Ideally you'd be seeing MojoVideoDecoder, which is a hardware decoder running in a separate thread with access to GPU resources. This should be coming by default to chromium / chrome soon. |
|
Hi @freefreeno, do you still meet this problem with latest iHD driver and chromium? |
|
We will close this issue since it exists for long time. Please feel free to re-open it again if you still meet similar issue. Thanks a lot. |
Sorry for the length of this but this is proof and I want to back up my claims. I am using Arch Linux with Intel HD 620 and Mesa and the this Intel-media-driver installed. No other drivers.
With the LIBVA_DRIVER_NAME=iHD set in /etc/environment the vainfo command shows this:
Also I have these settings in my graphics:
When I try to play a Vp 9 video it just loads and never plays.
But h 264 works fine
Ok. Now with if I remove the variable from the /etc/environment I can't use the vainfo command because it shows error because as far as I know you have to have the variable.
But even though the vainfo command shows error all my videos start back playing with both Vp9 and h 264. This is the exact same videos as above only this time without the variable.
This is the Vp9 youtube that would not play at all with variable set in Arch linux.
And I can still play my h264 content just as I could with variable set.
Same h264 video as above but this time without variable.
Now that is the problem. All the guides including Arch wiki say to set that variable and my system will not work with the variable set and and if you add the path which is LIBVA_DRIVERS_PATH=/usr/lib/dri/iHD_drv_video.so the vainfo command will not even work then even with both path and the normal LIBVA_DRIVER_NAME=iHD variable set. i said that because I know someone is gonna say to set the path also but I have tried.
The text was updated successfully, but these errors were encountered: