Arch Linux

altermetax

Member

Registered: 2016-03-19

Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

I found out about the NVD_LOG=1 flag, which enables logging for the Nvidia VAAPI driver, and this is the output whenever I play a video:

      3513.303833546 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c:2187       __vaDriverInit_1_0 Initialising NVIDIA VA-API Driver: 31
      3513.303842625 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c:2196       __vaDriverInit_1_0 Now have 0 (0 max) instances
      3513.303846396 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c:2222       __vaDriverInit_1_0 Selecting Direct backend
      3513.303867335 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/direct/nv-driver.c: 295            init_nvdriver Initing nvdriver...
      3513.303886156 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/direct/nv-driver.c: 313            init_nvdriver NVIDIA kernel driver version: 570.144, major version: 570, minor version: 144
      3513.303890144 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/direct/nv-driver.c: 320            init_nvdriver Got dev info: 100 1 2 6
      3513.338286778 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c: 672           nvCreateConfig got profile: 32 with 1 attributes
      3513.338295491 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c: 693           nvCreateConfig got config attrib: 0 0 1
      3513.338572181 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c:1019          nvCreateContext creating context with 0 render targets, 0 surfaces, at 1920x1080
      3513.338579723 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c:1045          nvCreateContext 0/1 surfaces have been passed to vaCreateContext, this might cause errors. Setting surface count to 32
      3513.345680173 [22597-24274] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c: 414          resolveSurfaces [RT] Resolve thread for 0x78c08261400 started
[22597:24270:0520/231410.370820:ERROR:media/gpu/vaapi/vaapi_video_decoder.cc:1218] failed Initialize()ing the frame pool
      3513.346759730 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c:1118         nvDestroyContext Destroying context: 2
      3513.346764688 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c: 323           destroyContext Signaling resolve thread to exit
      3513.346766598 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c: 329           destroyContext Waiting for resolve thread to exit
      3513.346772860 [22597-24274] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c: 456          resolveSurfaces [RT] Resolve thread for 0x78c08261400 exiting
      3513.346791760 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c: 331           destroyContext pthread_timedjoin_np finished with 0
      3513.592500473 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c:2095              nvTerminate Terminating 0x78c03d78200
      3513.592578233 [22597-24270] ../nvidia-vaapi-driver-0.0.13/src/vabackend.c:2109              nvTerminate Now have 0 (0 max) instances

Xephon

Member

Registered: 2024-12-22

Posts: 189

Re: No GPU acceleration at all on Chromium Wayland

Well, not much on the web regarding that error. It's not nvidia-specific. And there is no information on what cases it or how to avoid it.

adolfotregosa

Member

Registered: 2025-01-23

Posts: 7

Re: No GPU acceleration at all on Chromium Wayland

Hi. Did you happen to find a fix? 5070 TI, 575.64, no video acceleration. It tries but fails.

"VaapiVideoDecoder: error decoding stream"
"video decoder fallback after initial decode error."
"Cannot select VpxVideoDecoder for video decoding"

(same on firefox, no video acceleration).

running on the terminal "nvidia-smi dmon" it's easy to see if it's working by looking at the "dec" column.

Xephon

Member

Registered: 2024-12-22

Posts: 189

Re: No GPU acceleration at all on Chromium Wayland

I haven't been looking for a fix since I don't have NVIDIA GPU. I used to have it but not anymore.

There is a recent post on libva-nvidia-driver github with a set of options that reportedly work on 575.64.

I'd also suggest to disable your iGPU in BIOS, because headless iGPU often leads to issues

adolfotregosa

Member

Registered: 2025-01-23

Posts: 7

Re: No GPU acceleration at all on Chromium Wayland

Thank you. You pointed me somewhere!

3dsboy08

Member

Registered: 2025-07-07

Posts: 1

Re: No GPU acceleration at all on Chromium Wayland

For those still experiencing this issue, I found that disabling my AMD iGPU in BIOS fixes this. (I have a 7950X3D + 4090 setup, if others want to check if this is AM5-specific)

I assume that Chromium is trying to launch with the AMD iGPU, not finding drivers for it, and having the GPU process crash as a result.

Last edited by 3dsboy08 (2025-07-07 03:19:03)