egl-wayland

I don't think Wayland is fully ready, at least not with NVIDIA GPUs with limited GPU memory. I have a 7,000 word blog post and demo videos coming out this Tuesday with the details but I think I uncovered a driver bug having switched to native Linux a week ago with a low GPU memory card (750 Ti). Basically on Wayland, apps that request GPU memory will typically crash if there's no more GPU memory to allocate where as on X11 it will transparently offload those requests to system memory so you can open up as much as you want (within reason) and the system is completely usable. In practice this means opening up a few hardware accelerated apps in Wayland like Firefox and most terminals will likely crash your compositor or at the very least crash those apps. It can crash or make your compositor unstable because if it in itself gets an error all

The case that this is true is only if you don't have an Nvidia GPU or don't play D3D12 games. I tried it, discovered that Nvidia has a known regression that causes anywhere up to 25% lower performance compared to Windows in GPU limited games in D3D12, and immediately went back to Windows. I'll never understand why people keep championing Linux for gaming when it has such a severe regression on the most common gaming GPU vendor. Steam says 75%. An Nvidia employee even stated that the fix is not trivial so they're not committing to a timeline for a fix. This is a year+ old issue. They're never fixing it because it doesn't affect CUDA. https://github.com/NVIDIA/egl-wayland/issues/164#issuecommen...

Issue (1) has been a long-standing issue and a prolonged back and forth [0,1] between NVIDIA and Xorg/Wayland devs about implicit and explicit synchronisation protocols. It looks like the explicit sync protocol is in the process of getting merged upstream and the 555 series driver [1] will take advantage of this so hopefully things are looking better. Problem with wayland is that all of the driver, xwayland and every compositor must support the new protocol but it looks like mutter, kwin and wlr will eventually support it. That being said there are constantly new paper-cuts appearing with the NVIDIA driver and Wayland support so who knows what will break with the new driver. Definitely not a pleasant experience. I'm not saying that AMD is smooth sailing but at least you don't have to fight the driver at every new release. I'm afraid (2) w

Last time I tried the 535 driver, GPU copies from XWayland and Wayland were broken, as well as Vulkan in Wayland. Pretty much the only thing which works are GL applications in Wayland. I found that both of these had been previously reported by other issues: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1444 https://github.com/NVIDIA/egl-wayland/issues/72 I'm curious what kind of workloads you were running that you have had no issues. I wouldn't expect XWayland to have worked at all before Nvidia added GBM support.

Turns out that Ubuntu 22.04.2 LTS has a library out of sync.[1] No Wayland use of Vulkan on LTS until mid-2024. Apparently fixed in Ubuntu 22.10. Back to Xorg for now. [1] https://github.com/NVIDIA/egl-wayland/issues/80