Results 1 to 6 of 6

Thread: Reclocking Hits For Open-Source NVIDIA Driver

  1. #1
    Join Date
    Jan 2007
    Posts
    15,138

    Default Reclocking Hits For Open-Source NVIDIA Driver

    Phoronix: Reclocking Hits For Open-Source NVIDIA Driver

    Committed to the kernel repository for the open-source Nouveau driver for providing reverse-engineered NVIDIA hardware is now the initial GPU core/memory re-clocking support...

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

  2. #2
    Join Date
    Feb 2009
    Location
    France
    Posts
    309

    Default

    Michael, don't forget to set the kernel parameter nouveau.perflvl_wr=7777

    Also, don't forget to check the current perflvl: cat /sys/class/drm/card0/device/performance_level

    Please also check that the temperature is not skyrocketing. Nouveau reclocking won't be activated by default until we have a proper infrastructure for that. I'll talk about that @FOSDEM.

  3. #3
    Join Date
    Aug 2007
    Posts
    6,641

    Default

    Ah still the same funny hack

  4. #4
    Join Date
    Feb 2009
    Location
    France
    Posts
    309

    Default

    Quote Originally Posted by Kano View Post
    Ah still the same funny hack
    Yeah, safety first. I don't think there is a risk, but there could be one. If you set this kernel parameter, you ack the danger, so that's all good

  5. #5
    Join Date
    Sep 2007
    Location
    Connecticut,USA
    Posts
    965

    Default

    Quote Originally Posted by MPF View Post
    Yeah, safety first. I don't think there is a risk, but there could be one. If you set this kernel parameter, you ack the danger, so that's all good
    Yep, and make sure you got some decent cooling to handle the heat load!

  6. #6
    Join Date
    Aug 2007
    Posts
    6,641

    Default

    Basically you could specify the performance level as well using perflvl option together with the option mentioned above. At the time i tested nouveau last year it often worked for me, but did not do in all cases for others. Also reclocking resulted in full crashes, not real fun, but somehow you don't fear it anymore when you already hacked a binary driver - there this is even more common to crash

    @michael

    Also another note for doing benchmarks on oss drivers: it is really pointless when libtxc_dxtn is not used and enable-texture-float is not enabled. First of all that would allow more tests (like some with unigine engine) also why should games use compressed textures using binary drivers and not using oss ones? I dont think there is any law against publishing benchmarks with both things enabled, you still do not host binary files which might now be allowed in some weird countries. You should not compare speed when one driver

    a) uses diffenent clocks
    b) does not use all possible features
    c) enforces vsync that will cut framerates

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •