Announcement

Collapse
No announcement yet.

AMD Catalyst 8.8 Linux Driver

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

  • AMD Catalyst 8.8 Linux Driver

    Phoronix: AMD Catalyst 8.8 Linux Driver

    AMD had delivered same-day Linux support when launching the Radeon HD 4800 series this summer. This was a first for AMD when launching a major product revision that there was same-day support considering for the R500 and R600 (and earlier) generations it had taken months for any level of support on Linux. This was great to see and the Radeon HD 4850/4870 performance was terrific thanks to their new OpenGL driver introduced last September. Today AMD has announced another Catalyst driver release for Linux and this is arguably the most significant driver update since last October's release when AIGLX support was added. Catalyst 8.8 delivers CrossFire support on Linux, OverDrive overclocking support, adaptive anti-aliasing support, and other improvements.

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

  • #2
    Yay they have actually fixed tearing in normal window rendering, now tearing in x-video needs to be fixed!

    Comment


    • #3
      Not available here yet:
      http://ati.amd.com/support/drivers/l...ux-radeon.html

      But this link works:
      https://a248.e.akamai.net/f/674/9206...x86.x86_64.run



      Most happy to hear about fixes to segfaulting because of Textured Video. Let's see how this release turns out ...

      Comment


      • #4
        Release notes will likely be @ https://a248.e.akamai.net/f/674/9206..._88_linux.html
        Michael Larabel
        http://www.michaellarabel.com/

        Comment


        • #5
          W00t cant wait till its on their site.

          Comment


          • #6
            Originally posted by roberth View Post
            Yay they have actually fixed tearing in normal window rendering, now tearing in x-video needs to be fixed!
            the joke of xv video is still continuing ...

            Comment


            • #7
              But have they fixed that damned checkerboard corruption in MythTV / Wine / lots of other programs?

              Really, if they haven't fixed that after the amount of wailing and gnashing of teeth around here, then someone at AMD ought to be waterboarded.

              Comment


              • #8
                Just installed 8.8 and i have the same problems like 8.6 and 8.7. When i open xdtv (apart from that in all versions of fglrx driver when i open a program to watch tv from my tvcard the screen goes to black and i have to switch to a virtual terminal (ctrl+f[1-6]) and back again to desktop (ctrl+f7)) when i try to resize the xdtv window the image changes to interferences, but this only happens if i resize horizontally, if i resize only vertically the image resizes ok. Another problem is with mplayer or other movie plater when i have kde4 effects enabled, the image is flickering.

                Comment


                • #9
                  The problem here, from what I've heard, is that AMD doesn't have a team kicking out a driver every month. I've heard it's actually 3 teams with offset quarterly releases. Therefore when the Checkerboard of Doom was first spotted back in 8.6, it was already too late to fix it in 8.7 or 8.8, but probably will be fixed in 8.9. If it took >2-3 weeks to find the root cause and make a fix, it could be 8.10 or later before we get a proper fix.

                  In the meantime using Xorg libs instead of ATI ones (forced AIGLX for all) is a workaround for me and some.

                  Just be happy, RadeonHD is coming.

                  Comment


                  • #10
                    Originally posted by Forge View Post
                    The problem here, from what I've heard, is that AMD doesn't have a team kicking out a driver every month. I've heard it's actually 3 teams with offset quarterly releases. Therefore when the Checkerboard of Doom was first spotted back in 8.6, it was already too late to fix it in 8.7 or 8.8, but probably will be fixed in 8.9. If it took >2-3 weeks to find the root cause and make a fix, it could be 8.10 or later before we get a proper fix.
                    For information about their release practices, see The Truth About ATI/AMD & Linux
                    Michael Larabel
                    http://www.michaellarabel.com/

                    Comment


                    • #11
                      there is something fishy with xv.

                      tvtime: a small jerk every couple of seconds.
                      mplayer -vo x11 everything ok
                      mplayer -vo xv a big jerk every couple of seconds and:
                      arecord -D hw:1,0 -r 48000 -c 2 -f S16_LE | aplay -D hw:0,0
                      Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
                      Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
                      overrun!!! (at least 1219253171204,034 ms long)
                      underrun!!! (at least 1219253171580,699 ms long)
                      underrun!!! (at least 1219253171286,251 ms long)
                      overrun!!! (at least 1219253171200,482 ms long)

                      on a 3870, kde4.1 desktop effects turned off.

                      No problem with the 8.7 release.

                      Comment


                      • #12
                        Originally posted by kiwi_kid_aka_bod View Post
                        But have they fixed that damned checkerboard corruption in MythTV / Wine / lots of other programs?

                        Really, if they haven't fixed that after the amount of wailing and gnashing of teeth around here, then someone at AMD ought to be waterboarded.
                        Well, in the article on Phoronix it is said that there are no fixes for performance in wine, which is quite sad :/ I hope they'll make it one day :P

                        Comment


                        • #13
                          If there still no solution for wine? Or a workaround?

                          Comment


                          • #14
                            Originally posted by Forge View Post
                            The problem here, from what I've heard, is that AMD doesn't have a team kicking out a driver every month. I've heard it's actually 3 teams with offset quarterly releases. Therefore when the Checkerboard of Doom was first spotted back in 8.6, it was already too late to fix it in 8.7 or 8.8, but probably will be fixed in 8.9. If it took >2-3 weeks to find the root cause and make a fix, it could be 8.10 or later before we get a proper fix.
                            Hate to state the obvious, but that is really dumb if true. That would mean their latency is three months for everything! Oh yipee, we have crossfire and overclocking... that'll really help me with my laptop They really need to draw a line in the sand, and pick a release to call stable. No new features, just get it working properly with fixes. Then they can have their new features in an unstable release. Once they have a new release that contains all fixes from the stable, checked as OK, then that can become the next stable release.

                            However, this constant rolling breakage and regression is really annoying people. I'm a placid kinda guy, and very reasonable, but c'mon. For MythTV alone, we had blue tinting, then video tearing, then checkerboarding. As one issue gets fixed, another is introduced.

                            There is no point in monthly updates if each one is just as broken as the last.

                            @ Michael - If you are confirming the three months before we see a fix then I have this to ask: If there was an issue affecting the Windows drivers as badly as the checkerboarding is Linux, do you think they would wait 3 months to issue a fix? I have no problem with following a process, but I do have a problem with blindly following one without exception.

                            (Just to note, I haven't actually tried the release, so I might be getting worked up for no reason...)

                            Originally posted by Forge View Post
                            In the meantime using Xorg libs instead of ATI ones (forced AIGLX for all) is a workaround for me and some.

                            Just be happy, RadeonHD is coming.
                            Could you point me to some details about the workaround?
                            Last edited by kiwi_kid_aka_bod; 08-20-2008, 02:11 PM. Reason: clarify question to Forge

                            Comment


                            • #15
                              Originally posted by kiwi_kid_aka_bod View Post
                              Could you point me to some details about the workaround?
                              http://phoronix.com/forums/showthrea...t=10940&page=6

                              About 1/2 to 2/3 the way down the page, dscharrer discovered the way to trigger the X libs switch on Gentoo. Other distros would need to do slightly different things to get the same effect.

                              Basically, instead of the app talking to the driver and the driver accelerating, the app talks to X, X talks to the driver, and the driver accelerates.

                              It's actually very retro-tech, this was how all 3D worked prior to DRI/Nvidia. It works though, and that's 99% of what I need.

                              Comment

                              Working...
                              X