[–] 7 points 1 year ago (2 children)

Two pretty massive facts for anybody trying to answer this question:

  1. Since driver version 555, explicit sync has been supported. This makes a massive difference to the experience on Wayland. Most of the problems people report are for drivers earlier than this (eg. black screens and flicker).

  2. Since driver version 580, NVIDIA uses Open Source modules to interact with the kernel. These are not Open Source drivers. They are the proprietary drivers from NVIDIA that should now “just work” across kernel upgrades (like AMD has forever). This solves perhaps the biggest hassle of dealing with NVIDIA on Linux.

Whether you get to enjoy these significant improvements depends on how long it takes stuff to make it to your distribution. If you are on Arch, you have this stuff today. If you are on Debian, you are still waiting (even on Debian 13).

This is not an endorsement of either distro. They are simply examples of the two extremes regarding how current the software versions are in those distros. Most other distros fall somewhere in the middle.

All this stuff will make it to all Linux users eventually. They are solved problems. Just not solved for everyone.

  • source
  • [–] 1 point 1 year ago (1 child)

    For anybody tying to make sense of who has trouble on NVIDIA, keep in mind that Debian uses ancient drivers.

    Thankfully Debian Stable updated recently so it has gotten a lot better but, the last I checked, the Debian drivers still did not support explicit sync. This could lead to problems on Wayland.

    Remember that “stable” in Debian means that your system will not change much. That is often a good thing but it can often mean progress comes to Debian much later than other distros.

    Never use Debian as a benchmark for what works on Linux.

  • source
  • parent
  • context
  • [–] 4 points 1 year ago* (last edited 1 year ago) (1 child)

    UUtils has, until now, been a niche project with few users. Putting it in the most popular desktop distro is going to expose it to many new users and use cases. Some of those are bound to find differences in behaviour between UUtils and GNU which should be considered bugs. No doubt.

    But this “not-very-well tested” mantra is just silly. UUtils itself uses the exact same test suite as GNU does. They have been testing against this suite for years:

    https://github.com/uutils/coreutils-tracking/blob/main/gnu-results.svg

    While not all tests pass yet, the subset of functionality that people are likely to actually use is very well tested.

    And the reason some bugs were found recently is precisely because UUtils were put through the normal test cycle for Ubuntu. A small number of bugs were caught which is the goal of that process. These are things that were previously not in the test suite. I see there are some new tests. UUtils may have contributed to that as new use cases were encountered that showed differences in behaviour between GNU and UUtils. The issues discovered were quickly fixed.

    Think of what is involved in creating a distribution like Ubuntu and building the tens of thousands of packages that they ship in their repos—all with build scripts written for GNU Coreutils. This is all working with UUtils unmodified.

    With the distro live now, the number of users will have already exploded. Where are the bug reports and articles about all the problems encountered? Crickets.

    That does not mean there will not be any such cases. That is not my point at all. My point is that “not very well tested” does not jive with how well things are going considering what a massive change this is.

    UUtils is much better tested than much of the software I use.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago (2 children)

    What did they revert? I had not heard that.

    UUtils is just the “core” utils for now but that was always the plan. What got reverted?

    I thought all the reported bugs were fixed (mostly before the articles were even written).

    None of this means there are not more bugs or feature gaps of course. I am sure there are. This is the first test of UUtils at scale.

  • source
  • parent
  • context
  • [–] 13 points 1 year ago (1 child)

    I think the answer is if you are shooting for the high-end. AMD is better cost / performance but NVIDIA is still unchallenged for absolute performance if budget is not a consideration.

    And if you need CUDA…

  • source
  • [–] 3 points 1 year ago*

    I hope those things will come but no need to hold off if the performance is there. UEFI, ACPI, etc. are really about the boot process. For SBC class hardware, having a device tree in the kernel works fine. Even Apple Silicon Macs use device trees (no ACPI).

    On Apple Silicon, there is a project to add ACPi in software (firmware) so that they can boot operating systems that expect ACPi (like Windows). You do not need it for Linux.

    Of course, dynamic device discovery and power management would be nice. Bit it is not a deal-breaker for me.

  • source
  • parent
  • context
  • [–] 8 points 1 year ago* (1 child)

    Actually Trump renegotiated it, called it USMCA, said it was the best trade deal in history, signed it on camera in a huge White House press event, lost the Presidency, won the Presidency, and then called it the worst deal ever and that it was signed by a stupid “past President”. Then tariffs in violation of it.

    Even for Trump, that story arc is pretty wild.

  • source
  • parent
  • context
  • view more: ‹ prev next ›