Announcement

Collapse
No announcement yet.

NVIDIA 304.37 Linux Driver Brings 41 Official Changes

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

  • #31
    Originally posted by asdx
    Fuck this. Fuck nvidia. I hope the Linux kernel devs implement a "--disable-nvidia" feature at the kernel level also in order to kill all the crappy blobs like the nvidia one.

    Fuck you nvidia.
    This makes sense. IF oss nv drivers are installed its a pita to actually use nvidia drivers (you have to remove the module and all which is a pain for newbies), its easier from the foss driver point of view

    Comment


    • #32
      Originally posted by asdx
      Fuck this. Fuck nvidia. I hope the Linux kernel devs implement a "--disable-nvidia" feature at the kernel level also in order to kill all the crappy blobs like the nvidia one.

      Fuck you nvidia.
      oh come on, it's common knowlege why the drivers need that, stop trolling for the wrong reasons

      Originally posted by Naib View Post
      because fxaa is a different approach to aa which is fast, why use MSAA when FXAA looks suitable when/if you can reclaim some fps...
      Also there instances where fxaa actually provides better visual results as well as being faster. check out the white papers and results.
      Oh, geez, you missunderstood me, I know all about FXAA/SRAA/MLAA/TXAA/*AA, as a user, I ONLY said that it's not needed to APPLY FXAA OVER MSAA, use MSAA or FXAA, but not both... that's all :P

      BTW, in my test, Unigine Heaven 3.1, 1920x1080/16x AF, all HIGH, Tess Extreme, with in-engine 4xAA is (surprise) faster than with driver applied FXAA, I'll post the numbers once I get home later.
      Last edited by Licaon; 08-14-2012, 06:21 AM.

      Comment


      • #33
        but thats my point... I went into nv-settings and it has an option "override application" but it turned out it didn't actually override the application.
        ingame I had AA at x8

        in the nv control panel I can "force application" to x4 but it doesn't actually override it just adds aa, so app does x8 then nv does x4.
        So when I did FXAA it didn't override the program doing AA (as the nvidia-settings is implying) it does it on top of what the application is doing HENCE the x8 MSAA and then FXAA being applied by nv thus resulting in the fps drop.


        once ingame was disable reasonable fps was recieved (lower than MSAA to be fair but I am playing)


        you seem to be misunderstanding me, the issue here is with nvidia-settings not actually doing what it say. in windows force override does exactly that, in linux is does it in addition to

        Comment


        • #34
          I did understand, I repeat, given the nature of the FXAA (and of the other shader based AA things) I found it rather ugly when combined (blurred text and al).
          Also, since this sounds like a bug somehow, do report it too via http://nvidia.custhelp.com/app/utils...m/redirect/ask (not via nvnews since no nVidia dev posted there afaik since the June/July incidents)

          Comment


          • #35
            Originally posted by gedgon View Post
            I'm not doubting you that some people are experiencing it. I'm just saying that I am unable to reproduce it here.

            Comment


            • #36
              Originally posted by Licaon View Post
              oh, that one, yeah I get that too with mplayer2 but not mplayer1 so you can guess where to point the finger :P ( KDE 4.8.x 64bit w/ OpenGL composition + SMPlayer )
              I just removed mplayer2 and libav and replaced them with mplayer and ffpeg.

              The slowdown isn't there. But it's just as useless, because when I minimize the video or make it fullscreen, the whole desktop freezes and mplayer crashes after 6 seconds or so (at which point the desktop becomes responsive again.)

              Comment


              • #37
                Interesting to see the improved EDID support. Had to export the EDID.bin and fix it with some script on my monitor because otherwise the
                screen would be cropped. Maybe I can remove my Option "CustomEDID" from xorg.conf now.

                Comment


                • #38
                  Originally posted by Licaon View Post
                  [...]with mplayer2 but not mplayer1 so you can guess where to point the finger :P[...]
                  This is mplayer (not mplayer2) http://youtu.be/7VtHz4RNfac
                  It's not "5 fps cursor" but video shuttering is unacceptable, same as desktop experience at framerate < ~60 FPS

                  Comment


                  • #39
                    - A --disable-nouveau switch for the NVIDIA binary blob installer that will attempt to automatically kill the open-source Nouveau DRM driver to prevent it from being loaded and conflicting with NVIDIA's official driver.
                    This is wonderful news!

                    Now I'm hoping for a "--delete-Mesa" switch, followed by "--kill-GCC", and finally "--replace-everything-with-Win8", so people have no problems anymore and nothing conflicts with the official driver.

                    That's exactly what we want a hardware vendor to do -- not opening specification so we can use their shit, but deleting open source software from your computer if it doesn't fit in with their secretive master plan.

                    Kudos!

                    Comment


                    • #40
                      Originally posted by pingufunkybeat View Post
                      This is wonderful news!

                      Now I'm hoping for a "--delete-Mesa" switch, followed by "--kill-GCC", and finally "--replace-everything-with-Win8", so people have no problems anymore and nothing conflicts with the official driver.

                      That's exactly what we want a hardware vendor to do -- not opening specification so we can use their shit, but deleting open source software from your computer if it doesn't fit in with their secretive master plan.

                      Kudos!
                      Are you an idiot?

                      Comment


                      • #41
                        Originally posted by RealNC View Post
                        Are you an idiot?
                        Takes one to know one. What do you say?

                        Comment


                        • #42
                          @pingufunkybeat

                          nouveau is not killed it is just blacklisted. Btw. older installers asked already if you want to blacklist nouveau, so there is just a switch to do so, thats nothing magical. I would just prefer a switch to disable all X runtime, nouveau or whatever checks, that is really annoying. Every few releases there was a new check, some i avoided using mount --bind or so, but basically all that worked later was killing X inside screen. At least that works - a bit tricky but you can switch from nouveau to nvidia binary without rebooting. When you try the same with fglrx your system will definitely crash. Unloading radeon is however possible with the same trick.

                          Btw. on newer distributions with multiarch i highly recommend using the official distro packages (or correct backports) instead of running the nvidia installer directly - usually now they are very tightly integrated with switching support and other things that will definitely brake when you use the installer. The same is for fglrx, but there you could try to build distro specific packages. That does not work for Debian wheezy+ however.

                          Comment


                          • #43
                            Kano,

                            yes, my post was exaggerated satire, but I'm understandably upset that the only contribution Nvidia is making to the nouveau project is blacklisting it. This attitude is nothing new, but command line switches like this one are quite cynical.

                            I have to run Nvidia hardware at work (Cuda/OpenCL) and I had problems with official packages (Debian). The drivers themselves work (you have to pull them from experimental), but the Cuda/CL stuff is incomplete and broken, and I had to go back to the installer. This is also annoying -- I hate running closed source binaries as root. The whole process feels antiquated and alien to the operating system.

                            Comment


                            • #44
                              Originally posted by pingufunkybeat View Post
                              yes, my post was exaggerated satire, but I'm understandably upset that the only contribution Nvidia is making to the nouveau project is blacklisting it.
                              "Understandably" upset? Nope. You're just trolling about a command line option that actually helps ensure the drivers will work if you're currently running Nouveou.

                              Yes, making a driver more user friendly is a bad thing.

                              So the user should be greeted with an X11 that doesn't start and it should be impossible to disable the open driver. Yey, what a great idea. You're a genius.

                              Comment


                              • #45
                                Originally posted by pingufunkybeat View Post
                                yes, my post was exaggerated satire, but I'm understandably upset that the only contribution Nvidia is making to the nouveau project is blacklisting it. This attitude is nothing new, but command line switches like this one are quite cynical.
                                Want some cynic bits? Did you write your firmware for your hardware too? Guess who is running blobby bits as root, lol. But now enough with the trolling. mmmkay? :P

                                now, regarding VDPAU + KDE4 + composition + SMPlayer:
                                *mplayer2-windowed - some mouse slowdown for my USB mouse ( I won't notice it as I go for fullscreen anyway most of the time ) and almost none for my PS/2 one, makes me think about the powersaving options for USB, this can be debugged with PowerTop I guess
                                *mplayer2-fullscreen - almost no slowdown, it's not perfect but it's almost there
                                *mplayer1-full&window - almost no slowdown, it's not perfect but it's almost there
                                *Flash video even 1080p, 32bit version since the 64bit does not work ok/stable in Opera 64bit, accelerated display, accelerated decoding - no slowdown

                                Note that I'm using http://deb-multimedia.org/ builds of sm/mplayer so your results may vary.

                                Regarding FXAA:
                                Unigine Heaven 3.0
                                Render: opengl
                                Mode: 1920x1080
                                Shaders: high
                                Textures: high
                                Filter: trilinear
                                Anisotropy: 16x
                                Occlusion: enabled
                                Refraction: enabled
                                Volumetric: enabled
                                Tessellation: extreme

                                NoAA: FPS: 23.2 / Scores: 584 / Min FPS: 9.0 / Max FPS: 59.0
                                4xAA: FPS: 20.0 / Scores: 504 / Min FPS: 9.1 / Max FPS: 47.9
                                FXAA: FPS: 18.8 / Scores: 475 / Min FPS: 10.1 / Max FPS: 30.7

                                Strange... guess I'll retest with tess normal or something

                                Comment

                                Working...
                                X