chromium: hardware video acceleration with VA-API

agm28011997 · 2020-11-26 04:42:19

liewkj wrote:

AMDGPU MESA VA driver regressed since MESA 20.1.x for Ryzen. Only X11 session with --use-gl=desktop works. Wayland or --use-gl=egl caused AMDGPU to crash and unable to recover.
Bug had been filed, but issue likes this will take long time to resolve if ever. AMD is not very proactive in Linux driver quality, otherwise this is a very serious defect for user-space Va-API to crash the whole system.
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3656
Anyway, since it didn't crash on you, this is good news for you. Perhaps you aren't using Radeon Vega graphics. You should use chromium-vaapi instead. The log showed a known Wayland bug that was patched in AUR chromium-vaapi together with MESA package with ANGLE_sync_control_rate EGL extension.

then is only need to time to come to official repos.
I am using raven ridge man.
And I have another pc with amd graphics and I can not be more happy..
I had nvidias on my hand, intel and for the last amd. And I prefer amd and intel for support and amd for support and gaming. I am not agree with you on amd quality drivers.
Amd raven here and there is no session crash

agm28011997 · 2020-11-26 04:43:11

justkdng wrote:

@agm28011997
latest chromium needs some flags to enable ozone under wayland, you will be using xwayland without those flags I think.

the error is with these flags I think. Have you read that I use one flag to enabble egl?

agm28011997 · 2020-11-26 04:45:03

akarshanbiswas wrote:

agm28011997 wrote:
someone here with amdgpu has the chromium working in wayland with Vaapi?
Chromium vaapi on wayland/ozone is not implemented. Please check my earlier comment.
I have working chromium vaapi on xwayland by passing LIBVA_DRIVER_NAME=radeonsi as env.

I will be testing tomorrow because I am going to sleep now. I'll let you know if that helps but I think it won't since chromium is detecting the correct vaapi drivers and it's failing in the moment of playing. ( may be some regression since I am using manjaro day to day not arch)

agm28011997 · 2020-11-27 01:16:16

[25765:25765:1127/021520.131747:ERROR:gl_surface_presentation_helper.cc(259)] : GetVSyncParametersIfAvailable() failed for 3 times!

the same as before, vda error etc

justkdng · 2020-11-27 20:37:34

@agm28011997

I was talking about these flags, are you using them? Otherwise you'll be using xwayland.

--enable-features=UseOzonePlatform --ozone-platform=wayland

Last edited by justkdng (2020-11-27 20:37:54)

justkdng · 2020-12-05 06:23:58

Hello everyone, out of nowhere I started getting this errors under chromium, completely breaking gpu decode until I restart the browser:

