Sure. Until I get add to the wiki, here's how to set the fan speed:
env DISPLAY=:0.1 aticonfig --pplib-cmd "set fanspeed 0 70"
The important parts:
env <- Runs a shell command with the following variables set, so it doesn't affect the rest of your shell
DISPLAY=:0.1 <- Select GPU #2 (:0.0 would be GPU #1, :0.2 would be GPU #3, etc)
--pplib-cmd <- Undocumented aticonfig command, appears to directly interface with firmware on card
[get|set] fanspeed 0 <- I think the 0 is which register for the object (fanspeed), it appears 0 is the only valid value
70 <- Only necessary for "set", this is the percentage of maximum to set the fan speed to. I guess leaving the fan at very high value for a long time will burn it out. Use with caution.
I'm planning to write a small shell script to control my fan speed so I can increase it before using oclHashcat-* and reduce it once finished. Maybe it could work as a cron job that watches for oclHashcat processes and automatically increases the fan while processes found, and decreases the fan when no processes found. I'll have to think about the best way.
PS setting the fan to 70% (up from 33% it had selected on it's own) brought tempt down from 80c to 64c. That's a huge difference! I set it to 40% to keep it from burning out the fan while I figure out how to automate it.
Before I manually set the speed, I was watching it with 'get fanspeed 0' and it started at 20%, when oclHashcat-* was running it gradually went up to 33% and just stayed at 33%, even though the temp sensor showed 80c on the GPU.
env DISPLAY=:0.1 aticonfig --pplib-cmd "set fanspeed 0 70"
The important parts:
env <- Runs a shell command with the following variables set, so it doesn't affect the rest of your shell
DISPLAY=:0.1 <- Select GPU #2 (:0.0 would be GPU #1, :0.2 would be GPU #3, etc)
--pplib-cmd <- Undocumented aticonfig command, appears to directly interface with firmware on card
[get|set] fanspeed 0 <- I think the 0 is which register for the object (fanspeed), it appears 0 is the only valid value
70 <- Only necessary for "set", this is the percentage of maximum to set the fan speed to. I guess leaving the fan at very high value for a long time will burn it out. Use with caution.
I'm planning to write a small shell script to control my fan speed so I can increase it before using oclHashcat-* and reduce it once finished. Maybe it could work as a cron job that watches for oclHashcat processes and automatically increases the fan while processes found, and decreases the fan when no processes found. I'll have to think about the best way.
PS setting the fan to 70% (up from 33% it had selected on it's own) brought tempt down from 80c to 64c. That's a huge difference! I set it to 40% to keep it from burning out the fan while I figure out how to automate it.
Before I manually set the speed, I was watching it with 'get fanspeed 0' and it started at 20%, when oclHashcat-* was running it gradually went up to 33% and just stayed at 33%, even though the temp sensor showed 80c on the GPU.