Announcement

Collapse
No announcement yet.

New "NV30" Nouveau Driver Still Causes Pain

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

  • New "NV30" Nouveau Driver Still Causes Pain

    Phoronix: New "NV30" Nouveau Driver Still Causes Pain

    One week ago following the committing of the major libdrm re-write for the Nouveau project, the "NVFX" Gallium3D driver was dropped and succeeded by a new "NV30" driver for the GeForce FX/6/7 series GPUs. Unfortunately, for at least some hardware, this Nouveau support is still a busted mess...

    http://www.phoronix.com/vr.php?view=MTA5MDc

  • #2
    Old hardware ...

    It's no surprise that newer cards work better with gallium, after all there's only one person who perpetually and exclusively (as far as it comes to nouveau) works on (the 3D part of) nouveau gallium. And since I don't have the time to provide good coverage of all hardware generations, I focus on the ones I use, i.e. nv50 and Fermi/Kepler.

    Oh, and, show me the CPU that gets you 150 fps in OA at 1920x1080.

    Comment


    • #3
      150fps at all resolutions

      @calim

      That's running on i7 990x , 3.4GHz and 6 cores + HT.

      Comment


      • #4
        Originally posted by calim View Post
        Oh, and, show me the CPU that gets you 150 fps in OA at 1920x1080.
        If you're referring to the comment Michael made about llvmpipe possibly being faster, he was referring to the FX5200 card and that 150fps benchmark was running on the 6600.

        He's still probably wrong, but that 5200 wouldn't get anywhere close to 150fps.

        Comment


        • #5
          I also have a FX 5200 (AGP) and 6600 GT (both AGP and PCIe).
          All those cards have never had problems at all with modesetting or Compiz, Cinnamon and other accelerated desktops. It surprises me again that Michael has so much problems with Nouveau.

          About incorrect rendering, that also happens at times on my FX 5200 but nvfx was worse.

          Comment


          • #6
            and the concludion is ...?

            I don't get the intention behin bashing the open drivers again and again.
            One could argue this could help to shift focus to open-source development and attrackt more developers - which as far as I can see hasn't happend.
            Instead, what you do is to cause frustration for those few guys/girls that spend their free time writing those drivers, telling them over and over again how slow and feature-incomplete their driver is, compared to those binary blobs written by comapnies which invested millions and millions of dollars, because their whole buissness depends on these drivers.

            Comment


            • #7
              Originally posted by Linuxhippy View Post
              I don't get the intention behin bashing the open drivers again and again.
              You demotivate the current developers who obviously are incompetent because of the slow progress, they quit, and the hordes of good developers just waiting for a chance to show off their work get the final incentive to start working on making perfect open source drivers with OpenGL 4 support finished before the year is over.

              Comment


              • #8
                Originally posted by Linuxhippy View Post
                I don't get the intention behin bashing the open drivers again and again.
                One could argue this could help to shift focus to open-source development and attrackt more developers - which as far as I can see hasn't happend.
                Instead, what you do is to cause frustration for those few guys/girls that spend their free time writing those drivers, telling them over and over again how slow and feature-incomplete their driver is, compared to those binary blobs written by comapnies which invested millions and millions of dollars, because their whole buissness depends on these drivers.

                Among many reasons:

                - It's my form of bug reporting.

                - To inform such hardware owners thinking about X hardware that it may not work or perhaps that it's in great shape, depending upon the article...

                - If it's a busted mess, as a reference to cite when someone says, e.g. "Why haven't you run NV30 benchmarks yet?"
                Michael Larabel
                http://www.michaellarabel.com/

                Comment


                • #9
                  Originally posted by Michael View Post
                  Among many reasons:

                  - It's my form of bug reporting.

                  - To inform such hardware owners thinking about X hardware that it may not work or perhaps that it's in great shape, depending upon the article...

                  - If it's a busted mess, as a reference to cite when someone says, e.g. "Why haven't you run NV30 benchmarks yet?"
                  Without any logs (I'm not even going to mention bugzilla) it's not bug reporting - it's just bitching

                  It's just a cheap way to get click revenue

                  Comment


                  • #10
                    Originally posted by Michael View Post
                    - It's my form of bug reporting.
                    There is a public bug-tracker, where you can post useful bug-reports without causing demotivation and irritation.

                    - To inform such hardware owners thinking about X hardware that it may not work or perhaps that it's in great shape, depending upon the article...
                    - If it's a busted mess, as a reference to cite when someone says, e.g. "Why haven't you run NV30 benchmarks yet?"
                    So, what about a hardware-compatibility page/wiki, instead of some random articles without any in-depth information?
                    This would provide some real value to people interested in switching their graphic drivers.

                    For an phoronix-outsider (like me) it seems phoronix is trying in cases like this to generate news when there is none to catch the eye of visitors, in the hope to generate ad-revenue.
                    Last edited by Linuxhippy; 04-23-2012, 09:29 AM.

                    Comment


                    • #11
                      Originally posted by FireBurn View Post
                      Without any logs (I'm not even going to mention bugzilla) it's not bug reporting - it's just bitching

                      It's just a cheap way to get click revenue
                      Captured system logs are available via OpenBenchmarking.org.

                      Besides mentioning it on Phoronix, I also usually will ping Martin Peres or others on IRC when I spot something right away. BugZillas don't work for me due to lag time, etc. Unless they happen to be on IRC that instant with something in mind to try or check on, that's the only way it works out for furthering the bug testing/exploration process. As soon as my testing is done for whatever article is being worked on, the systems are almost immediately reworked to begin testing for the next article with either software and/or hardware changes so confirming a fix or change in behavior doesn't work out well.
                      Michael Larabel
                      http://www.michaellarabel.com/

                      Comment


                      • #12
                        Originally posted by Linuxhippy View Post
                        There is a public bug-tracker, where you can post useful bug-reports without causing demotivation and irritation.

                        So, what about a hardware-compatibility page/wiki, instead of some random articles without any in-depth information?
                        This would provide some real value to people interested in switching their graphic drivers.

                        For an phoronix-outsider (like me) it seems phoronix is trying in cases like this to generate news when there is none to catch the eye of visitors, in the hope to generate ad-revenue.
                        See my previous post about why the BugZilla, etc don't usually work. BugZillas also don't generate income.

                        Hardware compatibility page/wikis don't generate enough interest level or page impressions.
                        Michael Larabel
                        http://www.michaellarabel.com/

                        Comment


                        • #13
                          Originally posted by Michael View Post
                          See my previous post about why the BugZilla, etc don't usually work. BugZillas also don't generate income.

                          Hardware compatibility page/wikis don't generate enough interest level or page impressions.
                          This really is the attitude I've come to expect from you Michael

                          Yes bugzilla doesn't generate income - it does however solve the problems you so much like to complain about

                          You already have 90% of the information required for an excellent bug report in bugzilla. So why not focus some effort in updating the PTS to submit that directly to bugzilla - Gentoo's flameeyes has done something similar for his tinderbox. If you did you could genuinely say you're giving back to the community

                          Currently you're re-post blog entries, git and change logs, mailing list posts and shit (or should that be shiße) loads of graphs usually without much, if any, interpretation. You're repetitively taking cheap shots at all the real hard work going into making OSS better for everyone

                          There's been a few times when you've posted completely incorrect information and you don't update or edit your "articles" to reflect this or apologise to the developers you've trounced

                          I wonder how much trouble those developers got in when you announced to the world their plans to use OSS drivers on every platform before they even gave their presentation - did you even consider that you might have single handedly derailed their efforts?

                          Everyone is entitled to make a living but you make the reporters of New International look saintly - maybe you should consider running Phoronix part time if that means you can retain some level of integrity
                          Last edited by FireBurn; 04-23-2012, 10:02 AM. Reason: Grammar and punctuation

                          Comment


                          • #14
                            Michael, the problem is that you are continually and consistently shitting on open drivers. Regardless of what happens, you inevitably conclude that Mesa is shit, worthless, hopelessly behind and that the developers are useless.

                            With other projects, like Wayland or Clang, you are full of praise. When wayland manages to not lock up, you praise it as the future, the successor to X, the best thing since sliced bread, and the only way forward (tm). When Mesa achieves 80% performance of a blob, you call it hopelessly outdated, years late, too far to catch up, etc. It's ridiculous. If you applied your Mesa attitude to Wayland, Clang, brtfs, Unigine, or some other pet project of yours, it would make for very amusing articles.

                            At the moment, it's "Mesa can only do OpenGL3, and there is still OpenGL 3.1, 3.2. 3.2, 4.0, 4.1, etc, they are hopelessly behind and a pile of steaming shit", which is then followed by "Wayland does a Hello World! This is a huge milestone! It's replacing X! Daffodils! A tiling window manager OMG!!!! It's already better than X, which only has 143224 tiling Window managers! Such progress!"

                            It's getting silly and tiring. How about simply posting benchmarks (make sure you do them right), and then let the readers decide whether full OpenGL 3.0 support out of the box is a steaming pile of shit or not. At the and of the day, Mesa can run 99% of all software ever released for Linux, most of it with acceptable performance, and Wayland, well, can't.

                            Comment


                            • #15
                              Originally posted by asdx
                              Wow this Michael guy is a fucking cunt.
                              is there a google+ style +1 button?

                              Comment

                              Working...
                              X