Most of this article seems unnecessary in 2025 and is very specific to Arch.
For most distributions you can simply install the (proprietary) nvidia drivers and you're good to go.
There is generally no tweaking or command line changes necessary for Nvidia to work on Wayland, including multi-monitors with different resolutions and refresh rates.
In Arch, the current NVIDIA driver automatically sets KMS and the kernel command line and hyperland changes are no longer needed. Basically it just works now.
Almost true. Some versions of the drivers, yes. Other versions, no. I didn't notice this until a few months ago but every now and then I'd have things like external monitors not working or one of them not waking from sleep on its own. So after like a week of banging my head against the wall on what configuration file I must've changed to break something, I found massive amounts of posts saying "I updated the driver and the following is now broken" so as a desperate attempt I backdated. Fixed everything. Immediately told apt to never update that driver ever again. There are still issues sometimes (like if the computer has been up for a few weeks the driver fails to allocate memory on display plug in), but in general it's usable.
I recommend everyone not update those drivers unless they're not working, and don't be afraid to downgrade. Almost every version has people saying on their system something doesn't work.
How does the distribution make this an issue? You can always freeze drivers and install old ones. I get that it might not work out of the box, especially with rolling-release distros like Arch, but you also don't want rolling-releases for an older machine.
I had Nvidia up until a year ago or so. Every single time I had to do any kind of maintenance it was because of their drivers.
Since I don't play any more games than Minecraft and don't really need a fancy gpu I have switched to intel. Now I have two things which I buy intel only. GPUs and WiFi. I have had one glitch with opengl under a VM, but I am not sure that is intel only since it also had issues with my Nvidia card.
Half a dozen of NVidia cards in more than a decade on on Win/Lin. No major problems so far.. I had to install / remove drivers manually but only because I needed exact versions for some other software. Intel on Win/Lin works fine too.
What? The main difference between distros is the package manager. I don't see anything here that's distro specific other than editing the pacman config to enable multilib, which to be fair is default on with many distros.
But Systemd? That's on most distros these days. I'm pretty sure it is on all of those in the top 10.
Also, the OP is using CachyOS. You can tell b̶e̶c̶a̶u̶s̶e̶ ̶t̶h̶e̶y̶ ̶o̶p̶e̶n̶ ̶f̶i̶l̶e̶s̶ ̶w̶i̶t̶h̶ ̶n̶a̶n̶o̶ from the neofetch logo. But, I'll mention that if you checkout distrowatch, Arch based distros are incredibly common. Over the past 12 months the most downloaded distros are CachyOS (Arch), Mint (Deb/Ubuntu), MX (Deb), Debian, Endeavour (Arch), Pop (Ubuntu), Manjaro (Arch), Ubuntu, Fedora, Zorin (Deb/Ubuntu).
That said, you don't have to do any of this for either Endeavour (which I use) nor Manjaro (my old distro of choice). Along with Pop, one of the main motivations for these distros is Nvidia support. Really I don't expect most people to even be facing those problems these days. On Endeavour I've only run into one Nvidia problem over the last 5 years and it was when a beta driver conflicted with the most recent kernel. Super easy fix once I realized the problem.
On a side note/friendly reminder:
anyone that's using linux these days with an Nvidia card I suggest making sure your /efi partition is >1GB (at least 2GB but give it some headroom. Disk is still cheap). If you're putting the drivers in the kernel (you should), like done here, those are going to take up a lot of space. (If you get a space error, run `sudo du -ch --max-depth=3 /efi | sort -hr` to see the problem. You can, usually, safely delete any of the `initrd-fallback` versions and rerun `sudo reinstall-kernels`. They'll be built again but this will usually give you the headroom you need)
It feels surprising that there's people on hackernews without adblock considering that adblock is not just for blocking ads, but also malware, illegal tracking and blocking annoying and useless banners.
Well I run an ad blocker too, but maybe we should try browsing submitted URLs without blocking ads and only upvote them IF we can still read them like that.
brave seems to have some special sauce since it appears to be able to hide the fact that ads were removed. I am guessing they are doing so without triggering dom events.
My browser automatically blocked something that's triggering an overlay to "Disable any DNS / Extension Based AdBlocker to Continue" with no option to dismiss.
So the people on Hackernews with adblock aren't reading this.
Having failed to get Wayland working on Debian Trixie with a 1050 Ti as an upgrade from X11, I've given up for now and will try again when I switch to AMD. This is a workstation not used for games so it'd be good to have Wayland working right but I'm not wasting time fighting it, and it'll get the GPU from the gaming rig when it becomes due nullifying the problem.
What I don't get is if these are proscribed steps (and they do read as such) why are they not automated with the module install? Why are we still fighting these issues if the 'workaround' is linear and well described? Is it as flimsy a reason as "write-an-article, collect-advertising-revenue" rather than contribute code to the installer?
I have 3 intel gpus. One for light gaming and desktop use (3 screens), another one for light gaming and one for video transcoding. The experience is flawless for me. One of the cards seems to have issues with qemu and opengl rendering, but it is an older model and is no longer sold retail.
I have an intel/nvida 4080 pc and im running a regular Arch install, rocking KDE on Wayland. It works flawlessly, just installed the drivers and that was that. Stop inventing problems that do not exist.
You can do that now, and for at least the last year.
Very few games don't work anymore, and most that don't are using kernel level anti-cheat or are generally hostile to users anyways (Fortnite and Destiny 2 could work, but they actively block Linux).
I main Fedora with an Nvidia 3080 and haven't had issues for quite some time now.
I'd just go AMD. The drivers there are much more mature due to Google and Valve contributions, and the performance of an 9070 XT is great while being cheaper than the equivalent 5070 Ti. FSR4 is a solid competitor to DLSS and works in any game that supports FSR 3.1.
Anti-cheats won't work, I keep a Windows drive just for Battlefield 6.
I got fed up about a week ago and ditched my Nvidia GPU for a 9070XT.
I run CachyOS and have been having a nightmare of a time on Wayland with my 3D Printer slicer and other tools I use my computer for being unusable.
The only thing that has ever kept me on Nvidia all these years is that they have been killing AMD performance wise for gaming.
The 9070XT is easily performant enough for the gaming I'm doing at the moment, and I can finally ditch the last major headache I've had in two and a half decades of being a Linux user - NVIDIA drivers - good riddance.
I don't play online games other than Helldivers 2 (so anti-cheat is a non-issue) which is working just fine at 70-80FPS max settings in 4K. Also getting good performance with RT off playing Ghostwire in 4K with settings as high as I can get them while staying above 60 FPS with Freesync.
EDIT: 9070XT seems to have a bit of headroom too I got the Asus PRIME OC version; Using LACT I upped the power limit from the stock 317W to 340W and undervolted by -100mv (YMMV on this value) and can get a decent chunk of extra performance out of it.
I'd probably say at least Gold is "reliably click and play without fiddling", so probably we're around 20-50% there right now, if we consider the top 10 games on Steam. Once you start considering top 100 or top 1000, it starts to look a lot better. But still, mainstream games are lagging seemingly.
It has been my experience that this is currently the case. I haven't had to even open protondb or search for a workaround in over a year. The only titles I know that don't work are a handful of multiplayer games that have intentionally disabled linux support.
I can run 99% on Linux + AMD + X11, on Ubuntu 24. The only problematic one is Witcher 3 which insists on Wayland which breaks everything else. Even the UT5 titles work well enough, but then again our gaming is not your gaming and you might be more demanding that we are.
I'm trying to recall how NVidia behaved for games, but my daily driver is an old 1050 Ti that's been rock solid for years now, also X11.
Kinda now. That's what I've been doing for a while now.
I have a PC though, not a laptop. Running CachyOS with 4070Ti, GNOME with Wayland. Even VR works
I don't even know when I ran into a game that didn't run off Steam on Linux. There's some fiddling gamescope on Wayland to get them to perform well, but most just run out of the box with great performance.
The stuff that doesn't work typically don't work because kernel level anticheats, so a few competitive titles but even in that space many titles still run.
I'd wager that 95% of Steam titles does run on Linux. Admittedly some big and popular games use invasive anti-cheat that's not supported, but they're less than 5%.
Many of the replies completely missed the part about Nvidia, sigh.
I unfortunately still see a lot of Proton bug reports that don’t repro on AMD cards. Hoping that improves soon, I’m sure Valve would love to tell hardware makers that Nvidia GPUs are supported.
I've been using 30s and 40s just fine with both nvidia and nvidia-open so every time I see this I don't really understand what card or game we're talking about.
On the other hand when I tried a 6xx0 XT I always ran into an infamous "ring gfx timeout" GPU crash with certain applications on WINE [0]. Ended up giving that card to a cousin.
I have an nvidia card on catchyos with catchyos proton and I have not ran into a single game that does not run, well ok some only walk, but that's also a problem on AMD.
I am excluding games that rely on a kernelmode anticheat.
Games I've played on my Arch Linux desktop with a 4090 in the past few months: Clair Obscur, Disco Elysium, Outer Worlds, Red Dead Redemption 2, Cyberpunk, Dispatch, Silent Hill f, FFVII Rebirth. I haven't had a single issue with any of these games. What games do you think will struggle? I can give them a shot if I own then and let you know how they do.
I still get fairly regular graphical glitches on Bazzite (Wayland) with a 3060ti. Certainly better than it used to be, but doesn’t quite feel there yet.
Hm, I've recently noticed kwin taking up what seems like way too much CPU at idle. Fedora with KDE. Happens on both X11 and Wayland with Wayland being worse and perceptibly slower.
I think for me jetbrains applications cause a memory leak in KWin which actually is becoming less of a problem now that I am switching to neovim slowly but surely.
To be clearer, as each wayland desktop pretty much creates their own incompatible wayland compositor (because wayland protocol is minimal and not feature complete) this is just a guide to fixing the hyperland broken wayland desktop. Not all waylands' broken desktops.
This is an incomplete list of protocols that aren't part of core Wayland. Compositors implement additional protocols that aren't even part of this process (e.g. wlr-screencopy-unstable). See the wlroota protocols here: https://gitlab.freedesktop.org/wlroots/wlroots/-/tree/master...
Right but there's the xdg-portal for screen capture which runs through Pipewire and supports sand-boxing (because its negotiated over dbus), which all the main compositors support.
Just because a protocol isn't part of Wayland, doesn't mean a standard protocol does not exists.
nvidia on linux [for desktop] is utterly broken.
I ran nvidia cards for almost 15 years (shame on me): laggy X11 compositing, fragile and broken wayland. Broken suspend/resume.
Too many moving parts (selected drivers, modprobe quirks, suspend/resume scripts).
Moved to amd: slick x11, reliable wayland, NO MORE DRIVERS AT ALL, works like charm.
And yes, I do playing in Linux.
Suspend/resume was broken in nvidia since release on aug 2024. I have internal bug id for it. And dozen links with suspend scripts.
No more drivers I mean I don't need to install dozens of packages. While it not big deal by itself, but reverting broken driver is huge deal.
Laggy desktop -- this is my experience until nov 2025 when I dumped nvidia. Desktop on both intel and amd feels like magic after nvidia.
Suspend/resume is broken for my friend with an AMD card right now. That's what I mean: it's broken everywhere in slightly different ways, yes even on Windows. Thankfully I never use it anyway.
Dunno anything about dozens of packages, I installed 1 (one) package from my distro and haven't touched it since, no issues with updates either. That same friend with an AMD card keeps getting random hard PC freezes during gaming though.
Also absolutely zero issues with lags/latency for me (on GNOME. I did experience a bunch of weird bugs with KDE, but again - no lags)
One thing that is very real is DirectX 12 performance. This one really does suffer due to poor nvidia drivers. Hope they iron it out at some point
ChromeOS is a far better "Grandma" distribution than Windows or MacOS. Linux is simultaneously both the most Grandma friendly and least Grandma friendly, including every point in between.
You need to compare apples to apples, aka pre-installed vendor supported operating systems. If you're comparing installing an unsupported OS on unsupported hardware, Linux is far superior. Try installing MacOS on a Windows computer or Windows on a Mac if you're truly masochistic.
Are you saying windows and macos do not have any bugs? I have news for you.
Also wevare talking here about archlinux + hyperland compositor, not the typical Fedora, Mint or Ubunti/Zorin distro. Tinkerer's gonna tinker while the other users just use their computer regardless of the OS.
Linux isn't a single OS. It's hundreds of different and weird combinations.
There are Linux distributions that are better than Windows or iOS for grandma to use as well as distributions where you need to be an expert to do anything.
It doesn't matter, your options are either X11 or a Wayland-based compositor, both of them come with their respective headaches that a regular user has NO IDEA how to fix.
Most of this article seems unnecessary in 2025 and is very specific to Arch.
For most distributions you can simply install the (proprietary) nvidia drivers and you're good to go.
There is generally no tweaking or command line changes necessary for Nvidia to work on Wayland, including multi-monitors with different resolutions and refresh rates.
In Arch, the current NVIDIA driver automatically sets KMS and the kernel command line and hyperland changes are no longer needed. Basically it just works now.
Almost true. Some versions of the drivers, yes. Other versions, no. I didn't notice this until a few months ago but every now and then I'd have things like external monitors not working or one of them not waking from sleep on its own. So after like a week of banging my head against the wall on what configuration file I must've changed to break something, I found massive amounts of posts saying "I updated the driver and the following is now broken" so as a desperate attempt I backdated. Fixed everything. Immediately told apt to never update that driver ever again. There are still issues sometimes (like if the computer has been up for a few weeks the driver fails to allocate memory on display plug in), but in general it's usable.
I recommend everyone not update those drivers unless they're not working, and don't be afraid to downgrade. Almost every version has people saying on their system something doesn't work.
My "gaming" laptop is completely effed on most distributions, and forces me to use Linux Mint to select an older driver (which also causes problems.)
that sounds like a firmware issue rather than a driver one, laptops are known to have horrible apic including on windows (ex: asus laptops). https://github.com/Zephkek/Asus-ROG-Aml-Deep-Dive
I assume you have 2 GPUs and one is integrated?
I had Nvidia up until a year ago or so. Every single time I had to do any kind of maintenance it was because of their drivers.
Since I don't play any more games than Minecraft and don't really need a fancy gpu I have switched to intel. Now I have two things which I buy intel only. GPUs and WiFi. I have had one glitch with opengl under a VM, but I am not sure that is intel only since it also had issues with my Nvidia card.
Half a dozen of NVidia cards in more than a decade on on Win/Lin. No major problems so far.. I had to install / remove drivers manually but only because I needed exact versions for some other software. Intel on Win/Lin works fine too.
But Systemd? That's on most distros these days. I'm pretty sure it is on all of those in the top 10.
Also, the OP is using CachyOS. You can tell b̶e̶c̶a̶u̶s̶e̶ ̶t̶h̶e̶y̶ ̶o̶p̶e̶n̶ ̶f̶i̶l̶e̶s̶ ̶w̶i̶t̶h̶ ̶n̶a̶n̶o̶ from the neofetch logo. But, I'll mention that if you checkout distrowatch, Arch based distros are incredibly common. Over the past 12 months the most downloaded distros are CachyOS (Arch), Mint (Deb/Ubuntu), MX (Deb), Debian, Endeavour (Arch), Pop (Ubuntu), Manjaro (Arch), Ubuntu, Fedora, Zorin (Deb/Ubuntu).
That said, you don't have to do any of this for either Endeavour (which I use) nor Manjaro (my old distro of choice). Along with Pop, one of the main motivations for these distros is Nvidia support. Really I don't expect most people to even be facing those problems these days. On Endeavour I've only run into one Nvidia problem over the last 5 years and it was when a beta driver conflicted with the most recent kernel. Super easy fix once I realized the problem.
On a side note/friendly reminder:
anyone that's using linux these days with an Nvidia card I suggest making sure your /efi partition is >1GB (at least 2GB but give it some headroom. Disk is still cheap). If you're putting the drivers in the kernel (you should), like done here, those are going to take up a lot of space. (If you get a space error, run `sudo du -ch --max-depth=3 /efi | sort -hr` to see the problem. You can, usually, safely delete any of the `initrd-fallback` versions and rerun `sudo reinstall-kernels`. They'll be built again but this will usually give you the headroom you need)
Correct. Running Ubuntu 25.10 with a RTX 50 series GPU and it just works.
Careful there, I was almost able to see some parts of the article through the ads
The terminal screenshots are terrible, too. They're using a non-monospace font and the kerning is messed up, making everything double-wide.
Came to say something about the ads too. Ended up not even reading the article it was so bad.
It feels surprising that there's people on hackernews without adblock considering that adblock is not just for blocking ads, but also malware, illegal tracking and blocking annoying and useless banners.
Well I run an ad blocker too, but maybe we should try browsing submitted URLs without blocking ads and only upvote them IF we can still read them like that.
I take a similar approach, but with noscript. If you cannot read it without enabling js, then I won't read the article.
HN has many ad-apologists. It's more ironic than surprising that there's complaints.
Totally agree. Every time I see someone complaining about ads, I think "What ads?"
Their adblock shamming overlay is also blocking part of the screen (on mobile) by the way
Don't see that overlay on fennec + adblock, what are you using?
brave seems to have some special sauce since it appears to be able to hide the fact that ads were removed. I am guessing they are doing so without triggering dom events.
My browser automatically blocked something that's triggering an overlay to "Disable any DNS / Extension Based AdBlocker to Continue" with no option to dismiss.
So the people on Hackernews with adblock aren't reading this.
I was able to read it perfectly while using uBlock.
I did not get this on Firefox mobile using uBlock and JavaScript disabled.
no overlay here on fennec + ublock.
Reader mode also available but not even needed.
interesting, on brave such popup never came up.
Brave is automatically using some list to disable "cookie banners". The kind of thing that you need to manually turn on in uBlock.
Having failed to get Wayland working on Debian Trixie with a 1050 Ti as an upgrade from X11, I've given up for now and will try again when I switch to AMD. This is a workstation not used for games so it'd be good to have Wayland working right but I'm not wasting time fighting it, and it'll get the GPU from the gaming rig when it becomes due nullifying the problem.
What I don't get is if these are proscribed steps (and they do read as such) why are they not automated with the module install? Why are we still fighting these issues if the 'workaround' is linear and well described? Is it as flimsy a reason as "write-an-article, collect-advertising-revenue" rather than contribute code to the installer?
I have 3 intel gpus. One for light gaming and desktop use (3 screens), another one for light gaming and one for video transcoding. The experience is flawless for me. One of the cards seems to have issues with qemu and opengl rendering, but it is an older model and is no longer sold retail.
I have an intel/nvida 4080 pc and im running a regular Arch install, rocking KDE on Wayland. It works flawlessly, just installed the drivers and that was that. Stop inventing problems that do not exist.
When can I reliably run ~95% of Steam titles on Linux with a Nvidia card? That's what I'm waiting for, then it's bye-bye Windows.
You can do that now, and for at least the last year.
Very few games don't work anymore, and most that don't are using kernel level anti-cheat or are generally hostile to users anyways (Fortnite and Destiny 2 could work, but they actively block Linux).
I main Fedora with an Nvidia 3080 and haven't had issues for quite some time now.
same with a 4070 ti S on fedora
no issues.
I'd just go AMD. The drivers there are much more mature due to Google and Valve contributions, and the performance of an 9070 XT is great while being cheaper than the equivalent 5070 Ti. FSR4 is a solid competitor to DLSS and works in any game that supports FSR 3.1.
Anti-cheats won't work, I keep a Windows drive just for Battlefield 6.
I got fed up about a week ago and ditched my Nvidia GPU for a 9070XT.
I run CachyOS and have been having a nightmare of a time on Wayland with my 3D Printer slicer and other tools I use my computer for being unusable.
The only thing that has ever kept me on Nvidia all these years is that they have been killing AMD performance wise for gaming.
The 9070XT is easily performant enough for the gaming I'm doing at the moment, and I can finally ditch the last major headache I've had in two and a half decades of being a Linux user - NVIDIA drivers - good riddance.
I don't play online games other than Helldivers 2 (so anti-cheat is a non-issue) which is working just fine at 70-80FPS max settings in 4K. Also getting good performance with RT off playing Ghostwire in 4K with settings as high as I can get them while staying above 60 FPS with Freesync.
EDIT: 9070XT seems to have a bit of headroom too I got the Asus PRIME OC version; Using LACT I upped the power limit from the stock 317W to 340W and undervolted by -100mv (YMMV on this value) and can get a decent chunk of extra performance out of it.
I use Debian 13 with an Nvidia 50 series card and I’m able to play games fine. Currently playing ARC Raiders and it works great.
I think there are still some common anti cheats that don’t work. But single player has been flawless for me.
https://www.protondb.com/dashboard
> Top 10 - 20% Platinum - 30% Gold - 10% Silver - 30% Bronze - 10% Borked
I'd probably say at least Gold is "reliably click and play without fiddling", so probably we're around 20-50% there right now, if we consider the top 10 games on Steam. Once you start considering top 100 or top 1000, it starts to look a lot better. But still, mainstream games are lagging seemingly.
Gold isn't really play without fiddling. Like look at BeamNG or AOE2DE
Wait no longer! Per capita I doubt 5% of games use kernel-level anticheat. Almost anything else runs pretty painlessly.
It has been my experience that this is currently the case. I haven't had to even open protondb or search for a workaround in over a year. The only titles I know that don't work are a handful of multiplayer games that have intentionally disabled linux support.
I can run 99% on Linux + AMD + X11, on Ubuntu 24. The only problematic one is Witcher 3 which insists on Wayland which breaks everything else. Even the UT5 titles work well enough, but then again our gaming is not your gaming and you might be more demanding that we are.
I'm trying to recall how NVidia behaved for games, but my daily driver is an old 1050 Ti that's been rock solid for years now, also X11.
Maybe the problem is Wayland not NVidia?
Most likely Wayland, I don't recall many of the problems occuring before that
Kinda now. That's what I've been doing for a while now. I have a PC though, not a laptop. Running CachyOS with 4070Ti, GNOME with Wayland. Even VR works
I don't even know when I ran into a game that didn't run off Steam on Linux. There's some fiddling gamescope on Wayland to get them to perform well, but most just run out of the box with great performance.
The stuff that doesn't work typically don't work because kernel level anticheats, so a few competitive titles but even in that space many titles still run.
I play everything in Ubuntu on my 4080
From CS2 (native) to the Final Fantasy XV demo (not native) and everywhere in between
I'd wager that 95% of Steam titles does run on Linux. Admittedly some big and popular games use invasive anti-cheat that's not supported, but they're less than 5%.
Many of the replies completely missed the part about Nvidia, sigh.
I unfortunately still see a lot of Proton bug reports that don’t repro on AMD cards. Hoping that improves soon, I’m sure Valve would love to tell hardware makers that Nvidia GPUs are supported.
I've been using 30s and 40s just fine with both nvidia and nvidia-open so every time I see this I don't really understand what card or game we're talking about.
On the other hand when I tried a 6xx0 XT I always ran into an infamous "ring gfx timeout" GPU crash with certain applications on WINE [0]. Ended up giving that card to a cousin.
[0] Examples: https://forum.endeavouros.com/t/rant-ring-gfx-0-0-0-timeout-... https://forum.endeavouros.com/t/amdgpu-ring-gfx-0-0-0-timeou...
I have an nvidia card on catchyos with catchyos proton and I have not ran into a single game that does not run, well ok some only walk, but that's also a problem on AMD.
I am excluding games that rely on a kernelmode anticheat.
Games I've played on my Arch Linux desktop with a 4090 in the past few months: Clair Obscur, Disco Elysium, Outer Worlds, Red Dead Redemption 2, Cyberpunk, Dispatch, Silent Hill f, FFVII Rebirth. I haven't had a single issue with any of these games. What games do you think will struggle? I can give them a shot if I own then and let you know how they do.
I have been using Nvidia on Linux for years and am able to run 95%+ of my library on Steam.
That’s awesome! But not everyone’s library is the same, so YMMV. I regularly see problems with flight sims that are Nvidia-specific, for example.
Not seeing any issues with my NVidia card.
~30+ years
[dead]
I still get fairly regular graphical glitches on Bazzite (Wayland) with a 3060ti. Certainly better than it used to be, but doesn’t quite feel there yet.
Interesting coincidence, yesterday I was using a similar article to hopefully fix kwin starting to slow down after 10+ days of uptime.
Hm, I've recently noticed kwin taking up what seems like way too much CPU at idle. Fedora with KDE. Happens on both X11 and Wayland with Wayland being worse and perceptibly slower.
I noticed this myself, both gnome and kde. It turned out to be that leaving Firefox open for long periods of time caused this.
I think for me jetbrains applications cause a memory leak in KWin which actually is becoming less of a problem now that I am switching to neovim slowly but surely.
I’ve been running CachyOS with Hyprland on my RTX3070 with no glaring issues. But eventually I plan to switch to a Radeon card.
The monthly wayland news, that we would be there already. Reminds me of fusion energy.
Is this stable on a multi-monitor mixed resolutions & refresh-rates setups?
Yeah haven't had issues with mine (3090)
3840x2160@59.99700
3840x1080@143.99899
...there is a nvidia bug on some cards where they idle high with multi monitors ~50W. Pretty sure that's OS independent though
What a nightmare.
Wow the ads are killing this page
But still no console, right?
To be clearer, as each wayland desktop pretty much creates their own incompatible wayland compositor (because wayland protocol is minimal and not feature complete) this is just a guide to fixing the hyperland broken wayland desktop. Not all waylands' broken desktops.
What protocol is missing from Wayland?
Yes Wayland doesn't have a printer protocol like Xorg, I know.
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/t...
This is an incomplete list of protocols that aren't part of core Wayland. Compositors implement additional protocols that aren't even part of this process (e.g. wlr-screencopy-unstable). See the wlroota protocols here: https://gitlab.freedesktop.org/wlroots/wlroots/-/tree/master...
Right but there's the xdg-portal for screen capture which runs through Pipewire and supports sand-boxing (because its negotiated over dbus), which all the main compositors support.
Just because a protocol isn't part of Wayland, doesn't mean a standard protocol does not exists.
nvidia on linux [for desktop] is utterly broken. I ran nvidia cards for almost 15 years (shame on me): laggy X11 compositing, fragile and broken wayland. Broken suspend/resume. Too many moving parts (selected drivers, modprobe quirks, suspend/resume scripts). Moved to amd: slick x11, reliable wayland, NO MORE DRIVERS AT ALL, works like charm. And yes, I do playing in Linux.
Suspend/resume is broken in general (and everywhere besides Mac), including AMD on Linux.
No more drivers is just..false?
The rest was true up to roughly 3 years ago. Now I'm a happy camper
Suspend/resume was broken in nvidia since release on aug 2024. I have internal bug id for it. And dozen links with suspend scripts. No more drivers I mean I don't need to install dozens of packages. While it not big deal by itself, but reverting broken driver is huge deal. Laggy desktop -- this is my experience until nov 2025 when I dumped nvidia. Desktop on both intel and amd feels like magic after nvidia.
Suspend/resume is broken for my friend with an AMD card right now. That's what I mean: it's broken everywhere in slightly different ways, yes even on Windows. Thankfully I never use it anyway.
Dunno anything about dozens of packages, I installed 1 (one) package from my distro and haven't touched it since, no issues with updates either. That same friend with an AMD card keeps getting random hard PC freezes during gaming though.
Also absolutely zero issues with lags/latency for me (on GNOME. I did experience a bunch of weird bugs with KDE, but again - no lags)
One thing that is very real is DirectX 12 performance. This one really does suffer due to poor nvidia drivers. Hope they iron it out at some point
Suspend/Resume simply nvidia bug: https://forums.developer.nvidia.com/t/cant-resume-from-suspe...
Dozen of packages, official packages, you need bunch of, like, 590.44.01-1 packages installed: https://developer.download.nvidia.com/compute/cuda/repos/deb...
Lags: sorry, I have no more nvidia and can't record video.
(edit: formatting)
Suspend/resume never worked right, going back to as early as the 2000s
Meanwhile Grandma says: "what's a wayland?"
How can anybody seriously argue Linux is an OS ready for ordinary users when you have to do crap like this? Complete delusion.
Your grandma doesn't need to know what wayland is to use linux. This is an enthusiast forum for people interested in this exact topic.
This post shows that she does, if she is unfortunate enough to own a device with NVIDIA graphics, because without this fix Wayland will be broken.
Of course, this is only one example of probably hundreds where an average user would have no clue how to fix their broken computer.
It doesn't. And you shouldn't install Arch on your grandma's computer.
This isn't Linux, it's Arch running Hyprland. If Grandma wants that combination she knows what Wayland is.
If you want Linux that works, get a Chromebook. If you want to play games, use Bazzite.
ChromeOS is a far better "Grandma" distribution than Windows or MacOS. Linux is simultaneously both the most Grandma friendly and least Grandma friendly, including every point in between.
You need to compare apples to apples, aka pre-installed vendor supported operating systems. If you're comparing installing an unsupported OS on unsupported hardware, Linux is far superior. Try installing MacOS on a Windows computer or Windows on a Mac if you're truly masochistic.
Are you saying windows and macos do not have any bugs? I have news for you.
Also wevare talking here about archlinux + hyperland compositor, not the typical Fedora, Mint or Ubunti/Zorin distro. Tinkerer's gonna tinker while the other users just use their computer regardless of the OS.
Linux isn't a single OS. It's hundreds of different and weird combinations.
There are Linux distributions that are better than Windows or iOS for grandma to use as well as distributions where you need to be an expert to do anything.
It doesn't matter, your options are either X11 or a Wayland-based compositor, both of them come with their respective headaches that a regular user has NO IDEA how to fix.
>both of them come with their respective headaches that a regular user has NO IDEA how to fix.
Unlike Windows, right? Right? Guys?
This is only accurate for people who choose enthusiast-centric DIY distributions such as Arch.
“Regular” users have plenty of distribution choices where there are zero of these types of headaches.
> a regular user has NO IDEA how to fix.
Buy hardware that supports Linux and you won't have to think about it.
At this point hardware incompatibility is a self-imposed problem.
You're making this issue much bigger than it is in reality.
Dare I say that you frankly have NO IDEA what the experience on modern Linux is today.
The only easier one is ChromeOS
Hey Gemini Take this article and submit PRs to all major distros that applies all the fixes in each different situation. Thanks!