Announcement

Collapse
No announcement yet.

Catalyst 9.2 Released, Still Fails To Deliver XvBA

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

  • #61
    Originally posted by Moronix View Post
    What a load of bollocks. It would be perfectly sufficient to release a single driver that runs all the capabilities of the card and the feature software that existed at it's release, this that you propose Nvidia has done for a long time already. This is not something that has been done ever in fglrx. So don't try to blame the users for having bought them at one point. They're not the ones who implied a fully working driver would exist either.

    Did you even read or are just randomly venting?

    Comment


    • #62
      Originally posted by bridgman View Post
      <snip>
      Realistically, I think the open source drivers will probably become that "simpler option" for older/weaker cards running under a compositor.
      <snip>
      Yep, I hope so. And that's not a bad solution at all, considering that documentation is available and progress seems to be good.

      Comment


      • #63
        Originally posted by elsie View Post
        Has anyone else experienced X crashing/system freezes with XV video playback?
        Crashes computer everytime I go fullscreen.
        Same here... hard crash when I take an XV video to fullscreen.

        Comment


        • #64
          I'm getting a hard crash when turning compiz off... Usually I do this to start up a game, so it is quite a PITA right now.

          Comment


          • #65
            rotarychainsaw, if you "unredirect fullscreen windows" in the Compiz options then run your game fullscreen *without* stopping Compiz do you still get the crash ?

            Comment


            • #66
              No I can run the games with compiz on, its just that I have noticed that I usually take a FPS hit (which shouldn't happen I would think). Also issues with compiz and fullscreen windows when a notification bubble pops up and stuff like that.

              Comment


              • #67
                Originally posted by rotarychainsaw View Post
                I'm getting a hard crash when turning compiz off... Usually I do this to start up a game, so it is quite a PITA right now.
                I'm getting that as well though not 100% of the time but close to.
                Also happens when I want to drop back to a VT or switch to one, again not 100% but close to.

                Comment


                • #68
                  Originally posted by storma View Post
                  The FPS increase is unreliable, at times it will drop from 80 to 15 for no obvious reason.
                  It seems this occurs from enabling AA ingame, turning AA off, things have smoothed out again.

                  Comment


                  • #69
                    Originally posted by elsie View Post
                    Has anyone else experienced X crashing/system freezes with XV video playback?
                    Crashes computer everytime I go fullscreen. This happened to me on 9.1 and 9.2.
                    Doesn't make a difference if compiz is enabled, either way computer crashes every time I play a video.
                    I'm using ubuntu 8.04 and x1600 mobile.
                    I also get hard crashes when watching a fullscreen vid, but only when compiz is enabled though. In this regard, the recent improvements haven't really really improved anything for me at all: when I was using fglrx 8.10, videoplayback would flicker when using compiz, so I would turn it off then too. The main difference is that it didn't used to lock up, so right now, one mistake (forgetting to turn off compiz when watching a video) and it's off to rebootland...
                    I'm using a Radeon HD4870 with 1 GB of GDDR5 on Ubuntu Intrepid AMD64 here.


                    I'm also wondering (q for the AMD devvers): once Gallium3D goes stable in Mesa, will fglrx be switching to support it (and DRI2, etc etc) instead of the old driver arch? and if so, what time do you guys see youselves involving yourselves with it?

                    Comment


                    • #70
                      JeanPaul145, same question; do you have "unredirect fullscreen windows" checked ? Could you try both settings (checked, unchecked) ?

                      We moved our OpenGL driver onto an architecture similar to Gallium3D a couple of years ago (based around our proprietary IL rather than TGSI), so no plans to change there.

                      On the open source side we plan to jump across to Gallium3D pretty soon, but we want to get the "classic mesa" implementation running at 5xx level first. That code will be needed for distros which aren't running with DRI2, KMS and GEM; KMS is coming along well but it will be at least a year before all the major distros move over to use it.

                      We could implement a Gallium3D-based Mesa that didn`t need DRI2 and GEM, of course, but nobody seems to think that would be a good use of time.
                      Last edited by bridgman; 02-21-2009, 11:31 PM.

                      Comment


                      • #71
                        Originally posted by Moronix View Post
                        There is Xv flicker without composite on older cards. It's unusual and happens with cpu spikes more. Xv implementation is extremely wobbly on that hardware. In fact, with composite on said cards, Xv won't even show so it's moot.
                        Xv should be flicker-free and tear-free with radeon these days. I`m hoping you`re talking about fglrx re: flicker...

                        Originally posted by Moronix View Post
                        I'm talking about things like the older Xpress series which worse yet doesn't seem like radeonhd will support properly.
                        It`s not a matter of `supporting it properly`, there are no plans to support pre-5xx in radeonhd at all. The modesetting hardware is completely different on the older chips, and nobody sees any benefit to porting the pre-5xx modesetting and acceleration code across from radeon.

                        Comment


                        • #72
                          Originally posted by bridgman View Post
                          JeanPaul145, same question; do you have "unredirect fullscreen windows" checked ? Could you try both settings (checked, unchecked) ?

                          We moved fglrx to a driver model like Gallium3D a couple of years ago, so no plans to change there. On the open source side we plan to jump across to Gallium3D pretty soon; we want to get the "classic mesa" implementation running at 5xx level first, for the distros which aren't running with DRI2, KMS and GEM.

                          We could make a version of Gallium3D which doesn't need DRI2 and GEM, but that doesn't seem like a good use of time.
                          Well right now I've found that the "undirect fullscreen windows" checkbox in the compiz manager is set to enabled (before changing anything), so that's problematic for sure. I'll try it with the check disabled and edit this post then.

                          EDIT: watching a video with the "undirect fullscreen windows" checkbox disabled SEEMS to go without lockups.
                          I haven't had any so far anyway
                          Could you give me an explanation why this is?
                          (curiousity killed the cat, but I'm just so very catlike in this regard :P)
                          Last edited by JeanPaul145; 02-21-2009, 11:15 PM. Reason: extra info

                          Comment


                          • #73
                            I can never remember whether checked or unchecked is what changes the behavior, so I can`t give you a full answer yet.

                            Normally when running under a compositing manager the Composite extension is used which allows the output of the application to be redirected to an offscreen buffer, then Compiz combines all those offscreen buffers into a single desktop image.

                            The checkbox allows you to alter that behaviour when an app is running full screen (which would block all the other apps anyways) -- rather than drawing to an offscreen buffer the app is allowed to draw directly to the screen.

                            The crash could be happening when the window switches from being redirected to *not* being redirected, or it could be crashing when the app switches to fullscreen *while* redirected -- in order to know which I need to remember which checkbox setting really unredirects

                            Since there was also at least one report about crashing when exiting Compiz I suspect there might be a problem with unredirecting, ie telling the app "stop drawing to an offscreen buffer and start drawing directly to the screen again".
                            Last edited by bridgman; 02-22-2009, 12:31 AM.

                            Comment


                            • #74
                              Hm, since many people complain about xv, why don't you use radeon? It's as bridgman said, flicker- and tearfree, and it's a joy to watch 1080p videos with it (on an onboard HD3200, which isn't the fastest GPU on earth). The driver's also in my experience _very_ stable to use, even though it's still marked as experimental. Never hangs, no corruption, everything's fast. At least, it's more stable for me than Catalyst ever was.

                              I use XFCE, and it works flawlessly even with compositing enabled (I haven't checked if performance suffers, but the picture still looks awesome). No idea about Compiz.

                              So if you mainly watch video, there's a very good alternative with the FOSS drivers.

                              There are some helpful instructions how to compile and use both FOSS drivers at:

                              http://xorg.freedesktop.org/wiki/rad...xx_r7xx_branch
                              http://xorg.freedesktop.org/wiki/rad...xx_r7xx_branch

                              Now I understand if people had reasons to complain previously when Catalyst was the only option and they were more or less _forced_ to use it to watch HD video, and even then tearfree only over opengl, which is very CPU-intensive and quite beats the point. But cut ATI/AMD some slack here for their hard work, the FOSS drivers are already _now_ great and they're improving at a tremendous rate. There's no doubt at all that AMD is the future of graphics on GNU/Linux.

                              Comment


                              • #75
                                Originally posted by susikala View Post
                                Hm, since many people complain about xv, why don't you use radeon? It's as bridgman said, flicker- and tearfree, and it's a joy to watch 1080p videos with it (on an onboard HD3200, which isn't the fastest GPU on earth). The driver's also in my experience _very_ stable to use, even though it's still marked as experimental. Never hangs, no corruption, everything's fast. At least, it's more stable for me than Catalyst ever was.

                                I use XFCE, and it works flawlessly even with compositing enabled (I haven't checked if performance suffers, but the picture still looks awesome). No idea about Compiz.

                                So if you mainly watch video, there's a very good alternative with the FOSS drivers.

                                There are some helpful instructions how to compile and use both FOSS drivers at:

                                http://xorg.freedesktop.org/wiki/rad...xx_r7xx_branch
                                http://xorg.freedesktop.org/wiki/rad...xx_r7xx_branch

                                Now I understand if people had reasons to complain previously when Catalyst was the only option and they were more or less _forced_ to use it to watch HD video, and even then tearfree only over opengl, which is very CPU-intensive and quite beats the point. But cut ATI/AMD some slack here for their hard work, the FOSS drivers are already _now_ great and they're improving at a tremendous rate. There's no doubt at all that AMD is the future of graphics on GNU/Linux.

                                So what kind of CPU do you have? Becouse it is nothing to do with XV, there is no acceleration for hd content on amd/ati side neither on fglrx nor foss drivers. It is completely CPU related to play hd videos. So I can't play 1080p videos on my x2 4000+ CPU without frame drops. So if you don't have a fast enough CPU you can't play any hd content both on fglrx and radeon/radeonhd drivers.

                                Comment

                                Working...
                                X