![]() |
aticonfig fan speeds - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Deprecated; Previous versions (https://hashcat.net/forum/forum-29.html) +--- Forum: General Help (https://hashcat.net/forum/forum-8.html) +--- Thread: aticonfig fan speeds (/thread-692.html) |
aticonfig fan speeds - chort - 11-30-2011 I realized using the command: env DISPLAY=:0.1 aticonfig --pplib-cmd "get fanspeed 0" That the fan speed on my HD 5870 never went over 33%, even under heavy load. I set it to 70% manually and the temp went waaaaay down. Then I tried setting it to "auto" and the fan just stopped. Ouch! Is there any way to set the fan speed back to auto-scale, or am I stuck setting it manually once I've touched it at all? Also, this revelation that I can drastically improve cooling just by setting the fan speed on the card means I should be able to install a second card without any extra cooling. If I would have known that I would have bought a bigger PSU! RE: aticonfig fan speeds - atom - 11-30-2011 ok, good info. we should add this to this wiki: http://hashcat.net/wiki/changing_fan_speed_of_ati_under_linux seems the fan controller function in the amd driver is not working as we like it. they will have their reasons, but i think you are right. the cooler, the better. RE: aticonfig fan speeds - chort - 11-30-2011 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. RE: aticonfig fan speeds - KT819GM - 11-30-2011 Isn't it's easier to use some script.sh with your fan commands, when you launch script with hashcat job, on top write 70% at the end 30% and all will be done ... I would never trust other software to monitor activity of some process to manage fan speed of these not cheap cards. If you had 2xHD6990 on one box your default settings would be 90% to be on 80c temp. Also brushless fans on such cards have resource for much higher voltage/wattage so even 100% can be less healthy just for ball bearings. If you still want something automatic - use software called AMDOverdrive. It will do all for you without any scripting. p.s. besides, anyone noticed that new catalyst driver on linux allow to drop memory clock to 300mhz? ![]() ![]() RE: aticonfig fan speeds - chort - 11-30-2011 (11-30-2011, 08:22 PM)KT819GM Wrote: Isn't it's easier to use some script.sh with your fan commands, when you launch script with hashcat job, on top write 70% at the end 30% and all will be done ... Yes, but I'd have to create a script for each oclHashcat-* rather than just one. You have a good point though. (11-30-2011, 08:22 PM)KT819GM Wrote: p.s. besides, anyone noticed that new catalyst driver on linux allow to drop memory clock to 300mhz? Nice catch! The output of --odgc doesn't indicate that 300 is a valid value, but using --odsc it works! RE: aticonfig fan speeds - atom - 12-01-2011 (11-30-2011, 08:22 PM)KT819GM Wrote: p.s. besides, anyone noticed that new catalyst driver on linux allow to drop memory clock to 300mhz? cool, did not notice. i was forced to flash a modded bios, now i can switch back. thanks for info. RE: aticonfig fan speeds - chort - 12-19-2011 BTW here's the shell script I use. Keep in mind I have two GPUs and this script only adjusts the second one (the first one has no fan). Do I need a separate account for the wiki? Code: #!/bin/bash RE: aticonfig fan speeds - splash_ - 07-31-2012 I've got 4 graphic cards so I felt the need to add some stuff in the code. You can now set and get on all devices present at the same time plus some cosmetic changes and controls. Feel free to comment on it. Code: #!/bin/bash I don't have access to the wiki so after further evaluation from the community, please, update it there. |