Antminer S3 Help Please!!!

[maxman190]

When I click miner status, it gave me this error: "/usr/lib/lua/luci/dispatcher.lua:448: Failed to execute cbi dispatcher target for entry '/admin/status/minerstatus'.
The called action terminated with an exception:
/usr/lib/lua/luci/controller/cgminer.lua:32: bad argument #1 to 'floor' (number expected, got string)
stack traceback:
   [C]: in function 'assert'
   /usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch'
   /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194>"


I bought this off someone from ebay, miner status tab worked fine out of the box. For some reason, I decided to update the firmware, now it's throwing that error. I tried restoring the firmware that I backed up before flashing that firmware, but it didn't solve it. I also tried pushing the reset button, but it just powers off, but the fan is still spinning, so I just turned it off and on.

[ThriceGreatest]

For some reason, I decided to update the firmware

if it's not broken - don't fix it!

Now that you have however, I'd suggest you try all FW updates /from the bitmain site/ until you find one that works for your unit.

[nezroy]

The problem is actually that cgminer is not getting the frequency values set, so these are blank. The miner status page blows up on these blanks (since it expects numbers). EDIT: this appears to affect all FW versions since (and including) the cgminer 4.6.2 update, from what I can tell.

Verify this by going to "Processes" tab under "Status" and look for the cgminer entry. You'll see something like "--bitmain-options 115200:32:8:"; that option statement SHOULD have more values that specify the freq (it should look like "--bitmain-options 115200:32:8:18:218.75:1106).

I didn't look deeply into why this is happening, I just hacked a quick fix since I have to edit the startup script for other reasons anyway.

ssh into the antminer and edit the "/etc/init.d/cgminer" startup script. Change the line "local _freq" to:

Code:

local _freq="timeout:chip_freq:freq_value"

Where timeout, chip_freq, and freq_value are the numeric values from your /etc/config/asic-freq that you want to be using.

Then comment out the line "config_get _freq default freq" (add a # to the front of it).

When you restart cgminer you should see the correct bitmain options for cgminer in the process list with the specified frequency values. The miner status page should then render normally.

[NoahWL1]

I don't know if this is going to solve your problem or not, but whenever I have issues with my S3 I do this:

1. Hold down the reset button for 30 seconds
2. Release the reset button and wait for 60 seconds
3. Turn off the miner's power supply for 60 seconds
4. Turn the power supply back on and wait for the miner to boot up fully

That always works for me.  If not, it's something you did with the firmware :/ hopefully someone with more expertise than I will be able to help you.  Good luck!

[Shermand100]

Solved!!!!! (nearly a year late but I hope this may help someone anyway) I cant see a solution elsewhere.

Credit also to Nezroy for pointing me in the right direction. He is correct that this is caused by the cgminer not recieving instructions for freq settings and he saved me a lot of time trawling through code.

His solution would work in theory but I believe there is a better beginner friendly way.

With the most recent firmware installed, go to the tabs, System ==> Miner configuration ==> Advanced settings. And re-select the default freq for your device. then hit "save and apply". No power reset required. This will load the missing values back in.







For those that care, I believe this is caused by the "keep settings" box being ticked on the firmware update. This causes problems for those of us that are updating from the original installed cgminer by bitmain, to the updated cgminer v4.6.1 at firmware S320141013. The OS is probably trying to import the old freq settings into the new cgminer in an incorrect format. Those that don't tick this box on firmware update probably wont have this problem as default values will be used. Those that update between versions S320141013 and S320150109 firmware also are probably not affected as cgminer versions are unchanged.

Hope this helps.

[hashnest]

Solved!!!!! (nearly a year late but I hope this may help someone anyway) I cant see a solution elsewhere.

Credit also to Nezroy for pointing me in the right direction. He is correct that this is caused by the cgminer not recieving instructions for freq settings and he saved me a lot of time trawling through code.

His solution would work in theory but I believe there is a better beginner friendly way.

With the most recent firmware installed, go to the tabs, System ==> Miner configuration ==> Advanced settings. And re-select the default freq for your device. then hit "save and apply". No power reset required. This will load the missing values back in.







For those that care, I believe this is caused by the "keep settings" box being ticked on the firmware update. This causes problems for those of us that are updating from the original installed cgminer by bitmain, to the updated cgminer v4.6.1 at firmware S320141013. The OS is probably trying to import the old freq settings into the new cgminer in an incorrect format. Those that don't tick this box on firmware update probably wont have this problem as default values will be used. Those that update between versions S320141013 and S320150109 firmware also are probably not affected as cgminer versions are unchanged.

Hope this helps.

By the way, your S3 is still profitable??

[leowonderful]

Solved!!!!! (nearly a year late but I hope this may help someone anyway) I cant see a solution elsewhere.

Credit also to Nezroy for pointing me in the right direction. He is correct that this is caused by the cgminer not recieving instructions for freq settings and he saved me a lot of time trawling through code.

His solution would work in theory but I believe there is a better beginner friendly way.

With the most recent firmware installed, go to the tabs, System ==> Miner configuration ==> Advanced settings. And re-select the default freq for your device. then hit "save and apply". No power reset required. This will load the missing values back in.







For those that care, I believe this is caused by the "keep settings" box being ticked on the firmware update. This causes problems for those of us that are updating from the original installed cgminer by bitmain, to the updated cgminer v4.6.1 at firmware S320141013. The OS is probably trying to import the old freq settings into the new cgminer in an incorrect format. Those that don't tick this box on firmware update probably wont have this problem as default values will be used. Those that update between versions S320141013 and S320150109 firmware also are probably not affected as cgminer versions are unchanged.

Hope this helps.

By the way, your S3 is still profitable??

I bought two of them and run them where I live. The power is included with my rent, so my only condition is that they need to run near where I sleep. The S3 is the only one that I think I can get away with the custom fans making them near silent, (Nanoxia deep silent 120mm fans). That is the reason I still run them. I would love more powerful units as power cost is not an issue, but the extra heat needs venting and thus noisy fans. I'm very glad I've had success as a hobbyist miner, which is good, not just for me but there must be others in the community that can say that taking the gamble paid off and spread the word.

The details if you're interested, I bought two of them from ebay in December 2015. One for £105 as single unit. The other for £128 with corsair cs550m inc. I then spent £96 on a corsair rm750x to power them both. So spent £329. My slush pool page says my all time payout is 0.57777511BTC which right now is £548.38 so I'm up on my investment as I hodl. And I of course still have the hardware to sell if my circumstances change.

tl:dr yes it's profitable, free power, but slow returns due to low power units, but silent as in close proximity to where I sleep.

Nice! There's still nothing like a solid and quiet S3 in the Bitcoin world today, and there probably won't ever be one. The returns on even free power are slow but they're still fun to run

I've got a few running in my home simply because other miners are too loud or unreliable. There's really no alternative for me since I need the quiet in my house :/