Quote from: jjj0923 on June 12, 2014, 03:50:16 PM

Quote from: maxzilla on June 12, 2014, 03:46:49 PM

Quote from: jjj0923 on June 12, 2014, 02:13:34 PM

Quote from: iikun on June 12, 2014, 02:02:26 PM

Quote from: jjj0923 on June 12, 2014, 01:39:54 PM

I did upgrade one of my two units last night and it's been running fine but I did have to reboot it after upgrading

ok, cool. was there any performance or stability boost do you think?

my only observation(and this has not been proven with multiple tests) is that the unit did not need to be restarted multiple times after changing pools, like I've experienced with the stock firmware.

oh and even though it reboots itself after the update - I neede to reboot it a second time because after it's own reboot all I say was this in the syslog file:

Quote

Jun 12 14:18:54 hashracontroller cgminer: Started cgminer 3.1.1
Jun 12 14:18:59 hashracontroller single_ltc_monitor[2201]: Started LTC PRocess waiting 10 seconds to boot cgminer
Jun 12 14:18:59 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:18:59 hashracontroller cgminer: Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 00038d26
Jun 12 14:18:59 hashracontroller cgminer: All devices disabled, cannot mine!
Jun 12 14:19:04 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:09 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:14 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:19 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:24 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:29 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:34 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:39 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:44 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:49 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null

Jeff

The trick for rebooting is, first reboot the miner, and then reboot the pi. The miner has to be reset completely and alive, before connecting the pi to it.

thanks for the insight but how do you do that when your miners are remote - is there a command at the firmware level to reboot the miner?

Yea that would be difficult. There is no power cycle command from the PI to the miner.

Can you have a remote power switch installed ?
like this one? this one has a web interface
http://www.amazon.com/Managed-Designed-Manufactured-Synaccess-Networks/dp/B0039OZKPE