Ummmmmm.....

Any news on this yet?

Thanks, Tommo - looks like all is well again.   BTW, I come here because chat keeps not working between my workplace filters and likely my addons/extensions at home.  Hope here is OK.

Seems like the TomCoin SHA pool has been down for awhile - any news?

Refund received, thanks.

Refund PM request sent for #842.

If it's "stuck" at 225, then you have an s3+ (or at least the newest firmware that's what they use).  To overclock with these, the easiest solution is to go to the Miner Configuration tab and choose Advanced, then change the frequency that way.  (You can also edit the /etc/config/cgminer file directly, but that's more work)

The firmware on S3+s ignores the asic-freq file.

I'd be in for one plus a preprogrammed rPi (depending on price).

Thanks for putting this (and these) together!
- Tye

LOL!

Maybe if BTC were about $700...

MBW, you are thinking of the next-to-latest firmware.  The last one before the S3+ firmware does not have the 243.75 setting, but the one for the S3+ (and S3 works fine with, too) DOES have 243.75.  I have one S3 with each.

Only worthwhile if you're lacking by 5%, it would seem...

I have not had good experience with their support/RMA folks.  It took me a month to get a single S3 hashing board replaced, and that's when I had it fail, put a deposit so they could ship it before they received my return, AND they didn't send me the blade with heatsinks.

Total agreement.

Any plans to get NEOS (SHA256 version at least) on Tompool?

You *must* choose a frequency in the Advanced Options of the Miner Configuration, otherwise it will default to 100GH/s.  If you forget that step, you'll get only 100GH/s and you'll show no frequency in that column on the Miner Status page.

You're not the only one - this has been discussed here since about the time that the second-to-last firmware update was posted.  ;-)

Which commands, exactly?  It sounds like either you didn't set the execute flag to make it executable (won't run without it normally), you transferred it via the wrong protocol (ascii vs binary), or you simply had a bad transfer.

If you followed any of the instructions here, you wouldn't need to reflash the whole S3 since you would have a backup cgminer (the original one) still on hand.  Simply rename it (i.e. mv cgminer.bak cgminer) and you'd be back up and running.  Changing out cgminer shouldn't do anything else to your machine, so putting the old one back should be all it would take.

Here's the instructions I used, with a short explanation of what each does:


cd /usr/bin                         # move to the correct directory that has the original cgminer file
cp cgminer cgminer.orig      # makes a backup of the original file so I still have the original one on hand to copy back
wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer             # retrieves the new file on top of the old one
                                                                                                                            # (this preserves the permissions, including executability)
ls -tralF cgminer*               # list all files that begin with cgminer - look for the same execution settings
                                        # (Settings on the left should read "-rwxr-xr-x" indicating it is executable, and it should be 502276 bytes in size)
                                        # if the flags for x don't look the same simply type 'chmod a+x cgminer' without the quotes and hit return/enter
/etc/init.d/cgminer restart  # restart the miner process - no need to reboot!


Hope this helps!

Ack!  Didn't catch that - that explains the strange behavior I was seeing for the past week or two.  It wasn't quite shut off, but certainly was barely limping along.  Fixed on my end now and working fine.  Thanks!

Hi Tommo - looks like the SHA TomCoin ports on 3329 are dead, at least for me.  Do they no longer work in general, or is this just temporary?  (I keep missing you on chat, so I'm writing here in case I'm not the only one).

Thanks,
- Tye

Does anyone know the specs or screw type (size, length, pitch, etc) for the screws that mount the two heatsinks to the hashing boards?

Bitmain shipped me a board w/o heatsinks when I sent my old one back with heatsinks still attached.  Then they sent heatsinks but no screws.  My original warranty problem was reported on 2 August, and I'm still not back to full hashing on that unit because of things like this, not to mention the time when it took more than a week to hear from them in the middle of our interactions despite trying several times.  Meh.  Not happy with the customer service...  Never had to use them for the S1's, and everything was great.

Interesting - that's how I first noticed my problem, but for me it was more to do with the temperature of the PSU itself.  That's what exposed it being "on the edge."  But, you don't have quite the GH/s dip that I did, so it could well be the miner.  Either way, keep us in the loop to what the final answer is.  Good luck!

I had the same thing until I added more power or used better PSUs, even going from using a piss-poor 850.  If you have other PUSs handy, it might be worth it to test that and rule it out to be sure.  Other things could be network problems, pool problems, using the same miner, sub-optimal miner difficulty settings, or even the already-noted S3 mining rate instability.  I'm sure you've already ruled out most of those, just throwing them out there anyway...