Arch Linux

jeff_bh_221

Member

Registered: 2023-03-09

Posts: 5

Re: [wayland/ozone] Chromium based programs don't start | gpu errors

After some research, I personally concluded, and might be the closest reason (personally), it was "webgpu" features, which need some 3D/draw api supports that mesa(intel) didn't have(cuda?), then chome base things will looking for it(just like seth post), if not found, buggie~

Feels like~ similer to proton's dx api, some game run perfectly with very version , others won't.

checked paclog around if you have time, pkg egl-wayland(Provides libnvidia-egl-wayland.so) up? mesa you tested.

tried my best, good lucky~ both!!

edit:
Did some research more, (about chrome vaapi),check this paraments:

Full Vilkan support on native Wayland:
--ozone-platform=wayland --use-vulkan --enable-features=Vulkan,VulkanFromANGLE,DefaultANGLEVulkan

Optional hint for Vulkan:
--use-gl=angle --use-angle=vulkan
--enable-features=UseOzonePlatform

Optional Wayland hint:
--enable-features=WaylandWindowDecorations

VAAPI Decode (basic):
--enable-features=AcceleratedVideoDecodeLinuxGL

also zero copy variant:
--enable-features=AcceleratedVideoDecodeLinuxZeroCopyGL

VAAPI Decode (more options, not guarantee to work on new versions):
--enable-features=VaapiIgnoreDriverChecks,UseMultiPlaneFormatForHardwareVideo,PlatformHEVCDecoderSupport

VAAPI Encode:
--enable-features=AcceleratedVideoEncoder

also some other old options:
--enable-accelerated-mjpeg-decode --enable-global-vaapi-lock --use-gpu-scheduler-dfs --cast-streaming-hardware-h264

Other "performance" options
--enable-zero-copy --canvas-oop-rasterization --enable-gpu-rasterization
--enable-features=CanvasOopRasterization

Enabling Web GPU (only with unsafe option):
--enable-gpu --enable-unsafe-webgpu

Also a lot of workaround options like:
--disable-gpu-driver-bug-workarounds --ignore-gpu-blocklist
But they are for situations when "nothing helped"

!!! Do not try to enable Skia Graphite with Vulkan -- you will get neither Vulkan, nor Skia Graphite working !!!
!!! RawDraw with Vulkan "works" but you'll get content with all text disappeared !!!

from https://bbs.archlinux.org/viewtopic.php?id=244031&p=44 chaos-dremel

I have no problem when runs chromium on wayland(after use nvidia-dkms), but no hw acc , then saw this topic, lots of paraments about  vulkan,etc tried.
chromium was only chrome base software in my arch, same error when enable chromium's vulkan feature.
SO, DO YOU HAVE vulkan-intel pkg ? MAY NEENED!!

Last edited by jeff_bh_221 (2025-01-07 20:33:54)

seth

Member

Registered: 2012-09-03

Posts: 60,807

Re: [wayland/ozone] Chromium based programs don't start | gpu errors

In that case everybody w/ "only" an intel GPU could not run chromium…
Do you also have card0 and card1 reversed?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

TopCheddar27

Member

Registered: 2024-04-03

Posts: 2

Re: [wayland/ozone] Chromium based programs don't start | gpu errors

Just want to echo the same exact thing as OP. This happens on both my Arch Linux and Ubuntu 24.10 laptops under wayland.

These are both hybrid laptops, with the same exact errors in journalctl. For me, it mainly effects Chromium and disabling GPU rendering is a deal breaker.

Please note that I launch Chromium with Preferred Ozone Platform Wayland.

I have tried setting the prime profile to launch with the internal Intel Graphics and the NVIDIA discrete graphics, to no avail.

The frustrating thing is I'm not sure where the best place to file a bug for this. This is the first post with the actual problem that I have found. I have been running into this for a couple of months now with this hybrid laptop.

Last edited by TopCheddar27 (2025-01-20 16:30:33)

seth

Member

Registered: 2012-09-03

Posts: 60,807

Re: [wayland/ozone] Chromium based programs don't start | gpu errors

We lack a report on https://bbs.archlinux.org/viewtopic.php … 6#p2218726 (the theory being that the nvidia GPU ends up being card0 and chromium tries to run on that but using the mesa stack)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ComradeVanti

Member

Registered: 2025-01-23

Posts: 1

Re: [wayland/ozone] Chromium based programs don't start | gpu errors

Add i915 to the MODULES array, regenerate the initramfs and see what happens after the next reboot

I can tentatively confirm that this solved the issue for me.

I have a Lenovo Legion which has an integrated Intel GPU + Nvidia. I run Wayland and Plasma. In my case, the slow starting app was VSCodium, but only when specifying the wayand option. Adding the above to my MODULES, in addition to all the nvidia modules which were already there seems to have fixed it for me. App start is now as fast as with X11.

dext

Member

From: Poland, Kraków

Registered: 2008-02-01

Posts: 121

Re: [wayland/ozone] Chromium based programs don't start | gpu errors

Add i915 to the MODULES array, regenerate the initramfs and see what happens after the next reboot

I confirm it works. The order of cards is reversed, and I started getting many strange artifacts in the terminal. I always had them, but I didn't notice when they stopped. I mostly ignore it, because I have no issues in xorg/wayland sessions.
Also, my Nvidia card is not going to sleep anymore, but this is for another topic.

Thank you Seth.

seth

Member

Registered: 2012-09-03

Posts: 60,807

Re: [wayland/ozone] Chromium based programs don't start | gpu errors

Also, my Nvidia card is not going to sleep anymore, but this is for another topic.

Sure you didn't somehow ending up running the system/session on the nvidia GPU?
Doe "glxinfo -B" suggest you're defaulting to the IGP?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

dext

Member

From: Poland, Kraków

Registered: 2008-02-01

Posts: 121

Re: [wayland/ozone] Chromium based programs don't start | gpu errors

Also, my Nvidia card is not going to sleep anymore, but this is for another topic.

Sure you didn't somehow ending up running the system/session on the nvidia GPU?
Doe "glxinfo -B" suggest you're defaulting to the IGP?

"glxinfo -B" returns Intel.
I'm also not sure if that change broke Nvidia going to sleep, I was just verifying if hybrid system still works well and noticed it doesn't.
I'll go through tutorial on the Wiki, to verify everything and create another topic if necessary. Furthermore, I'll try to revert adding i915, but this is for when I'll need to reboot again.