Topic: BITMAIN Antminer S3 support and OverClocking thread - page 18. (Read 158132 times)

Try just !w and see what it says. What are the file permissions? When you !wq you don't get a chance to get any feedback if there is a problem writing to the file. Also check the time/date of the file to see if the write is actually occurring.

I would like an answer for this as well. I have used the "old" S3 SSH overclocking method to OC my new batch 8's but when I try to SSH and type "!wq" it doesn't save as it should. Another method maybe?

I used the method above to overclock my S1s, but I thought you could change the freq from the advanced menu in the S3. My first S3s still in the mail. Do you still have to SSH to overclock the S3?

Welp
Just tried calling the UK number above and its just a mailing forward address.

Bitmain S1 upgrade kits..


Well after pulling my hair out for a couple of hours it dawned on me that you need to update the firmware with the latest S3+ ver.
At stock 225 freq its running at 450 GH/s  pulling  385 watts from a very high grade server power supply.
Want to let it run for a while before I try to ramp up the freq.
Stock form temp is 39C
will let you know how I make out with overclocking, If I get it to 500  I'll be happy.
Bob

wow, that vreg chip had the magic smoke escape!

contact who you got it from?

5 days in and my antminer s3+ caught fire!



This literally just happened like 5 minutes ago.
Rig went offline, went out to see what's what and try and give it a power cycle, no go.. So I swapped the psu for a brand new one and went to turn it on and was met with a huge cloud and smoke and an adrenaline rush. (all cables correct etc, I have 9 others from the same batch running on the same corsair rm1000 PSUs with uptimes of 5 days, no overclocking involved)


Does anyone have info for UK bitmain support?

If I am hashing above 500GH/s but there is a "-" and "x" for one of my blades is this bad or should I ignore it?
Ever since switching to nicehash this has happened.

Goxed,

You got a really nice unit if it's remaining stable at 250 clock and 504GH/s, congrats!  Mine apparently are part of the batch that caused Bitmain to set the clocks back to 218.75.  I tried 225, 237.5 and 250.  I would consistently get "x" and "-" in the ASIC stats and the units never got anywhere near the 504GH/s you're showing.  I left them running like that for 7 hours while I slept last night, hoping things might get better over time.  When I woke up and checked, Ant 1 was averaging 450GH/s and Ant 2 was averaging 387.  At 250 clock.  I set them back to stock and after 13 hours I'm at 441 and 439 with 0.0002% and 0.0004% HW errors.  All ASICs are "o".  It's definitely not a power issue - I've got an EVGA 1300 G2.  I even went so far as to hook only 1 up at a time on the PSU to see if it made a difference.  All 4 PCI-e connected.

Also, that solution for the random beeping did not work for me unfortunately.  They still randomly beep at me.  It's like they're just letting me know they're still going.  If somebody does come up with a valid solution to this, I'd be very much... well, my little lady will be very much appreciative of it

As for temps and fans, mine are in an ambient 22C room.  Ant 1 shows 38/39 and Ant 2 shows 39/40 on stock speeds.  Fans are 1560/1380 and 1620/1380, respectively.  With the same PSU as I have, philipma1957 reported 665W at the wall to run them both at stock.