You are not logged in.

Pages: 1 2

#1 2025-05-18 22:06:11

altermetax
Member
Registered: 2016-03-19
Posts: 94

No GPU acceleration at all on Chromium Wayland

Hi, I'm having some issues with HW acceleration on Chromium on Plasma Wayland with the official nvidia drivers.
If I let Chromium run on XWayland (which it does by default) GPU support is ok:

*   Canvas: Hardware accelerated
*   Direct Rendering Display Compositor: Disabled
*   Compositing: Hardware accelerated
*   Multiple Raster Threads: Enabled
*   OpenGL: Enabled
*   Rasterization: Hardware accelerated on all pages
*   Raw Draw: Disabled
*   Skia Graphite: Disabled
*   Video Decode: Hardware accelerated
*   Video Encode: Software only. Hardware acceleration disabled
*   Vulkan: Disabled
*   WebGL: Hardware accelerated
*   WebGL2: Hardware accelerated
*   WebGPU: Disabled
*   WebNN: Disabled

However for some reason the framerate goes down a lot when scrolling (this only seems to happen on KWin, Hyprland is fine on XWayland). I thought using Wayland instead of XWayland would fix the issue, but if I set the flag --ozone-platform=wayland, no GPU support is available:

*   Canvas: Software only, hardware acceleration unavailable
*   Direct Rendering Display Compositor: Disabled
*   Compositing: Software only. Hardware acceleration disabled
*   Multiple Raster Threads: Enabled
*   OpenGL: Disabled
*   Rasterization: Software only. Hardware acceleration disabled
*   Raw Draw: Disabled
*   Skia Graphite: Disabled
*   Video Decode: Software only. Hardware acceleration disabled
*   Video Encode: Software only. Hardware acceleration disabled
*   Vulkan: Disabled
*   WebGL: Software only, hardware acceleration unavailable
*   WebGL2: Software only, hardware acceleration unavailable
*   WebGPU: Disabled
*   WebNN: Software only, hardware acceleration unavailable

Looking on the Internet, it looks like some people were having the same issue a couple of years ago, but it was fixed on a later version of Chromium. I'm on the latest version and I'm still getting this.

Last edited by altermetax (2025-05-18 22:07:23)

Offline

#2 2025-05-19 06:41:24

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

The fact that you see

Video Decode: Hardware accelerated

under XWayland doesn't mean that hardware acceleration actually works. The most reliable way to check if you have it is nvtop

To enable hardware video acceleration on NVIDIA you need two things:
1. https://wiki.archlinux.org/title/Chromi … celeration

Install the correct VA-API driver for your video card and verify VA-API has been enabled and working correctly, see Hardware video acceleration. For proprietary NVIDIA support, installing libva-nvidia-driver is required.

2. use the appropriate flags https://bbs.archlinux.org/viewtopic.php … 2#p2236902

Offline

#3 2025-05-19 11:57:13

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

I have done step 1 and 2, and vainfo shows this:

Trying display: wayland
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: VA-API NVDEC driver [direct backend]
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileVP8Version0_3          :	VAEntrypointVLD
      VAProfileVP9Profile0            :	VAEntrypointVLD
      VAProfileAV1Profile0            :	VAEntrypointVLD
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileHEVCMain12             :	VAEntrypointVLD
      VAProfileVP9Profile2            :	VAEntrypointVLD
      VAProfileHEVCMain444            :	VAEntrypointVLD
      VAProfileHEVCMain444_10         :	VAEntrypointVLD
      VAProfileHEVCMain444_12         :	VAEntrypointVLD

My Chromium flags are currently the following:

/usr/lib/chromium/chromium --enable-zero-copy --ignore-gpu-blocklist --use-cmd-decoder=passthrough --password-store=kwallet6 --enable-gpu-rasterization --disable-gpu-driver-bug-workarounds --enable-features=AcceleratedVideoDecodeLinuxZeroCopyGL,AcceleratedVideoDecodeLinuxGL,VaapiOnNvidiaGPUs --ozone-platform=wayland --flag-switches-begin --force-dark-mode --scroll-tabs=never --flag-switches-end

Still, on Wayland I have no acceleration:

*   Canvas: Software only, hardware acceleration unavailable
*   Direct Rendering Display Compositor: Disabled
*   Compositing: Software only. Hardware acceleration disabled
*   Multiple Raster Threads: Enabled
*   OpenGL: Disabled
*   Rasterization: Software only. Hardware acceleration disabled
*   Raw Draw: Disabled
*   Skia Graphite: Disabled
*   Video Decode: Software only. Hardware acceleration disabled
*   Video Encode: Software only. Hardware acceleration disabled
*   Vulkan: Disabled
*   WebGL: Software only, hardware acceleration unavailable
*   WebGL2: Software only, hardware acceleration unavailable
*   WebGPU: Disabled
*   WebNN: Software only, hardware acceleration unavailable

