![]() Here, not so much.īasic web browsing functioned, but a crucial function didn’t: new windows. I have always had to set things up a lot to get it work even remotely acceptably, but under X11 it was always usable after that initial setting up process. This thing really does like to cause me problems. There were still issues that turned out to be rather major. With software, I did have to play around with stuff like VSCodium as that needs some extra launch flags to run under Wayland in general, but nothing too bad. Screen refresh rate and such also did not give me any problems either. There are a ton more, but shortcuts worked well.Īs mentioned earlier, graphical issues were not present. I could launch kitty (a terminal emulator) with Super and Enter and the app menu with Super and Escape. Using Super and my wasd keys I could position windows on my screen. Not quite as nice as a proper WM, but not bad at all. The UI worked with nice shortcuts and all that. Now that it was configured somewhat properly, it ended up being quite nice, mostly. Here are screenshots of the desktop and the sirula app menu config that I have: Just a bar, but none of the app menu or activities view stuff. I customized GNOME to be more usable for me. I had no flickering issues and apps ran, with a caveat: I was never able to run OBS on Wayland with my Nvidia card. This might be weird for a standalone WM person like me, but it is possible to strip down GNOME quite a bit, so it was viable in itself. I thus gave up on Sway and decided to try GNOME instead as GNOME had been supported for a long time. I adjusted the output to my screen’s refresh rate (240Hz) in the config and it did not help at all. However, there were a whole lot of graphical issues, such as flickering all over the place. This time software could run, which was a definite improvement. Yet again it launched fine, but the experience was still not very good. I followed the NixOS Wiki instructions for Sway and got it running with the same extra steps as before. I now run NixOS, but that should not affect Wayland much. Return to WaylandĪpproximately 2 weeks ago I figured I could try Wayland again. I did not bother troubleshooting too far as it was a beta driver and I did not feel like putting in the time at that point. I was able to run XWayland software, but nothing native. Namely, I was unable to run any software under Wayland. Secondly, I had to launch Sway with their unsupported GPU launch flag nonsense. Firstly, I had to ensure that the variable WLR_NO_HARDWARE_CURSORS was equal to 1 or the cursor would be invisible. The compositor worked, but it had its caveats. I tried Sway as that is a very well-known Wayland compositor. I first tried Wayland back when I was using Gentoo shortly after the 495 drivers were released into beta in Portage’s repositories as I felt like it might be functional at this point. My graphics card has been a RTX 2070 Super that I have had since long before I even tried Linux. This is also where I started my experience with Wayland. Thanks to this support, XWayland can now provide decent performance.ĭriver 495 finally brought along support for the more common GBM API. The driver version 470 brought along hardware acceleration for XWayland, which is a compatibility layer of sorts for running X11 software on Wayland. However, Nvidia has improved its support in recent times. There is also an EGLStreams compatible modification of wlroots called wlroots-eglstreams, though, which allowed more compositors (a compositor being the equivalent of a window manager/desktop), but I do not know how well that works. The only desktops or compositors properly supporting EGLStreams are GNOME and KDE. There is the Nouveau driver, which is an alternative open-source Nvidia driver, but I’ll discuss that later, too. The community hasn’t been able to implement the functionality either since those drivers are proprietary. Whereas the open-source drivers for Intel and AMD had implemented support for the GBM API, which is the more standard approach, Nvidia chose to go with the less used EGLStreams API. Some historyįor a long time, Nvidia has been far behind in terms of Wayland compatibility when compared to AMD or Intel. Wayland is another display protocol that, from what I understand, aims to be more modern, compact and secure than X11. However, it is an old piece of software that is to a degree optimized for the needs of an older age, which can be considered bloated and has some inherent security flaws like keylogging vulnerabilities. Traditionally, we have been using XOrg, or X11 in its current iteration, as the standard display server in Linux. My Experiences with Wayland and Nvidia in 2022
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |