Announcement

Collapse
No announcement yet.

AMD Puts Out A Beta Catalyst Linux Driver For The Public

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

  • AMD Puts Out A Beta Catalyst Linux Driver For The Public

    Phoronix: AMD Puts Out A Beta Catalyst Linux Driver For The Public

    While NVIDIA puts out beta Linux graphics drivers quite often as a means of soliciting testing prior to declaring a new stable GPU driver update, AMD does not but rather they rely upon their NDA-covered select beta testers to put each Catalyst release through its paces before declaring a stable update in their timed monthly manner. Today though it seems AMD has put out a Catalyst Beta driver that's targeting their workstation customers (those with the FirePro / FireGL / FireMV hardware) but as in their usual unified manner, it will work with any supported Radeon (R600+ GPU) as well...

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

  • #2
    Please let it fix tearing, please let it fix tearing... Oh who am I kidding.

    Comment


    • #3
      While NVIDIA puts out beta Linux graphics drivers quite often as a means of soliciting testing prior to declaring a new stable GPU driver update
      Well truth be known, Nvidia's "public betas" are usually tested by a bunch of NDA'd individuals as well before soliciting more feedback on the betas from the masses.

      Comment


      • #4
        Originally posted by unimatrix View Post
        Please let it fix tearing, please let it fix tearing... Oh who am I kidding.
        are you sure its the driver and not a problem somewhere else ?

        Comment


        • #5
          Originally posted by unimatrix View Post
          Please let it fix tearing, please let it fix tearing... Oh who am I kidding.
          Just installed the beta on a triple head system with 5870.

          Rebooted.

          Looked for V-Sync locking.


          ........and guess what I found.





          Tearing

          Comment


          • #6
            Another thing still there is if you un-fullscreen SMPlayer you still get corruption on the desktop. Grabbing a window and dragging it round the screen the corruption is fixed due to the repainting effect.

            Comment


            • #7
              Yep driver still causes tearing here. Also some other annoying bugs that are present in 10.12 also present in this one. Looks like the same pile of crap as 10.12, just with an "Unsupported hardware" logo planted on it.

              Comment


              • #8
                O.K. In the video playback department, if you use GL for output you can get V-Synced playback from VLC and SMPlayer.

                From other's reports this was previously working only if you had a single monitor and as I had three I had to suffer the jitters and tears (as in video tearing, not tears from the eyes. Though it could bring some to tears I guess ). Now, yay, at last I can now playback video in tear free goodness. Now to configure Totem to use GL playback.

                ....But even though GL Vsync is set to force on in Catalyst Control Center and Compiz is set to V-Sync on, it still tears like a b_stard when moving windows around. This is the less important area for frame locked video out of the two though I guess, so I consider this a slight win.

                Another thing it still does it when starting video playback via VLC or SMPlayer the monitor connected to the display port goes to black for about a second and then comes back. It's like when the playback software is grabbing a display context or something the driver probes that status of the port which throws the DP->DVI adaptor.

                When starting a video from VLC the screen goes black and then comes back. If you pause playback and then re-start it you don't get the "to black" crap happening. If you stop the video playback and then hit play, you get another dose of blackness.

                Now when starting a video from SMPlayer the screen goes black and then comes back. Pausing playback and then restarting it you don't get more blackness. When stopping playback and hitting play again, no blackness.

                I guess VLC re-does something that SMPlayer doesn't re-do when beginning playback after hitting stop.

                Totem with it's default video output path doesn't produce this annoying effect but you get video tearing with it. Yay.

                Comment


                • #9
                  That's not the driver you are waiting for. You can certainly use gl output with mplayer but for vlc the cpu usage was way too high with it. vlc can only use xv in a half optimal way - even with xvba/libva the cpu usage is really high complared to mplayer.

                  Comment


                  • #10
                    Originally posted by Kano View Post
                    That's not the driver you are waiting for. You can certainly use gl output with mplayer but for vlc the cpu usage was way too high with it. vlc can only use xv in a half optimal way - even with xvba/libva the cpu usage is really high complared to mplayer.
                    I was only testing for V-Sync with low-def stuff.

                    I'd hate to see what CPU usage was like with 25mb/s media

                    Comment


                    • #11
                      This beta is a very old build, relative to what we have now. The beta is not indicative of what will be in Catalyst 11.1. It is targeted to the GPGPU / high end customers (think 12 monitors connected to 3-way Crossfire HD5970s or equivalent FireGL) who pour in $$$ and demand more heavily tested drivers so they don't get random kernel panics and stuff.

                      It's like when Red Hat releases a 5.x beta update -- my reaction is "um, OK..." because it provides no new features and maybe fixes a few tiny bugs or security issues. And corporations would rather pay for that stability / "known quantity" factor than use the latest developments.

                      Catalyst 11.1 will be using "old" code relative to the development trunk, but not quite as old as this beta. So you should see a really, really, really often desired feature show itself.

                      Comment


                      • #12
                        Originally posted by allquixotic View Post
                        Catalyst 11.1 will be using "old" code relative to the development trunk, but not quite as old as this beta. So you should see a really, really, really often desired feature show itself.
                        Sounds good.

                        Having complained about the v-sync issue and all I still get the feeling this driver's better then 10.12 so it's always good to see progress I guess.

                        Comment


                        • #13
                          Originally posted by allquixotic View Post
                          This beta is a very old build, relative to what we have now. The beta is not indicative of what will be in Catalyst 11.1. It is targeted to the GPGPU / high end customers (think 12 monitors connected to 3-way Crossfire HD5970s or equivalent FireGL) who pour in $$$ and demand more heavily tested drivers so they don't get random kernel panics and stuff.

                          It's like when Red Hat releases a 5.x beta update -- my reaction is "um, OK..." because it provides no new features and maybe fixes a few tiny bugs or security issues. And corporations would rather pay for that stability / "known quantity" factor than use the latest developments.

                          Catalyst 11.1 will be using "old" code relative to the development trunk, but not quite as old as this beta. So you should see a really, really, really often desired feature show itself.
                          What, a working driver after a number of years?

                          Comment


                          • #14
                            Originally posted by mugginz View Post
                            Another thing still there is if you un-fullscreen SMPlayer you still get corruption on the desktop. Grabbing a window and dragging it round the screen the corruption is fixed due to the repainting effect.
                            I think this is a problem in newer versions of Mesa.
                            My Intel card does that too.

                            Comment


                            • #15
                              Just for an interesting tidbit on the beta, it really does look like a workstation only release. More info here: http://fireuser.com/blog/firepro_dri...ows_and_linux/

                              Comment

                              Working...
                              X