Quote from: dogie on November 06, 2014, 08:03:42 PM

Quote from: pikachuy on November 06, 2014, 07:28:17 PM

Quote from: Tim.Shao19 on November 06, 2014, 06:27:05 AM

can you please let me know how many s4 you have in hand and how many of these miners arise with this chip issues?
How long will the Os last each time after you reset the X's on the chips and Xs show up again? please contact my email address info@bitmaintech.com. And i will be incontact with our engineers and tech guys to find a solution for you.

Quote from: pikachuy on November 04, 2014, 07:28:10 PM

How do we do something like a power cycle to reset the O's and X's on the chips through SSH?

For example, sometimes I see X's on the chips and when I reboot through the GUI, it doesn't get corrected. It's only when I manually do a power cycle by powering it off and on from the power button is when all the chips turn back to O's on the status page.

The reason I am asking is because sometimes I get X's and i reboot it from the GUI remotely through a VPN and it doesn't get fixed. I don't want to have to keep going there and manually power cycle it every time because my S4 is located about an hour away and it's a hassle =(.

Any ideas?

I get X's randomly because i overclock the frequency to 225, and it runs without a problem at that frequency for awhile. It just randomly get's some X's here and there, which is why I was asking how to do a hard reboot through SSH because a soft reboot through the webpage/GUI won't correct the X's. It's only when I pull the plug or press the button on the PSU is when it's able to fix itself.

Any commands or hard reboot cycle through SSH that you can share?

I don't believe you can do a hard enough reboot via SSH that will reawaken X'ed chips. PSU restart it is.

I manage and oversee datacenters around the world for a global telecomm where I come from a hard reset means pulling the plug without question ..