Thats why i never buy their shit after having one laptop with one of their graphics.

Worst part? I’m still using that laptop, im doing troubleshooting right now.

Anyone else?

  • manpacket@lemmyrs.org
    link
    fedilink
    English
    arrow-up
    55
    arrow-down
    1
    ·
    1 year ago

    The context seems to be missing.

    Not an nvidia dev, but so far all my cards been nvidia, went over a quite a few of them, both laptop and desktops. In my experience they just work once you install proprietary drivers and the only type of a problem is when ubuntu silently decides to upgrade it behind your back - in this case you need to restart the machine so kernel modules match the drivers.

    • Hopscotch@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      In my experience they just work once you install proprietary drivers

      That’s not my experience with dual-GPU (Intel+Nvidia) hardware and multiple displays, where the standard xrandr functions are often used to modify the output configuration.

      In my case, the Nvidia GPU is supported by Nouveau, so I can compare it with Nvidia’s proprietary drivers “side-by-side”. With Nouveau, display output configuration and per-application GPU selection both “just work” (I did add a nouveau.config kernel parameter to enable acceleration). I’ve never been able to make the proprietary drivers do those things reliably.

      So I suggest that users with simple single-display, single-GPU systems are likely to have a better experience with the proprietary drivers.

      As is the general consensus here, I do not plan to purchase any Nvidia GPU hardware in the future, especially considering that more recent Nvidia GPUs now require signed firmware, making Nouveau support impossible.

      • noddy@beehaw.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        I agree. Nvidia drivers work fine for desktop systems with a single GPU and a single display. Everything else is a bit hit and miss. Here are a couple of real world experiences I’ve had with using linux on systems with nvidia.

        Laptops with switchable graphics are the worst. You might have set up switchable graphics with bumblebee or something thinking that everything works fine. Until you need to connect your laptop to a projector for holding a presentation or something. Then you find that you can’t connect an external display without disabling the integrated graphics in UEFI settings (causing terrible battery life), because the hdmi out is only connected to the nvidia GPU.

        I’ve also had issues on a desktop with two monitors recently, where nvidia wouldn’t respect my preferences for main monitor. The XFCE main panel would be stuck on my secondary monitor, as nvidia has decided that it is the primary display, even if I’ve selected something else in settings. If I worked around this by creating a new panel on the correct monitor, this panel would not be visible if I try to connect remotely with XRDP.

    • SwissJackalope@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Do agree for the most part, I had issues every now and again with having to downgrade cause some games didn’t work on the newest driver. But for the most part they’ve been pretty ok

    • dustyData@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      9
      ·
      1 year ago

      That’s still neither Ubuntu, Linux or the user’s fault. It’s still 100% Nvidia’s responsibility. So, even with context it looks bad. OS auto-updates should never break the system, and if it does, you’re a bad engineer doing bad things. An update causing the system to show no video signal is awful.

      • AProfessional@lemmy.world
        link
        fedilink
        English
        arrow-up
        10
        arrow-down
        1
        ·
        1 year ago

        Online updates are unsafe but it is Ubuntu’s fault for how they manage kernels. Fedora gets it correct keeping multiple versions around.

        • dustyData@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          1
          ·
          1 year ago

          Having multiple versions of a kernel doesn’t solve this issue. It’s the driver dying and video signal stops working until system reboot that is really a bad implementation. Your new driver should work at least well enough with the previous kernel as to at least prompt the user that a reboot is necessary to finish the update. Bad engineering.

      • manpacket@lemmyrs.org
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        1 year ago

        Proprietary nvidia driver consists of (at least until recently) from two parts - closed userspace part and open kernel part. Those parts talk to each other with some protocol they change every once in a while and the only combination they support is that kernel module and userspace part must be of the same version. When they mismatch you still get video, you don’t get acceleration. And reboot fixes the problem.

        • dustyData@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          1
          ·
          1 year ago

          the only combination they support is that kernel module and userspace part must be of the same version

          AKA bad engineering.

  • rzlatic@lemmy.ml
    link
    fedilink
    arrow-up
    20
    ·
    edit-2
    1 year ago

    first thing i faced while distrohopping before i settle with fedora, is the instability of nvidia on linux.

    it was short path to decision to spare myself of waiting for driver fixes, googling for driver statuses, waiting, posting questions, messing around, switching this and that in hope for better stability, getting frustrated in the end because wherever i search for fixes, there were posts about same problems with same subject: nvidia.

    stable system throughout distro/kernel/driver/system updates is hugely more valuable than having GTX Ti 90000 inside my system and it was a very short bye bye.

    since i ditched nvidia card and went for amd one, my system just works, it’s been years, I’ve never looked back and very honestly, i couldn’t care less about never ending stubborn struggle with nvidia.

    • SinJab0n@mujico.orgOP
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      Same, I’m still using my powerful rx 490 in desktop and not even once has gave me problems.

      I bought this laptop back when I was still using windows, a really good Asus x450LN, wich still allows me to play battlebit, xcom, openxcom, sunless sea/sky, and so on. Not even talkin about office work. So yeah, I’m gonna change it in maybe 2 or 3 years.

      For now ? Dealing with nvidia shenanigans. I have a GUI again wich is good, but steam is fricking dead, so yeah, hopefully I’m not gonna need to reinstall.

    • Dubious_Fart@lemmy.ml
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      edit-2
      1 year ago

      Same, Recently updated my AMD card. Literally did nothing but turn the computer off, remove the old one, install the new one,turn it back on, and it just worked.

      I’ve had enough experience with trying to get nvidia cards working in linux that I know that I’ll never, ever, ever use a nvidia card, and thats including trying to use distros that supposedly bake nvidia bullshit in to make it no hassle, like Pop.

      Which sucks. I’m not a corporate fanboy, I just want something affordable and that works… and right now, on linux, thats just amd. Intel is a close second, though they need another generation or two to iron out their flaws.

  • NaoPb@beehaw.org
    link
    fedilink
    arrow-up
    17
    arrow-down
    1
    ·
    1 year ago

    This reminds me of the nightmare of those laptops with intel and nvidia gpu so you could switch to nvidia if you wanted to game. And what a nightmare it was to even get the nvidia gpu working in linux.

    When I’m buying new hardware I’ll make sure never to buy nvidia again. However sometimes I am gifted things and it would be rude to refuse to accept.

    • Itsamelemmy@lemmy.zip
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      This is what mine has. I was able to get it working with bumblebee on kali. Just switched to Debian 12, and I thought it would work after installing the non-free drivers, but nope. So guess I get to do some reading up on that now. Maybe look into bumblebee again.

      • Hopscotch@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        If you haven’t already, check for Nouveau support. And if your card is supported, you may need a kernel parameter. I needed nouveau.config=NvClkMode=15 (but be warned some parameters like that have some risk, like possibility of overheating, and may or may not be applicable or safe for your GPU).

        For me, it has worked to just set environment variable DRI_PRIME=1 to use the Nvidia GPU for that specific application. (Maybe this is what Bumblebee does; I don’t know.)

        In the future, though, I recommend avoiding Nvidia hardware.

      • NaoPb@beehaw.org
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        I did get mine working eventually. Though that laptop died years ago. I did not get it to switch though so when I ran Linux it was always on the Nvidia GPU. But that wasn’t an issue for me.

        I remember there being a name for this that made it easier to search for a solution. But for the life of me I cannot remember what it was.

        Good luck on your quest and I hope you get it working.

        • Crozekiel@kbin.social
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          omg i’ve been in this rabbit hole trying to get a friend’s laptop working right for the last 2 weeks… I found the name of the thing you are talking about, where the dGPU HAS to talk to the integrated graphics to get to the laptop screen… and then promptly forgot it after getting so mad at such a stupid idea and when I went to google it again to find articles i had previously read I couldn’t find it. :(

        • Itsamelemmy@lemmy.zip
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I finally got it working and feel like an idiot now. Secure boot was enabled. Thing is, I know I disabled it because you have to set a bios password in order to do so. But it somehow got re-enabled. Once I disabled secure boot again the Debian wiki instructions worked and it was pretty simple to do.

    • Hopscotch@lemmy.ml
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      1 year ago

      As I mentioned in another comment, in my experience Nouveau does a much better job with multi-display and multi-GPU systems than Nvidia’s proprietary drivers. Unfortunately Nouveau’s actual hardware support is somewhat limited, so that is only relevant for a subset of Nvidia GPUs.

      I, too, don’t want any more Nvidia hardware.

      • DaPorkchop_@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        nouveau is hardly better than software rendering in most cases. heck, for pretty much every GPU from the last decade, it isn’t even able to adjust the GPU clock frequency (so it’s permanently stuck on the lowest frequency).

    • teawrecks@sopuli.xyz
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      1 year ago

      I remember finding large text file in the win 10 base install that was just a list of game titles. I assumed it was so they could specifically choose which processes should always use the dGPU. I’m searching around now and can’t find any evidence it ever existed though. Anyone else remember seeing it? I feel like there was something about an inappropriate/porn game being included on the list.

  • Anarch157a@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    1 year ago

    On the Radeon camp, it’s just “apt dist-upgrade; systemctl reboot”

    Done.

    The only time I had issues with the open source AMD drivers was when I was doing GPU pass through to play Elite: Dangerous, the drivers really didn’t like the state Windows left the card in when it was time to reattach it to Linux.

    • 5redie8@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Do you have any good suggestions on where to start with using pass through? Have an AMD card as well and would love to be able to do this but I always get stuck at one point or another

      • Anarch157a@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        first is to have a second graphics card - it can be an integrated one, like on Ryzen 7xxx or Intel CPUS - or a second computer that can SSH into the gaming box, just in case you need to open a terminal to fix stuff that broke. Then hit the Level1Tech forums, there’s a lot of knowledge there about the stuff.

  • arapirilous@lemm.ee
    cake
    link
    fedilink
    arrow-up
    9
    ·
    1 year ago

    Same. Thankfully I found that pop!_os works beautifully out of the box and serves my purpose. But I’m done with nvidia. Once my 3090 lives till EOL I’m getting whatever XTX model AMD has

    • kronarbob@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      I did that a few months ago, from a 3060ti to a 6700xt. Best decision since I decided to erase my windows partition.

    • De Lancre@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Wanna change? I have amd 7900xtx, and that shit awesome video card with not working opensource drivers just awesome! I’m sure you will have fun with it.

  • sudoku@programming.dev
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 year ago

    Every once in a while, a new snapshot gets released for OpenSUSE Tumbleweed and mailing list gets flooded with “nvidia PC no longer boots” messages. Meanwhile Radeon users can’t get certain positive changes in the distro because nvidia users get no-video’d from it.

    • Cethin@lemmy.zip
      cake
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      2
      ·
      1 year ago

      Nvidia is a plague. They purposefully make the experience worse in any way possible if you don’t buy Nvidia products. Meanwhile AMD makes their drivers open source and promote open source software.

      The outrage after Starfield announced they would support FSR and didn’t comment about DLSS was frustrating. FSR works on all hardware, while DLSS only works if you buy Nvidia products. Most people I saw were complaining about AMD being an issue though…

    • SinJab0n@mujico.orgOP
      link
      fedilink
      arrow-up
      9
      ·
      edit-2
      1 year ago

      Linux mint forum, and my own laptop with plasma.

      Steam still dead, and the nvidia config got fuck up, gonna try reset xorg and then launch nvidia settings later

      • SALT@lemmy.my.id
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        is there any possibility to lock the nvidia version to make this not happenning instead of having problem with every update each time?

        • Ghoelian@feddit.nl
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          I don’t think nvidia drivers update automatically on ubuntu, right? Pretty sure I’ve had to manually switch to new drivers every time

  • cevn@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    This exact same thing happened on my Ubuntu desktop. I had to restart into safe mode, dpkg configure -a. Dunno what dumb ass thought having your screen go black and not respond to any input was acceptable during an update