Announcement

Collapse
No announcement yet.

Nouveau "Boost" Patches Show Much Performance Potential

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

  • #21
    I didn't mean the core clock.


    I mean, the memory clocks.


    If I try to relax it to, for instance, 03, after a 0f state, this is what I see :

    Code:
    03: core 300 MHz shader 600 MHz memory 100 MHz AC DC *
    07: core 400 MHz shader 800 MHz memory 300 MHz
    0f: core 576 MHz shader 1242 MHz memory 999 MHz
    AC: core 300 MHz shader 601 MHz memory 999 MHz
    And dmesg shows me "nouveau 0000:01:00.0: fb: Could not calculate MR" when I try a lower pstate.

    Don't happen when I switch to a higher.



    PS : GTX 260, Linux 4.4, 64 bit.
    Last edited by DebianLinuxero; 17 April 2016, 05:59 PM. Reason: My mistake, I meant, from 0f state

    Comment


    • #22
      Originally posted by DebianLinuxero View Post
      I didn't mean the core clock.


      I mean, the memory clocks.


      If I try to relax it to, for instance, 03, after a 0f state, this is what I see :

      Code:
      03: core 300 MHz shader 600 MHz memory 100 MHz AC DC *
      07: core 400 MHz shader 800 MHz memory 300 MHz
      0f: core 576 MHz shader 1242 MHz memory 999 MHz
      AC: core 300 MHz shader 601 MHz memory 999 MHz
      And dmesg shows me "nouveau 0000:01:00.0: fb: Could not calculate MR" when I try a lower pstate.

      Don't happen when I switch to a higher.



      PS : GTX 260, Linux 4.4, 64 bit.
      Mhh this is Tesla. I never looked into it, but I guess the issue is something trivial. You should open a bug if you didn't do it already. And if nobody commented on that, ask again

      Comment

      Working...
      X