Announcement

Collapse
No announcement yet.

Catalyst 9.8 - "compiz default maximize" = effect significant lag

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

  • Catalyst 9.8 - "compiz default maximize" = effect significant lag

    Does anyone else experience a HUGE lag/stutter when you maximize a window with compiz enabled? Other effects such as "wobbly windows" is rendered without problems. But the 'maxmize/unmaximize" effect is terribly laggy.

    Config:
    Ubuntu 9.04
    01:00.0 VGA compatible controller: ATI Technologies Inc RV770 [Radeon HD 4870]
    Linux fermmy 2.6.28-15-server #49-Ubuntu SMP Tue Aug 18 19:30:06 UTC 2009 i686 GNU/Linux
    Latest Catalyst 9.8 fglrx driver:
    fglrx-amdcccle_8.640-0ubuntu1_i386.deb
    fglrx-kernel-source_8.640-0ubuntu1_i386.deb
    fglrx-modaliases_8.640-0ubuntu1_i386.deb
    libamdxvba1_8.640-0ubuntu1_i386.deb
    xorg-driver-fglrx_8.640-0ubuntu1_i386.deb

  • #2
    Yes, everyone has that. It's an old problem. And there's no work-around other that patching xorg with 107_fedora_dont_backfill_bg_none.patch (which will result in some temporary screen garbage while opening and maximizing windows/menus/lists/etc.

    Comment


    • #3
      Oh I see. Good to know.

      So what is the problem then? A bug in X (which we need to wait to be fixed and come downstream to Ubuntu), or a bug in fglrx (which we need to wait for ATI to fix).

      Comment


      • #4
        By RealNC's answer it sounds like the real answer is "developers don't yet know where the real problem is". You can't fix what you cannot understand.

        Comment


        • #5
          Interesting. Well, I can confirm that the problem does not exist with the open source radeon driver ... so that might narrow it down to a problem with fglrx, (maybe). heh

          Comment


          • #6
            fglrx doesn't seem to accelerate something in X that assumes the driver offers EXA support (fglrx uses the old XAA acceleration). If you take the open drivers and switch to XAA, you will have the same problem.

            Comment


            • #7
              So is there a bug report submitted to XServer, or should we expect a workaround from fglrx?

              Comment


              • #8
                I've no idea what the situation is. There was a lot of "ping-pong" the last time I looked it up (X saying it's the driver's problem, Ubuntu saying it's an X problem, ATI saying they have no idea and don't really care go patch your X since they don't really support upstream X...)

                It isn't pretty

                Comment


                • #9
                  Originally posted by RealNC View Post
                  I've no idea what the situation is. There was a lot of "ping-pong" the last time I looked it up (X saying it's the driver's problem, Ubuntu saying it's an X problem, ATI saying they have no idea and don't really care go patch your X since they don't really support upstream X...)

                  It isn't pretty
                  they care about in catalyst 9.10 ... but yes ubuntu 9.10 is still broken.

                  i mean broken in meaning of broken...

                  Comment


                  • #10
                    the problem is known. But ati devs say it's X fault, X devs say it is ati's fault.

                    Interessting tidbit: nvidia has/had the same problem, also by that change that is reversed with the patch. And this change was introduced to make intel less horrible. Most X devs have something to do with Intel.

                    You can think about that for a moment.

                    Comment


                    • #11
                      Originally posted by energyman View Post
                      the problem is known. But ati devs say it's X fault, X devs say it is ati's fault.

                      Interessting tidbit: nvidia has/had the same problem, also by that change that is reversed with the patch. And this change was introduced to make intel less horrible. Most X devs have something to do with Intel.

                      You can think about that for a moment.
                      Interesting tidbit: nvidia drivers seem to do something similar to the "no backfill" patch, where some windows show garbage for a split second when maximized.

                      Fglrx without "no backfill" = no garbage but slow maximization
                      Fglrx with "no backfill" = garbage for a split second but fast maximization
                      Nvidia without "no backfill" = garbage for a split secont but fast maximization

                      I see behavior this on both a Quadro NVS135M (190.xx drivers) and a 9500GT (185.xx drivers). Obviously, I cannot be 100% certain, but it seems that nvidia drivers have some kind of hack for the slow maximization issue.

                      Comment


                      • #12
                        Man I just can't wrap my mind that fglrx really,STILL,uses XAA acceleration for their driver.
                        Are they gonna update that in future releases or are we have to wait for that like it was with aiglx,and what the hell were they thinking with XAA !?

                        Comment


                        • #13
                          Originally posted by BlackStar View Post
                          Interesting tidbit: nvidia drivers seem to do something similar to the "no backfill" patch, where some windows show garbage for a split second when maximized.

                          Fglrx without "no backfill" = no garbage but slow maximization
                          Fglrx with "no backfill" = garbage for a split second but fast maximization
                          Nvidia without "no backfill" = garbage for a split secont but fast maximization

                          I see behavior this on both a Quadro NVS135M (190.xx drivers) and a 9500GT (185.xx drivers). Obviously, I cannot be 100% certain, but it seems that nvidia drivers have some kind of hack for the slow maximization issue.
                          nvidia just replace a lot of X infrastructure in their drivers

                          Comment


                          • #14
                            Originally posted by kUrb1a View Post
                            Man I just can't wrap my mind that fglrx really,STILL,uses XAA acceleration for their driver.
                            Are they gonna update that in future releases or are we have to wait for that like it was with aiglx,and what the hell were they thinking with XAA !?
                            well? it works? it is proven and stable? workstation customers prefer stable over the lastest cool and unproven buzz word of the moment?

                            seriously, if you did not look into xorg.0.log you would not know the difference.

                            Comment


                            • #15
                              I guess you are wright.It's just that with every release(new and old ones) i have to to read long posts in forums how fglrx driver is bad and how ati just doesn't give a damn and to hear now that drive uses XAA over EXA and that might be the reason for the problem since i installed my first Linux Distro just makes me angry right now but i guess ati knows better than me,...sooo,...keep up the good work ati.

                              Comment

                              Working...
                              X