On Thu, Feb 18, 2010 at 5:59 PM, Ákos Maróy <akos@maroy.hu> wrote:
Alex Deucher wrote:
yes. that messges just prints the default clock. ForceLowPowerMode sets the clock to half of the default value.
but how does one know if this setting succeeds?
The GPU didn't lock up. You can call the get engine clock table if you want to verify.
Really depends where the thermal chip is and how well it's calibrated. If it's right under the north bridge or something, it well always run hot.
yes, but the machine is quite hot to the touch as well, and the fan is always quite loud... it's also strange that there seems to be no difference in temperature between the forced low power mode and normal mode. on my old laptop with also an ATI card, the temperature difference was significant, depending on GPU load.
There's no interface for reading it. The current ddx code only sets the default clock and default clock divided by 2 so you always know what the clock is. In the case of the power management options we don't print the clock to avoid spamming the log with tons of clock changes.
well, a /proc like interface to read it on demand would prevent spamming, but provide the information as needed. or some signal to dump the current state into the log file. or some dedicated program that just shows this information on stdout.
You need a kernel driver to use /proc. the ddx is in userspace.
Rafał Miłecki wrote:
I wanted to make sure engine was really changed. Maybe it needs some additional magic for evergreen or sth? Just for debugging purposes.
yes, something like this would be nice..
kms already has this. Alex -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org