|
Title: CGMiner "temp-cutoff" option Post by: tremor.hash on August 01, 2012, 01:11:01 PM Hey everyone, i'm using the latest and greatest CGminer 2.6.1 with no issues at all.
All options do exactly what they are supposed to do except one, the "temp-cutoff" one. According to official readme: --temp-cutoff <arg> Temperature where a device will be automatically disabled, one value or comma separated list (default: 95) My config: -o http://de.btcguild.com:8332 -u xxx -p xxx -I 9 --gpu-engine 800 --gpu-memclock 300 --gpu-fan 80 --temp-cutoff 90 I am using 5970s and NO GPU gets disabled when i reach the 90 value or even higher!:( Any ideas? Title: Re: CGMiner "temp-cutoff" option Post by: Merrick on August 02, 2012, 07:16:07 AM Well that's concerning. Time to lower my values and go test, I suppose. :(
Title: Re: CGMiner "temp-cutoff" option Post by: tremor.hash on August 02, 2012, 01:21:41 PM yeah i would appreciate some feedback ..it doesnt make any sense ???
i even tried the --temp-cutoff 90,90,90,90 with no result.. Title: Re: CGMiner "temp-cutoff" option Post by: Zanatos666 on August 02, 2012, 01:23:28 PM Ive always had problems getting arguments to work with command line/shortcut arguments. I always have more success using the .conf file to make any changes that actually take affect. Maybe you can try that (also is your option for using failover for multiple pools).
Title: Re: CGMiner "temp-cutoff" option Post by: tremor.hash on August 03, 2012, 10:25:02 AM Guys thanks
it seems after all that temp-cutoff absolutely depends on auto-gpu being set. once set it can disable gpu threads once you reach the cutoff limit 8) Title: Re: CGMiner "temp-cutoff" option Post by: MTJ151 on April 25, 2014, 12:06:13 AM Guys thanks it seems after all that temp-cutoff absolutely depends on auto-gpu being set. once set it can disable gpu threads once you reach the cutoff limit 8) Sorry for digging up an old topic... but that is really important info. One of my cards fans stopped working and the temp-cutoff didn't work when it started to overheat.... turns out it was because I didn't have the --auto-gpu |