30 votes

How bad are Nvidia GPUs for Linux really?

I've been interested in switching to Linux, or at least dual booting, for some time now as Windows has kept getting worse and Proton for Steam has been getting better. I'm particularly interested in trying Mint Cinnamon.

In every Linux thread on here or Lemmy, I always hear people complaining about Nvidia drivers for Linux or other hardware problems that they avoid by having AMD.

I have an Intel CPU and Nvidia GPU. How big of a problem is that, really? Does it make it an unbearable experience? Does it make it a lot more work to get things working? Does it make certain things impossible to get working? What's your experience?

Also for dual booting, I hear people have problems with Windows messing up their Linux install. Is that a common problem, or a few people having bad luck? Is that avoidable?

47 comments

  1. [4]
    Oxalis
    Link
    Most videocards aside from the really bleeding edge stuff are reasonably stable in linux. At least from my experiences with Fedora/Ubuntu over the last 6 years. Things can get complex for laptop...

    Most videocards aside from the really bleeding edge stuff are reasonably stable in linux. At least from my experiences with Fedora/Ubuntu over the last 6 years. Things can get complex for laptop hardware that has weird high-power/low-power hardware switching and other idiosyncratic setups that don't get much support.

    Regarding dual-booting. Just install your OSes on separate physical drives and switch between them at boot time by launching your bios. Most bios have an option to select a hardware device to boot from that runs before any bootloader is read, so check with your motherboard book to see how to access it.

    Just make sure to install the bootloader partition for each OS onto their drive as if that drive was the only one in the system.

    19 votes
    1. [3]
      lou
      (edited )
      Link Parent
      I've been doing that on a single drive. The BIOS doesn't require each system to be on its own drive. I'm not sure why anyone would think booting to any system is an issue with modern BIOS anymore....

      Regarding dual-booting. Just install your OSes on separate physical drives and switch between them at boot time by launching your bios. Most bios have an option to select a hardware device to boot from that runs before any bootloader is read, so check with your motherboard book to see how to access it.

      I've been doing that on a single drive. The BIOS doesn't require each system to be on its own drive. I'm not sure why anyone would think booting to any system is an issue with modern BIOS anymore. Just make whatever system you want is the first in the list.

      2 votes
      1. [2]
        Oxalis
        Link Parent
        Just out of curiosity, since my experiences with windows nuking/editing/removing GRUB were from years ago, I did a search for "windows 11 kills grub bootloader" and I'm still seeing numerous...

        Just out of curiosity, since my experiences with windows nuking/editing/removing GRUB were from years ago, I did a search for "windows 11 kills grub bootloader" and I'm still seeing numerous stackoverflow questions, reddit threads, manjaro discourse threads, and lastly on the microsoft support forum as just a small taste of the issues people are having in 2023-24.

        Nearly all of these have to do with windows updates or upgrades messing around with the MBR or generally augmenting things that invalidate GRUB. Most can be fixed for sure with a cup of coffee, a rescue stick, and some wiki diving but I'd rather never have two systems at risk again if I can help it.

        3 votes
        1. lou
          (edited )
          Link Parent
          That does happen. However, my BIOS (which is a very cheap one) doesn't really care, and I can just override this with a setting in the bios. Probably because my partition table is EFI, which I...

          That does happen. However, my BIOS (which is a very cheap one) doesn't really care, and I can just override this with a setting in the bios. Probably because my partition table is EFI, which I believe is default nowadays. You may have a real problem with an MBR partition table.

          1 vote
  2. [3]
    Odysseus
    Link
    I use an RTX4070 with my void linux system and I've not encountered a single GPU-related issue with running games, both pirated and on steam. Getting everything set up was a cakewalk, just...

    I use an RTX4070 with my void linux system and I've not encountered a single GPU-related issue with running games, both pirated and on steam. Getting everything set up was a cakewalk, just installing the appropriate drivers via the default package manager

    14 votes
    1. 0xSim
      Link Parent
      I have an RTX4060, and I have recently installed a Linux Mint partition to see how viable that would be. It runs great out of the box with the drivers directly installed from the "proprietary...

      I have an RTX4060, and I have recently installed a Linux Mint partition to see how viable that would be.

      It runs great out of the box with the drivers directly installed from the "proprietary drivers" app, though I mostly own and play "not-AAA" games. The Steam Proton compatibility layer and Lutris do a lot of heavy lifting, and you can usually find some fixes from user feedback on https://www.protondb.com/. All in all I'm pleasantly surprised how well it goes without any fiddling.
      I only noticed that the most demanding games (e.g. Portal 2 with raytracing) were generally performing a bit worse than on Windows, and I also had to (un)check a few checkboxes in the nVidia driver app to fix anti-aliasing.

      Diablo IV had issues with missing ground textures and framerate dips. I fixed them with a custom command line, but they came back when I installed the most up-to-date drivers. I ended up uninstalling and I just boot Windows if I want to play.

      Edit:

      Also for dual booting, I hear people have problems with Windows messing up their Linux install. Is that a common problem, or a few people having bad luck? Is that avoidable?

      Install Windows first, and then Linux. Always.

      10 votes
    2. tobii
      Link Parent
      Same here with voidlinux + RTX4080 Super, I read the wiki just in case, but really zero issues.

      Same here with voidlinux + RTX4080 Super, I read the wiki just in case, but really zero issues.

      2 votes
  3. V17
    Link
    Unless something changed in the last few years, it was a regular issue for me with Windows 10, it kept overwriting the boot partition with certain updates. Ignoring and reverting any non-standard...

    Also for dual booting, I hear people have problems with Windows messing up their Linux install. Is that a common problem, or a few people having bad luck? Is that avoidable?

    Unless something changed in the last few years, it was a regular issue for me with Windows 10, it kept overwriting the boot partition with certain updates. Ignoring and reverting any non-standard user settings really is a staple of Win10.

    The solution in my case was to install Linux and Windows on separate (physical) drives with their own boot partitions, set the Linux drive as primary boot in EFI config and let GRUB find the Windows boot partition with its own boot manager on the other drive automatically with I think the grub-install script. This worked first try without any manual settings, I did not have to do any manual changes like hungariantoast.

    I think this is possible to do without having to have separate physical drives (it was just the easiest solution for me), EFI should be able to detect and select separate bootable partitions on one drive, and then it's just the case of having the first partition on the drive to be the Windows one, but then installing GRUB on the second one and booting into it. IIRC Windows shouldn't touch any bootable partitions that are behind it.

    9 votes
  4. [5]
    vord
    Link
    NVIDIA used to be the only game in town for gaming on Linux. That changed with the relase of amdgpu. This has made working with AMD cards much less painful than getting NVIDIA cards working,...

    NVIDIA used to be the only game in town for gaming on Linux. That changed with the relase of amdgpu. This has made working with AMD cards much less painful than getting NVIDIA cards working, especially on a rolling distro.

    And yes, windows will fuck with your bootloader. I don't dual boot anymore, so any advice I'd have for that is probably outdated.

    8 votes
    1. [3]
      hungariantoast
      (edited )
      Link Parent
      Just a few months ago I upgraded my desktop and went back to using that as my main workstation, which unfortunately means dual booting Linux alongside Windows. (For the past few years I was just...

      And yes, windows will fuck with your bootloader.

      Just a few months ago I upgraded my desktop and went back to using that as my main workstation, which unfortunately means dual booting Linux alongside Windows.

      (For the past few years I was just using a laptop as my "work machine" and my desktop/Windows strictly for games. The simplicity was nice while it lasted, but that's just it, laptops don't last.)

      Figuring out how to install Arch on a separate SSD from Windows, but still have both operating system entries appear in the boot menu, had me scratching my head for a while. The solution is actually very simple (though kind of hard to explain) and should prevent Windows from ever being able to mess with my bootloader.

      For the record, I use systemd-boot, but this might apply to other bootloaders as well.


      So when I was installing Arch, I needed a root partition to install the operating system to, and then a separate boot partition that would contain the EFI images and other bootloader files.

      I already had a Windows installation on an SSD in my desktop, let's call that SSD1. I wanted to install Arch to a separate SSD, let's call that SSD2.

      The problem that I ran into was that Windows had already set up its own winboot partition on SSD1, so I could theoretically use that as my boot partition for Arch, but it was far too small, only 100 megabytes.

      These days I set my boot partition to 2GB, because that's nothing on a 2TB drive, and it means I can install multiple kernels and don't have to worry about compressing initramfs images every time I update one of them.

      So I had to create a new boot partition for Arch, and I couldn't just resize the winboot partition either.

      Thus the new problem became: if I have a separate winboot bootloader partition for Windows, and another boot partition for Arch (again, on separate drives), how do I make the system's UEFI and systemd-boot aware of both operating systems, so that both of their entries are present in the boot menu?

      If I were to set my UEFI boot target to Windows, it would just boot straight into Windows and never give me the option to boot Arch. If I set the UEFI boot target to Arch, systemd-boot would not display a boot entry for Windows, because the winboot partition was on a separate drive, so I could not boot into Windows.

      So what do?

      Just copy the files from the winboot partition, to Arch's boot partition. Works like a charm. Both OS entries show up, boot fine, and Windows should never be able to fuck with Arch's boot partition since it's on a separate drive. If for some reason I ever need to "update" the Windows boot files in Arch's boot partition, I can just copy them over from the winboot partition again.

      When I stumbled onto this solution, I simultaneously felt like the dumbest person ever and a living god.

      9 votes
      1. [2]
        bitwaba
        Link Parent
        Isn't this already the solution to your problem? You just pick the UEFI boot target at boot time. No need to copy the winboot files over. Is there some specific reason why you want to be able to...

        If I were to set my UEFI boot target to Windows, it would just boot straight into Windows and never give me the option to boot Arch. If I set the UEFI boot target to Arch, systemd-boot would not display a boot entry for Windows, because the winboot partition was on a separate drive, so I could not boot into Windows.

        Isn't this already the solution to your problem? You just pick the UEFI boot target at boot time. No need to copy the winboot files over.

        Is there some specific reason why you want to be able to boot windows from the systemd-boot menu instead of one step earlier on your motherboard 's UEFI menu?

        8 votes
        1. hungariantoast
          (edited )
          Link Parent
          Maybe it’s a limitation of my motherboard specifically, but regardless of what boot target I selected in the firmware, it did not find both operating system entries or provide a menu to choose...

          Maybe it’s a limitation of my motherboard specifically, but regardless of what boot target I selected in the firmware, it did not find both operating system entries or provide a menu to choose one. My motherboard is pretty old (April 2018).

          Systemd-boot also does not automatically search and find Windows boot partitions and I’m not sure you can tell it to, which is why I had to copy the files manually to Arch’s boot partition. (Other boatloaders like Grub might be able to do this.)

          2 votes
    2. CunningFatalist
      Link Parent
      Okay, I'm glad to see it's not just me...

      Okay, I'm glad to see it's not just me...

      1 vote
  5. Pavouk106
    Link
    I'm running Nvidia GPU since around 2012. I run Gentoo linux - rolling release distro. I never had any problems. GPU gives comparative numbers as it would on Windows machine (ie. in Cyberpunk) and...

    I'm running Nvidia GPU since around 2012. I run Gentoo linux - rolling release distro. I never had any problems. GPU gives comparative numbers as it would on Windows machine (ie. in Cyberpunk) and it is smooth experience. I only used GTS450, GTX750, GTX960 and GTX1650 cards in all those years - no really high end stuff. There are tons of software features you may and will miss though. But basics graphics drivers works very well for me.

    If you already have the hardware, which you do, I wouldn't stress over it - just go for it and see for yourself. You can buy some 256GB SSD for cheap and try Linux on that while disconnecting all oher drives, you don't have to nuke your PC (yet, when you don't know if it will work). This will prevent you from messing up Windows install and will prevent Windows messing up linux install (bootloaders...).

    My friend has 7900XTX from AMD and uses Arch linux and is very pleased with the experience.

    5 votes
  6. [3]
    Promonk
    Link
    I haven't had many problems running Mint with my GTX 1060, but it's an older card and I don't game with it aside from a little emulation. Most of the problems I have had were fixed satisfactorily...

    I haven't had many problems running Mint with my GTX 1060, but it's an older card and I don't game with it aside from a little emulation. Most of the problems I have had were fixed satisfactorily by adjusting settings, but again, I'm not taxing the hardware overmuch, so YMMV for sure.

    3 votes
    1. [2]
      EmperorPenguin
      Link Parent
      I see, thanks for your input. I have a 3080 myself. I can run the games I want to play on Steam Deck, so I don't suspect the hardware's power or Linux itself to be an issue, just any Nvidia...

      I see, thanks for your input. I have a 3080 myself. I can run the games I want to play on Steam Deck, so I don't suspect the hardware's power or Linux itself to be an issue, just any Nvidia specific problems. I think I've heard in passing that newer Nvidia cards like 3000 or 4000 series are an issue, while older cards aren't, and I'm hoping that's not the case...

      1. zod000
        (edited )
        Link Parent
        I've been running a 3070 on Linux since the card was released with no issues. I also had no issues with my previous AMD and Nvidia cards though, so my advice is to just stick to the more up to...

        I've been running a 3070 on Linux since the card was released with no issues. I also had no issues with my previous AMD and Nvidia cards though, so my advice is to just stick to the more up to date distro releases. I also think you'll have better luck with more mainstream WM and DE. The more exotic setups may not have as much exposure to gaming GPUs.

        Edit: I just wanted to mention that I also have a W10 installation on a separate SSD (that I barely use at this point) and it's fine other than it doesn't seem to love that I use its drives from Linux. I don't recommend sharing the same drive, for booting the OSes. If you don't have a choice, I have found the trick with Windows is to install it first, that way Windows won't bulldoze over anything !Windows in the bootloader.

  7. [2]
    dysthymia
    Link
    In my own personal experience, the only issue I've had with NVIDIA GPUs on linux is the installation and maintaining of the driver. If you're using an Ubuntu-based distro, fine, the driver manager...

    In my own personal experience, the only issue I've had with NVIDIA GPUs on linux is the installation and maintaining of the driver. If you're using an Ubuntu-based distro, fine, the driver manager application thingy will do it for you, and you'll never have to think about it again. If you're using Debian, Fedora, or any other distro that I've ever tried, you're most likely going to have to do the whole process by yourself - which also means that you'll have to maintain it every time something goes wrong. Which eventually it might.

    2 votes
    1. vord
      Link Parent
      And on a rolling distro that patches regularly, it becomes painful.

      And on a rolling distro that patches regularly, it becomes painful.

      1 vote
  8. freestylesno
    Link
    One of the issues the Linux community has with Nvidia is that the drivers are proprietary. Meaning no source code provided. So you can't see exactly what the drivers are doing, and need Nvidia to...

    One of the issues the Linux community has with Nvidia is that the drivers are proprietary. Meaning no source code provided. So you can't see exactly what the drivers are doing, and need Nvidia to update them.

    2 votes
  9. Chobbes
    Link
    In my experience in the past Nvidia proprietary drivers generally work just fine on Linux. You may occasionally have some random black screen issues when booting up or resuming from suspend or...

    In my experience in the past Nvidia proprietary drivers generally work just fine on Linux. You may occasionally have some random black screen issues when booting up or resuming from suspend or something, but it mostly just works with some small annoyances every so often. If you tend to hold onto your hardware for a long time you may eventually run into an issue where the binary blob driver no longer supports your GPU, which can be annoying, especially since the old drivers that do support your GPU might not support new Linux kernel versions, so eventually you might get to the point where you can't upgrade your OS until you upgrade your hardware... Presumably this can be an issue with amdgpu as well, but since it's open source you can potentially hack it to work if you or somebody else really wants to. Occasionally there is some fight between Linux kernel devs and Nvidia that will break the drivers on bleeding edge kernels, but this isn't super common (and likely won't be an issue for you unless you're on a rolling release distro, which Mint is not).

    In general AMD gpus are kind of hassle free on Linux and are more plug-and-play than Nvidia GPUs, but if you want to try Linux out I really wouldn't worry that much about having an Nvidia card. You likely won't have any problems, especially on a stable distro like Mint.

    2 votes
  10. elight
    Link
    Given how much Nvidia GPUs are leveraged for LLM training, I'd expect stellar support in Linux. It's hard to imagine OpenAI, Amazon, Google, et al investing in Windows for all of their machines!...

    Given how much Nvidia GPUs are leveraged for LLM training, I'd expect stellar support in Linux. It's hard to imagine OpenAI, Amazon, Google, et al investing in Windows for all of their machines!

    Anecdotally, I've not had any problem with my 2060 laptop but then I've only leveraged the GPU for Plex and, soon, running an LLM.

    2 votes
  11. epitten
    Link
    My experience with a desktop was generally fine in this setup. With a laptop, it was a lot of work that never quite got to where I wanted it. In my case, the external display ports were wired...

    My experience with a desktop was generally fine in this setup. With a laptop, it was a lot of work that never quite got to where I wanted it.

    In my case, the external display ports were wired through the GPU, so to get both the laptop display and external displays working properly (with screen scaling), I had to make the Nvidia GPU my primary and sacrifice my battery life. The alternative was to have no screen scaling, as if the Intel GPU was the primary and I scaled the Nvidia displays, the Nvidia GPU would have a disconnect between where it drew my mouse cursor and where the cursor actually was.

    So if you're considering this on a laptop, my advice would be to set aside a good amount of time to figure this kind of setup out and tweak things.

    1 vote
  12. ButteredToast
    Link
    My experience with a 3080 Ti FTW3 and Linux is that it sometimes won’t play nice with Wayland — for example a few months ago discovered VS Code is super glitchy under Nvidia+Wayland. To be clear,...

    My experience with a 3080 Ti FTW3 and Linux is that it sometimes won’t play nice with Wayland — for example a few months ago discovered VS Code is super glitchy under Nvidia+Wayland. To be clear, this is an Nvidia problem, not a Wayland problem because Wayland works fine on my Linux boxes with Intel iGPUs or AMD dGPUs. Nvidia has traditionally been a pain in the ass for Linux devs and this is no exception.

    The other thing is that the proprietary Nvidia drivers can be a pain to maintain through updates on some distros. As someone else noted Ubuntu-based distros are fine here, and Fedora can be after some command line finagling though.

    All that considered, if I were to run Linux full-time (currently I dual boot on the machine in question, staying in Windows most of the time) I’d almost certainly invest in an equivalent or more powerful AMD card to my 3080 Ti. I was leaning that direction anyway with all the RTX 4000 power connector nonsense.

    1 vote
  13. [4]
    knocklessmonster
    Link
    Never had that issue myself. If you have a destkop, I would recommend dropping in a separate drive and using a separate EFI partition for your Linux install.

    As with dual booting, I hear people have problems with Windows messing up their Linux install. Is that a common problem, or a few people having bad luck? Is that avoidable?

    Never had that issue myself. If you have a destkop, I would recommend dropping in a separate drive and using a separate EFI partition for your Linux install.

    1 vote
    1. [3]
      dysthymia
      Link Parent
      I was always told this is a "UEFI vs legacy" issue. I have UEFI and I've never had actual problems either when dual-booting, excluding the fact that, after windows updates, Windows would always...

      I was always told this is a "UEFI vs legacy" issue. I have UEFI and I've never had actual problems either when dual-booting, excluding the fact that, after windows updates, Windows would always put itself as the first partition in the boot table, meaning that GRUB would not show up until I manually went into the boot menu and reordered the partitions as they originally were. But I was always told that if you're using legacy BIOS or whatever, windows may in fact actually overwrite the partition.

      I have not personally tested this, however, so I do not actually know if it's true.

      1 vote
      1. lou
        Link Parent
        I believe that was more of an issue when UEFI was not the default. I also just change boot order to fix that.

        I believe that was more of an issue when UEFI was not the default. I also just change boot order to fix that.

        1 vote
      2. knocklessmonster
        Link Parent
        Yeah it was definitely an issue in the BIOS days where Windows would overwrite the MBR with its bootloader. I still separate my EFI partitions to keep things clean on the Windows side so that if I...

        Yeah it was definitely an issue in the BIOS days where Windows would overwrite the MBR with its bootloader.

        I still separate my EFI partitions to keep things clean on the Windows side so that if I yank one or the other disks the one system still works fully

        1 vote
  14. ADwS
    Link
    Going against the flow, I’m sadly going to have to report issues with my GTX 1080 on both Mint and Ubuntu, specifically regarding rendering in Cycles on Blender. It would detect my CPU without...

    Going against the flow, I’m sadly going to have to report issues with my GTX 1080 on both Mint and Ubuntu, specifically regarding rendering in Cycles on Blender. It would detect my CPU without issue, and would allow me to render with the GPU, but without CUDA optimization which is a major draw of Nvidia cards in the first place. This was back in 2020 and then again in 2021. I have tried Mint since then (summer of 2023), but I still had issues getting CUDA to render on my currentt build’s 3070ti.

    For other applications, such as games, I really had no issue, but with Blender specifically (both standalone and through a package manager) it did not ever want to detect the CUDA competent, which is significantly more efficient for Blender’s Cycles raytracing.

    I plan on trying it again once I get a higher vram GPU, but Window’s Blender performance still seems relatively unmatched vs other OS’s for CUDA, which means I’m probably going to be paying an arm and a leg.

    I know of several workarounds, and recognize that people with more free time might be able to get it to work, but I sculpt in my free time, and when I do (occasionally) render for clients, it’s imperative that everything works without issue and as efficiently as possible. At the moment, for my specific work case, Linux is not there (circa 2023).

    I plan on doing a quick test run again come January prior to upgrading my system, just to see if there have been any changes that might affect my hardware choices, but I’m keeping my expectations low. As much as people hate to hear it, there is a massive benefit and reason to have Nvidia GPUs over the (significantly better on paper) AMD ones. More VRAM would help me significantly, but I personally find optimizing a scene for less VRAM less disruptive than optimizing a scene for less render time. And that goes for running Linux vs Windows. I would love a system that doesn’t track me, but I can’t rely on a system that might refuse to recognize a key feature of my hardware for any number of reasons.

    1 vote
  15. [12]
    ngz
    Link
    I haven’t really had many issues with the proprietary Nvidia driver (using a 3090 and 2080Ti in the same machine), aside from the periodic attempts to try Wayland that invariably fail utterly due...

    I haven’t really had many issues with the proprietary Nvidia driver (using a 3090 and 2080Ti in the same machine), aside from the periodic attempts to try Wayland that invariably fail utterly due to stuff being broken and not having the time to go debug it. There’s some occasional weirdness but on the whole it’s been pretty stable. If you’ll mostly be playing games, chances are the Nvidia drivers will work fine - just note that some newly-released stuff might not work until Proton has a chance to patch things, and some Wayland stuff is really hostile to Nvidia users. For example, it took a few months for Starfield to be playable on an Nvidia GPU after release. Older stuff generally works fine (or if it doesn’t, it’s not the Nvidia driver that’s the issue).

    That said, it’s not like I have any other option. If you want to do compute work on your GPU(s), you’re essentially forced to go with Nvidia. OpenCL is a joke, the ecosystem around Vulkan compute shaders isn't really usable, and ROCm doesn’t have broad compatibility so you have to be very careful to make sure you buy a card that supports it. Whereas CUDA works on all Nvidia cards, most distros, has a ton of good libraries and tooling, and is supported by most pre-written applications. I wouldn’t mind trying an AMD card because open graphics drivers are a good idea, but that’s not really an option until the GPU compute story improves.

    Also, since some other people have mentioned it, this is all based on desktop hardware. I think there was some weirdness around hybrid graphics on laptops, but my knowledge there is almost a decade out of date so there’s a good chance that’s been fixed by now.

    1. [10]
      vord
      (edited )
      Link Parent
      That's a bit backwards really, NVIDIA has always been a bit hostile to the Linux community. I don't have time to dig up ny sources for details right now, but they take a 'my way or the highway'...

      Wayland stuff is really hostile to Nvidia users. For example, it took a few months for Starfield to be playable on an Nvidia GPU after release. Older stuff generally works fine (or if it doesn’t, it’s not the Nvidia driver that’s the issue).

      That's a bit backwards really, NVIDIA has always been a bit hostile to the Linux community.

      I don't have time to dig up ny sources for details right now, but they take a 'my way or the highway' approach, which was needlessly slowing down the transition to Wayland.

      They seem to be doing some level of better recently than in the past, but I suspect that's because AMD has finally gotten back into the realm of remotely competitive, and that makes them nervous.

      4 votes
      1. [9]
        ngz
        Link Parent
        I’m definitely aware of the background here, but I was specifically referring to the “we don’t support Nvidia, and if you want to use Wayland you should just buy a new GPU, ignoring the fact that...

        I’m definitely aware of the background here, but I was specifically referring to the “we don’t support Nvidia, and if you want to use Wayland you should just buy a new GPU, ignoring the fact that AMD cards are not viable for a lot of usage scenarios” position of Sway and other Wayland projects. It’s dismissive at best and actively hostile at worst to simultaneously claim that:

        1. X is legacy and nobody should be using it anymore, as Wayland is ready for almost all use-cases
        2. Nvidia cards (80%+ of the desktop GPU market, IIRC) are unsupported in many Wayland projects

        I get that it’s not Wayland’s fault, but it’s also frustrating to see it claimed as ready for use when in reality it doesn’t have good support for common use cases (GPU compute) or the majority of discrete GPUs. If I’m suggesting someone migrate to Linux, it’s unrealistic to ask them to drop several hundred dollars on a new GPU just because the Wayland community doesn’t like the perfectly-functional card they already have.

        3 votes
        1. [4]
          lou
          (edited )
          Link Parent
          Calling a program that works perfectly and as expected 99% of the time "legacy" sounds like a bit of an exaggeration. I suppose that is something a developer might think, not something that would...

          Calling a program that works perfectly and as expected 99% of the time "legacy" sounds like a bit of an exaggeration. I suppose that is something a developer might think, not something that would be relevant to a user.

          The amount of things that I find relevant which did not work correctly on Wayland was quite relevant to me. Conversely, the amount of things I care about, including software with very recent versions, which did not work on X was zero.

          I don't really have an use case that hits on X issues enough to warrant switching a lot of the programs I love for Wayland-friendly alternatives.

          So, to me, as a user who is not a programmer, X is objectively superior. The fact that a particular category has a Wayland alternative doesn't necessarily mean that it is an alternative that I would wanna use.

          1 vote
          1. [3]
            vord
            Link Parent
            Objectively speaking though, X is legacy. Absolutely minimal work is being done on X itself, in part because all of the X developers have been working on Wayland instead. We're at a tipping point...

            Objectively speaking though, X is legacy. Absolutely minimal work is being done on X itself, in part because all of the X developers have been working on Wayland instead.

            We're at a tipping point now...wayland is now more often than not the default for a given DE.

            2 votes
            1. [2]
              lou
              (edited )
              Link Parent
              X is as much legacy as Tildes is, than. Programs that work perfectly, will work perfectly for a very long time, and will probably never see any substantial development in the future. But that is...

              X is as much legacy as Tildes is, than. Programs that work perfectly, will work perfectly for a very long time, and will probably never see any substantial development in the future. But that is only true and relevant for developers, telling that to a regular user means something very different. It's a misleading term because users do not care about which technology is behind a product. They only care if they work, and the word "legacy" gives the impression that they don't.

              1. vord
                Link Parent
                I grok that. Windows XP is still perfectly functional, depending on your use case. Doesn't make it not-legacy though. X11 is officially in "Deprecated, removal date TBD' status.

                I grok that. Windows XP is still perfectly functional, depending on your use case. Doesn't make it not-legacy though.

                X11 is officially in "Deprecated, removal date TBD' status.

                1 vote
        2. [4]
          vord
          Link Parent
          Welcome to the world of 'voting with your wallet.' Linux devs are voting with their dev time. If NVIDIA users really want to use these Linux projects, either they need to pressure NVIDIA, develop...

          Welcome to the world of 'voting with your wallet.'

          Linux devs are voting with their dev time. If NVIDIA users really want to use these Linux projects, either they need to pressure NVIDIA, develop their own patches, or they need to hop ship to Intel or AMD.

          Way back, the answer to "I want Linux to support my modem" was "Well then buy one off this list."

          1. [3]
            ngz
            Link Parent
            My position isn’t “Wayland devs should be forced to support Nvidia.” As far as I’m concerned, people should be able to work on developing whatever they’re interested in and/or are paid to work on....

            My position isn’t “Wayland devs should be forced to support Nvidia.” As far as I’m concerned, people should be able to work on developing whatever they’re interested in and/or are paid to work on.

            What I’m saying is that given that they’ve made the choice not to provide that support, claiming that Wayland as an ecosystem is ready for the majority of users is a gross overstatement at best.

            It’d be like if I developed an alternative browser, refused to support any machines with fewer than 30 physical cores, and then claimed it was the future and everyone should switch to it. The software might be feature-complete on its supported platforms, but if you explicitly refuse to support a large fraction (if not the majority) of the people you’re suggesting try your software you can’t then claim surprise when they don’t adopt it.

            1 vote
            1. [2]
              vord
              Link Parent
              If it would help, lets reframe to what Wayland is: X12. X developers release X12, say "OK X11 is EOL, please migrate to X12." NVIDIA says "Nah thats too much work, we're gonna stay on X11." Then...

              If it would help, lets reframe to what Wayland is: X12.

              X developers release X12, say "OK X11 is EOL, please migrate to X12."

              NVIDIA says "Nah thats too much work, we're gonna stay on X11."

              Then all the users blame X developers for claiming X12 isn't ready for prime time even though it is...for pretty much everyone that isn't stuck behind NVIDIA's decision to not bother.

              The only reason Wayland isn't X12 is because the developers wanted to shed the multiple decades of obsolete baggage the X specs require.

              1 vote
              1. ngz
                Link Parent
                That… doesn’t actually change the dynamic I’m talking about at all? It doesn’t matter if it’s X12 or not - it’s about the framing and dynamic. Supported use cases might be fine (debatable, though...

                That… doesn’t actually change the dynamic I’m talking about at all? It doesn’t matter if it’s X12 or not - it’s about the framing and dynamic. Supported use cases might be fine (debatable, though that’s not relevant to the point), but the issue is that it’s not being framed as the future of the Linux desktop for non-Nvidia users - the qualifier is missing.

                For a less Linux-world-focused example, consider Microsoft dropping support in Windows 11 for machines that don’t have TPMs - a large fraction of their target user base. They’ve rightly been criticized for it, and it’s slowing adoption because people have perfectly functional machines they already own. “Tough luck, we’re not supporting half our market anymore, better buy new hardware” is equally bad there as it is in Wayland’s case. People are upset with them about it, for the same reasons.

                You could argue that users should be holding Nvidia accountable, and I can see the reasoning there. But you can’t exactly blame the users for resenting and disliking the Wayland devs using them as a political weapon against Nvidia when all they want is to be able to use their machines.

                1 vote
    2. streblo
      Link Parent
      ROCm doesn't have many (any?) officially supported consumer cards but most recent cards will do just fine even going back as far as the Vega. I've been playing around with GPU compute for the past...

      ROCm doesn’t have broad compatibility

      ROCm doesn't have many (any?) officially supported consumer cards but most recent cards will do just fine even going back as far as the Vega. I've been playing around with GPU compute for the past year with an AMD card and Arch Linux and have had maybe a handful of driver crashes while running the ROCm stack.

      For example, it took a few months for Starfield to be playable on an Nvidia GPU after release.

      This is one of the bigger advantages to using an AMD card in Linux if you play newer games. Valve has paid developers working on radv and the company has a vested interest in making the latest games playable. With Nvidia, they really only care about consumer desktop support on Linux for compute purposes, so you'll probably get things eventually because they don't want their drivers to diverge too much but you're basically at their mercy or at the mercy of unpaid nouveau developers.

      1 vote
  16. sazed
    Link
    I also have Intel+Nvidia and have yet to find a single game that doesn't work for me, even after several years. Check the site ProtonDB to see how your favorite games fair. I can't offer advice on...

    I also have Intel+Nvidia and have yet to find a single game that doesn't work for me, even after several years. Check the site ProtonDB to see how your favorite games fair.

    I can't offer advice on dual booting as I haven't done that in years. I will say, however, to be sure you understand what Linux is and isn't. Its not meant to be Windows so if you're expecting it to be, you may become frustrated. I do agree that Linux Mint is an excellent distro for somebody coming from Windows, though.

  17. l_one
    Link
    My experience: Linux Mint Cinnamon, 5.15.0-112-generic Kernel Hardware: ASRock H570 Phantom Gaming 4, i9-11900K, Nvidia RTX A2000 I have also used Mint/Cinnamon on my previous hardware which I...

    My experience:

    Linux Mint Cinnamon, 5.15.0-112-generic Kernel
    Hardware: ASRock H570 Phantom Gaming 4, i9-11900K, Nvidia RTX A2000

    I have also used Mint/Cinnamon on my previous hardware which I believe used a GeForce 1060 Ti.

    I haven't really had much in the way of problems. Oh, at first install on the RTX A2000 display was crappy low resolution (but functional), but all I had to do was open the Driver Manager and tell it to use the Nvidia drivers instead of the open source xorg driver. I did have an issue years later where I had to switch between (if I remember correctly) the 525.x and 535.x driver metapackage (one mouse click in the driver manager) because an update to the package made it act weird, but after clicking on the different package, all good.

    I am currently looking into switching away from Mint in favor of MX Linux because of issues with Flatpack being kind of dumb with how large its update downloads are (I have Comcast service, and not unlimited), but the overall experience with Mint has been great and I love the desktop environment.

    Mint would still be what I would recommend to anyone making the initial transition away from Windows.

    As to Windows messing with dual boot? Honestly I don't know for sure. I have a dual-boot setup on my laptop that I use for on-site IT and haven't had problems there, but that's barely one data point as I almost never use it.

  18. Rudism
    Link
    I have a Ryzen board with integrated graphics that I use as my main card on Linux, plus a discrete GeForce RTX 3060 Ti that I use in Windows when I dual-boot for games. Running steam under Linux...

    I have a Ryzen board with integrated graphics that I use as my main card on Linux, plus a discrete GeForce RTX 3060 Ti that I use in Windows when I dual-boot for games.

    Running steam under Linux using nvidia's prime-run utility actually works really well for every game I've thrown at it. The only reason I still dual-boot is because I'm a couch/controller gamer so I do all my gaming remotely over Steam Link, and that doesn't work for sh** on Linux for me.

    I do still use the geforce for non-gaming purposes under Linux (mostly running local LLM AI chatbots and APIs using docker and the nvidia container toolkit, which also all works quite nicely).

  19. jess
    Link
    In my experience (1070, running Linux from within Proxmox) it has been awful. Can't compare to AMD but can compare to Windows 11 with the exact same hardware + Proxmox setup. Was using it as a...

    In my experience (1070, running Linux from within Proxmox) it has been awful. Can't compare to AMD but can compare to Windows 11 with the exact same hardware + Proxmox setup. Was using it as a media PC hooked up to a TV.

    The Linux attempt had severe performance issues trying to decode 4k videos that simply weren't a problem when we tried on windows, and Steam streaming stuttered horribly.

    It could be the Proxmox setup causing problems, but I'd have expected Linux to work better virtualised than Windows rather than the other way around.

  20. ThrowdoBaggins
    Link
    I’ll sidestep the dual boot question and mention that I recently bought a cheap 8GB USB thumb drive and that’s enough capacity to install a portable Linux Mint Cinnamon with some spare room for...

    I’ll sidestep the dual boot question and mention that I recently bought a cheap 8GB USB thumb drive and that’s enough capacity to install a portable Linux Mint Cinnamon with some spare room for future updates. As long as your motherboard supports booting from USB drive (and I’m hard pressed finding any that don’t support that even in the last decade or so)

    I went for portable because it’s a basically risk-free option to try it out, and only costs a few dollars. I’m planning on trying it out for a few months to a year, and see if there are any dealbreakers that I haven’t spotted yet or if it’s gonna be my next full time OS at home.

    If you have access to cheap USB drives like I do, I’d say go for it!

  21. Tuaam
    Link
    I have a GT 710 for my linux box and driver installation was relatively painless on my end - but there are essentially two drivers that you choose here. The first one is the 'noveau' ones which...

    I have a GT 710 for my linux box and driver installation was relatively painless on my end - but there are essentially two drivers that you choose here. The first one is the 'noveau' ones which are open source third-party ones and the second ones are the official drivers Nvidia has on their website. You can use either one, but I think the takeaway is that they may or may not be for gaming, it depends on what you use your machine for. I don't use my linux box for gaming (mostly schoolwork and programming), sometimes it is weird getting certain settings to work (I tried running quake once and it would display on both my monitors with the crosshair set at the edge of both), and other times it is relatively painless.