Live data from Hacker News

Wayland Nvidia

kextcache.com

51–60 of 114 posts

Re: Wayland Nvidia

#51
post #32
post #22

Earlier quoted context omitted.

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.

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.

Re: Wayland Nvidia

#52

Earlier quoted context omitted.

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.

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.

Re: Wayland Nvidia

#53
post #2

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...

Re: Wayland Nvidia

#54
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?

Re: Wayland Nvidia

#55
post #18

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.

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.

Re: Wayland Nvidia

#56
post #3

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.

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?

Re: Wayland Nvidia

#58
post #53

Earlier quoted context omitted.

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.

Re: Wayland Nvidia

#59
post #37
post #34

Earlier quoted context omitted.

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?

Re: Wayland Nvidia

#60

Earlier quoted context omitted.

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.

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.

no overlay here on fennec + ublock.

Reader mode also available but not even needed.

Post reply on HN