Arch Linux User Repository

@mirh Fixed the dependencies, but I don't think an environment variable specific to Firefox is in the purview of this (or any) package; rather, Firefox users should add it to their system manually if and when they need it.

You should adjust the dependencies to more closely mirror those of the normal package

Btw last time I checked you also needed MOZ_DISABLE_RDD_SANDBOX=1 to make firefox happy.

To get this working on arch/firefox I had to 2 things:

1. Install firefox-vaapi to get dmabuf working. (they recently added my patch for nvidia)
2. Then I needed to recompile the official ffmpeg package adding --enable-vaapi to the PKGBUILD.

And now about:support shows I have HW support for video codecs

Thanks for this package. I'd just like to share what worked for me using a 3080 (drivers 525) on Xorg and Firefox 111.0.1:

Installing this package since it has direct-backend merged

In Firefox's about:config set:
- media.ffmpeg.vaapi.enabled to true
- media.rdd-ffmpeg.enabled to true [default]
- media.av1.enabled to true (if supported by the GPU) [default]
- gfx.x11-egl.force-enabled to true
- widget.dmabuf.force-enabled to true (required on drivers 500+, see the README upstream)

Then, though running vainfo alone didn't show the driver working, running vainfo --display drm --device /dev/dri/renderD128 shows that it works (typical of this current direct-backend stuff I guess?). So all it was needed (at least for me) was to explicitly tell Firefox to use the correct Nvidia gpu device (even with only one installed) with the environment variable export MOZ_DRM_DEVICE=/dev/dri/renderD128 where the number 128 may change to something like 129 when the local hardware includes multiple GPUs like having an Intel iGPU on 128 and then a dedicated Nvidia one on 129.

These steps have been scattered around the issues page upstream so checkout there if it doesn't work with this.

to conform with the other VA-API driver packages

@kajlao What part of this do you not understand. libva-intel-driver is also changed for this reason.

@Neurognostic libva-nvidia-driver should be renamed to nvidia-vaapi-driver, this is the correct name of the repo and the project.

@vkxx Your warning is unnecessary. This is a VCS PKGBUILD and behaves exactly as expected. Only thing wrong with it is it should be renamed to libva-nvidia-driver-git to conform with the other VA-API driver packages.

@alphabitserial The repository includes the headers from the open-gpu-kenel-modules project, so to use the direct backend the patch is not strictly necessary but can be used if you want the latest headers.

Warning: do not install this AUR because libva-nvidia-driver AUR is the same library but current version with bugs corrected! Maybe it's more optimal to remove AUR nvidia-vaapi-driver-git completely, but I don't know how to request it.

@kajlao: Please see the repository's README.

IMPORTANT: The direct backend is currently required on NVIDIA driver series 525 due to a regression (see issue #126).

and in the section on the direct backend:

This backend uses headers files from the NVIDIA open-gpu-kernel-modules project.

Sure, it compiles fine without it, but the EGL backend doesn't work on the latest version of the Nvidia driver. The PKGBUILD should be updated as per Sapphirus's suggestion to enable the user to choose between the default EGL backend and the Direct backend that works with the latest driver.

Please makes it conflict with libva-vdpau-driver