Announcement

Collapse
No announcement yet.

AMD Catalyst 13.12 GPU Driver For Linux Released

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

  • #16
    Originally posted by tomtomme View Post
    So the REAL count is thus reduced to 116, that makes solving 1 bug or 1 feature (like kernel or x-server version) every 3 days... is that much? I am not a developer at all, but to me it seems, that there is only 1 guy left for bugfixing the linux-catalyst.
    Hmm, my take on that would be that only the bugs that get logged by the internal testing team is ones that would get recorded in the release notes. Bugs probably get fixed on a scheduling basis, meaning they
    Now if a team of say 7 developers were working on this, and they spend a small amount of their time doing formal bugfixes, then it would make sense.
    Often things get fixed that doesn't appear in the release notes, so I suspect that like any reasonable developer, they fix a bug when they come across it.

    Working on a large project myself, you really just need one idiot that is not rooted out by the management (because they either talk too well, play the toady, or whatever), to introduce hundreds of really difficult to find bugs. It works best if this person knows they mess up, and go on the attack whenever it seems that an issue of theirs is uncovered. Management that doesn't actually code, see this guy always berating people about bad code, so they often think this person has the highest standards (when it is the opposite, really).
    Ok, I should stop this before it turns into a proper tirade... :-P

    Comment


    • #17
      [384194]: Tear-Free Desktop sets V-Sync to 30Hz instead of 60Hz
      [376115]: Display corruption when using rotation

      Cool! It took them several months, but they fixed it!

      Comment


      • #18
        From where do you get, that they have only one guy who fixes the bugs? As I see Marek, Alex and other guys fixes hundreds defects a a year on the FOSS driver side. Is this is just assumption?

        Comment


        • #19
          I think people are sometimes too harsh with AMD and not so with NVIDIA...."Na'vi People" in flash anyone ?

          How much time did it took for Nvidia to fix it ?

          Comment


          • #20
            Originally posted by Espionage724 View Post
            I got this error in make.log on Xubuntu 13.10 with these drivers:

            Code:
            DKMS make.log for fglrx-13.251 for kernel 3.11.0-14-generic (x86_64)
            Thu Dec 19 03:06:45 EST 2013
            AMD kernel module generator version 2.1
            doing Makefile based build for kernel 2.6.x and higher
            rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
            make -C /lib/modules/3.11.0-14-generic/build SUBDIRS=/var/lib/dkms/fglrx/13.251/build/2.6.x modules
            make[1]: Entering directory `/usr/src/linux-headers-3.11.0-14-generic'
              CC [M]  /var/lib/dkms/fglrx/13.251/build/2.6.x/firegl_public.o
              CC [M]  /var/lib/dkms/fglrx/13.251/build/2.6.x/kcl_acpi.o
            /var/lib/dkms/fglrx/13.251/build/2.6.x/kcl_acpi.c: In function ‘KCL_ACPI_ParseTable’:
            /var/lib/dkms/fglrx/13.251/build/2.6.x/kcl_acpi.c:999:5: warning: passing argument 1 of ‘(acpi_status (*)(u32,  void *, void *))handler’ makes integer from pointer without a cast [enabled by default]
                 ((acpi_table_handler)handler)(hdr);
                 ^
            /var/lib/dkms/fglrx/13.251/build/2.6.x/kcl_acpi.c:999:5: note: expected ‘u32’ but argument is of type ‘struct acpi_table_header *’
            /var/lib/dkms/fglrx/13.251/build/2.6.x/kcl_acpi.c:999:5: error: too few arguments to function ‘(acpi_status (*)(u32,  void *, void *))handler’
            make[2]: *** [/var/lib/dkms/fglrx/13.251/build/2.6.x/kcl_acpi.o] Error 1
            make[1]: *** [_module_/var/lib/dkms/fglrx/13.251/build/2.6.x] Error 2
            make[1]: Leaving directory `/usr/src/linux-headers-3.11.0-14-generic'
            make: *** [kmod_build] Error 2
            build failed with return value 2
            13.11 9.4 beta drivers seem to be fine though
            Confirmed, got me the same error when trying to install the build packages in Ubuntu GNOME 13.10. Reverted to 13.11 9.4 beta again.

            Comment


            • #21
              Originally posted by LN17 View Post
              From where do you get, that they have only one guy who fixes the bugs? As I see Marek, Alex and other guys fixes hundreds defects a a year on the FOSS driver side. Is this is just assumption?
              I am assuming that. Because of the one-bug-fix every 3 days I counted above. I am NOT talking about the FOSS team - they make a great job from my point of view. I was only talking about catalyst. READ my post!

              Comment


              • #22
                Linux Mint 16

                Originally posted by Forage View Post
                Confirmed, got me the same error when trying to install the build packages in Ubuntu GNOME 13.10. Reverted to 13.11 9.4 beta again.
                And definitely not works with Linux Mint 16 and kernel 3.12.5
                Code:
                Building module:
                cleaning build area....
                cd /var/lib/dkms/fglrx/13.251/build; sh make.sh --nohints --uname_r=3.12.5-031205-generic --norootcheck.....(bad exit status: 1)
                [Error] Kernel Module : Failed to build fglrx-13.251 with DKMS
                [Error] Kernel Module : Removing fglrx-13.251 from DKMS
                
                ------------------------------
                Deleting module version: 13.251
                completely from the DKMS tree.
                ------------------------------
                Done.

                Comment


                • #23
                  I'm glad to see v13.12 released even their dev team must be very small. Seeing the list of bug fixes from 13.11, I estimate the size of their team to 2-3 persons, max. Maybe 1 if the guy is very productive and motivated.

                  I have logged a problem with XvBA that doesn't work at all for me. It must be very low in their list of priorities:

                  http://ati.cchtml.com/show_bug.cgi?id=950

                  As they will probably focus on openGL first. The AMD hardware situation is very frustrating right now. Each set of drivers have their strengths andf weaknesses.

                  Sure if video hardware decoding was very important, I would go to the open source driver but by doing so, I would kiss goodby opencl and opengl performance.

                  No idea how important economically the linux crowd is for AMD (probably small but growing) but I am personnally upholding a purchase a purchase of an AMD graphic card upgrade until they give adequate support to their new hardware (I'm thinking about R290X). With some luck, I'll uphold till the next gen hw!

                  I'll give the driver a try. Maybe they will be some hidden surprises. Maybe I'll see a big fps increases with my games. If so, then I guess, I'll be overall happy.

                  Comment


                  • #24
                    Originally posted by AJSB View Post
                    I think people are sometimes too harsh with AMD and not so with NVIDIA...."Na'vi People" in flash anyone ?

                    How much time did it took for Nvidia to fix it ?
                    That was a Flash bug and NVIDIA only "fixed it" after it became apparent that Adobe had no interest in cleaning up their mess. And NVIDIA's fix was something like "if (program == flashplugin) { unDumbifyAdobesCrap(); }"

                    Comment


                    • #25
                      Originally posted by johnc View Post
                      That was a Flash bug and NVIDIA only "fixed it" after it became apparent that Adobe had no interest in cleaning up their mess. And NVIDIA's fix was something like "if (program == flashplugin) { unDumbifyAdobesCrap(); }"
                      Yeah i knew about be a Adobe Flash bug...but was only affecting some Nvidia cards and actually Nvidia launched a driver version that they said would solve bug and i continued with the darn thing affecting a 9600GT for several more drivers and many months until it finally was solved...

                      Comment


                      • #26
                        This driver is basicly the Beta 9.4 with some additional fixes, so don't expect huge changes.

                        From what I have heard... the next driver based on a new branch and therefore including new features and performance improvements will be Catalyst 14.1 Beta and is scheduled for early-mid January. There have only been some minor fixes in the current branch since 13.11 Beta 6 which was released two months ago. I expect much improved OpenGL performance due to SteamOS, and maybe Valve can leak the driver early.

                        Comment


                        • #27
                          Originally posted by d2kx View Post
                          This driver is basicly the Beta 9.4 with some additional fixes, so don't expect huge changes.

                          From what I have heard... the next driver based on a new branch and therefore including new features and performance improvements will be Catalyst 14.1 Beta and is scheduled for early-mid January. There have only been some minor fixes in the current branch since 13.11 Beta 6 which was released two months ago. I expect much improved OpenGL performance due to SteamOS, and maybe Valve can leak the driver early.
                          Thanks for the info about new branch and all !
                          I was expecting something like that and precisely for reasons mentioned by you: "Valve Pressure" (pun intended )

                          Comment


                          • #28
                            Originally posted by Agakonna View Post
                            And definitely not works with Linux Mint 16 and kernel 3.12.5
                            Code:
                            Building module:
                            cleaning build area....
                            cd /var/lib/dkms/fglrx/13.251/build; sh make.sh --nohints --uname_r=3.12.5-031205-generic --norootcheck.....(bad exit status: 1)
                            [Error] Kernel Module : Failed to build fglrx-13.251 with DKMS
                            [Error] Kernel Module : Removing fglrx-13.251 from DKMS
                            
                            ------------------------------
                            Deleting module version: 13.251
                            completely from the DKMS tree.
                            ------------------------------
                            Done.

                            Same DKMS issue in Ubuntu 13.10.

                            Comment


                            • #29
                              For those with build issues, especially on Ubuntu/DKMS:

                              http://archive.ubuntu.com/ubuntu/poo....debian.tar.gz

                              Have a look in "/debian/dkms/patches/", especially "replace_acpi_table_handler.patch". It already landed in Ubuntu 14.04 LTS-dev.

                              Comment


                              • #30
                                Originally posted by Espionage724 View Post
                                I got this error in make.log on Xubuntu 13.10 with these drivers:

                                13.11 9.4 beta drivers seem to be fine though

                                I too had a similar error with the 13.250 drivers with kernel 3.12+ (git), by manually patching the kcl_apci file it worked. the same fix probably applies to the 13.12 drivers. Its a hack..

                                build the debian packages using the installer..
                                dpkg-deb -x fglrx_13.250-0ubuntu1_amd64.deb extract/
                                dpkg-deb -e fglrx_13.250-0ubuntu1_amd64.deb extract/DEBIAN
                                patch the kcl_apci file (http://pastebin.com/YW2XtTpq)
                                fakeroot dpkg-deb -b extract fglrx_13.250-0ubuntu1_patched_amd64.deb

                                Now the package should install

                                Comment

                                Working...
                                X