Announcement

Collapse
No announcement yet.

Nouveau On Linux 3.16 Will Allow You To Try Re-Clocking

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

  • Nouveau On Linux 3.16 Will Allow You To Try Re-Clocking

    Phoronix: Nouveau On Linux 3.16 Will Allow You To Try Re-Clocking

    The Nouveau DRM graphics driver for open-source NVIDIA support hasn't seen any fundamental re-clocking support breakthroughs for the upcoming Linux 3.16 kernel but the support can be easily enabled for select GeForce GPU models...

    http://www.phoronix.com/vr.php?view=MTcwOTc

  • #2
    Originally posted by phoronix View Post
    This re-clocking support is still disabled by default
    Correction: For nv40 (all nv4x), nvaa (nvaa/nvac), and nve0 (nve0+), it'll actually be enabled by default. Hence the advice to use with caution

    For NV40, it should generally work, with rare exceptions, NVAA/NVAC should be in good shape too. Kepler is largely turned on because it does work fine for a bunch of boards, but there's another bunch for which it won't. But seemed like the nice thing to do was to let users try and see which bucket they're in.

    For all of these, it's still manual switching through /sys/class/drm/card0/device/pstate -- no automatic switching yet. (That'll happen after switching between levels works reliably.)

    Comment


    • #3
      Originally posted by imirkin View Post
      Correction: For nv40 (all nv4x), nvaa (nvaa/nvac), and nve0 (nve0+), it'll actually be enabled by default. Hence the advice to use with caution

      For NV40, it should generally work, with rare exceptions, NVAA/NVAC should be in good shape too. Kepler is largely turned on because it does work fine for a bunch of boards, but there's another bunch for which it won't. But seemed like the nice thing to do was to let users try and see which bucket they're in.

      For all of these, it's still manual switching through /sys/class/drm/card0/device/pstate -- no automatic switching yet. (That'll happen after switching between levels works reliably.)
      Thanks for the information! The article has been updated.
      Michael Larabel
      http://www.michaellarabel.com/

      Comment


      • #4
        Originally posted by imirkin View Post
        Correction: For nv40 (all nv4x), nvaa (nvaa/nvac), and nve0 (nve0+), it'll actually be enabled by default. Hence the advice to use with caution

        For NV40, it should generally work, with rare exceptions, NVAA/NVAC should be in good shape too. Kepler is largely turned on because it does work fine for a bunch of boards, but there's another bunch for which it won't. But seemed like the nice thing to do was to let users try and see which bucket they're in.

        For all of these, it's still manual switching through /sys/class/drm/card0/device/pstate -- no automatic switching yet. (That'll happen after switching between levels works reliably.)
        For the others, it's behind a flag, or it's blocked and one has to patch the kernel like in 3.13/3.14/3.15?

        Comment


        • #5
          Originally posted by Spittie View Post
          For the others, it's behind a flag, or it's blocked and one has to patch the kernel like in 3.13/3.14/3.15?
          It's blocked and one has to patch. However the reason it's disabled is that it's generally not worth trying. The memory reclocking logic that was there for nv50-era cards got essentially dropped in the 3.13 rewrite. Work is ongoing to reinstate it. Once it is, and it works on a bunch of cards, we'll turn it back on.

          Comment


          • #6
            Originally posted by imirkin View Post
            Correction: For nv40 (all nv4x), nvaa (nvaa/nvac), and nve0 (nve0+), it'll actually be enabled by default. Hence the advice to use with caution

            For NV40, it should generally work, with rare exceptions, NVAA/NVAC should be in good shape too. Kepler is largely turned on because it does work fine for a bunch of boards, but there's another bunch for which it won't. But seemed like the nice thing to do was to let users try and see which bucket they're in.

            For all of these, it's still manual switching through /sys/class/drm/card0/device/pstate -- no automatic switching yet. (That'll happen after switching between levels works reliably.)
            wait what ?

            just when I had removed the card (currently using on-board Intel) - Re-clocking support is added

            if feedback is positive I might have to re-install it


            you guys think the GTX 760 would work with it ?

            Comment


            • #7
              Originally posted by Spittie View Post
              For the others, it's behind a flag, or it's blocked and one has to patch the kernel like in 3.13/3.14/3.15?
              It's not commited to the kernel versions you have posted. You would have to backport the patch from here:
              http://cgit.freedesktop.org/~darktam...7dab04e76b8742

              But - i guess, it's not that easy and a lot of work inbetween has happend to make that change possible, so better
              stay on the safe side and wait for 3.16.

              Cheers

              EDIT: imirkin beat me to the answer.

              Comment


              • #8
                Wait wait wait.. what is re-clocking? i've heard of overclocking, underclocking but never reclocking...

                Comment


                • #9
                  Originally posted by rabcor View Post
                  Wait wait wait.. what is re-clocking? i've heard of overclocking, underclocking but never reclocking...
                  reclocking is "all of the above".

                  Comment


                  • #10
                    ok, so how would one activate it ?

                    nouveau.allow_reclock=1 ?

                    Comment


                    • #11
                      reclocking on Ubuntu

                      Originally posted by kernelOfTruth View Post
                      ok, so how would one activate it ?
                      1) Update kernel to 3.16 or newer
                      2) Install oibaf's or edgers Mesa ppa
                      3) $ sudo su root
                      4) $ echo 0f> /sys/class/drm/card0/device/pstate
                      where 0f is the desired power state and /card0 is your card's id

                      Comment


                      • #12
                        Missed a step.

                        1) Update kernel to 3.16 or newer
                        2) Install oibaf's or edgers Mesa ppa
                        3) $ sudo su root
                        4) $ NvReclock=1
                        5) $ echo 0f> /sys/class/drm/card0/device/pstate
                        where 0f is the desired power state and /card0 is your card's id

                        Comment


                        • #13
                          So. Reclock it's not automatic? You have to set the desired clock state?

                          Comment


                          • #14
                            Originally posted by marciocr View Post
                            So. Reclock it's not automatic? You have to set the desired clock state?
                            Absolutely NOT. In fact it's now hidden in 3.17 kernel. So the new way to test this out is


                            1) Update kernel to 3.17
                            2) Add the following kernel boot parameter: nouveau.pstate=1
                            3) Install oibaf's or edgers Mesa ppa
                            4) $ sudo su root
                            5) $ export NvReclock=1
                            6) $ echo 0f> /sys/class/drm/card0/device/pstate

                            There really should be a central wiki that documents these steps and current hardware support status.

                            Comment

                            Working...
                            X