This isn’t “I want to believe”, this is “it would be irresponsible to not consider”.

  • 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: September 3rd, 2023

help-circle





  • What motivated you to switch branches? Did it solve another issue? Why were you not on the latest branch yesterday, ie, why did you roll back originally? Does one driver work better for some games, and another driver works better for others?

    Nvidia drivers are jank. I honestly haven’t touched them since 2017. I remember having to reboot and switch drivers to switch games I was playing with friends and finding the whole experience annoying as hell. I realized that Linus Torvalds was right, fuck nvidia, AMD is the way to go. Have not had to touch anything with my drivers since switching. All of my interactions with nvidia since have confirmed that they are not a company deserving of my patronage.



  • There’s usually only like 5 tracks. “What’s recommended” is nouveau, which works but not for gaming. It’s recommended because it’s open source and can do most things that the proprietary nvidia drivers can do. Nvidia is really bad at maintaining their drivers, and different drivers work better for different cards.

    Nvidia sucks. Switch to AMD and never have a problem again. Or spend an hour testing each of the proprietary options maintained in the debian repos, and most likely find that at least one of them works. Until an update to the drivers or kernel comes along, and breaks it again, so you have to play around with driver versions and kernel versions to find a combo that works. That’s less likely to happen if you stick with a debian-based distro vs a bleeding-edge distro like arch.

    And buy AMD for your next machine to send a message to nvidia that their driver support sucks!








  • Thanks for pointing out that in this case the DM is using X regardless of whatever graphical environment gets loaded when the user logs in. This really is a moot point/discussion. I’m still glad I raised it to get perspectives like yours.

    You’re right that I should play around with wlroots a bit more. It’s been a while, personally. Mostly because it’s been a while since I’ve had time to just play around with my system. My life is at a point that it looks like I’ll have that free time soon, for better or for worse.

    I’ll note that I do like alternative init systems for diversity and competition and because systemd was very hungry and rigid. An init system is also a bit more fundamental to system stability than a display server, so I think it’s reasonable to be critical of systemd and Wayland for contradictory reasons. Systemd has also come a very long way in the past decade plus. I have also seen it learn from the other ideas implemented in its competition, mirroring your argument. Diversity and unification are not at odds with each other, but are different parts of the same cycle of improvement.


  • Good to know that this has been implemented in your favorite DE! Considering how Wayland often implements things, it’s probably implemented on the DE-level, leading to a fractured configuration ecosystem. Being implemented in Wayland is different from being implemented in some of the DEs that use Wayland.

    edit: if I’m wrong about that, and it is implemented in Wayland itself, please continue to correct me!




  • I’ve never needed any of those things.

    I do need to change monitor configurations.

    I once had an old TV that I used as a monitor that had 1027p worth of pixels instead of 1080p. Auto detection tools said it was 1080p. With xrandr I was able to modify the output to 1027p so I didn’t lose the edges of the display to the TV’s broken forced overscan design. Could you do that with Wayland?