Announcement

Collapse
No announcement yet.

Likely Radeon Gallium3D Regression On Linux 3.14 + Mesa 10.2

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

  • #16
    Originally posted by jonty789 View Post
    Hm I never seem to get any problem with hyperz so how would I enable it? I using the oibaf PPA.

    Change the flag to DBG_HYPERZ and reverse the logic
    so setting the flag enabled the feature. This disables
    hyperz on r600g and radeonsi by default. It can be
    enabled by setting the env var.

    Where can i apply the settings please?

    Thank you
    Code:
    env R600_DEBUG=hyperz your_app
    edit.
    too late

    Comment


    • #17
      Originally posted by _SXX_ View Post
      I think mostly everybody who actually play games with open source drivers use Oibaf PPA or other sources with fresh Mesa as well as latest kernel. Also as games I mean not only SuperTuxKart or OpenTTD.

      PS: I use those drivers from git for about a year and never get any serious glitch or GPU lockup because of that.
      Then, lucky you. I understand that people using AMD open source drivers have for a long time been used to running on the edge of only the latest versions of software, even from git, because of the huge backlog they had to clear until recently. For the several AMD boxen I happen to take care of, I did that myself, emerged recent versions, tested them, then handed over the system to its users if OK. However, between a non-bootable system, black screens, no X or simple graphics corruption, anything can happen. That's why, given the choice, you simply don't advertise this to regular users. And you are wrong if you think the majority is doing it.

      Comment


      • #18
        Originally posted by genstorm View Post
        Then, lucky you. I understand that people using AMD open source drivers have for a long time been used to running on the edge of only the latest versions of software, even from git, because of the huge backlog they had to clear until recently. For the several AMD boxen I happen to take care of, I did that myself, emerged recent versions, tested them, then handed over the system to its users if OK. However, between a non-bootable system, black screens, no X or simple graphics corruption, anything can happen. That's why, given the choice, you simply don't advertise this to regular users. And you are wrong if you think the majority is doing it.
        For that matter I anti-recommend Catalyst.

        Its more likely to get You into troubles. (And well. Clearing bad Mesa/kernel duo is as simple as using legacy kernel from Advanced options at boot time. Try that for Catalyst...)

        Comment


        • #19
          People have to report the regression first!

          Originally posted by genstorm View Post
          When they matter, e.g. in final versions, yes. Have YOU ever used software based on live sources? Regressions may happen on any commit, might be fixed in one of the following commits.
          The sooner a regression is reported, the sooner it can be fixed. Why *on Earth* should anyone wait for a "final" version to be released first, when that *by definition* is going to impact ordinary users?

          Thanks for noticing this, Michael.

          Comment


          • #20
            I beg to differ:

            Originally posted by chrisr View Post
            The sooner a regression is reported, the sooner it can be fixed.
            That's when you report it upstream as soon as you notice.

            Originally posted by chrisr View Post
            Why *on Earth* should anyone wait for a "final" version to be released first
            That's when you write an article about it.

            Remember when Michael bisected a regression in the kernel, then decided to _not_ disclose the bad commit until several days later?

            Comment


            • #21
              Originally posted by genstorm View Post
              However, between a non-bootable system, black screens, no X or simple graphics corruption, anything can happen.
              Looks like you talking about AMD Cataclysm.

              Originally posted by genstorm View Post
              That's why, given the choice, you simply don't advertise this to regular users. And you are wrong if you think the majority is doing it.
              Unfortunately AMD open source drivers isn't mature yet, so old "stable" drivers are usually more bugged than newer versions from git. If you want to run actual games that released on Steam with playable framerate have to use recent drivers stack.

              Stable version that included in popular distributions usually missing important functionality. As long as I remember Geometry shaders for R600 won't be merged into 14.04 so what regular user should do, wait for 14.10? Or install Catalyst?

              Comment


              • #22
                Ah i see thank you guys for your reply. Sorry i know i am noob lol but where do i put R600_DEBUG=hyperz in?

                Do i just paste it in terminal?

                Thank you guys

                Comment


                • #23
                  Originally posted by jonty789 View Post
                  Ah i see thank you guys for your reply. Sorry i know i am noob lol but where do i put R600_DEBUG=hyperz in?

                  Do i just paste it in terminal?

                  Thank you guys
                  either boot with it (for example with /etc/env.d/) or write it in front of the application (terminal: R600_DEBUG=hyperz glxgears). The second one you can even do on a per-game basis on steam, just modify the games startup options to something like R600_DEBUG=sb,nollvm,hyperz %command%

                  Comment


                  • #24
                    Originally posted by _SXX_ View Post
                    Looks like you talking about AMD Cataclysm.
                    I haven't used blobs in years. Maybe I'm following upstream git more closely than you, or what you get through the PPA (whatever that is ) are vaguely tested snapshots instead of the steaming hot deal from trunk, maybe you were really simply lucky thus far.

                    Originally posted by _SXX_ View Post
                    Stable version that included in popular distributions usually missing important functionality. As long as I remember Geometry shaders for R600 won't be merged into 14.04 so what regular user should do, wait for 14.10? Or install Catalyst?
                    I can not really give advice on binary distributions. I am sure there are PPAs (or whatever overlays/repositories are called on the various distros) with patched stable versions or at least snapshots, so you don't have to deal with the daily fallout that a git repository can bring.
                    Last edited by genstorm; 03-02-2014, 08:51 AM.

                    Comment


                    • #25
                      Michael, this is not completely from HyperZ and so still worth investigating. We have reports from Luke and dungeon on this forum that confirm there's another regression besides the intended hyperz change.

                      Luke specifically tested it, dungeon's case is media apps that do not use the Z buffer.

                      Comment


                      • #26
                        Originally posted by _SXX_ View Post
                        Unfortunately AMD open source drivers isn't mature yet, so old "stable" drivers are usually more bugged than newer versions from git. If you want to run actual games that released on Steam with playable framerate have to use recent drivers stack.
                        Not anymore. Well, in any case it depends on your hardware. But right now, all my AMD systems (each being older than 1yr) run perfect with stable upstream versions, that is kernel 3.13, mesa-10.0.3, x11-base/xorg-server-1.15.0, xf86-video-ati-7.3.0.

                        Comment


                        • #27
                          Originally posted by jonty789 View Post
                          Ah i see thank you guys for your reply. Sorry i know i am noob lol but where do i put R600_DEBUG=hyperz in?

                          Do i just paste it in terminal?

                          Thank you guys
                          Yup, in your terminal, right before application name.

                          Further reading: Ubuntu Community Help Wiki - Environment Variables

                          Comment


                          • #28
                            Originally posted by genstorm View Post
                            I haven't used blobs in years. Maybe I'm following upstream git more closely than you, or what you get through the PPA (whatever that is ) are vaguely tested snapshots instead of the steaming hot deal from trunk, maybe you were really simply lucky thus far.
                            I'm not saying that your opinion is wrong, for users that don't know how to deal with a console this may not be the best, but I too haven't head any problems with most recent mesa git in years and I build it on a regular basis (every 2-5 days). The only problems I got were build problems or performance regressions (so nothing that actually stopped working). But if it does not build in the first place you don't install it Usually there is a full piglit run before major changes get in, so there's a high chance that it will not break everything.

                            Comment


                            • #29
                              "Beg to differ" as much as you want.

                              Originally posted by genstorm View Post
                              That's when you write an article about it.
                              Personally speaking, I'm not arrogant enough to presume to try and tell someone what they can and can't write articles about on their own website. But the bottom line is that Michael chooses to assist with the development of the Open Source drivers, unlike many others who just sit back and complain.

                              Comment


                              • #30
                                Originally posted by droste View Post
                                I'm not saying that your opinion is wrong, for users that don't know how to deal with a console this may not be the best, but I too haven't head any problems with most recent mesa git in years and I build it on a regular basis (every 2-5 days). The only problems I got were build problems or performance regressions (so nothing that actually stopped working). But if it does not build in the first place you don't install it Usually there is a full piglit run before major changes get in, so there's a high chance that it will not break everything.
                                Hardware is a difficult beast; Regressions/problems may only happen (or become visible) on certain chips, or even revisions. That's why UVD works on most, but not on two systems of mine; that's why enabling DPM broke 1/3 of my AMD boxen in 3.12.0. In general, I have to agree that mesa git is doing fine most of the time, but you can never be sure. Anyway, everyone is free to use it; I just want to make sure it is not too widely advertised to regular users as they do not have the ability to cope with errors that might happen in their myriad of systems. It certainly isn't the go-to solution for newbie support threads.

                                Comment

                                Working...
                                X