Announcement

Collapse
No announcement yet.

Five Years With The Modern AMD Catalyst Linux Driver

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

  • Five Years With The Modern AMD Catalyst Linux Driver

    Phoronix: Five Years With The Modern AMD Catalyst Linux Driver

    Today marks five years since the revolutionary AMD Catalyst Linux graphics driver was announced to the world by Phoronix. While the driver still had a lot of work ahead, it was September 2007 that brought the brand new Catalyst Linux driver that shared more code with the Catalyst Windows driver and ushered in a new era for AMD with providing same-day Linux driver support, performance improvements, and new functionality to match the Windows driver...

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

  • #2
    Having just done an upgrade from a Radeon HD3870 to a Nvidia GTX660Ti, I must say that AMD drivers are fairly good.

    I think AMD are better at Linux integration as in RandR and start up modes where my Nvidia driver starts Kubuntu with the screen orientation wrong for my dual monitor setup. I also have been getting flash video overlay problems which I didn't get on AMD/ATI.

    Nvidia seems to be better for Wine games, as I now don't get missing textures in Everquest, that I was experiencing before and is a known problem with AMD/ATI.

    I wouldn't have a problem getting another ATI if this Nvidia card I have now, dies. I worry as Nvidia cards are known to have burn out problems with past releases.

    Comment


    • #3
      In the first moment i read. " Five fears with the ...."
      Sorry I'm still a little angry about abandon HD2k-HD4K

      Comment


      • #4
        Five Years With The Modern AMD Catalyst Linux Driver
        Sounds like a prison sentence...

        Comment


        • #5
          The Catalyst Linux driver still faces its share of criticism these days, but the changes introduced in September 2007 set the stage for a much better driver compared to going back further.
          I just tested 12.8 again on my Notebook with a HD 6550M. It still doesn't wake up from suspend. Screen remains black, the fans are running fast, indicating 100% cpu usage and no response from any keys including sysrq. I didn't even bother to read the log file this time and just reinstalled the open source driver.
          Why is it that amd can't wake up their own hardware properly?

          Comment


          • #6
            AMD needs to update their fglrx driver more quickly after a X.org release to bring support for it.
            Don't want to wait months for AMD to push their driver update out for the latest X.org.

            Also, the open source driver definitely needs drastically better Southern Islands support.

            Comment


            • #7
              Originally posted by e8hffff View Post
              Having just done an upgrade from a Radeon HD3870 to a Nvidia GTX660Ti, I must say that AMD drivers are fairly good.

              I think AMD are better at Linux integration as in RandR and start up modes where my Nvidia driver starts Kubuntu with the screen orientation wrong for my dual monitor setup. I also have been getting flash video overlay problems which I didn't get on AMD/ATI.

              Nvidia seems to be better for Wine games, as I now don't get missing textures in Everquest, that I was experiencing before and is a known problem with AMD/ATI.

              I wouldn't have a problem getting another ATI if this Nvidia card I have now, dies. I worry as Nvidia cards are known to have burn out problems with past releases.

              Use Options "Primary" "True" in your xorg on the screen you wish to be, erm the primary :P

              I have to do this myself with the oss radeon drivers, else the hdmi takes over from the vga port (it must think Digital > Analogue)

              Comment


              • #8
                Originally posted by ChrisXY View Post
                I just tested 12.8 again on my Notebook with a HD 6550M. It still doesn't wake up from suspend. Screen remains black, the fans are running fast, indicating 100% cpu usage and no response from any keys including sysrq. I didn't even bother to read the log file this time and just reinstalled the open source driver.
                Why is it that amd can't wake up their own hardware properly?

                I experience the reverse of your situation.

                fglrx always suspends and resumes my notebook properly upon lid close / open. But the OSS driver instantly causes a hard lockup upon lid open, with the only open being a power cycle to reboot the machine.

                YMMV.

                Comment


                • #9
                  @e8hffff

                  What nvidia driver do you use? xrandr changed with 300 series.

                  Comment


                  • #10
                    Ok, let's see how soon it'll get Xorg 1.13 support.. hehe.

                    Comment


                    • #11
                      It seems I been rather lucky with Catalyst Drivers, because my last 2 purchases of graphics cards (HD 3850 and hd 7850) has worked fine for me with Catalyst, i do not know if it is a big difference between brands because both card was from Sapphire, and my next card will probably also be from Sapphire because of this.

                      Comment


                      • #12
                        Originally posted by Kano View Post
                        @e8hffff

                        What nvidia driver do you use? xrandr changed with 300 series.
                        Latest, 304.43

                        The video orientation is correct once the desktop is logged into, but not before. Example the login screen puts the secondary monitor on the right, when I have it set as above. Since I use LightDM I may have to set the monitor also up in Gnome?

                        Comment


                        • #13
                          Everytime I've attempted to use this crap, I've gotten random hard locks, and it never resumes from sleep, OSS Radeon stack never locks for me, and always resumes.

                          Comment


                          • #14
                            @e8hffff

                            Because what you changed is a user setting. If you use kdm you could place xrandr commands in

                            /etc/kde4/kdm/Xsetup

                            Look for something similar for lightdm. I doubt that there exists a config tool to do so, that has absolutely nothing to do with nvidia - would be with oss drivers the same.

                            Comment

                            Working...
                            X