Package Details: chromium-vaapi 70.0.3538.67-1

Git Clone URL: https://aur.archlinux.org/chromium-vaapi.git (read-only)
Package Base: chromium-vaapi
Description: Chromium with VA-API support to enable hardware acceleration
Upstream URL: https://www.chromium.org/Home
Keywords: browser web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: samcv
Maintainer: OneObsession (maximbaz)
Last Packager: maximbaz
Votes: 55
Popularity: 9.083650
First Submitted: 2016-07-09 09:44
Last Updated: 2018-10-18 12:22

Dependencies (47)

Required by (36)

Sources (8)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

maximbaz commented on 2018-10-18 12:25

Thank you everyone once again, success is confirmed, I updated chromium-vaapi and chromium-vaapi-bin :)

maximbaz commented on 2018-10-18 08:19

Thanks to all of you! I think I realized where my confusion was. Because I saw the CFI patches being removed from upstream PKGBUILD, I thought the patch "cfi-issues-fix.patch" is also not needed. The build with CFI diagnostics failed over night, but I'm pretty sure restoring cfi-issues-fix.patch will fix everything. Will update this package in 4 hours if everything works well ;)

Bevan commented on 2018-10-18 07:37

I have not tested the build provided by @maximbaz, but was successful with my own build (at least on my system it works). Here's a diff that can be applied to this repository using git am:

https://gist.github.com/michaellass/307db43ae80f2fad6e68fb1297cf9c1f

Additionally you may replace the vaapi patch by the one provided by @xsmile to get rid of the offset warning during patch application.

foutrelis commented on 2018-10-17 20:44

Try doing a test build with CFI diagnostics enabled (jumbo also halves the build time):

use_jumbo_build=true use_cfi_diag=true use_cfi_recover=true

(It's probably a CFI issue since it SIGILL's at a ud2 instruction.)

xsmile commented on 2018-10-17 18:02

@maximbaz: Same issue here with your build. You could try building with the original PKGBUILD first. If that works, apply the VA-API patch on top of the existing source directory and rebuild to save some time. I did a build with the same VA-API patch (among others) and it works well.

maximbaz commented on 2018-10-17 17:42

I rebuilt it and still have the issue, could someone try this build and tell me if it works fine or you also reproduce the issue? I've just tried a regular chromium from [community], it opens fine for me.

Terence: the last build took 3h 50m, I have 8 CPU cores and 32GB of RAM, I build on ramdisk to speed things up a bit (BUILDDIR=/tmp/makepkg makepkg -scf).

Terence commented on 2018-10-17 13:41

@maximbaz : I'm curious to know how long it takes you to build it + your hardware.

maximbaz commented on 2018-10-17 13:27

Thanks as usual! The old patch still applied, so I already compiled a build, however it doesn't work properly, after I start chromium all I see is gray screen. Will try to recompile with your patch now.

xsmile commented on 2018-10-17 12:57

@maximbaz: See https://privatebin.net/?237cfe431420d5ba#/36wWT5rbY8gMS0yv9h1IF3JCUClytk1lztV7Fp5cZc= for the patch.

digitalone commented on 2018-10-07 13:47

Good news, after updating bin package, it's working now on AMD/ATI Radeon (without libva-vdpau-driver-chromium). Thank you. :)