You are not logged in.

#1 2023-04-04 03:09:55

Katherine1
Member
Registered: 2011-05-02
Posts: 44

Wayland trouble after Mesa and Intel-Vulkan update

ROG Zephyrus M16 GU603ZX_GU603ZX
6.2.9-zen1-1-zen
KDE Plasma 5.27.3
Intel/NVIDIA Optimus


So things were previously fine. At some point today an update for Mesa and the Intel Vulkan drivers went out and I updated to them. It seems to have had a pretty poor effect on my browser. In a Wayland desktop, my browser (Vivaldi) is no longer running with any sort of hardware acceleration (it previously was just fine). Switching between it running in XWayland or natively in Wayland made no difference. Turning on Vulkan support in the browser caused starting the browser to lock up the entire desktop session. Something about the update is not sitting right.

EDIT: I've done downgrading and upgrading of the mesa drivers and Vivaldi, and it seems to be the mesa drivers. I've downgraded both the drivers and the browser to get back to a working state, and then merely upgrading the mesa drivers back to the current ones broke hardware acceleration on the known good Vivaldi build.

EDIT2: Here's what I'm seeing in the browser's diagnostic information:
When things are working:

GPU0
VENDOR= 0x10de, DEVICE=0x2420, DRIVER_VENDOR=Mesa, DRIVER_VERSION=23.0.1
GPU1
VENDOR= 0x8086, DEVICE=0x46a6, DRIVER_VENDOR=Mesa, DRIVER_VERSION=23.0.1 *ACTIVE*
Optimus
true

When hardware acceleration is broken:

GPU0
VENDOR= 0xffff [Google Inc. (Google)], DEVICE=0xffff [ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver-5.0.0)], DRIVER_VENDOR=SwANGLE, DRIVER_VERSION=5.0.0 *ACTIVE*
Optimus
false

It looks like something is breaking with detection of my laptop's hardware, but the why of it is still a mystery to me.

Last edited by Katherine1 (2023-04-07 11:22:54)

Offline

Board footer

Powered by FluxBB