Announcement

Collapse
No announcement yet.

Radeon VRAM Optimizations Coming, But Help Is Needed

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

  • #31
    GamingOnLinux has also covered this:
    http://www.gamingonlinux.com/article...rs-better.2938

    Comment


    • #32
      Nice. I think that covers all the sites with technical Linux audience interested in graphics, all two

      Comment


      • #33
        Originally posted by phoronix View Post
        Phoronix: Radeon VRAM Optimizations Coming, But Help Is Needed

        Got a workload that runs badly on the r600g Radeon Gallium3D driver? You can help fix it! Optimizations are coming to the open-source Radeon Linux driver for video memory usage...

        http://www.phoronix.com/vr.php?view=MTU2Nzk
        Hi, I have a laptop with a rv710and 512mb vram, so I guess it's the perfect candidate for you.
        I have however, one problem with it: the cpu cooling is far too weak. I use TurionPowerControl to enable C1E and htc at startup, if not (and this is a problem in recovery when bypassing sysinit) I can guarantee it ends in an mce followed by a kernel shutdown.
        But when it's jumping in and out of htc slowdown, won't the results of your research be severely affected by this malfunction? I don't want to post corrupt data

        Comment


        • #34
          I try to help however I have couple questions.

          At first I use Wsnipex MESA ppa as I mainly use XBMC and Oibaf's PPA not always worked with it.

          Question 1.
          Do I need to purge Wsnipex PPA before I execute

          sudo add-apt-repository ppaibaf/graphics-drivers
          sudo apt-get update
          sudo apt-get dist-upgrade

          Question 2.
          Do I need to restart my desktop before/after update to Oibaf's ppa?

          Question 3.
          I have Steam games however I do not know when my steam library stored. Where is it? (default)

          Question 4.
          How and where I need to setup the environment variable?

          I know it is basic questions, but not everybody experts here. THANK YOU/

          Comment


          • #35
            Originally posted by LN17 View Post
            I try to help however I have couple questions.

            At first I use Wsnipex MESA ppa as I mainly use XBMC and Oibaf's PPA not always worked with it.

            Question 1.
            Do I need to purge Wsnipex PPA before I execute

            sudo add-apt-repository ppaibaf/graphics-drivers
            sudo apt-get update
            sudo apt-get dist-upgrade

            Question 2.
            Do I need to restart my desktop before/after update to Oibaf's ppa?

            Question 3.
            I have Steam games however I do not know when my steam library stored. Where is it? (default)

            Question 4.
            How and where I need to setup the environment variable?

            I know it is basic questions, but not everybody experts here. THANK YOU/
            1. Yes.
            2. All 3D apps started before the upgrade will still use the old driver, so if you want compiz to use the new drivers, 'yes'.

            Comment


            • #36
              Are the patches compatible with mesa 10.0.2 ?

              Comment


              • #37
                I've pushed a stats7 branch, rebased to work with the radeonsi naming changes, and added a 32-bit fix for LFS (2g file limit). Can any SI user test?

                Originally posted by jsollie View Post
                Hi, I have a laptop with a rv710and 512mb vram, so I guess it's the perfect candidate for you.
                I have however, one problem with it: the cpu cooling is far too weak. I use TurionPowerControl to enable C1E and htc at startup, if not (and this is a problem in recovery when bypassing sysinit) I can guarantee it ends in an mce followed by a kernel shutdown.
                But when it's jumping in and out of htc slowdown, won't the results of your research be severely affected by this malfunction? I don't want to post corrupt data
                How big FPS jumps does it cause for you? A variance within 5% would be well acceptable, but 20% wouldn't.

                Comment


                • #38
                  Originally posted by TAXI View Post
                  Are the patches compatible with mesa 10.0.2 ?
                  The latest (stats7) are definitely not, due to the SI renames. stats6 may work, untested.

                  Comment


                  • #39
                    Originally posted by curaga View Post
                    I've pushed a stats7 branch, rebased to work with the radeonsi naming changes, and added a 32-bit fix for LFS (2g file limit). Can any SI user test?
                    Produced https://anonfiles.com/file/1382dac3c...d2db9433ce51ee for me, seems to work.

                    Comment


                    • #40
                      Originally posted by curaga View Post
                      stats6 may work, untested.
                      No, damn.

                      Comment


                      • #41
                        Originally posted by curaga View Post
                        I've pushed a stats7 branch, rebased to work with the radeonsi naming changes, and added a 32-bit fix for LFS (2g file limit). Can any SI user test?



                        How big FPS jumps does it cause for you? A variance within 5% would be well acceptable, but 20% wouldn't.
                        It highly depends on what I'm doing: uvd decoding is not skipping any frames, opengl games like wolfenstein:et seem to be running fine with it, but modern games, where the gpu is already too weak, downclocking a turion zm-86 to 600 mhz on both cores is killing it . do you have recommendations for testing applications?

                        Comment


                        • #42
                          Well, any game you like will do; I don't have any ET samples yet, for one.

                          Comment


                          • #43
                            Finally got my 6850 system rebuilt and got the stats7 branch compiled working, and produced a test glxgears bostats file via ssh... When I get home from work tonight, I can start producing stats files from all of the steam games that I installed last night.

                            Comment


                            • #44
                              Maybe other people find this helpful:

                              Choose any directory you like for $BUILDDIR and git clone the repository to $BUILDDIR/mesa_stats/ and $BUILDDIR/mesa_stats32/

                              Then in $BUILDDIR/mesa_stats/ do ./autogen.sh and configure with:

                              ./configure --with-egl-platforms=x11,drm --enable-shared-glapi --with-dri-drivers= --with-gallium-drivers=radeonsi --enable-glx-tls --enable-egl --enable-gallium-egl --enable-gallium-llvm --enable-osmesa --enable-texture-float --enable-gbm --enable-gallium-gbm --with-llvm-shared-libs --enable-openvg --disable-dri3

                              Of course, change --with-gallium-drivers=radeonsi to --with-gallium-drivers=r600g if applicable. Then simply "make -j8" or so to build

                              Then, if you have a 64 bit system and 32 bit cross compile libraries etc. installed, go to $BUILDDIR/mesa_stats32/, ./autogen.sh and ./configure with:

                              CC="gcc -m32" CXX="g++ -m32" PKG_CONFIG_PATH="/usr/lib32/pkgconfig" LLVM_CONFIG=/usr/bin/llvm-config32 ./configure --with-egl-platforms=x11,drm --enable-shared-glapi --with-dri-drivers= --with-gallium-drivers=radeonsi --enable-glx-tls --enable-egl --enable-gallium-egl --enable-gallium-llvm --enable-osmesa --enable-texture-float --enable-gbm --enable-gallium-gbm --with-llvm-shared-libs --enable-openvg --disable-dri3 --libdir=/usr/lib32 --enable-32-bit

                              Maybe llvm-config32 is different for you, or pkgconfig path, etc., then again build with "make".

                              Then, choose a specific shell and export:

                              export LIBGL_DRIVERS_PATH=$BUILDDIR/mesa_stats/lib/gallium:$BUILDDIR/mesa_stats32/lib32/gallium LD_LIBRARY_PATH=$BUILDDIR/mesa_stats32/lib32/egl:$BUILDDIR/mesa_stats32/lib32/gallium:$BUILDDIR/mesa_stats32/lib32:$BUILDDIR/mesa_stats/lib/egl/:$BUILDDIR/mesa_stats/lib/gallium/:$BUILDDIR/mesa_stats/lib/ R600_DEBUG=bostats DRI_PRIME=1 LIBGL_DEBUG=verbose GALLIUM_HUD=fps

                              (Maybe not DRI_PRIME=1, if you don't have hybrid graphics, LIBGL_DEBUG=verbose is helpful to see if it opens the correct driver, GALLIUM_HUD=fps is just nice to use)

                              And in that shell you can start your 3d programs and it will use this mesa over the one installed on the system.

                              Comment


                              • #45
                                Originally posted by curaga View Post
                                Well, any game you like will do; I don't have any ET samples yet, for one.
                                Deal,
                                I'll give it a try next weekend (wolfet and doom3, the vacuum cleaner will help.), i'm currently on a business trip and not in the mood for installing games on a pc I need.
                                Can contributors read your thesis when you 're done ?

                                Comment

                                Working...
                                X