Announcement

Collapse
No announcement yet.

NVIDIA 495.44 Linux Driver Released With GBM Support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #51
    Originally posted by blacknova View Post
    Ok, I was not aware solaris provided KMS, sure I know they had framebuffer interface, but how close it to current KMS I don't know. And I assumed that actually working KMS on FreeBSD was provided by their most recent push to adopt linux DRM and drivers, which is 3 or 4 years old.
    That recent push is a different problem. https://www.phoronix.com/scan.php?pa...item&px=OTYzMA That push in fact started 9 years ago not 3 or 4.



    In 2006 freebsd was backing kgi that really was a different way to get to KMS. So 3 OS Nvidia Unix binary driver support wanted Kernel mode setting in 2009 just they were not in agreement at that point on how todo it. 2011 all the OS that Nvidia binary drivers support were in agreement.

    This is just Nvidia being stubborn pain in the ass to deal with. Yes eglstreams and nvidia modesetting and their binary driver blob in general on Linux is basically Nvidia wants todo their own thing with no cooperation with any other developers. 2006 is kind of a key year when everyone on the Unix/Linux platforms started serous-ally thinking about kernel mode setting. Thinking and having agreement are two different things.

    Comment


    • #52
      Originally posted by X_m7 View Post
      Does anyone know if this is going to help with Wayland on Optimus laptops? Or about the status of Wayland on Optimus laptops in general with the proprietary driver?

      Not sure if I'm just blind or what but when I try searching basically all I see is either one or the other but never both together (or if they are it's nothing concrete or it's talking about nouveau or AMD). Last time I tried it myself nothing worked when I try to run them on NVIDIA, both Wayland native apps and XWayland stuff.
      Since 470 Optimus (because of DMA-BUF) works fine in Wayland. You just install a 470+ nvidia driver and, at least on Fedora, Intel iGPU still gets selected as primary video device. Then if you want to run any application using your Nvidia dGPU you just use the same CLI arguments you can use in Xorg. I don't remember tweaking anything else, and I'm not in my Nvidia laptop right now. Hope you can get it working, should be 5 minutes. If you do glxgears for testing, remember it is limited to vsync (60/144fps) unless specified otherwise.

      Cheers,

      Comment


      • #53
        Can anyone tell me if this solves the problem with Nvidia and HDMI when connected to TVs?

        Comment


        • #54
          Originally posted by Goddard View Post
          Can anyone tell me if this solves the problem with Nvidia and HDMI when connected to TVs?
          That one is how long is a piece of string. Sorry to say not all TVs are made equal and not all cables are made equal. Intel, AMD, Nvidia, Playstations, Xbox, Sony cameras..... Fairly much everything with a HDMI out has at least some TVs out there they are not going to get along with.

          Depending on what the variation from HDMI specification is alters what device does not work. Yes I can have a TV where every works bar Intel or a TV where everything works bar a Sony camera....... Nvidia is one of the more picky for getting upset when communication from the TV is outside HDMI specification.

          Solve is most likely asking too much because that would require all TV and cables to be inside specification. Nvidia could come less picky so making the issue less common.

          Goddard I wish it was true solvable problem but a large amount of the problem is how much HDMI hardware be it cables or devices are not in fact to HDMI specification. Also part of the problem is how much tools cost to confirm that X device is not to specification and that is why you are having problems. Yes this not to specification problem also explains having TVs the same model where one works with Nvidia and one does not work with Nvidia but everything else works as well. Yes one of those TVs most likely has a defective part from factory.

          I really wish HDMI was not such a mess.

          Comment


          • #55
            Originally posted by sabian2008 View Post

            Since 470 Optimus (because of DMA-BUF) works fine in Wayland. You just install a 470+ nvidia driver and, at least on Fedora, Intel iGPU still gets selected as primary video device. Then if you want to run any application using your Nvidia dGPU you just use the same CLI arguments you can use in Xorg. I don't remember tweaking anything else, and I'm not in my Nvidia laptop right now. Hope you can get it working, should be 5 minutes. If you do glxgears for testing, remember it is limited to vsync (60/144fps) unless specified otherwise.

            Cheers,
            Welp, I tried setting it back up again and it doesn't work right even on X11, some windows are either just black (like glxgears if I run it with the info parameter) or ends up looking like a screenshot of whatever was behind it when it opens (like Steam), while others seem to straight up ignore everything and just run on the iGPU anyway (like Firefox). I remember it did work on X11 at least when I tried it last time, guess it's even more Novideo for me now. glxinfo does at least manage to show NVIDIA when I try it in Wayland now, so yay I suppose.

            Even if it did work I'd still be missing proper power management (as in turning the dGPU off properly), since I have a GTX 960M, rather frustrating since bbswitch has managed it for years now, hell even nouveau can do it now, reclocking and Wayland included, damn shame it's performance isn't up to scratch.

            Edit: I'm still on the 470 driver here, might check it out again when I get 495.

            Edit 2: Just got the 495 driver + egl-wayland 1.1.9 and fixed the issues on X11, turns out I was just missing early KMS. Now when I try Wayland the things running via XWayland works (although when I tried Skyrim SE via Proton I get diagonal screen tearing and some jank, don't have that on plain X11), while native Wayland stuff completely ignores the existence of the dGPU.
            Last edited by X_m7; 01 November 2021, 08:56 AM.

            Comment


            • #56
              Originally posted by Leopard View Post

              Nvidia literally owns laptop market when it comes to dgpu ones.

              Nvidia at that time supported both Linux and Windows.

              Nvidia at that time only supported Optimus on Windows, not Linux.

              All of those decisions made Linux inferior compared to Windows at that time? Yes

              When proper Optimus support landed on Linux? At 2019 August

              Linus's "NV fuck you" reaction happened at 2012.

              So it should be obvious why that "fuck you" was well deserved.
              Problem is, problem is way bigger then just that. Eg. you want optimus mostly to save energy, but most laptops on battery aren't so energy efficient on Linux as they are on windows, eg. my Haswell (4712mq with gtx850m from MSI) laptop during optimus comfortably could work 5 hours on battery on windows, but couldn't do 3 hours in linux with entire nvidia gpu disabled (only intel igpu was working). Intel power managment is diffrent on linux and windows, and it is bettter on windows a ton, inherently Optimus aims to do same thing, just everybody says "nvidia fuck you" while nobody says "intel fuck you" despite that outcome for end user (me) was the same.

              And if you still claim it is nvidia fault, well later i had one more laptop intel only without nvidia gpu and i saw similar outcome.

              Comment


              • #57
                Originally posted by piotrj3 View Post

                Problem is, problem is way bigger then just that. Eg. you want optimus mostly to save energy, but most laptops on battery aren't so energy efficient on Linux as they are on windows, eg. my Haswell (4712mq with gtx850m from MSI) laptop during optimus comfortably could work 5 hours on battery on windows, but couldn't do 3 hours in linux with entire nvidia gpu disabled (only intel igpu was working). Intel power managment is diffrent on linux and windows, and it is bettter on windows a ton, inherently Optimus aims to do same thing, just everybody says "nvidia fuck you" while nobody says "intel fuck you" despite that outcome for end user (me) was the same.

                And if you still claim it is nvidia fault, well later i had one more laptop intel only without nvidia gpu and i saw similar outcome.
                Interesting, I also happen to have a MSI laptop with Optimus (Skylake 6700HQ and GTX 960M), and back when I had Windows on it still it only lasted about 3 hours, while on Linux I could do 4. Now that my battery has worn down somewhat it's down to like 3 hours on Linux too. Of course, other stuff changing probably had an effect, for example I used to use a basic window manager only setup, and now I'm back on full KDE.

                Comment


                • #58
                  Originally posted by piotrj3 View Post
                  Problem is, problem is way bigger then just that. Eg. you want optimus mostly to save energy, but most laptops on battery aren't so energy efficient on Linux as they are on windows, eg. my Haswell (4712mq with gtx850m from MSI) laptop during optimus comfortably could work 5 hours on battery on windows, but couldn't do 3 hours in linux with entire nvidia gpu disabled (only intel igpu was working). Intel power managment is diffrent on linux and windows, and it is bettter on windows a ton, inherently Optimus aims to do same thing, just everybody says "nvidia fuck you" while nobody says "intel fuck you" despite that outcome for end user (me) was the same.

                  And if you still claim it is nvidia fault, well later i had one more laptop intel only without nvidia gpu and i saw similar outcome.
                  It really not that simple either.
                  Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

                  No the power management is not always better on Windows by a ton over Linux.



                  Choice of distribution and desktop environment both are big factors under Linux on battery life.

                  Intel did a white paper on why Linux on some laptops are so bad in power usage. ODM/OEM can be to blame. Intel did cover a stack of setting that can be set in the EFI/BIOS that can result in Linux using more power yet windows being fine after you had installed your ODM/OEM drivers as well.

                  That paper said if windows performance on laptop was not decent without installing the vendors own drivers you had something that was screwed at the firmware level. Yes cheaper to make a windows driver than have to reflash the bios/EFI. MSI ones are quite common that if you put a stock windows them and don't add MSI drivers battery life is shorter as well due to EFI/BIOS issue. Yes this not being able to work with generic windows can be problem when attempting data recovery out of device using a Windows portable execution environment as well so not a Linux only problem caused by ODM/OEM taking a short cut.

                  When it comes to bad battery life there are quite a few people who need the F you message in your case one of the peoples who might be due a F you message is MSI, the Linux distribution, Desktop environment and Intel.

                  I wish this was a simple problem with a single party to blame with the battery life problem most cases it not.

                  Comment


                  • #59
                    Multiple users: I was experiencing problems with NVIDIA GPU.
                    birdie: I was not, so you are wrong or lying.

                    This whole thread basically LOL

                    Comment


                    • #60
                      Originally posted by Goddard View Post
                      Can anyone tell me if this solves the problem with Nvidia and HDMI when connected to TVs?
                      Curious to know: which problems?

                      From my years-long experience of using nVidia GPUs in my HTPCs, I've never encountered any problems whatsoever.
                      On the contrary, 'nvidia-settings' allows me to easily set the color range to 'limited' [studio levels], so that blacks are not crushed & whites not overblown.

                      And just to put this into perspective:
                      AMDGPU still doesn't have this very basic support after all these years:



                      bridgman
                      Anyone left over at AMD that still cares about the above issue?

                      Comment

                      Working...
                      X