Announcement

Collapse
No announcement yet.

AMD's New Catalyst Driver Is Available To All Linux Users

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

  • AMD's New Catalyst Driver Is Available To All Linux Users

    Phoronix: AMD's New Catalyst Driver Is Available To All Linux Users

    Yesterday saw a SteamOS Linux update that shipped a new AMD Catalyst Linux driver that reportedly worked much better for popular Steam Linux games. That driver update led Valve to officially support AMD (and Intel) graphics on SteamOS. For non-SteamOS Linux users, that new AMD driver update is available for other distributions...

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

  • #2
    Finaly support for xorg 1.14!

    But xorg 1.15 already on arch testing repository and xorg 1.16 already proposed =(

    Comment


    • #3
      13.11 v9.95 after 13.12??

      Kind of strange that they release a beta numbered 13.11 beta v9.95 after releasing a driver numbered 13.12.

      http://support.amd.com/en-us/downloa...Linux%20x86_64

      The package maintainers are going to love the numbering the implies a downgrade ...

      Comment


      • #4
        Originally posted by rrohbeck
        radeonsi is slow but doesn't crash my X session (any more.)
        You should test the distance alpha then http://survivethedistance.com/
        It hangs the radeonsi driver pretty hard for me...

        But on a positive note: That's the only thing that I have had any problems with for a rather long time.

        I even have much more problems with the intel driver randomly hanging. But intel pretty much always recovers after 10 seconds.

        Code:
        $ dmesg | grep stuck
        [30860.843896] [drm] stuck on render ring
        [75901.275528] [drm] stuck on render ring
        [100180.921909] [drm] stuck on render ring
        [115240.793172] [drm] stuck on render ring

        Comment


        • #5
          Originally posted by gerddie View Post
          Kind of strange that they release a beta numbered 13.11 beta v9.95 after releasing a driver numbered 13.12.

          http://support.amd.com/en-us/downloa...Linux%20x86_64

          The package maintainers are going to love the numbering the implies a downgrade ...
          This! This! Can we PLEASE have sane version numbering? I can see that I have nvidia 325.15 installed (with dpkg --list, no less!), and that 330 is newer. But fgrlx you have the catalyst version which is stupid as hell, and has no relation to the installed version number (I love when different fglrx versions all generate the same deb package version), and before we had version-betaXX now we have beta vsubversion.subsubversion. CAN WE PLEASE END THIS HELLISH MADNESS?!?

          Comment


          • #6
            Originally posted by ChrisXY View Post
            You should test the distance alpha then http://survivethedistance.com/
            It hangs the radeonsi driver pretty hard for me...

            But on a positive note: That's the only thing that I have had any problems with for a rather long time.

            I even have much more problems with the intel driver randomly hanging. But intel pretty much always recovers after 10 seconds.

            Code:
            $ dmesg | grep stuck
            [30860.843896] [drm] stuck on render ring
            [75901.275528] [drm] stuck on render ring
            [100180.921909] [drm] stuck on render ring
            [115240.793172] [drm] stuck on render ring
            Which Intel CPU do you have? And what is the version of the kernel you used?
            I had the same issue with 3.13-rc7 then I downgraded to 3.12.6. Also do you have any problems with heating?
            I noticed that the temperatures of my laptop are much higher with 3.13-rc7 compared to 3.12.6.

            Comment


            • #7
              I've been using the radeon drivers for about a half year now and so far I only have 1 game completely unplayable in it (immediate crash). Otherwise, I've had a noticeably better experience with the open source drivers. I'd like to use Catalyst because then I get Crossfire support, but crossfire doesn't even work in any games I own (only the Heaven benchmark) so it isn't really worth using.

              It's kind of irritating, because what one driver is good at, the other one is bad at, and vice versa. Since the open source drivers are improving at a rapid rate and since I don't tend to play games in linux that often, I've decided to stick with the open source drivers. Whenever I get the opportunity to switch to wayland, I guess that'll help make my decision much easier.

              Comment


              • #8
                WTF?

                The following packages must be installed in order for the AMD Catalyst™ Linux graphics driver to install and work optimally:
                - gimp-help-en
                - gimp-help-common
                ...
                Why the hell Catalyst is depending on GIMP help files?

                Comment


                • #9
                  Originally posted by Rakot View Post
                  Which Intel CPU do you have? And what is the version of the kernel you used?
                  I had the same issue with 3.13-rc7 then I downgraded to 3.12.6.
                  Ivy Bridge and yes, 3.13, but this has been going on for a long time now.
                  Not sure about the heat.

                  Comment


                  • #10
                    So, here is a question: I have been out of the Linux game for the past 3 years and when I left AMD looked like they would have working OS drivers in the next one or two years.; why are these closed drivers still neccesary? Are the OS drivers done yet? If so; what's taking so damn long?

                    Comment


                    • #11
                      Don't work with Kubuntu 14.04 x64 Kernel 3.13.0-1

                      This time too gives me error while trying to compile the kernel... i have Kubuntu 14.04 x64 kernel 3.13.0-1, someone managed to solve?

                      Comment


                      • #12
                        I added the 3.13 patches from the Debian fglrx-driver 13.12 package to the fglrx-driver package from SteamOS, but thats not installable in Ubuntu. Feel free to fetch just the patches from the debian.tar.gz.

                        http://kanotix.com/files/fix/fglrx.w...3.11~betav9.9/

                        Comment


                        • #13
                          I complain about catalyst all the time. However, I find some posts here unrealistic. Kernel 3.13 is not even officially released yet. And no I wouldn't demand AMD to care about my distribution packaging. On the other hand I absolutely expect cross distribution binaries from amd.com and support of officially released kernel, xorg, etc. It would be nice to not have to wait a couple of months after an ubuntu release to get a non-beta driver.
                          Last edited by zoomblab; 01-10-2014, 04:30 AM.

                          Comment


                          • #14
                            Originally posted by MaestroMaus View Post
                            So, here is a question: I have been out of the Linux game for the past 3 years and when I left AMD looked like they would have working OS drivers in the next one or two years.; why are these closed drivers still neccesary? Are the OS drivers done yet? If so; what's taking so damn long?
                            The closed drivers still have slightly more performance (thanks to things like game-specific hacks that would not fit a clean codebase of the FOSS drivers) and support for higher versions of OpenGL (since bits of OpenGL support are still missing in Mesa core). And there are some edge cases, like OpenCL working better with the blob, or UVD 1 not being implemented in the FOSS drivers yet (though neither is the UVD in the blob usable). But overall the benefits of using the FOSS drivers outweighs the benefits of using Catalyst, in my opinion.

                            That's if talking about r600g, for radeonsi (GCN cards) there are more problems due to it still being a new project and things are relying on very experimental things like Glamor and recent LLVM versions. But the progress there is pretty fast and it's already usable, if not quite on par with the closed driver.

                            Comment


                            • #15
                              Biggest weakness of AMD is showing itself right now.

                              AMD is just to small.

                              They got great tech for consoles? They had not enough $$ for production technology to make it all-round-nice.
                              They got great idea bout 3D API? They had not enough ETF (Engineering Task Force ;P ) to make it into all supported Catalyst platforms.
                              They got great sound solution? Actually its nice, and I can not see much drawbacks here. Nice job! (However one could always argue that there is never enought lib support )
                              They got console deals? PC clones got a bit abandoned (with Linux taking biggest hit in Catalyst, radeon grew nicely).
                              They got nice OpenCL gpu's? But not enough ETF to make good compilers/middleware.

                              And now they play catch up with SteamOS.

                              That may sound like bashing (and it is), but it also signal how much success AMD have recently... Like too much
                              And there is always good news:

                              If product sell nicely You have more $ for developing it more.

                              (And lets not pretend that world without AMD would be better. There is no competition to Nvidia in high-perf GPU market but that one company. And right now they are revolutionazing 3D space, as only they have opportunity and necessity (Nvidia turned support of "old ways" into strenght. Intel do not have that much advanced APU alternative, and they are interested in DX right now.)



                              Anyway, those that Catalyst use some new binaries? If so, when radeon drivers will be updated?

                              Comment

                              Working...
                              X