Announcement

Collapse
No announcement yet.

AMD Catalyst 12.3 For Linux Officially Released

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

  • AMD Catalyst 12.3 For Linux Officially Released

    Phoronix: AMD Catalyst 12.3 For Linux Officially Released

    AMD has officially released Catalyst 12.3 for Linux as its March 2012 update for those relying upon this binary graphics driver...

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

  • #2
    This is the 4th (!!!) driver in a row that sucks with my hd 5670. can't somebody at amd fix the rendering issues with that card? i did not test xvba but most likely it is broken as well. What i test is really easy to install:

    http://phoronix.com/forums/showthrea...793#post251793

    The first test already does not render correctly. Last time the rendering issues (test 3/4) needed 11 month to fix, do i have to wait this time again 11 month?

    Comment


    • #3
      What is the most recent Kernel this works with?

      Comment


      • #4
        Broken Record

        Michale just copies and pastes this text for every catalyst release with the only change being a bump to the version number:

        "Catalyst 12.3 isn't too interesting in terms of features or bug-fixes, and it doesn't have X.Org Server 1.12 support."

        That's why I still use Nvidia... not because the cards are necessarily better, but because Nvidia actually puts forth at least a modicum of effort on developing drivers.

        Comment


        • #5
          "Catalyst 12.3 isn't too interesting in terms of features or bug-fixes, and it doesn't have X.Org Server 1.12 support."

          no issue for me, I just use the open Radeon driver then. If it would matter, I would just switch to CentOS, a Ubuntu based distro or openSUSE where AMD's proprietary driver is almost always supported, if a stable distro release is used.

          IMHO it's good enough if Catalyst 12.4 brings support for this X.Org Server version. Maybe I would think different, if I knew that X.Org Server 1.12 has important new features or fixes compared to 1.11.

          Comment


          • #6
            [QUOTE=chuckula;256190]Michale just copies and pastes this text for every catalyst release with the only change being a bump to the version number:

            "Catalyst 12.3 isn't too interesting in terms of features or bug-fixes, and it doesn't have X.Org Server 1.12 support."


            Lol yea. It's the monthly appointment one can't miss!

            Comment


            • #7
              Originally posted by chuckula View Post
              Michale just copies and pastes this text for every catalyst release with the only change being a bump to the version number:

              "Catalyst 12.3 isn't too interesting in terms of features or bug-fixes, and it doesn't have X.Org Server 1.12 support."

              That's why I still use Nvidia... not because the cards are necessarily better, but because Nvidia actually puts forth at least a modicum of effort on developing drivers.
              I'd suggest something like.

              "Catalyst 12.3 is out and includes some exciting new bugs, no new features, and still doesn't support the current stable X server."

              Comment


              • #8
                AMD continues to disappoint

                doesn't have X.Org Server 1.12 support.
                Keeps on disappointing.

                I am glad I chose Nvidia instead of AMD.

                Comment


                • #9
                  How long until we have a working Catalyst with KWIN_DIRECT_GL=1 (i.e. the new KWin drawing code)? And does this Catalyst work properly with X.org 1.11?
                  Last edited by Alejandro Nova; 03-28-2012, 03:35 PM.

                  Comment


                  • #10
                    Originally posted by DaemonFC View Post
                    I'd suggest something like.

                    "Catalyst 12.3 is out and includes some exciting new bugs, no new features, and still doesn't support the current stable X server."
                    @Michael I think this comment is more true than yours. Can you please start using it in the future Catalyst for Linux news? Because of this truth I dropped some time ago all Radeons and buy only Intel/Nvidia and recommend them to others. Maybe Radeon is similar or equally good hardware when compared to Intel or Nvidia but who cares if these features are not exposed by driver to the user and Operating System. The hardware is as good as its drivers - I do not remember who wrote this but this opened my eyes as hardware buyer and I always follow this.
                    Last edited by zbiggy; 03-28-2012, 04:36 PM.

                    Comment


                    • #11
                      Originally posted by zbiggy View Post
                      @Michael I think this comment is more true than yours. Can you please start using it in the future Catalyst for Linux news? Because of this truth I dropped some time ago all Radeons and buy only Intel/Nvidia and recommend them to others. Maybe Radeon is similar or equally good hardware when compared to Intel or Nvidia but who cares if these features are not exposed by driver to the user and Operating System. The hardware is as good as its drivers - I do not remember who wrote this but this opened my eyes as hardware buyer and I always follow this.
                      IMHO the radeon open source drivers are the best hardware drivers available for Linux. Problem is, they only start to really look good (and by that I mean, actual gaming and professional 3d applications, NOT just KMS and a composited desktop) for a given piece of hardware after it's been on the market for about 2 years. It's their "goal" to reduce this time, but they seem to be making baby steps toward their goal, not leaps and bounds.

                      But if you're willing to wait, it's the best.

                      Comment


                      • #12
                        Btw. when you look at version it can be only a slight modification of the former one (everything after 8.911 is broken). 12-2 was not released in feb, so 8.94 was most likely too broken... but 8.951 is definitely a joke...

                        11-11 - good - 8.911 - Tue Nov 8 10:30:38 EST 2011
                        11-12 - bad - 8.92 - Wed Dec 7 11:21:44 EST 2011
                        12-1 - bad - 8.93 - Thu Jan 19 11:56:34 EST 201
                        12-2 - bad - 8.95 - Wed Feb 29 15:34:55 EST 2012
                        12-3 - bad - 8.951 - Fri Mar 23 16:38:51 EDT 2012

                        Get rid of that stupid monthly releases. Fix the drivers and release it when done!
                        Last edited by Kano; 03-28-2012, 07:54 PM.

                        Comment


                        • #13
                          Originally posted by Kano View Post
                          Btw. when you look at version it can be only a slight modification of the former one (everything after 8.911 is broken). 12-2 was not released in feb, so 8.94 was most likely too broken... but 8.951 is definitely a joke...

                          11-11 - good - 8.911 - Tue Nov 8 10:30:38 EST 2011
                          11-12 - bad - 8.92 - Wed Dec 7 11:21:44 EST 2011
                          12-1 - bad - 8.93 - Thu Jan 19 11:56:34 EST 201
                          12-2 - bad - 8.95 - Wed Feb 29 15:34:55 EST 2012
                          12-3 - bad - 8.951 - Fri Mar 23 16:38:51 EDT 2012

                          Get rid of that stupid monthly releases. Fix the drivers and release it when done!
                          This time, I've to agree with you. They should spend more time and resources in developing their FOSS driver (as it's already being caught by nouveau ), and less with Catalyst (they should do releases, for instance, for every Xorg update cycle or 3 months, and not every month).

                          Btw, time to test CUDA with bumblebee in my new nVidia laptop... (hope it works)

                          Cheers

                          Comment


                          • #14
                            So as 12-3 was a useless test i tried the OpenCL1.2 beta. Surprise, the hd 5670 issues are fixed there. But amd still does not manage to fix the drivers for kernel 3.2.13+ on 32 bit. So lets add this:

                            OpenCL1.2beta - good - 8.96 - Fri Mar 16 04:03:00 EDT 2012

                            I set this driver a default in my script now, the control file was different however, but my hd 4550 did not show an unsupported watermark. The supported pci-ids are the same from 8.95 to 8.96. I really hope that amd could get rid of forced watermarks. Nvida NEVER did that - those watermarks caused by the control file are just plain stupid and the check if a valid signature file is there is so old that nobody cares about. Best save some bytes and remove th

                            The supported pci-ids did not change at all from 12-2 to 12-3 when you look at the fglrx kernel module. from 12-1 to 12-2 only 2 ids where added (679e and 990a). So the only change could be in the control file to get rid of unsupported hardware. And the devs needed so long to do that, really really bad joke. That whole control/signature file thing is pure crap, give it up! at code. It was introduced first with 8.39.4 driver, but then it was disabled for 8.39.4. As those drivers are always generic there is absolutely no need to annoy users with watermarks, if the drivers dont work be sure they will not use it anyway if amd tested it or not...

                            One last thing to add: usually not only the control file has got a supported pci id list, also the amdconfig/aticonfig tool has got one. That should be removed as well of course. Do you agree bridgman?
                            Last edited by Kano; 03-28-2012, 09:47 PM.

                            Comment


                            • #15
                              Originally posted by Kano View Post
                              The supported pci-ids did not change at all from 12-2 to 12-3 when you look at the fglrx kernel module. from 12-1 to 12-2 only 2 ids where added (679e and 990a). So the only change could be in the control file to get rid of unsupported hardware. And the devs needed so long to do that, really really bad joke.
                              Kano, I know you understand this and are just having fun, but in case anyone else was confused by this...

                              The PCI IDs in the code determine which hardware the driver will *try* to run on. The code might work perfectly, or be buggy, or fail to run at all.

                              The PCI IDs in the control file show which hardware the driver has passed QA on. The time and effort is not to add IDs to the file (that's all automated anyways) but to do the testing, bug fixing and re-testing required to pass QA on the hardware.

                              Once testing and bug fixing on specific hardware is completed, the IDs in the control file are updated to reflect that these binaries form a production driver for the hardware it's running on, whereas previously it displayed a "hey this might run but be aware it's not a production driver" message.

                              Is the watermark too intrusive ? In my personal opinion something like a one-time splash at startup would be better. The question though is whether the devs should be working on getting production support in place more quickly or spending that time on rewriting the watermark code so that running a pre-production driver isn't as annoying. I would put available people on speeding up production support myself, which is what seems to be happening, but I realize not everyone agrees with that and it's kind of academic because I'm not involved with fglrx development anyways.

                              As we get more consistent at posting SKU-specific launch drivers if a regular Catalyst release with support isn't coming out at the right time, I think you'll find the watermarks become less of an issue anyways.
                              Last edited by bridgman; 03-28-2012, 11:24 PM.

                              Comment

                              Working...
                              X