Quote from: alh on February 04, 2015, 06:30:54 AM

My recollection is that with the setting of timed "actions", the time specified must be in UTC. Of course if you live in Greenwich England, this won't matter. This is kinda a surprise, but not so much when consider that Linux is inside there.

i changed the system time to local time though. I set another adjustment to occur during the night and it seems like that one happened correctly as expected, but unfortunately i wasnt awake to hear if the system changed its fan speeds drastically in the adjustment.

I see 2.6.12 is now available so am downloading it to see whats new. hopefully some further abilities are added to scheduling
EDIT: 2.6.12 is crap - voltage settings are all lost and cant be configured, so all loops are Off/null/disabled. I cant seem to input any settings to make it start mining. The fan keeps revving from 0-20 every 3-4 seconds.
EDIT 2: went to change back firmware, clicked manula selection, my only options are 1.5.8 and 1.5.10. The Sp20 now seems to think its an SP10 - what do i do?
EDIT 3: used SSH, typed "echo SP2x > /model_id; echo SP20 > /model_name;" and was able to get the device to download the 2.6.12 again, this time operational

2.6.12: seems like theres a wifi function (requires dongle, presumably in the system's USB port). no visible changes or improvements to scheduling though. For that reason im curious to know how changes to the /etc/mg_custom/mode are implemented. Is a reboot required, or just restarting the minergate process?

seems like it could be easy to create a cron task that simply copies different mg_custom_mode(day) and mg_custom_mode(night) files to the actual mg_custom_mode and then re-initiates the miner. It would allow better fan control and precision tuning the voltages and wattage limits for each schedule, rather than just the max voltages