Originally posted by not.sure
View Post
Announcement
Collapse
No announcement yet.
Trying Out Nouveau GPU Re-Clocking On Linux 3.16
Collapse
X
-
Originally posted by not.sure View PostIt's probably better to make such tests on a laptop system (no fan, and as usual it's a good guess that some developers use laptops/thinkpads).
The Sager NP8655(trying to remember model #, 15.6") w/GFX 780m has a separate HS/fan setup for the CPU and another for the GPU.
My old MSI GT725 w/4850 mobility had a shared setup like the 7330.
Pretty much any dGPU is going to have some kind of fan setup and NOT just rely on a heatsink. Mobile dGPUs run a bit warmer than their desktop counterparts, e.g. 780m is specwise, very similar to the GTX 670(which I have), not sure what the 765m corresponds to from the desktop... 660 or 650 maybe?(768 shaders) And the old 4850 was an oddity, same specs as the 4850 desktop variant(shader count) but w/lower core/mem clocks(the ONLY time that I can recall that current mobile GPUs had identical specs other than core/mem clocks as analogous desktop parts, didn't last long though, next iteration was back to the not quite matching similarly "named" desktop part).
Comment
-
So still no reclocking for the GTX 460... what a pain. The old performance_level interface worked fine. I hate it when they remove something that works to replace it with something that doesn't. I've been stuck at 50/135 MHz for several months, while I could set 675/1800 MHz without any problem until kernel 3.12 with "echo 3 > performance_level"
Comment
-
For that one solution is obvious
Originally posted by zequav View PostSo still no reclocking for the GTX 460... what a pain. The old performance_level interface worked fine. I hate it when they remove something that works to replace it with something that doesn't. I've been stuck at 50/135 MHz for several months, while I could set 675/1800 MHz without any problem until kernel 3.12 with "echo 3 > performance_level"
Comment
Comment