Announcement

Collapse
No announcement yet.

AMD Catalyst 12.11 Beta 11 Released For Linux

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

  • #16
    Originally posted by sfievet View Post
    I second your remark as I suffer from the exact same problem.
    Chris Wilson said : "There is nothing I can do about this since fglrx plays tricks with the intel hardware without knowledge of the driver."
    AMD didn't reply at all. Sad situation, because it seems to affect quite a lot of people...
    Seb.
    They just don't care. Once we've paid our money, AMD isn't interested in us. Sad but true. fglrx+intel compatibility has been broken for me since catalyst 11.8.
    There is at least 3 bug reports in AMD's unofficial bugzilla.

    So every time they release new driver, I spend the whole day on trying to find working combination of Mesa and intel driver.
    Sometimes I even have some kernel oops.

    Is there any catalyst developer around?
    Or can Bridgman tell what to do in that situation? The bug reports are there, but no reaction, no release notes.

    Comment


    • #17
      I didn't think we supported switchable graphics under Linux; we've always told OEMs to include a BIOS switch for "discrete" or "integrated". On muxless systems the choice is usually "switchable" or "whichever GPU has the display connectors, usually integrated".

      I'll ask to see if anything has changed but AFAIK "true" switchable graphics was always "windows only". I think we default to integrated only on AMD+AMD muxless and rely on the BIOS switch for AMD+Intel muxless.
      Last edited by bridgman; 12-06-2012, 10:03 PM.

      Comment


      • #18
        In this beta 11 Catalyst 12.11 in my Mageia 2 x64 the web brower Google Chrome 23 work good on Flash In the other driver is still laggy. In now I don't must use prefix "--blacklist-accelerated-compositing"

        Comment


        • #19
          Originally posted by bridgman View Post
          I didn't think we supported switchable graphics under Linux; we've always told OEMs to include a BIOS switch for "discrete" or "integrated". On muxless systems the choice is usually "switchable" or "whichever GPU has the display connectors, usually integrated".

          I'll ask to see if anything has changed but AFAIK "true" switchable graphics was always "windows only". I think we default to integrated only on AMD+AMD muxless and rely on the BIOS switch for AMD+Intel muxless.
          In essence, AMD does support Enduro under linux, link :
          AMD Enduro™ technology requires either an AMD “A” series or “E” series APU or an Intel processor, plus an AMD Radeon™ HD 7000M series discrete graphics configuration and is available on Windows® 7 Professional, Windows® 7 Ultimate, Windows® 7 Home Premium, and/or Windows® 7 Home Basic OS. Linux OS supports manual switching which requires restart of X-Server to switch between graphics solutions. Not all AMD Radeon™ HD 7000M series GPU features and capabilities may be supported on all AMD Enduro™ technology-enabled components or systems – always check with your component or system manufacturer for specific mode capabilities and supported technologies
          I wouldn't blame AMD if the company didn't state it and didn't really support. In that case I wouldn't just buy a laptop with AMD video card. But in a case when you state something and don't do it...

          Also the way fglrx works with intel driver is somewhat ugly. There are some scripts which change links to libgl.so and driver. Some changes in Mesa or in intel break compatibility with driver.
          As far as I know there were at least two such changes in the past: the change withing intel driver and rename of Mesa's libgl.so.1.2 to libgl.so.1.2.0.
          That's why we (owners of laptops with switchable graphics) must know the compatibility between fglrx versions and the rest of graphics stack (intel driver, Mesa, X server, kernel etc).
          I think even bumblebee's way is better. I'm just curious, why didn't fglrx folks support switchable graphics withing bumblebee or primus?

          PS.
          Bridgman, I don't blame on you. You've been doing great work, I just don't understand why such a big company isn't responsible for its own words.
          Could you tell us where can we find the information about plans of AMD to support switchable graphics?

          Comment


          • #20
            Interesting, looks like fglrx is starting to pick up support. I'm pretty far away from that these days (focusing on HSA) but it's good to see. Not sure if we're saying "here are the combinations of distro & intel driver we tested with, start with one of those if you have problems" but that seems like something which would help.

            Comment


            • #21
              Originally posted by bridgman View Post
              Not sure if we're saying "here are the combinations of distro & intel driver we tested with, start with one of those if you have problems" but that seems like something which would help.
              Unfortunately, AMD doesn't provide this information. And you're right, it should, because now the only way to find working combination is trial and error method!

              I think, more important is that the way fglrx works now doesn't allow independent developers to make something like bumblebee, because fglrx works directly with intel driver by means of dirty hacks (not surprising that why Chris Wilson doesn't want to do anything with intel driver in order to keep compatibility with fglrx).
              For example, even if I don't use discrete card, fglrx is still loaded. That's why if something is wrong with it, I can't even use intel driver. (Usually it means segfault of Xserver).
              And finally, there is no other choice for >=HD77XXM users since radeonsi isn't mature enough.

              Comment


              • #22
                Originally posted by Rakot View Post
                I think, more important is that the way fglrx works now doesn't allow independent developers to make something like bumblebee, because fglrx works directly with intel driver by means of dirty hacks (not surprising that why Chris Wilson doesn't want to do anything with intel driver in order to keep compatibility with fglrx).
                Are you talking about a specific change to fglrx, or just "making it all open source" ?

                There might be a disconnect here -- I know we worked closely with Intel on making all this work. Maybe that didn't happen for Linux ?

                Comment


                • #23
                  Originally posted by bridgman View Post
                  Are you talking about a specific change to fglrx, or just "making it all open source" ?
                  I just want it to work. I understand why AMD cannot open it and I'm not blaming on it since the company already has put a lot of effort in radeon development. What I don't understand is what is preventing to publish release notes and software compatibility list?! AMD did it before but for some reasons stopped doing so some time ago. Did you guys just fire the last person doing it?

                  There might be a disconnect here -- I know we worked closely with Intel on making all this work. Maybe that didn't happen for Linux ?
                  I don't know. According to Chris Wilson's reaction not really.

                  Is there any catalyst developer in the forum?
                  There a lot of questions I'd like to ask: when will driver be fixed, is there any plans to make seamless support (bumblebee, primus or DMA-BUF) etc.
                  How can I and other people ask these and other questions to catalyst developers? Bug tracker at this point doesn't work (a lot of open bugs without even responses).

                  Anyway thank you for your responses.

                  Comment


                  • #24
                    Originally posted by Rakot View Post
                    How can I and other people ask these and other questions to catalyst developers? Bug tracker at this point doesn't work (a lot of open bugs without even responses).
                    The Catalyst developers do respond on the bug tracker as time permits, but when the answer is just "yeah, we know, it's on the list but we don't know when we'll be able to get to it" or "there isn't anything like enough information here for me to quickly reproduce the problem" I think they would rather spend time working on the driver instead. Don't think there are any Catalyst developers on the forums...

                    Comment


                    • #25
                      Originally posted by Rakot View Post
                      Unfortunately, AMD doesn't provide this information.
                      Known working combination for Enduro is Ubuntu 12.04 and Catalyst 12.10 (and probably Catalyst 12.11).

                      Comment

                      Working...
                      X