Closed Dirleye closed 9 months ago
Same here. Hasn't worked for a few driver versions including 545
is your ffmpeg version compiled with vaapi support? you can check this with ffmpeg -hwaccels
the output should include vaapi.
also, just adding the various variables to the enviroment files doesn't do anything until you log out and back in again.
@rkoot Thanks for the suggestions, I can confirm vaapi is listed under hardware acceleration methods and reboots did occur between switching where the environment variables were set.
@Dirleye Pending a better solution I found a workaround. I could not make it work with wayland but it did work in X11 with direct backend.
MOZ_DISABLE_RDD_SANDBOX=1 LIBVA_DRIVER_NAME=nvidia NVD_BACKEND=direct firefox
@Dirleye Pending a better solution I found a workaround. I could not make it work with wayland but it did work in X11 with direct backend.
MOZ_DISABLE_RDD_SANDBOX=1 LIBVA_DRIVER_NAME=nvidia NVD_BACKEND=direct firefox
Works fine for me in Wayland with same prerequisites
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.29.02 Driver Version: 545.29.02 CUDA Version: 12.3 |
|-----------------------------------------+----------------------+----------------------+
But with a little difference in the launch string:
NVD_BACKEND=direct MOZ_ENABLE_WAYLAND=1 EGL_PLATFORM=wayland MOZ_DISABLE_RDD_SANDBOX=1 LIBVA_DRIVER_NAME=nvidia firefox
MOZ_ENABLE_WAYLAND
will be unnecessary since 121
(I'm not sure that we still need to disable RDD sandboxing in newer versions of Firefox, cause it seems to be fixed)
NVD_BACKEND=direct MOZ_ENABLE_WAYLAND=1 EGL_PLATFORM=wayland MOZ_DISABLE_RDD_SANDBOX=1 LIBVA_DRIVER_NAME=nvidia firefox
Copying and pasting this to make sure everything is set up correctly still doesn't work for me. @m00r3ik what GPU are you using?
If it's working in Wayland on this driver for others, there's probably something set somewhere that's interfering somehow unless it's a generational thing with the GPUs.
@m00r3ik what GPU are you using?
+---------------------------------------------------------------------------------------+ | NVIDIA-SMI 545.29.02 Driver Version: 545.29.02 CUDA Version: 12.3 | |-----------------------------------------+----------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+======================+======================| | 0 NVIDIA GeForce RTX 2060 Off | 00000000:09:00.0 On | N/A | | 32% 34C P8 13W / 160W | 899MiB / 6144MiB | 1% Default | | | | N/A | +-----------------------------------------+----------------------+----------------------+
Also have this one (using Gentoo)
VDPAU_DRIVER=nvidia
#GST_VAAPI_ALL_DRIVERS=1
LIBVA_DRIVERS_PATH=/usr/lib64/dri
LIBGL_DRIVERS_PATH=/usr/lib64/dri
GBM_BACKENDS_PATH=/usr/lib64/gbm
$ file /usr/lib64/gbm/nvidia-drm_gbm.so
/usr/lib64/gbm/nvidia-drm_gbm.so: symbolic link to ../libnvidia-allocator.so.1
My symlink is a bit more direct but they lead to the same file so there shouldn't be a difference there.
'''
file /usr/lib64/gbm/nvidia-drm_gbm.so
/usr/lib64/gbm/nvidia-drm_gbm.so: symbolic link to ../libnvidia-allocator.so.545.29.02
'''
Adding those environment variables didn't help either. Perhaps it's a Turing vs Pascal thing? Thank you all for the suggestions so far.
Adding those environment variables didn't help either. Perhaps it's a Turing vs Pascal thing? Thank you all for the suggestions so far.
Maybe, but I don't think so, because all ok in 980Ti too And the last question. Perhaps you are using a flatpak/snap-installed version of Firefox? In this case, this driver may not work
Perhaps you are using a flatpak/snap-installed version of Firefox? In this case, this driver may not work
I'm using the version from the standard repos with Pacman so no issues there. Once I get some time I'll make a fresh install on another SSD and do nothing but set this up to rule out something external to this being the problem.
~Can you post a log of Firefox playing back a video with NVD_LOG=1
set? (make sure you don't have any other Firefox instances running when you start it, or it'll just reuse them and ignore the NVD_LOG environment variable).~
Sorry, I missed that you've already done that and didn't see anything. Can you try running Firefox with MOZ_LOG="PlatformDecoderModule:5,Dmabuf:5"
set instead?
Here is the log: log.txt
D/Dmabuf Failed to open drm render node ⁄dev⁄dri⁄renderD128 error No such file or directory
is odd since it definitely exists.
I'll try again without MOZ_DRM_DEVICE=⁄dev⁄dri⁄renderD128
set.
Edit: Removing MOZ_DRM_DEVICE=⁄dev⁄dri⁄renderD128
from my environment variables allows Firefox to correctly set the device to /dev/dri/renderD128
(???) and now both H264 and VP9 are working again via NVDEC.
I have absolutely no idea why that environment variable broke it but please do let me know if you find out. Thank you everyone for your suggestions once more.
I haven't had working video decode for a few driver versions now and I haven't been able to figure out why. I'm using EndeavourOS (Arch) with the latest Firefox and standard ffmpeg package.
nvidia-smi
:NVD_LOG=1 vainfo
about:config
:Additionally, the following environment variables are set in
~/.config/environment.d/moz.conf
:Though setting them in
/etc/environment
doesn't seem to make a difference./etc/environment
also contains:But setting these in the environment.d conf file also makes no difference.
Running
NVD_LOG=1 firefox
outputs nothing to the console - it's immediately ready for the next command. I feel like I'm missing something simple but I'm not sure what. Thanks in advance to anyone who tries to help me figure this out.