Announcement

Collapse
No announcement yet.

AMD Catalyst 9.5 Driver For Linux Released

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

  • #91
    Originally posted by mtippett View Post
    There are no plans at this stage. Most people I have spoken to don't have an interest in seeing kernel messages appear on their screen. Last time I saw that in a production system was on old Sparc X Terminals.
    I'm sorry, but why is this an issue? Perhaps I'm mistaken, but shouldn't the kernel messages only appear onscreen when the driver locks-up? It seems to me that most people don't have an interest in that period.

    On the other hand, kms allows for a graphical boot, less flickering during the boot process and vt switching with less chance of crashes. It will make suspend and resume functions more reliable as well. These are things that users expect from modern systems, sticking to an error-prone system that is less visually rich seems pointless.

    If it's the error messages you're worried about, I'm sure it's possible to only enable them in testing systems and not production systems.

    Please correct me if I'm wrong, but it seems to me the benefits far outweigh the disadvantages.

    Comment


    • #92
      KMS would probably require open-sourcing a part of fglrx as well as splitting that part of it and putting it into the kernel. I don't think this is ever gonna happen.

      Comment


      • #93
        Originally posted by RealNC View Post
        KMS would probably require open-sourcing a part of fglrx as well as splitting that part of it and putting it into the kernel. I don't think this is ever gonna happen.
        I don't see how this is an obstacle - The mode setting part is something which _really_ shouldn't contain any IP affected code, esp. since the mode setting registers have been documented publicly anyways (well, on the other hand I don't know in what way the DRM code is split all over the driver)

        Comment


        • #94
          Originally posted by gzunk View Post
          As for the RadonHD problems, that's not really appropriate for this thread (I was venting), but suffice to say that 2D acceleration is only enabled on RV770 in version 1.2.5, but on Jaunty the standard version is 1.2.4. I believe 1.2.5 requires kernel 2.6.30, and Jaunty is on 2.6.28.

          I try and stick to the defaults as far as possible since that normally makes things more stable.
          My question was more related to the open source drivers; the default driver on Jaunty is radeon, not radeonhd, and the version of radeon shipped with Jaunty should have out-of-box support including 2D acceleration. Jaunty also contains kernel driver (drm) code to support 2D acceleration.

          There are sites such as www.pastebin.com which allow you to paste a big hunk of text then give you a URL you can post. Feel free to start another thread on the open source side if you want.
          Last edited by bridgman; 05-23-2009, 10:33 AM.

          Comment


          • #95
            Does AMD have some secret vendetta with S2Games? With every release of fglrx Savage2 become more and more unplayable. I'm happy when I can actually join a game after the 10th try, because the game just crashes when it should start loading stuff. It's really getting awful.
            Last edited by ningo; 05-23-2009, 02:44 PM.

            Comment


            • #96
              No, quite the opposite AFAIK.

              Can you please check bugzilla ticket 1519, see if the workaround in comment #1 helps for now, and update the ticket with your system and driver info ?

              Here's a link to the existing ticket : http://ati.cchtml.com/show_bug.cgi?id=1519
              Last edited by bridgman; 05-23-2009, 11:43 PM.

              Comment


              • #97
                Originally posted by bridgman View Post
                No, quite the opposite AFAIK.

                Can you please check bugzilla ticket 1519, see if the workaround in comment #1 helps for now, and update the ticket with your system and driver info ?

                Here's a link to the existing ticket : http://ati.cchtml.com/show_bug.cgi?id=1519
                No, it doesn't. What I'm experiencing here was added with 9.5, 9.4 works fine. There was a fix for the 9.4 issue in S2 2.0.1 as well.
                Just to rephrase that: 9.5 added *additional* crashes.

                Comment


                • #98
                  Originally posted by bridgman View Post
                  No, quite the opposite AFAIK.

                  Can you please check bugzilla ticket 1519, see if the workaround in comment #1 helps for now, and update the ticket with your system and driver info ?

                  Here's a link to the existing ticket : http://ati.cchtml.com/show_bug.cgi?id=1519
                  No it doesn't. The crashes were added in 9.5 and there was a fix for the 9.4 issue in S2 2.0.1. Just to rephrase that: 9.5 introduced additional crashes.

                  Comment


                  • #99
                    Originally posted by NeoBrain View Post
                    I don't see how this is an obstacle - The mode setting part is something which _really_ shouldn't contain any IP affected code, esp. since the mode setting registers have been documented publicly anyways (well, on the other hand I don't know in what way the DRM code is split all over the driver)
                    It will also affect the memory manager. AMD/ATI has already stated that they don't want to use the open source stack, but to use their own driver with memory manager.

                    Comment


                    • Originally posted by NeoBrain View Post
                      I don't see how this is an obstacle - The mode setting part is something which _really_ shouldn't contain any IP affected code, esp. since the mode setting registers have been documented publicly anyways (well, on the other hand I don't know in what way the DRM code is split all over the driver)
                      Modesetting includes output control. Output control includes HDCP, Macrovision, and a bunch of other things that prefer the dark.

                      Comment

                      Working...
                      X