logoalt Hacker News

Wayland Nvidia

56 pointsby brevelast Thursday at 10:00 AM73 commentsview on HN

Comments

jwcooperyesterday at 3:50 PM

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.

show 2 replies
juliangmpyesterday at 3:52 PM

Careful there, I was almost able to see some parts of the article through the ads

show 2 replies
antonyhyesterday at 4:25 PM

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?

yokoprimeyesterday at 8:41 PM

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.

tietjensyesterday at 3:35 PM

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.

show 13 replies
letwhileyesterday at 4:34 PM

The monthly wayland news, that we would be there already. Reminds me of fusion energy.

bogdanyesterday at 3:42 PM

Is this stable on a multi-monitor mixed resolutions & refresh-rates setups?

show 1 reply
kachapopopowyesterday at 3:56 PM

Interesting coincidence, yesterday I was using a similar article to hopefully fix kwin starting to slow down after 10+ days of uptime.

show 1 reply
j3th9nyesterday at 11:10 PM

What a nightmare.

thenthenthenyesterday at 4:09 PM

Wow the ads are killing this page

pshirshovyesterday at 3:39 PM

But still no console, right?

superkuhyesterday at 3:33 PM

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.

show 1 reply
rmrfchikyesterday at 3:58 PM

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.

cedwsyesterday at 3:49 PM

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.

show 5 replies
lacooljyesterday at 5:27 PM

Hey Gemini Take this article and submit PRs to all major distros that applies all the fixes in each different situation. Thanks!