If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
There are definitely differences from generation to generation but I *think* the main breakpoints were in the middle of the 6xx generation and then more changes between 6xx and 7xx. We'll know more in a month or so, but AFAIK Evergreen should be able to leverage most of the 7xx code.
I probably should have posted in another thread to avoid confusion: my card is an R300. I just thought ForceLowPowerMode also worked for legacy cards. Should owners of these cards keep using rovclock then?
I probably should have posted in another thread to avoid confusion: my card is an R300. I just thought ForceLowPowerMode also worked for legacy cards. Should owners of these cards keep using rovclock then?
ForceLowPowerMode works on all asics. rovclock should be avoided.
ForceLowPowerMode works on all asics. rovclock should be avoided.
So rovclock is reporting the wrong numbers? If it's not, why is the card at its highest frequency settings with the ForceLowPowerMode option activated and why should this tool be avoided?
So rovclock is reporting the wrong numbers? If it's not, why is the card at its highest frequency settings with the ForceLowPowerMode option activated and why should this tool be avoided?
Last time I looked at rovclock it did not take into account the post divider for the engine or memory clocks so if the post divider is anything other an 1, it will set/report the wrong value. Also, IIRC, some of the vram setup stuff in the memory reclocking code is wrong for r2xx+ chips.
Stupid $^$^&% edit limit. If the post divider is initially set to 1 and you half the engine clock, the post divider will likely be 2. since rovclock does look at the post divider, it will still report the old clock.
I can't say I fully understood you, but I take it that there are some technical drawbacks with using rovclock. The point is that if ForceLowPowerMode is just halving the clocks, that's a bit conservative, isn't it? This is, I use rovclock to set the core and memory frequencies to the values reported by fglrx in its lowest power settings, and those are 1/4 and 1/3 their original values, respectively.
Comment