On 1/21/22 03:21, Martin Dosch wrote:
Hi,
there you go.
Best regards,
Martin
Thanks!
Wow, okay, this is not what I expected. The upstream version has
hardware acceleration disabled for your graphics hardware. Yet it's only
disabled if running in wayland native mode; it's enabled for X11 mode.
On the (intel-based gpu) install that I'm testing here, chromium in
wayland-native mode has hardware acceleration enabled.
I'm not sure why wayland native mode wouldn't be able to access hardware
acceleration; maybe wayland combined with mesa for some reason doesn't
support the hardware acceleration? But either way, it makes sense that
Debian's version crashes - we don't (yet) build swiftshader, which is
what the upstream version is using for software rendering. So either
mesa and wayland need to play nice together on newer amd hardware before
we can re-enable native wayland support, or we need to start building
swiftshader (and users will likely complain about slow graphics/heavy
cpu usage).
--- /tmp/debian-chromium.txt 2022-01-21 13:41:00.045761594 -0500
+++ /tmp/upstream-chromium.txt 2022-01-21 13:41:07.334007210 -0500
@@ -1,74 +1,35 @@
Graphics Feature Status
-Canvas: Hardware accelerated
+Canvas: Software only, hardware acceleration unavailable
-GPU0 VENDOR= 0x1002, DEVICE=0x15d8 *ACTIVE*
-GPU1 VENDOR= 0x1002, DEVICE=0x67ef
+GPU0 VENDOR= 0xffff [Google Inc. (Google)], DEVICE=0xffff [ANGLE
(Google, Vulkan 1.2.0 (SwiftShader Device (Subzero) (0x0000C0DE)),
SwiftShader driver-5.0.0)] *ACTIVE*
