Announcement

Collapse
No announcement yet.

R600 Gallium3D Loses To AMD Catalyst Legacy Driver On Windows 8

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

  • R600 Gallium3D Loses To AMD Catalyst Legacy Driver On Windows 8

    Phoronix: R600 Gallium3D Loses To AMD Catalyst Legacy Driver On Windows 8

    For those ATI/AMD customers with graphics cards of the Radeon HD 2000/3000/4000 generations, they are supported by the "Catalyst Legacy" driver but this older proprietary driver branch is seldom updated for new Linux kernel and X.Org Server releases. Thus, the only real option for those with these older Radeon GPUs is to use the open-source Radeon Gallium3D graphics driver. But how does this driver compare to the still-maintained Catalyst Legacy driver for Windows 8? Here are some benchmarks.

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

  • #2
    Ouch. Didn't see that one comming. Sad, but lets test it again in a year

    Comment


    • #3
      Its "high end"? r600g maybe wont ever get enough optimizations (backend for radeonSI changed, and will be main focus now), to suprass Catalyst in support for GPUs requiring lots of them.

      Comment


      • #4
        yet again.. MICHAEL... FRAME LATENCY IS IMPORTANT NOT ON AVERAGE, BUT ON THE FREQUENCY OF THE SPIKES, ERGO AN HIGHER FRAME LATENCY AVERAGE WITH WAAAY LESS LATENCY SPIKES IS BETTER THAN LOWER AVERAGE WITH LOTS OF SPIKES

        Comment


        • #5
          And now how does the Windows 8 catalyst compare to the Linux one? They're not exactly the same, and the legacy Catalyst for Linux still exists, even if it requires downgrading the X server.

          Comment


          • #6
            lockups

            radeon hd 3650 still gets lockups while or after running games/3D apps on free drivers (it's random but once u start 3D app it's 100% of getting a lockup within an hour)

            Comment


            • #7
              Useless comparison... Apples to oranges...

              Comment


              • #8
                Framerate speed is not the only thing that matters in a graphics driver. In Windows 7, Blender feels much more responsive, and selecting objects takes less than a second, whereas in Linux (with the lastest open source AMD drivers) sometimes it takes more than 5 seconds to select a different object.

                Comment


                • #9
                  Originally posted by sireangelus View Post
                  yet again.. MICHAEL... FRAME LATENCY IS IMPORTANT NOT ON AVERAGE, BUT ON THE FREQUENCY OF THE SPIKES, ERGO AN HIGHER FRAME LATENCY AVERAGE WITH WAAAY LESS LATENCY SPIKES IS BETTER THAN LOWER AVERAGE WITH LOTS OF SPIKES
                  Second that.

                  For latency avrg is equal to avrg FPS... Here is some good article about good methodology for couting and comparing latency:
                  http://techreport.com/review/21516/i...e-benchmarking

                  Hope its easy enought to integrate into PTS.

                  Comment


                  • #10
                    Originally posted by wargames View Post
                    Framerate speed is not the only thing that matters in a graphics driver. In Windows 7, Blender feels much more responsive, and selecting objects takes less than a second, whereas in Linux (with the lastest open source AMD drivers) sometimes it takes more than 5 seconds to select a different object.
                    AFAIK Blender is using GL_SELECT which is not hardware accelerated in mesa. There has been a mesa patch though I think.

                    Comment


                    • #11
                      Was this the stock AMD WDDM 1.1 drivers, 13.1 legacy or 13.4 beta legacy?

                      I found that WDDM, 13.1 and 13.4 are all terrible when it comes to coming. My gaming performance with those drivers on an HD4200 IGP was horrid compared to latest drivers on Windows 7.

                      Comment


                      • #12
                        Nice work Michael, you got all the combinations I wanted to see.

                        Comment


                        • #13
                          The news here is: Catalyst is losing more and more of its edge against the free driver. Last year we were speaking about 1/6th of the performance across the board, now we're talking about 1/2, 1/3.

                          Now please, Mesa guys, boost that triangle figure! If we focus in GPUTest / Triangle we can have some serious optimizations.

                          Comment


                          • #14
                            Originally posted by przemoli View Post
                            Second that.

                            For latency avrg is equal to avrg FPS... Here is some good article about good methodology for couting and comparing latency:
                            http://techreport.com/review/21516/i...e-benchmarking

                            Hope its easy enought to integrate into PTS.
                            Maybe adding a Frame Time Variance to PTS would be a good thing then.

                            Comment


                            • #15
                              Originally posted by log0 View Post
                              AFAIK Blender is using GL_SELECT which is not hardware accelerated in mesa. There has been a mesa patch though I think.
                              If what you say is true, then how come the problem started to happen like 6-8 months ago with a mesa update ? It sounds like a regression to me.

                              Comment

                              Working...
                              X