Can it be that --avalon-auto is only working with a reading for the fan rpm's? I use water cooling and have no fans...
Also is it possible that the setting for 16 miners instead of 24 is not working?
Last time i looked at your screen i found a huge amount of hw errors even at moderate frequencies,
i would try in simular case (if auto fails) to increment manually in 5 Mhz steps and look at hw error rate.
The only possible way fan data can make a "collision" with auto frequency option in this piece of code,
if (!info->optimal) {
if (info->fan_pwm >= opt_avalon_fan_max) {
applog(LOG_WARNING,
"AVA%i: Above optimal temperature, throttling",
avalon->device_id);
avalon_dec_freq(info);
}
but info->fan_pwm is not rpm sensor reading, its pwm setting for fan speed. Even if you don't have one or
it just not connected - it will keep on passing pwm value to controller. So if your fan reading is zero -
there is no protection besides
--avalon-cutoff option, its just for info purpose in current version.
Thats how i figured it out after looking at sources when my new fans went to 0 rpm and temperature starts growing.
I see no reason for changing 24 to 16 miners options to not work, only one thing - they must be plugged in DATA_P1 and P2 ports.