At this point I would assume I have no acceleration on Xwayland either, but at least the scrolling is sometimes smooth on Xwayland (it only stutters in certain moments). On Wayland it always runs at low framerates.

[Edit] When running on Wayland, I get the following errors on the command line:

Unsupported modifier, resource creation failed.
[5583:5583:0519/140506.826997:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT
Unsupported modifier, resource creation failed.
[5583:5583:0519/140506.827168:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ
[5583:5583:0519/140506.827254:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:916] CreateSharedImage: could not create backing.
Unsupported modifier, resource creation failed.
[5583:5583:0519/140506.827381:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT
Unsupported modifier, resource creation failed.
[5583:5583:0519/140506.827541:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ
[5583:5583:0519/140506.827683:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:916] CreateSharedImage: could not create backing.
Unsupported modifier, resource creation failed.
[5583:5583:0519/140506.827751:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT
Unsupported modifier, resource creation failed.
[5583:5583:0519/140506.827957:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ
[5583:5583:0519/140506.828202:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:916] CreateSharedImage: could not create backing.
[5583:5583:0519/140506.828301:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:401] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
[5583:5583:0519/140506.828484:ERROR:components/viz/service/gl/gpu_service_impl.cc:1173] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[5544:5544:0519/140506.833483:ERROR:content/browser/gpu/gpu_process_host.cc:956] GPU process exited unexpectedly: exit_code=8704
[5651:1:0519/140506.833579:ERROR:gpu/ipc/client/command_buffer_proxy_impl.cc:127] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
Unsupported modifier, resource creation failed.
[5790:5790:0519/140507.003125:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT
Unsupported modifier, resource creation failed.
[5790:5790:0519/140507.003292:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ
[5790:5790:0519/140507.003309:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:916] CreateSharedImage: could not create backing.
Unsupported modifier, resource creation failed.
[5790:5790:0519/140507.003327:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT
Unsupported modifier, resource creation failed.
[5790:5790:0519/140507.003342:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ
[5790:5790:0519/140507.003359:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:916] CreateSharedImage: could not create backing.
Unsupported modifier, resource creation failed.
[5790:5790:0519/140507.003374:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT
Unsupported modifier, resource creation failed.
[5790:5790:0519/140507.003389:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ
[5790:5790:0519/140507.003403:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:916] CreateSharedImage: could not create backing.
[5790:5790:0519/140507.003420:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:401] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
[5790:5790:0519/140507.003452:ERROR:components/viz/service/gl/gpu_service_impl.cc:1173] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[5544:5544:0519/140507.007238:ERROR:content/browser/gpu/gpu_process_host.cc:956] GPU process exited unexpectedly: exit_code=8704
Unsupported modifier, resource creation failed.
[5826:5826:0519/140507.199896:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT
Unsupported modifier, resource creation failed.
[5826:5826:0519/140507.200362:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ
[5826:5826:0519/140507.200677:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:916] CreateSharedImage: could not create backing.
Unsupported modifier, resource creation failed.
[5826:5826:0519/140507.201210:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT
Unsupported modifier, resource creation failed.
[5826:5826:0519/140507.201446:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ
[5826:5826:0519/140507.201578:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:916] CreateSharedImage: could not create backing.
Unsupported modifier, resource creation failed.
[5826:5826:0519/140507.201714:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT
Unsupported modifier, resource creation failed.
[5826:5826:0519/140507.201854:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ
[5826:5826:0519/140507.202127:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:916] CreateSharedImage: could not create backing.
[5826:5826:0519/140507.202537:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:401] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
[5826:5826:0519/140507.202786:ERROR:components/viz/service/gl/gpu_service_impl.cc:1173] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[5544:5544:0519/140507.216278:ERROR:content/browser/gpu/gpu_process_host.cc:956] GPU process exited unexpectedly: exit_code=8704
[5668:3:0519/140507.334587:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:10:0519/140507.334590:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.334612:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.334620:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:3:0519/140507.334654:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.334659:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:10:0519/140507.334657:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.334665:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.334687:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:3:0519/140507.334681:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:10:0519/140507.334687:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:3:0519/140507.334711:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:10:0519/140507.334711:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.334723:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.334724:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:3:0519/140507.334734:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:10:0519/140507.334741:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.334749:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.334787:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.334833:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.334873:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.334911:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.334953:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.334993:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.335040:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.335077:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.335107:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.335135:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:3:0519/140507.335439:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:10:0519/140507.335454:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335497:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:10:0519/140507.335530:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:3:0519/140507.335532:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.335449:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:10:0519/140507.335561:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335557:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:3:0519/140507.335577:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:10:0519/140507.335582:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335589:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.335589:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:3:0519/140507.335604:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:10:0519/140507.335607:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335609:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:9:0519/140507.335620:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:3:0519/140507.335623:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:10:0519/140507.335630:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335632:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335669:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335692:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335711:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335729:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335748:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335768:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335786:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335805:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.
[5668:4:0519/140507.335867:ERROR:cc/raster/zero_copy_raster_buffer_provider.cc:136] Creation of MappableSharedImage failed.

Last edited by altermetax (2025-05-19 12:06:03)

Offline

#4 2025-05-19 16:15:10

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

Some of the flags you're using are outdated and could even have harmful effect. Remove all of them except

--enable-features=AcceleratedVideoDecodeLinuxZeroCopyGL,AcceleratedVideoDecodeLinuxGL,VaapiOnNvidiaGPUs
--ozone-platform=wayland

If that won't work add VaapiIgnoreDriverChecks to the first flag

Last edited by Xephon (2025-05-19 16:15:47)

Offline

#5 2025-05-19 16:20:00

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

Nope, nothing changed with just those flags, both with VaapiIgnoreDriverChecks and without sad

Offline

#6 2025-05-19 16:37:32

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

Do you have iGPU?

Offline

#7 2025-05-19 16:38:50

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

Nope, I'm on a desktop with an Nvidia GeForce RTX 4070. The CPU does have integrated graphics, but they're not being used (the monitor is attached to the GPU).

Offline

#8 2025-05-19 16:49:01

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

Post output of

eglinfo -B

Offline

#9 2025-05-19 16:49:52

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

$ eglinfo -B
GBM platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.144
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.144
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.144
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Wayland platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.144
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.144
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.144
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

X11 platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.144
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.144
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.144
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.144
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.144
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.144
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.144
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.144
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.144
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
libEGL warning: egl: failed to create dri2 screen
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: zink Vulkan 1.4(NVIDIA GeForce RTX 4070 (NVIDIA_PROPRIETARY))
OpenGL core profile version: 4.6 (Core Profile) Mesa 25.0.5-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: zink Vulkan 1.4(NVIDIA GeForce RTX 4070 (NVIDIA_PROPRIETARY))
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 25.0.5-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: zink Vulkan 1.4(NVIDIA GeForce RTX 4070 (NVIDIA_PROPRIETARY))
OpenGL ES profile version: OpenGL ES 3.2 Mesa 25.0.5-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #2:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Graphics (RPL-S)
OpenGL core profile version: 4.6 (Core Profile) Mesa 25.0.5-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Graphics (RPL-S)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 25.0.5-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Graphics (RPL-S)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 25.0.5-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #3:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 25.0.5-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 25.0.5-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 25.0.5-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Offline

#10 2025-05-19 18:03:02

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

So iGPU is not disabled. Let's try this one

__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json chromium [flags]

Offline

#11 2025-05-19 20:14:24

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

Same results sad

Offline

#12 2025-05-19 20:56:12

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

Could you post the entire content of chrome://gpu?

Offline

#13 2025-05-19 20:59:08

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

Sure, here it is: https://moffa.xyz/tmp/gpu_internals.html

[Edit] and this is chrome://gpu while running on XWayland: https://moffa.xyz/tmp/gpu_internals_xwayland.html

Last edited by altermetax (2025-05-19 21:41:27)

Offline

#14 2025-05-20 07:36:23

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

It seems that chromium under wayland doesn't recognize your nvidia card as a rendering device. It uses swiftshader - a CPU-based implementation of vulkan. I'm not sure what could cause that.

Under xwayland chromium uses OpenGL on dGPU for composing but not for video acceleration. Let's focus on getting hw acceleration to work under xwayland first.

Post outputs of

printenv | grep -iE 'backend|libva|vendor'
cat /sys/module/nvidia_drm/parameters/modeset

Offline

#15 2025-05-20 12:14:19

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

First command doesn't seem to give anything useful, there's just the `PATH` variable with an unrelated occurrence of `vendor`:

$ printenv | grep -iE 'backend|libva|vendor'
PATH=/home/altermetax/.local/bin:/home/altermetax/.local/opt/flutter/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/cuda/bin:/opt/cuda/nsight_compute:/opt/cuda/nsight_systems/bin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl

Second command says Y.

Xephon wrote:

It seems that chromium under wayland doesn't recognize your nvidia card as a rendering device. It uses swiftshader - a CPU-based implementation of vulkan. I'm not sure what could cause that.

Have you looked at the logs at the end of chrome://gpu? Seems like there are GPU errors which end up triggering a GPU process crash.

Last edited by altermetax (2025-05-20 12:17:10)

Offline

#16 2025-05-20 15:37:25

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

I saw those errors. Something triggered GPU process to crash. But it's unclear what  that was.

Let's start with the following command

LIBVA_DRIVER_NAME=nvidia NVD_BACKEND=direct chromium [no --ozone-platform=wayland flag]

Offline

#17 2025-05-20 17:25:20

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

I got the following on stdout:

libva error: /usr/lib/dri/nvidia_drv_video.so init failed
[11771:11782:0520/192303.376200:ERROR:net/cert/ev_root_ca_metadata.cc:162] Failed to decode OID: 0
Warning: Couldn't find an EGLConfig rendering to a window for TextureFormat::RGBA8Unorm.
 - While trying to discover a BackendType::OpenGL adapter.
    at Initialize (../../third_party/dawn/src/dawn/native/opengl/ContextEGL.cpp:96)

And the following chrome://gpu: https://moffa.xyz/tmp/gpu_internals_xwa … irect.html

Offline

#18 2025-05-20 18:17:44

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

You dropped --enable-features along with --ozone-platform flag. You were not supposed to do it.

LIBVA_DRIVER_NAME=nvidia NVD_BACKEND=direct chromium [no --ozone-platform=wayland, add back --enable-features flag, add --render-node-override=/dev/dri/renderD<NUM>]

The last flag will be either --render-node-override=/dev/dri/renderD128 or ...D129

Run

ls -l /sys/class/drm/renderD*/device/driver

to find out which one corresponds to nvidia card

Offline

#19 2025-05-20 18:47:22

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

Stdout is same as above, without the libva error.

chrome://gpu: https://moffa.xyz/tmp/gpu_internals_xwa … tures.html

A curiosity: what do you look at in chrome://gpu to see whether video acceleration is working? I thought "Video Decode: Hardware accelerated" would be enough. Or are you talking about video encode?

Last edited by altermetax (2025-05-20 18:56:37)

Offline

#20 2025-05-20 19:01:04

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

A table called Video Acceleration Information, and according to chrome://gpu from your last post hw acceleration might be working now because it looks like this

Decoding 	
Decode h264 baseline 	 	48x16 to 4096x4096 pixels
Decode h264 main 	 	48x16 to 4096x4096 pixels
Decode h264 high 	 	48x16 to 4096x4096 pixels
Decode vp8 	 	 	48x16 to 4096x4096 pixels
Decode vp9 profile0 	 	128x128 to 8192x8192 pixels
Decode vp9 profile2 	 	128x128 to 8192x8192 pixels
Decode hevc main 	 	144x144 to 8192x8192 pixels
Decode hevc main 10 	 	144x144 to 8192x8192 pixels
Decode hevc main still-picture	144x144 to 8192x8192 pixels
Decode av1 profile main 	128x128 to 8192x8192 pixels

Before that it was empty. Check it with nvtop

Last edited by Xephon (2025-05-20 19:03:51)

Offline

#21 2025-05-20 19:07:30

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

Oh yeah, got it. But when I open the "media" tab in the devtools while playing a YouTube video it still says "hardware decoder: false": https://moffa.xyz/tmp/devtools-media.png
[Edit] How do I check it with nvtop? I see a chromium process in there, but I don't know if it's related to video decoding.

Last edited by altermetax (2025-05-20 19:09:47)

Offline

#22 2025-05-20 19:34:07

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

There should be a DEC % value > 0 above the graph if acceleration is working. But Dav1dVideoDecoder is AV1 software decoder, so it still doesn't work obviously.

Try to add additional environment variables

__GLX_VENDOR_LIBRARY_NAME=nvidia __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json LIBVA_DRIVER_NAME=nvidia NVD_BACKEND=direct chromium [flags]

Offline

#23 2025-05-20 19:38:39

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

This doesn't seem to change anything, unfortunately.

Offline

#24 2025-05-20 20:41:56

Xephon
Member
Registered: 2024-12-22
Posts: 125

Re: No GPU acceleration at all on Chromium Wayland

I found some info that AV1 often falls back to software rendering on libva-nvidia-driver.

Can you test a video with a different codec?

Offline

#25 2025-05-20 20:44:59

altermetax
Member
Registered: 2016-03-19
Posts: 94

Re: No GPU acceleration at all on Chromium Wayland

I tried a local MP4 with H.264, it says "Decoder name: FFmpegVideoDecoder" and "Hardware decoder: false".

Offline

Pages: 1 2

Board footer

Powered by FluxBB