Announcement

Collapse
No announcement yet.

AMD Catalyst 9.11 For Linux Released

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

  • #31
    Originally posted by chaos386 View Post
    I can't get Xv to work at all on my 5850, so consider yourself lucky...

    xvinfo shows "ATI Radeon AVIVO Video" with 4 ports, and gstreamer-properties can do the Xv test playback *once*, but if I try to watch a video in totem, MPlayer or VLC with xv, the video is all black, and then when I try the test playback in gstreamer-settings after this, it's black too.
    You mean like this?
    Code:
    X-Video Extension version 2.2
    screen #0
      Adaptor #0: "ATI Radeon AVIVO Video"
        number of ports: 4
        port base: 131
        operations supported: PutImage 
        supported visuals:
          depth 24, visualID 0x23
          depth 24, visualID 0x24
          depth 24, visualID 0x25
    <snip>
    [EDIT]oops forgot to use code tags instead of quote...[/EDIT]

    I'll try playing a video using Xv, not sure what I've got it set to ATM but it's working fine although I don't watch very many videos.

    4850 Mobility Radeon (512MB)

    9.11 installed fine for me, Ubuntu 9.10 x86-64 although I've not really tested anything yet and will likely not bother trying compiz/beryl again as I find it to be more annoying than not, or at least with the last few releases...

    [EDIT]
    Hmmm... just went and checked mplayer, and it was already set to use Xv and has been working fine for me. Even "fullscreen" seemed to work ok, but I'll try some of the other options too I guess...

    minor update, mplayer is being a little flakey, so apparently I need to ensure that there are not a few things left over from 9.04, plus I was also using the medibuntu packages...
    [/EDIT]
    Last edited by cutterjohn; 11-20-2009, 10:40 AM.

    Comment


    • #32
      Originally posted by cutterjohn View Post
      You mean like this?
      Yup, exactly like that. Here's a pastebin of the whole output for anyone curious. I'm running Catalyst 9.11 on 32-bit Ubuntu 9.10, but I had the same problem with the 9.10 beta included with Ubuntu and the drivers for use with the Stream SDK 2.0 beta4.

      Comment


      • #33
        Just to add in something semi-trivial, that appearance of black rectangle corruption seems to be gone now, and now that I think of it may have been an X.org bug(or some layer thereof) exposed as IIRC it disappeared when I switched to Ubuntu 9.10.

        I went back and checked over my installation, and it's "clean" barring what I installed locally, so that mplayer flakiness must be OOB, but it only seems to occur when I'm interacting with the UI, e.g. mucking around in the prefs while playing videos it doesn't crash, or at least it hasn't on me but I don't watch many or long videos, or I skip through them. (Mainly looking to see some particular effect or other, or a piece of info from something that's only in video.)

        [EDIT]
        I'd been earlier using the official catalyst 9.10 release rather than the earlier drop provided for Ubuntu since I was upgrading from a previously installed system... plus last I messed with Ubuntu's fscked way of installing proprietary drivers it was a nightmare to get rid of them, or at least much more work than it should've been...

        catalyst 9.10 also played video back fine for me, and must've been already set to Xv for mplayer, which is what I prefer to use.

        [EDIT2] better put in catalyst before 9.10 so as not to accidentally confuse it with Ubuntu 9.10 ... [/EDIT2]
        [/EDIT]
        Last edited by cutterjohn; 11-20-2009, 10:44 AM.

        Comment


        • #34
          I have a question, mostly for the devs.

          How much effort is putting into developing and stabilizing new opengl extensions? Well actually I'm satisfied with fglrx, but I have the impression that the more advanced opengl features is in a bad shape.

          Right now there isn't any advanced opengl app in linux, besides maybe unigine and wine trying running advanced games. I just tried using fglrx with wine and I got a lot of games up and running. But some games, which should run ok cf. winehq.org, doesn't work / are slow or have graphic artifacts.

          Well I went in #winehq asking why fglrx didn't like wine or vice-versa. A wine direct3d developer said, that fglrx still have a lot of bugs in the more advanced opengl areas. But it should actually support wine as good as nvidia, but the support is just buggy. He told me that the more advanced windows apps makes wine trying to call advanced opengl code-paths. Those advance code path is very buggy on fglrx still. Though he noted that the fglrx driver has improved very much lately.

          So will there be more in stabilizing and optimizing the opengl stack?
          Last edited by tball; 11-20-2009, 02:01 PM.

          Comment


          • #35
            I don't remember seeing any OpenGL bug reports filed against newer extensions recently so not sure what the specific issues might be (which makes it hard to *fix* them)...

            ... but "yes the OpenGL support will continue to improve". Most of the 3D stack is shared across multiple OSes, so fixes made for one OS will usually benefit the other OSes.
            Last edited by bridgman; 11-20-2009, 02:38 PM.

            Comment


            • #36
              @bridgman

              Got it.
              Will you care of bugs with a lot of wine fixme's and console spawn?
              Or is there a specific way to get debugging informations?

              Comment


              • #37
                Well you need at least a nv gpu to crosscheck it is a fglrx problem

                Comment


                • #38
                  Originally posted by tball View Post
                  @bridgman

                  Got it.
                  Will you care of bugs with a lot of wine fixme's and console spawn?
                  Or is there a specific way to get debugging informations?
                  Most of the improvements have come when the Wine devs take the problem from "Windows app ABC does something bad" to "we expect this OpenGL call to do X but it actually does Y" -- then we either respond with "calling that way has undefined results in the OpenGL spec, but if you called <this> way it would work on everyones HW" or "that's not right, we'll fix it".

                  Comment


                  • #39
                    can someone help me here, i got 9.10 and well got all working not stable ofc but manageable. but with 9.11 well kde4 composite is broken (wierd ja )but the black texture corruption is gone in 2d it seems for now.

                    here is my pctested with default clocks too ofc and with windows 7 x64. is not a hardware issue)
                    athlon x4 620 cache unlocked @ 3.7ghz
                    mobo msi gd-70 ht @ 2.250 ghz
                    Radeon hd 4850x2 x 2 aka quadfire (tried with 1 card too ofc)
                    kubuntu 9.10 x64 fresh install + update + nothing custom or ppa all is distro repos

                    so the thousand dollars question how the [email protected][email protected][email protected] i debug or fix it??

                    and plz focus more devs in oss driver to get at least the same lvl of 3d than intel driver, so i can switch and lets this nigthmare behind, i dont wanna be rude but when you have to actually works with a pc. this erratic behaviour is a liver killer, lol 9.9 xv broken + hard lockups. 9.10 3d semi stable, 2d really corrupted but composite fixed it, 9.11 2d no corruption 3d broken. really some QA wont harm anyone, ok maybe is my fault for do the crazy stuff of buying an X2 card and it works fine in x1 cards, i can live with that cuz 1 4850 is powerful enough to work but in that case at least force disable the second chip by default and enabled it only when someone actually tested it in next releases. for now ill try google, disable all that aticonfig let me, and ofc gdb my 3d apps once again to try to trace where is the broken stuff, and make a script that do this automatic so less trauma every "release"

                    UPDATE:
                    after more testing and disabled everything i could, well stream is broken, flash is broken(especially 10.1 using stream but ok is beta but well in nvidia/intel works just fine)(flash suddenly stop rendering and hang the browser but the audio keeps playing), crossfire is broken aka every 3d app using crossfire after few mins black screen then deathlock, i suspect kernel panic but well i cant see it cuz everything including keyboards just dies, composite like i said before keep broken even without crossfire, xv have less tearing but compared to nvidia/intel is very noticeable (maybe im just too picky here, not the big deal), 2d works fine for first time since i remember, wine is ***working*** first time since i remember but ofc it hangs few mins later if i dare to activate crossfire, so no hardcore games in wine for now
                    Last edited by jrch2k8; 11-23-2009, 12:47 AM.

                    Comment


                    • #40
                      Originally posted by bridgman View Post
                      Most of the improvements have come when the Wine devs take the problem from "Windows app ABC does something bad" to "we expect this OpenGL call to do X but it actually does Y" -- then we either respond with "calling that way has undefined results in the OpenGL spec, but if you called <this> way it would work on everyones HW" or "that's not right, we'll fix it".
                      Extending John's comments somewhat.

                      Most wine devs use NV. So the open-to-interpretation parts of the spec opt for the NV behaviour. This paired with DX to OGL being a black art itself results in something akin to...

                      wine+game have an affinity to NV. It might be that the game doesn't work under ATI, but that is most likely that it has never been tested against ATI by a dev, so the NV behaviour becomes the defacto path for wine. People hold then look at the NV+wine pairing as working perfectly, and ati+wine as being broken. The only variable changing is the vendor, so it is possibly a valid (albiet vastly simplified, nearly naive) assumption to make.

                      The reality is that the NV bugs and the wine bugs become mutually compatible and fit together nicely. The ATI bugs and the wine bugs simply don't play nicely together. A wine bug may be present because of a behaviour with NV, where without that behaviour wine is actually misbehaving and the ATI driver is actually correct.

                      This doesn't make the pairing any easier to handle, nv+wine just works better. But until the wine devs have a representative mix of hw to the market, it will be a slow, painful path to stability.

                      Matt

                      Comment

                      Working...
                      X