Announcement

Collapse
No announcement yet.

ATI Radeon Driver Re-Write Still Has Work Left

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

  • #16
    Originally posted by bridgman View Post
    As I understand it, the patch was removed because on certain GPUs (not ours AFAIK) it resulted in on-screen corruption which sometimes brought back older screen info. This was treated as a security issue and so the patch was pulled. ...

    It's funny that this is exactly what happens now with fglrx . Oh well, this sort of stuff always happens; fix something to break something else. Just hope it eventually gets resolved.

    Comment


    • #17
      Yeah, some days you're the hydrant

      It happens; the problem that it fixed on other GPUs was felt to be more severe than the problem it introduced on our GPUs, so...

      Comment


      • #18
        Originally posted by bridgman View Post

        Alex added some power savings features to the radeon driver a month or so ago. I think you want "ForceLowPowerMode" but check the radeon man page to be sure.

        I'm not having a sensor directly on my 4850 but I believe those poewr-saving features do a good job already

        currently I'm using
        Code:
                Option     "ForceLowPowerMode"  "True"
                Option     "DynamicPM"          "True"
                Option     "ClockGating"        "True"
        great job guys !

        Comment


        • #19
          My thinkpad T42 has this card:

          Code:
          01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
          Would this benefit from the radeon rewrite?

          EDIT: Would the new TTM and/or mesa be of benefit for this one?
          Last edited by DeepDayze; 06-15-2009, 09:47 AM.

          Comment


          • #20
            Originally posted by mattst88 View Post
            Why? TTM (and before that, KMS) are requirements for getting any improvements out of this new code.

            Surely since you run this site you're aware of that -- so why did you not use TTM? If that's for another article, why not state it? It makes this article look half-baked.
            Originally posted by damentz View Post
            Mesa 7.6 benchmarks are meaningless without TTM. Not to mention, there should be more bugs without it since that's what all the new code is for.

            I'm appalled that these tests were even done. It's like taste testing two different bags of tea, seeped into iced water.
            It makes perfectly sense to test the new mesa even with a current (non-TTM) kernel. The radeon-rewrite had several goals, other than making a radeon mesa capable of using TTM, the code was also reworked to be better shared among all radeon cards, and for both DRI and DRI2. This meant rewriting also the old non-TTM path (DRI1 and not DRI2).

            The new code is meant to work as well as the old code did, and has now replaced the old code in mesa. It will be used by normal users as soon as mesa 7.6 is released, and until the default kernel uses TTM (2.6.31 or later) it will be the default mesa stack. So finding regressions in the rewritten DRI1 code is definitely important, and it is good that Phoronix looks into this. Many developers are focusing on the DRI2 path and are not giving so much attention to the old path since it "soon" will not be of use any longer. The radeon-rewrite got merged even with many known regressions (search for radeon-rewrite on bugs.freedesktop.org), but hopefully they will be fixed quickly now that this is in the main (master) branch.

            Comment


            • #21
              Yep... the thing to remember is that the goal of radeon-rewrite is to be able to use a single code base for both TTM and non-TTM systems, since both of them will need to be fully supported over the next year or two. On a non-TTM system, radeon-rewrite is supposed to be "no worse, and easier to maintain in the future", while on a TTM system it should provide a good base for adding new features (eg the VBO and OQ work already in progress).

              Between non-TTM and TTM, testing on non-TTM systems is definitely the most time-critical since all future Mesa releases will be using this code base and any problems translate directly into regressions for current users.

              Michael's testing confirmed that there is more work to do before the next Mesa release. This was understood by the devs before the merge, but the consensus was that it made more sense to merge now and get more people testing the code than to try and "make the code perfect in a branch" and drop it into master at the last minute.
              Last edited by bridgman; 06-15-2009, 01:05 PM.

              Comment


              • #22
                So, say I have an Ubuntu 9.10 Karmic alpha install (kept updated), a Radeon 4670 (on an RS690/X1250 board, so I could test that, too)... would that be a non-TTM system? Would I be able to help with the testing?

                Comment


                • #23
                  Ubuntu 9.10 is a non-TTM system. TTM is in the process of being merged into the 2.6.31 kernel, but that hasn't gone through yet and Ubuntu 9.10 uses the 2.6.30 kernel.

                  Still, it might be useful to try it out and see if there are regressions or if there are any improvements. It might help the devs find problems with non-TTM systems.

                  Comment


                  • #24
                    Note that neither radeon-rewrite nor mesa master include support for 6xx-7xx GPUs (6xx-7xx is in the 6xx-rewrite branch) so for now you'll need to test with a display connected to the RS690.

                    Comment


                    • #25
                      Originally posted by Pitabred View Post
                      So, say I have an Ubuntu 9.10 Karmic alpha install (kept updated), a Radeon 4670 (on an RS690/X1250 board, so I could test that, too)... would that be a non-TTM system? Would I be able to help with the testing?
                      Yes, Karmic is (still) a non-TTM system. But please see http://phoronix.com/forums/showthread.php?t=17615 about testing out TTM/KMS on it

                      Ubuntu 9.10 will probably have 2.6.31, and it is not certain that 2.6.31 will have the radeon KMS. However, it is possible that Ubuntu 9.10 will patch the kernel for it if the bits get stable enough in time.

                      Comment


                      • #26
                        Well, I thought enough time had passed and chose an asus mobo with ati 3300 HD onboard (1080p capable said the box). It sucks. Admittedly, it does work, but not well enough for 1080p. So after a couple reconfiguration attempts, I sent a nastly letter to AMD and bought a passive nvidia 9600GT. glxgears showed ~1200fps for the ATI (using their fglrx drivers) and ~12000+fps for an nvidia 6800 GTS (also w. proprietary drivers). Good luck ATI, perhaps I'll revisit their stuff in another couple years.
                        Last edited by benow; 06-22-2009, 04:40 AM.

                        Comment


                        • #27
                          Originally posted by benow View Post
                          I sent a nastly letter to AMD
                          They've got you, you know where

                          But to be serious, I think that someone should add big warning banner like big warning sign on Phoronix home site, which would advertise user not to buy ATI shitty products.

                          Comment


                          • #28
                            Originally posted by tormod View Post
                            Yes, Karmic is (still) a non-TTM system. But please see http://phoronix.com/forums/showthread.php?t=17615 about testing out TTM/KMS on it

                            Ubuntu 9.10 will probably have 2.6.31, and it is not certain that 2.6.31 will have the radeon KMS. However, it is possible that Ubuntu 9.10 will patch the kernel for it if the bits get stable enough in time.
                            Pretty sure 2.6.31 is confirmed to have Radeon KMS in the Staging section. I highly, highly doubt that Ubuntu includes modules or has built in support for stuff in the Staging section though, so you'd probably have to compile the kernel yourself on Ubuntu.

                            Comment

                            Working...
                            X