-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VAAPI/Intel acceleration in Chromium 87 on Ubuntu 20.04 broken on initialization with VDA Error 4
#98
Comments
Same here (but nvidia, not intel) with 87.x. - downgrading to 86.x.y works (including hardware acceleration for everything(?) but 4k-60fps). |
Same thing here @miwalter |
@saiarcot895 problem reproduced with recently-released Can you reproduce the issue? Should I file a Chromium bug? |
VDA Error 4
VDA Error 4
I haven't had a chance to debug this, because I'm trying to play catch-up with the weekly releases. |
Can confirm on amdgpu, so something's generally broken with VAAPI on 87. I haven't yet had time to investigate. |
Same here, details |
Note: I am using VDPAU so I think this is not an issue related to Vaapi itself. I think this is related to recent Chromium code. |
With Nvidia and VDPAU, a workaround is to use a launch command This apparently is related to another filed bug and the angle driver: #91 (comment) |
I use "--use-gl=desktop" for a couple of month now, it does not enable hardware acceleration for 87.* builds (it does for 86.* builds!) on nvidia gpus. This is my command line (seen at chrome://gpu).
Using Xorg. Nvidia driver 450.80.02, GeForce GTX 1660 Ti. |
Weird. My current version is 87.0.4280.20 and working with —use-gl=desktop. Are you using nouveau/vaapi or proprietary drivers and vdpau? |
I'm using the proprietary drivers (so vdpau I guess). Are you sure, that "mojovideodecoder" (chrome://media-internals/) is used (e.g. using this video: https://www.youtube.com/watch?v=Xt5kJp9xOLw&t=0s)? Chrome tells me at the top of "chrome://gpu" it will be using hardware acceleration - but it does not (so, not using MojoVideoDecoder") for 87.* builds. |
You should ensure that vdpau-va-driver is installed. Yes, Mojo is used with 87, using --use-gl=desktop string. |
My friend, I'm sure, that hardware acceleration is working very good for many month (ok, maybe weeks) using 86.* - only thing different on my setup without working hardware acceleration is 87.* (I downgraded to 86 because of this bug). I think the problem is somewhere in the 87-release, not in my setup. vdpau is working here. I'm using it for mpv- and celluloid accelerated video playback, too.
|
Just to be sure, I tested the current 87-build a couple of minutes ago. No hardware acceleration - no video at all, to be honest (using --use-gl=desktop, otherwise plays video without acceleration): [42539:42539:1018/195341.402159:WARNING:gpu_video_decode_accelerator_factory.cc(223)] : Initializing VAAPI VDA. |
As a small update here, on 87.0.4280.11 on Ubuntu 20.04, hardware video decoding appears to be working on both AMD GPU (integrated GPU on Ryzen 3400G) and Intel GPU. AMD GPU:
On AMD GPU, h264 appears to be smooth (with the h264ify extension), but vp9 at 720p or greater (maybe 1080p or greater in some cases) is choppy, where it plays 2-3 seconds, pauses for 0.5-1 second, and resumes playing again. I've only tested up to 1080p. Intel GPU:
On Intel GPU, playback is smooth up to 1440p. |
Additionally, the |
Seems to be mandatory for Nvidia/VDPAU users. See: #91 (comment) |
it looks like my GPU (Intel UHD Graphics G1 (Ice Lake 32 EU)) is to new for the i965_drv_video.so driver. $ LIBVA_DRIVER_NAME=iHD vainfo $ LIBVA_DRIVER_NAME=i965 vainfo I want start Chromium with forced iHD but i looks like it always falls back or is hardwired to i965_drv_video.so and failed Hardware Acceleration. $ LIBVA_DRIVER_NAME=iHD chromium-browser --enable-logging=stderr --loglevel=0 --vmodule=vaapi_wrapper=4,vaapi_video_decode_accelerator=4 --ignore-gpu-blocklist --use-gl=desktop 'https://www.youtube.com/watch?v=1d0Zf9sXlHk' it try to move HD_drv_video.so -> i965_drv_video.so, so it is forced to use HD_drv_video.so an then i got this chromium-browser --enable-logging=stderr --loglevel=0 --vmodule=vaapi_wrapper=4,vaapi_video_decode_accelerator=4 --ignore-gpu-blocklist --use-gl=desktop 'https://www.youtube.com/watch?v=1d0Zf9sXlHk' Please help, i need Hardware Acceleration otherwise my Notebook get to hot and noisy :( |
@janek-git look in this file @saiarcot895 i only use iHD driver but get the same error as other here. Still can't stay full linux just because of that :') then bye windows ! Thanks for the work anyway ! |
@xontik Thanks for the Answer :) |
@janek-git it's normal, but at least with my solution you don't mess your system driver :) |
@saiarcot895 thanks for digging. My problem was that, as pointed by @JurgenWolf at #91 (comment) ,
After passing flag I'm editing the description to make that clear to new passersbys, and apparently Arch Wiki / Chromium / Hardware video acceleration (which is the reference documentation even on an Ubuntu machine) was already edited to mention this. With that, closing. To people still unable to get their accel working in 87, please create a new issue, to reduce confusion and isolate your case. Thanks everyone! |
https://www.linuxuprising.com/2018/08/how-to-enable-hardware-accelerated.html After 1 month of trying finally Hardware Accelerating is working on both Nvidia and Intel. For other people and my future reference I will write up the steps. OS: POP_OS! 20.04 run : if you are intel you should see output not -1 error. But if you see error. Install the vaapi driver listed above. or search and set this in environment variable sudo nano /etc/environment LIBVA_DRIVER_NAME=i965 here i965 is my driver name. for intel core i5 haswell architecture. if you are in NVIDIA: $ sudo nano /etc/environment add this two line LIBVA_DRIVER_NAME=vdpau check out if there's any output in $ vainfo you should see output. saying it's NVIDIA. $ LIBVA_DRIVER_NAME=vdpau chromium-browser --use-gl=desktop These are the flags I use in chromium --ignore-gpu-blacklist but in developer version .conf doesn't work. so turn of flags manually from chrome://flags |
This does not work for Nvidia.
|
It works. Follow the extras steps I wrote |
Of course I did - it did not work, as I wrote. FYI the switch --ignore-gpu-blacklist is deprecated, in the future you have to use --ignore-gpu-blocklist. |
I'm in POP_OS! 20.04 too. |
@saiarcot895 confirming that Intel VAAPI accel works great in |
The LIBVA_DRIVER_NAME=vdpau chromium-browser --ignore-gpu-blocklist --use-gl=desktop --enable-oop-rasterization didn't work for me either , ubuntu 20.04 , Version 88.0.4315.5 , nVidia RTX 2070 proprietary drivers, same VDA error 4 Failed to create dedicated X11 display! |
@cAstraea did you (or anyone else?) ever get this working? It is failing for me for the same error (google led me here). On |
I'm getting these issues as well.
|
Just to update everyone, I was getting the exact same error as @janek-git, on an Intel i7-1065G7 running Ubuntu 20.04 LTS
In order to fix the issue I had to compile Intel's Media Driver (https://github.com/intel/media-driver) That will compile the lib Pretty disappointing a distro like Ubuntu LTS is not keeping these libs up to date, expected better from a distro like Ubuntu. |
Just like @dylangerdaly I solved my issues with a new Intel driver. I did not recompile, but I installed intel-media-va-driver-non-free, and it now works perfectly. |
may can you post here from where you got the non free driver (ie direct from intel?) and which version number you use please? |
I run Pop!_OS 20.10 with default apt sources. I just ran apt to install intel-media-va-driver-non-free |
Hi Guys, ~$ chromium-browser --use-gl=desktop I had previosly Ubuntu 20.10, the same was working fine. |
Also on Mint 20.1 (focal), nvidia-driver-450, opera 74 (chromium 88) |
Hi same error here with Linux Mint, |
i also compiled the newest intel driver but sadly it doesnt work :( chromium-browser --enable-logging=stderr --loglevel=0 --vmodule=vaapi_wrapper=4,vaapi_video_decode_accelerator =4 --ignore-gpu-blocklist --use-gl=desktop 'https://www.youtube.com/watch?v=1d0Zf9sXlHk' Chromium Version: 89.0.4356.6 vainfo: |
Hi Guys, ///////////////////// I did follow this steps: https://www.linuxuprising.com/2021/01/how-to-enable-hardware-accelerated.html it work with this command (In my case): I hope this solution work for you guys |
@JohnBFrm thank you so much, dude, I had the same |
EDIT 2020-10-21 SOLVED
The Hardware-accelerated video decode flag is set to Disabled by default in 87, you need to enable it manually, by:
--enable-accelerated-video-decode
chrome://flags
and settingHardware-accelerated video decode
toEnabled
With the flag set, I confirm that hardware acceleration works for me in
87.0.4280.20-0ubuntu1~ppa1~20.04.1_amd64
on my Intel GPU with H264, VP8, VP9 videos.@saiarcot895 the usual thread 😄. This time,
Logs using --use-gl=desktop, failing on VAAPI init with "VDA Error 4"
chromium --incognito --ignore-gpu-blocklist --use-gl=desktop --enable-logging=stderr --loglevel=0 'https://www.youtube.com/watch?v=1d0Zf9sXlHk'
Logs using --use-gl=egl, failing differently:
chromium --incognito --ignore-gpu-blocklist --use-gl=egl --enable-logging=stderr --loglevel=0 'https://www.youtube.com/watch?v=1d0Zf9sXlHk'
Extra details:
86.0.4238.0-0ubuntu1~ppa1~20.04.1
acceleration was working well with--use-gl=desktop
on the same video (yes, my Intel GPU accelerates VP9, confirmed by vainfo and intel_gpu_top/media-internals on 86)LIBVA_DRIVER_NAME
betweeniHD
/i965
makes no difference.Feel free to ask for more details. As usual, thanks a lot for your packaging work 🙂.
The text was updated successfully, but these errors were encountered: