|
|
|
|
Moderator
Videocard:
Processor:
Mainboard:
Memory:
Soundcard:
PSU:
|

08-28-2008, 08:53
| posts: 10,312 | Location: Taganrog, Russia
Quote:
Originally Posted by LuxZg
1) changing voltages through Rivatuner (like ATT beta allows, when right BIOS is applied; right BIOS=BIOS which was tweaked with RBE 1.13/1.14 to enable low volts on 4870's)
|
Principle of not providing access to voltage controls in RT was declared about 5 years ago when the first GPUs with software controlable voltage (NV3x) were announced. And this principle won't change neither now nor in future, sorry. And honestly I won't like to beat the dead horse again, so please use search, it was discussed many many times in the forum. And PowerUsers always have a CLI interface for any part of GPU including VRM control via direct access to I2C or GPIO, but that's a different (and not public) story.
Quote:
Originally Posted by LuxZg
2) will there be stuttering when polling sensors in Vista - to explain a bit: when I use GPU-Z or Everest on Vista SP1 64bit I get small pauses during any rendering. Any means not only running 3D app, but also dragging windows around. Every time sensors get polled for an update, you get one small pause. It does not happen in XP, and I have one other user confirming it happens in Vista. I have no confirmation if it's only Vista 64bit or any Vista for that matter. Have not tried with ATT cos of driver signing problems, but if Overdrive stays open in background I don't get the stutters. Interesting enough, it seems that for example 3dmark score stays the same even with polling (or application which does the polling) turned off.
|
There will be some kind of stuttering when polling sensors in any OS with any hardware, polling sensors is not a free operation (in terms of CPU performance hit) and it always requires some CPU time. And the amount of stutterning depends on used graphics chip (completely different sensor access protocols for different hardware) and the amount of sensor data you're displaying.
Quote:
Originally Posted by LuxZg
As much as I've understood everything else should be fine by now: GPU/VRM monitoring (all 3+3 temperatures and amps?), underclocking/overclocking both memory and GPU, automatic profiles, fan speed changes, monitoring/logging/OSD of all sensor and clock data, 64bit support, etc etc.. Right?
|
Almost right.
As the very first pposting says, probably this version won't give VRM monitoring at all. Also, there won't be additional RV770 GPU sensors and VRM slave chips monitoring neither now nor in future. These sensors are not dedicated for frequent polling and dynamic logging and can cause noticeable perofmance hit and side effects. As an example, additional RV770 temperature sensors cannot be accesses simultaneously, the chip can read just one at time and sensor source must be switched (rather slow process) before reading an alternate sensor, also the chip automatically uses currently selected sensor as input for automatic fan control circuit, so constantly switching the sensors can cause unwanted fan speed fluctuations. The same applies to multiple VRM temperature sources. So there will be just one GPU temperature and 1 VRM slave chip temperature available.
Alexey Nicolaychuk aka Unwinder, RivaTuner creator
|
|
|
|