Chromium fails to start with Nouveau in dual GPU laptop (

[punishm...@gmail.com]

Hello all,

I just got a second-hand laptop with an Nvidia GTX 950M and an Intel iGPU. Distribution is Debian 10, with a custom-built 5.1 kernel and a custom-built Mesa 19.1.1

When Chromium / Chrome is run with DRI_PRIME=1 --enable-features=UseOzonePlatform,CanvasOopRasterization,UseSkiaRenderer --ozone-platform=wayland  --incognito --ignore-gpu-blocklist --enable-gpu-rasterization , the result is a corrupted window in Plasma Wayland (see image) while under Gnome Wayland the window doesn't even launch, and instead fills the console with a bunch of errors.

When running it in my workstation using a dedicated Nvidia GPU (GT 610) on the same installation of Debian 10, with the same custom-built 5.1 kernel and custom-built Mesa 19.1.1, Chromium can launch properly with GPU acceleration under Nouveau

This issue occurs on all versions of Chromium (and Chromium-based browsers) that I have built over the past two months. It may also have existed before then, but I no longer have my old builds anymore.

Logs will be added in followup emails.

Any help or information on this will be greatly appreciated!

[punishm...@gmail.com]

This is a screenshot of the corrupted window that shows up when running in Plasma Wayland:

[punishm...@gmail.com]

Please see attached  information:

• aboutGPU --> System information from Chromium 's chrome://gpu with using the --use-gl=swiftshader switch, which is the only way to get Chromium working on this laptop
• GnomeLogs --> console output information under Gnome (as mentioned earlier, the window doesn't even appear in Gnome)
• GnomeLogs-WaylandDebug --> console output information under Gnome with the WAYLAND_DEBUG=1 environment variable passed

[punishm...@gmail.com]

Bug 1209623 for this issue has also been filed under crbug.com

Please have a look and kindly assist, thanks!

On Sunday, May 16, 2021 at 10:45:49 PM UTC+8 punishm...@gmail.com wrote:

[matcheydj]

Apart from rebuilding Debian or trying proprietary drivers, have you looked at the chromium gpu flags?

Chromium - ArchWiki (archlinux.org)

>Force acceleration section

Other than that, DRI_PRIME=0 and/or allowing chromium to automatically select the most appropriate GPU might be worth a try (which might mean leaving that option off), I'm not sure, from my own experience, that you can force that identification on an integrated gpu; This ofc is with the force flags enabled in config. Pretty neat buggy screenshot :/ 

[punishm...@gmail.com]

Tried those as well, same results. :(

DRI_PRIME=0 works, but that's only because it uses the Intel iGPU. 

[Nicolas Capens]

On Sun, May 16, 2021 at 10:50 AM punishm...@gmail.com <punishm...@gmail.com> wrote:

Please see attached  information:

• aboutGPU --> System information from Chromium 's chrome://gpu with using the --use-gl=swiftshader switch, which is the only way to get Chromium working on this laptop

For what it's worth, using --disable-gpu should be a bit faster as it uses SwiftShader only for WebGL support, and more specialized CPU rendering for everything else. It doesn't solve the GPU problem you're experiencing, but should provide a better fallback experience.

• GnomeLogs --> console output information under Gnome (as mentioned earlier, the window doesn't even appear in Gnome)
• GnomeLogs-WaylandDebug --> console output information under Gnome with the WAYLAND_DEBUG=1 environment variable passed

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/d1d293aa-4ae4-4905-94c8-817858057d50n%40chromium.org.