[108932:108932:1205/011839.877629:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[108935:108950:1205/011840.243942:ERROR:ev_root_ca_metadata.cc(841)] Failed to register OID: 0
Fontconfig error: Cannot load default config file: No such file: (null)
[108941:28:1205/011922.492140:ERROR:batching_media_log.cc(38)] MediaEvent: {"error":"video decode error!"}
[108941:28:1205/011922.492225:ERROR:batching_media_log.cc(38)] MediaEvent: {"error":"video decode error!"}
[109443:109443:1205/011922.577815:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[108941:1:1205/011922.581521:ERROR:batching_media_log.cc(35)] MediaEvent: {"pipeline_error":3}
[109552:109552:1205/011928.167557:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[109228:7:1205/011932.248329:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[109247:7:1205/011932.250191:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[108941:8:1205/011932.253584:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[108941:7:1205/011932.253604:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.

Only some videos trigger this problem, mainly reddit ones, is it a problem with reddit or with my setup? my gpu is an rx 570.

This is an example video that triggers the problem.

Mischa85 · 2020-12-07 00:02:54

Video Decode Hardware acceleration is broken on Chromium 87:

Using libva-vdpau-driver-vp9-git on X11.

Chromium 86 works fine.

--use-gl=desktop triggers fault.

[47758:48536:1207/004928.612890:ERROR:vaapi_utils.cc(47)] vaMapBuffer failed: invalid VABufferID
[47758:48536:1207/004928.613097:ERROR:vaapi_video_decode_accelerator.cc(528)] Error decoding stream
[48183:20:1207/004928.633351:ERROR:batching_media_log.cc(38)] MediaEvent: {"error":"VDA Error 4"}
[48183:20:1207/004928.633474:ERROR:batching_media_log.cc(38)] MediaEvent: {"error":"video decode error!"}
[48183:1:1207/004928.633594:ERROR:batching_media_log.cc(35)] MediaEvent: {"pipeline_error":3}

https://github.com/saiarcot895/chromium … issues/102

Last edited by Mischa85 (2020-12-07 00:04:21)

yochananmarqos · 2020-12-07 00:05:19

Mischa85 wrote:

Video Decode Hardware acceleration is broken on Chromium 87:
Using libva-vdpau-driver-vp9-git.

Have you tried libva-vdpau-driver-chromium?

RotoDhoulmagus · 2020-12-19 01:39:33

On my Broadwell notebook with native wayland(sway with xwayland disabled), while no hardware video decode yet, lastest chromium finally boots and runs butter smooth.
So I suppose Electron apps may also work in native wayland in the near future? And then wayland can finally works as my main work envrionment.

primeos · 2020-12-19 11:43:13

I'll dump some information here regarding some of the recent questions:
- VA-API support for Ozone/Wayland is still WIP:
- Tracking issue: https://bugs.chromium.org/p/chromium/is … id=1116701
- WIP patchset (just found this, the previous one was deleted, not sure if this one's already usable): https://chromium-review.googlesource.co … /+/2592787
- VA-API via XWayland:
- Not sure if this still works. AFAIK it should still work with --use-gl=egl and Chromium+Mesa patches (but it wasn't fun to maintain so I stopped using that setup).
- Ozone/Wayland support in Electron (off-topic):
- Electron 12+ will support it (still experimental of course): https://github.com/electron/electron/pull/26022
- But it'll likely take quite some time until apps switch to that version (and e.g. RTC_USE_PIPEWIRE is still disabled)

Also: Many thanks to Ted Meyer (use_vaapi will default to true in M88+, we got a Linux flag to enable/disable it at runtime, and a few other nice fixes and improvements along the way) and Maksim Sisov (for his work on Ozone and working on VA-API support for Ozone/Wayland).

DAC324 · 2020-12-23 17:25:41

Hello,

looks like everything discussed here, is not (anymore?) possible if you are using Nvidia driver version 390 or lower. The MojoVideoDecoder built into Chromium simply does not work with that driver, no matter what you try to configure using libva-vdpau-driver-chromium or the flags.

If my memory serves me right, this should have been possible with previous Chromium builds.

Does anybody know since when MojoVideoDecoder ceased working with the legacy Nvidia drivers?

Thank you very much in advance.

Screenshot: https://i.imgur.com/06yxJqA.png

Last edited by DAC324 (2020-12-24 08:09:24)

liewkj · 2020-12-23 20:10:44

I use nvidia-390xx on GT730 (GK208) and H.264 always works for me. The GPU does not support VP9.
Frankly, no one really care. If it works, good. If it doesn't, you can't complain, or those who care step in and provide solutions.

That is the harsh reality, or use Windows.

seth · 2020-12-23 20:29:13

Where the GPU also doesn't support VP9…

@DAC324 please replace the oversized image w/ a link - or even better the about:gpu details…

DAC324 · 2020-12-24 08:35:52

seth wrote:

Where the GPU also doesn't support VP9…

That's why I have h264ify installed. It is supposed to force YouTube into delivering H.264 instead of VP9, if I am not completely mistaken.

seth wrote:

@DAC324 please replace the oversized image w/ a link - or even better the about:gpu details…

Fixed. Thank you for the hint.

About: GPU says:

https://pastebin.com/yjm8t5id

Last edited by DAC324 (2020-12-24 08:41:41)

seth · 2020-12-24 08:43:03

It is supposed to force YouTube into delivering

https://www.youtube.com/watch?v=5RyYrs5tu60
https://bbs.archlinux.org/viewtopic.php … 8#p1945088

pastebin wrote:

Graphics Feature Status
Canvas: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Hardware accelerated
OpenGL: Enabled
Hardware Protected Video Decode: Hardware accelerated
Rasterization: Hardware accelerated on all pages
Skia Renderer: Enabled
Video Decode: Hardware accelerated
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Version Information
Data exported 2020-12-24T08:25:06.763Z
Chrome version Chrome/87.0.4280.88
Operating system Linux 5.9.16-1-MANJARO

So it's HW accelerated and you're asking funny questions because you're using manjaro…

DAC324 · 2020-12-24 09:21:52

seth wrote:

It is supposed to force YouTube into delivering
https://www.youtube.com/watch?v=5RyYrs5tu60
https://bbs.archlinux.org/viewtopic.php … 8#p1945088
pastebin wrote:
Video Decode: Hardware accelerated
So it's HW accelerated.

Yes but as soon as HW acceleration is enabled, I get output similar to the following trying to playback a video: https://i.imgur.com/06yxJqA.png

I have to disable accelerated video decode in order to be able to watch a video.

Last edited by DAC324 (2020-12-24 09:29:43)

seth · 2020-12-24 09:36:00

I'd link the artifacts to the WM compositor or the selectively erased fact that this is actually a manjaro installation.
I can even play videos w/ ANGLE on the 390xx driver (and VP9 oc. isn't accelerated anyway - so you may want to look at the video stats what format yt streams when you get the artifacts and whether there's even a chance that this is GPU decoded at all)

DAC324 · 2020-12-24 10:53:34

seth wrote:

I'd link the artifacts to the WM compositor or the selectively erased fact that this is actually a manjaro installation.

Indeed, I was told that Arch does not have the Nvidia driver 390 for kernels >= 5.9 anymore. So it looks like that good old 550 GTX cannot be used with Arch

Plus: Version info in Chromium says Version 87.0.4280.88 (Offizieller Build) Arch Linux (64-Bit)

The WM compositor sound like an interesting hint as I am using xfce, and according to the wiki, the xfwm compositor may cause video tearing https://wiki.archlinux.org/index.php/Xfwm.

Unfortunately, disabling display compositing in xfwm4-tweaks-settings does not seem to help.

Reboot after that change did not help, either.

seth wrote:

I can even play videos w/ ANGLE on the 390xx driver (and VP9 oc. isn't accelerated anyway - so you may want to look at the video stats what format yt streams when you get the artifacts and whether there's even a chance that this is GPU decoded at all)

Here's the statistics of an example video:

https://i.imgur.com/P3eH2I6.png

Last edited by DAC324 (2020-12-24 12:04:37)

seth · 2020-12-24 13:45:50

https://aur.archlinux.org/packages.php? … _Search=Go
Information by random dudes on the interwebz is random…

It also doesn't matter that Manjaro shovels arch packages on your disk.
Manjaro is not archlinux the same way I don't magically become a car by tacking wheels to my hands and feet.

But in better news, the video is avc1 (ie. h.264) and should indeed be accelerated.

pacman -Qs '(vdpau|chromium)'

DAC324 · 2020-12-24 14:08:50

seth wrote:

pacman -Qs '(vdpau|chromium)'

Says:

local/chromium 87.0.4280.88-2
    A web browser built for speed, simplicity, and security
local/lib32-libva-vdpau-driver 0.7.4-6
    VDPAU backend for VA API (32-bit)
local/lib32-libvdpau 1.4-1
    Nvidia VDPAU library
local/lib32-mesa-vdpau 20.3.1-1
    Mesa VDPAU drivers (32-bit)
local/libva-vdpau-driver-chromium 0.7.4-7
    VDPAU backend for VA API. (special version for chromium)
local/libvdpau 1.4-1
    Nvidia VDPAU library
local/mesa-vdpau 20.3.1-1
    Mesa VDPAU drivers
local/vdpauinfo 1.4-1
    Command line utility for querying the capabilities of a VDPAU device

liewkj · 2020-12-24 20:53:22

@DAC324 Your NVIDIA GPU acceleration is busted. This is likely caused by Linux 5.9.x and you had failed to update or use nvidia-390xx-dkms.

GPU0	VENDOR= 0x10de [Mesa/X.org], DEVICE=0x1244 [llvmpipe (LLVM 11.0.0, 256 bits)] *ACTIVE*
Driver vendor	Nvidia
Driver version	390.138
GL_VENDOR	Mesa/X.org
GL_RENDERER	llvmpipe (LLVM 11.0.0, 256 bits)
GL_VERSION	4.5 (Core Profile) Mesa 20.3.1

seth · 2020-12-24 22:11:13

He's using manjaro because he "was told that Arch does not have the Nvidia driver 390 for kernels >= 5.9".
The driver says "nvidia" so the kernel module should™ be in place, but he's using the wrong libGL (?)

@DAC324, If that's not a misrepresentation in chromium, chromium should be the least of your problems.
Post

glxinfo
pacman -Qs '(nvidia|linux)'

and your xorg log.

You should not even be able to run glxgears and I'm surprised that chromium does't outright crash on you.
In any event, that's a good illustration why manjaro isn't supported. We don't know what you've installed and configured and you apparently don't either.

DAC324 · 2020-12-25 18:18:12

seth wrote:

Post
glxinfo

https://pastebin.com/cjurpZDx

seth wrote:

pacman -Qs '(nvidia|linux)'

https://pastebin.com/UUZ5RKEt

seth wrote:

and your xorg log.

https://pastebin.com/Bf0iCbzn

seth wrote:

You should not even be able to run glxgears

Interestingly, glxgears seems to run without problems (no stuttering).

5418 frames in 5.0 seconds = 1083.594 FPS
5039 frames in 5.0 seconds = 1007.659 FPS
4984 frames in 5.0 seconds = 996.796 FPS
...

seth wrote:

and I'm surprised that chromium does't outright crash on you.

Me either, after having read for a while here

But it runs, I am even writing this reply within Chromium.

seth wrote:

In any event, that's a good illustration why manjaro isn't supported. We don't know what you've installed and configured and you apparently don't either.

To be honest, you're completely right. But I guess installing Arch perhaps would not prevent me from not knowing what's installed, either

seth · 2020-12-25 18:41:17

[     4.277] (II) LoadModule: "glx"
[     4.278] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     4.289] (II) Module glx: vendor="X.Org Foundation"
…
[     4.305] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[     4.305] (EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
[     4.305] (EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
[     4.305] (EE) NVIDIA(0):     you continue to encounter problems, Please try
[     4.305] (EE) NVIDIA(0):     reinstalling the NVIDIA driver.
…
[     4.773] (II) GLX: Initialized DRISWRAST GL provider for screen 0

You do have

local/nvidia-390xx-utils 390.138-1
NVIDIA drivers utilities

so the problem is that the module path isn't extende what would be done by /usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf provide by that package - if this was archlinux.

=> Manjaro problem. Completely unrelated to chromium. Ask the Manjaro boards. Nobody here can possibly help you and it would violate board rules anyway.

digitalone · 2020-12-26 13:28:59

Guys, if you have issues in Chromium, start using Firefox, hardware acceleration is working good there.

Arch Linux

#451 2020-11-26 04:42:19

Re: chromium: hardware video acceleration with VA-API

#452 2020-11-26 04:43:11

Re: chromium: hardware video acceleration with VA-API

#453 2020-11-26 04:45:03

Re: chromium: hardware video acceleration with VA-API

#454 2020-11-27 01:16:16

Re: chromium: hardware video acceleration with VA-API

#455 2020-11-27 20:37:34

Re: chromium: hardware video acceleration with VA-API

#456 2020-12-05 06:23:58

Re: chromium: hardware video acceleration with VA-API

#457 2020-12-07 00:02:54

Re: chromium: hardware video acceleration with VA-API

#458 2020-12-07 00:05:19

Re: chromium: hardware video acceleration with VA-API

#459 2020-12-19 01:39:33

Re: chromium: hardware video acceleration with VA-API

#460 2020-12-19 11:43:13

Re: chromium: hardware video acceleration with VA-API

#461 2020-12-23 17:25:41

Re: chromium: hardware video acceleration with VA-API

#462 2020-12-23 20:10:44

Re: chromium: hardware video acceleration with VA-API

#463 2020-12-23 20:29:13

Re: chromium: hardware video acceleration with VA-API

#464 2020-12-24 08:35:52

Re: chromium: hardware video acceleration with VA-API

#465 2020-12-24 08:43:03

Re: chromium: hardware video acceleration with VA-API

#466 2020-12-24 09:21:52

Re: chromium: hardware video acceleration with VA-API

#467 2020-12-24 09:36:00

Re: chromium: hardware video acceleration with VA-API

#468 2020-12-24 10:53:34

Re: chromium: hardware video acceleration with VA-API

#469 2020-12-24 13:45:50

Re: chromium: hardware video acceleration with VA-API

#470 2020-12-24 14:08:50

Re: chromium: hardware video acceleration with VA-API

#471 2020-12-24 20:53:22

Re: chromium: hardware video acceleration with VA-API

#472 2020-12-24 22:11:13

Re: chromium: hardware video acceleration with VA-API

#473 2020-12-25 18:18:12

Re: chromium: hardware video acceleration with VA-API

#474 2020-12-25 18:41:17

Re: chromium: hardware video acceleration with VA-API

#475 2020-12-26 13:28:59

Re: chromium: hardware video acceleration with VA-API

Board footer