Topic: ANTMINER S3+ Discussion and Support Thread - page 191. (Read 710164 times)
Finally got the newest cgminer install on both my miners. Thank you twib2 and everyone for their help. ANd thanks to Kolivas for the fantastic job
Got 1 of my 2 S3 Batch 8s today hooked up and running. Seems the other one is still out for delivery.
So what freq and hash rates are you seeing?My 2 b8's came in today. After 10mins stock, I noticed hashrate near 453gh as advertised. Just oc'd both of them, but way too early to tell. I will let them run the rest of day and post back if they are stable. I assume they will run ~500gh, my 2 b6's run stable at 504gh. I may have to move them around and that will require restarting them, so I may not know if they run stable OC until tomorrow.
Got 1 of my 2 S3 Batch 8s today hooked up and running. Seems the other one is still out for delivery.
So what freq and hash rates are you seeing?Got 1 of my 2 S3 Batch 8s today hooked up and running. Seems the other one is still out for delivery.
So what freq and hash rates are you seeing?
Got 1 of my 2 S3 Batch 8s today hooked up and running. Seems the other one is still out for delivery.
testing cgminer 4.6 again on a single miner now that the DDOS has let up...
It is sitting at 500+ now. I suppose that DDOS that was going on effected my speeds yesterday and or one of those odd blocks that 'seems' harder to work on...
It is sitting at 500+ now. I suppose that DDOS that was going on effected my speeds yesterday and or one of those odd blocks that 'seems' harder to work on...
I don't think that after August updates you can change speed by ssh. It seems that advanced config, indeed, overrides ssh values.
Cheers BiodomDo you know is it possible to add the higher settings to the drop down?
cut and pasted from another post...
/usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
that has the frequencies that are available via the user interface
conf:tab("advanced", translate("Advanced Settings"))
pb = conf:taboption("advanced", ListValue, "freq", translate("Frequency"))
pb.default = "18:218.75:1106"
pb:value("16:250:0982", translate("250M"))
pb:value("17:243.75:1306", translate("243.75M"))
pb:value("17:237.5:1286", translate("237.5M"))
pb:value("17:231.25:1206", translate("231.25M"))
pb:value("18:225:0882", translate("225M (S3+ default)"))
pb:value("18:218.75:1106", translate("218.75M (S3 default)"))
pb:value("18:212.5:1086", translate("212.5M"))
pb:value("19:206.25:1006", translate("206.25M"))
pb:value("20:200:0782", translate("200M"))
pb:value("20:196:1f07", translate("196M"))
pb:value("20:193:0f03", translate("193M"))
pb:value("23:175:0d83", translate("175M"))
pb:value("27:150:0b83", translate("150M"))
pb:value("33:125:0983", translate("125M"))
pb:value("40:100:0783", translate("100M"))
I don't think that after August updates you can change speed by ssh. It seems that advanced config, indeed, overrides ssh values.
Cheers BiodomDo you know is it possible to add the higher settings to the drop down?
Hey just a quick one - I feel I am missing something here. Maybe someone can enlighten me.
I have an S3 B1, running the following...
antMiner_S320140826.bin
cgminer 4.6
Load is nice and low - but the hash rate seemed to be below what I am seeing on other S3's - so I was trying to push it a bit beyond to see if I could 'encourage' a few extra GH/s from it.
So SSH'd in and added the following -
option 'freq_value' '1406' #256.25M
option 'chip_freq' '256.25'
option 'timeout' '15
:wq -> reboot - but it is still showing as 250 in the gui - can anyone confirm if the new 'Advanced Settings' tab under 'Miner configuration' will over ride the manual entries I made in the asic-freq file?
Also - while I am at it...
I have such wide variance in the hashrate of the S3's anyone any suggestions on coaxing the slower ones towards 500. 2 of them are consistently at 505+ but some just seem determined to go slower - like sub 440 and even down as far as 400. Have tried playing around with freq's and FW and different PSU's etc. Has anybody had any solid results with checking/re-applying the thermal paste or even just re-seating the heat sinks, as I have not gone down this road yet?
Thanks
I have an S3 B1, running the following...
antMiner_S320140826.bin
cgminer 4.6
Load is nice and low - but the hash rate seemed to be below what I am seeing on other S3's - so I was trying to push it a bit beyond to see if I could 'encourage' a few extra GH/s from it.
So SSH'd in and added the following -
option 'freq_value' '1406' #256.25M
option 'chip_freq' '256.25'
option 'timeout' '15
:wq -> reboot - but it is still showing as 250 in the gui - can anyone confirm if the new 'Advanced Settings' tab under 'Miner configuration' will over ride the manual entries I made in the asic-freq file?
Also - while I am at it...
I have such wide variance in the hashrate of the S3's anyone any suggestions on coaxing the slower ones towards 500. 2 of them are consistently at 505+ but some just seem determined to go slower - like sub 440 and even down as far as 400. Have tried playing around with freq's and FW and different PSU's etc. Has anybody had any solid results with checking/re-applying the thermal paste or even just re-seating the heat sinks, as I have not gone down this road yet?
Thanks
I don't think that after August updates you can change speed by ssh. It seems that advanced config, indeed, overrides ssh values.
Hey just a quick one - I feel I am missing something here. Maybe someone can enlighten me.
I have an S3 B1, running the following...
antMiner_S320140826.bin
cgminer 4.6
Load is nice and low - but the hash rate seemed to be below what I am seeing on other S3's - so I was trying to push it a bit beyond to see if I could 'encourage' a few extra GH/s from it.
So SSH'd in and added the following -
option 'freq_value' '1406' #256.25M
option 'chip_freq' '256.25'
option 'timeout' '15
:wq -> reboot - but it is still showing as 250 in the gui - can anyone confirm if the new 'Advanced Settings' tab under 'Miner configuration' will over ride the manual entries I made in the asic-freq file?
Also - while I am at it...
I have such wide variance in the hashrate of the S3's anyone any suggestions on coaxing the slower ones towards 500. 2 of them are consistently at 505+ but some just seem determined to go slower - like sub 440 and even down as far as 400. Have tried playing around with freq's and FW and different PSU's etc. Has anybody had any solid results with checking/re-applying the thermal paste or even just re-seating the heat sinks, as I have not gone down this road yet?
Thanks
I have an S3 B1, running the following...
antMiner_S320140826.bin
cgminer 4.6
Load is nice and low - but the hash rate seemed to be below what I am seeing on other S3's - so I was trying to push it a bit beyond to see if I could 'encourage' a few extra GH/s from it.
So SSH'd in and added the following -
option 'freq_value' '1406' #256.25M
option 'chip_freq' '256.25'
option 'timeout' '15
:wq -> reboot - but it is still showing as 250 in the gui - can anyone confirm if the new 'Advanced Settings' tab under 'Miner configuration' will over ride the manual entries I made in the asic-freq file?
Also - while I am at it...
I have such wide variance in the hashrate of the S3's anyone any suggestions on coaxing the slower ones towards 500. 2 of them are consistently at 505+ but some just seem determined to go slower - like sub 440 and even down as far as 400. Have tried playing around with freq's and FW and different PSU's etc. Has anybody had any solid results with checking/re-applying the thermal paste or even just re-seating the heat sinks, as I have not gone down this road yet?
Thanks
it okay answered my own question the s3 will take the s3+ updates
just a question is the s3 antminer able to take the s3+ firmware update 
?
? They showed 0 Gh on Slush for past 5 + hours, then I re-entered my pool settings and applied and they started hashing for me again. My Norton sees the M's Ant Miner as a virus.
But after all that, my speeds are OK average as usual, but last few blocks since they have been running again, my earnings per block have dropped substantially from about 0.002 to about 0.0015 that's a 25% drop off in earnings per block.
Bear in mind that if you stop mining for a period on slush, you are punished due to the unique payment scheme in place there.But after all that, my speeds are OK average as usual, but last few blocks since they have been running again, my earnings per block have dropped substantially from about 0.002 to about 0.0015 that's a 25% drop off in earnings per block.
Is that really true? The hashrate reflects an hourly average updated every 10 minutes. So if you put a 44GH/s miner on toward the end of an hour, the average will be very low. I don't really see what I'd call an accurate hashrate there until a move to the next block.
100% true. if slush is on a 16 hour block and u move all your stuff there 30minutes before it ends u get paid as if u were there 16.5 hours. pool hoppers that leave before the end get 0.
Would anyone be able to explain something for me.
I upgraded to 4.6 today I believe, I am unsure how to check it worked, as in the units GUI it still shows 3.12 or something.
I also installed the M's Ant Monitor.
After doing both the R-Box on my laptop that I installed M's Ant Monitor, and my Ant S3 both were hashing, but not for me. They showed 0 Gh on Slush for past 5 + hours, then I re-entered my pool settings and applied and they started hashing for me again. My Norton sees the M's Ant Miner as a virus.
But after all that, my speeds are OK average as usual, but last few blocks since they have been running again, my earnings per block have dropped substantially from about 0.002 to about 0.0015 that's a 25% drop off in earnings per block.
Any Idea what has caused this?
Can someone give me specifics on how to revert to undo the changes? I am very unskilled at changes and needed to find the right post to understand or at least copy how to upgrade. So I would need some pretty specific info to revert back as well.
Thanks for your time in advance. This dropoff is a game killer for me to have that much less earnings.
I upgraded to 4.6 today I believe, I am unsure how to check it worked, as in the units GUI it still shows 3.12 or something.
I also installed the M's Ant Monitor.
After doing both the R-Box on my laptop that I installed M's Ant Monitor, and my Ant S3 both were hashing, but not for me. They showed 0 Gh on Slush for past 5 + hours, then I re-entered my pool settings and applied and they started hashing for me again. My Norton sees the M's Ant Miner as a virus.
But after all that, my speeds are OK average as usual, but last few blocks since they have been running again, my earnings per block have dropped substantially from about 0.002 to about 0.0015 that's a 25% drop off in earnings per block.
Any Idea what has caused this?
Can someone give me specifics on how to revert to undo the changes? I am very unskilled at changes and needed to find the right post to understand or at least copy how to upgrade. So I would need some pretty specific info to revert back as well.
Thanks for your time in advance. This dropoff is a game killer for me to have that much less earnings.
maybe your pools' hashrate increased, thereby dropping your expected share proportionately .
I heard recently Slush pool hashrate jumped from 6 PH/s to 9 PH/s, maybe this is your answer.
Yes, noon yesterday Slush was hashing at 6,527 and now 9,678 and share payout went from .004xxxxx to .003xxxxx.
yup other pools were having problems connecting too and defaulted to Slush. hopefully they move back off Slush soon!
They showed 0 Gh on Slush for past 5 + hours, then I re-entered my pool settings and applied and they started hashing for me again. My Norton sees the M's Ant Miner as a virus.
But after all that, my speeds are OK average as usual, but last few blocks since they have been running again, my earnings per block have dropped substantially from about 0.002 to about 0.0015 that's a 25% drop off in earnings per block.
Bear in mind that if you stop mining for a period on slush, you are punished due to the unique payment scheme in place there.But after all that, my speeds are OK average as usual, but last few blocks since they have been running again, my earnings per block have dropped substantially from about 0.002 to about 0.0015 that's a 25% drop off in earnings per block.
Is that really true? The hashrate reflects an hourly average updated every 10 minutes. So if you put a 44GH/s miner on toward the end of an hour, the average will be very low. I don't really see what I'd call an accurate hashrate there until a move to the next block.
Would anyone be able to explain something for me.
I upgraded to 4.6 today I believe, I am unsure how to check it worked, as in the units GUI it still shows 3.12 or something.
I also installed the M's Ant Monitor.
After doing both the R-Box on my laptop that I installed M's Ant Monitor, and my Ant S3 both were hashing, but not for me. They showed 0 Gh on Slush for past 5 + hours, then I re-entered my pool settings and applied and they started hashing for me again. My Norton sees the M's Ant Miner as a virus.
But after all that, my speeds are OK average as usual, but last few blocks since they have been running again, my earnings per block have dropped substantially from about 0.002 to about 0.0015 that's a 25% drop off in earnings per block.
Any Idea what has caused this?
Can someone give me specifics on how to revert to undo the changes? I am very unskilled at changes and needed to find the right post to understand or at least copy how to upgrade. So I would need some pretty specific info to revert back as well.
Thanks for your time in advance. This dropoff is a game killer for me to have that much less earnings.
I upgraded to 4.6 today I believe, I am unsure how to check it worked, as in the units GUI it still shows 3.12 or something.
I also installed the M's Ant Monitor.
After doing both the R-Box on my laptop that I installed M's Ant Monitor, and my Ant S3 both were hashing, but not for me. They showed 0 Gh on Slush for past 5 + hours, then I re-entered my pool settings and applied and they started hashing for me again. My Norton sees the M's Ant Miner as a virus.
But after all that, my speeds are OK average as usual, but last few blocks since they have been running again, my earnings per block have dropped substantially from about 0.002 to about 0.0015 that's a 25% drop off in earnings per block.
Any Idea what has caused this?
Can someone give me specifics on how to revert to undo the changes? I am very unskilled at changes and needed to find the right post to understand or at least copy how to upgrade. So I would need some pretty specific info to revert back as well.
Thanks for your time in advance. This dropoff is a game killer for me to have that much less earnings.
maybe your pools' hashrate increased, thereby dropping your expected share proportionately .
I heard recently Slush pool hashrate jumped from 6 PH/s to 9 PH/s, maybe this is your answer.
Yes, noon yesterday Slush was hashing at 6,527 and now 9,678 and share payout went from .004xxxxx to .003xxxxx.
I feel faint burning smell near s3 fan.
is it normal?
Sometimes it can be on newer items but Bitmain doesnt exactly sell new items so you could have a fan going bad.is it normal?
I don't know where this belief comes from. I've never received anything from Bitmain that looked like it had ever sat running for any length of time, barely a spec of dust on my seven different units. I'm not even convinced that they were tested before shipping. And all had that burning electronics smell when first fired up which I'm assuming is from thermal paste heating up and manufacturing chemicals and oils burning off.
I agree. More likely guys with miner farms, get a dog of a unit, resell it quick, spread rumors under a different name that it was run at the factory for a long time.
Still, they would have to be factory tested and a question might be how long they test the units for.
The one I got from Florida compared to the first one I got from the mid-west - both advertised new on Amazon. The first was fine, the one from Florida not so much and that repackaged in a larger box. Both S3's. Perhaps he had a box from an S2 or earlier that was in best condition. I'll have a better idea when my S3+'s arrive. There are many creeps out there in the bitcoin world.
If the S3+'s come in the size box I got from the mid-west, I'll feel more sure giving a bad report to Amazon when they ask my opinion.
S3+'s ordered the 19th, shipped to arrive by end of day Monday.
Figured out the different box size thing. Florida S3 reseller got a return from a dissatisfied customer who marked the S3's box well with something like RETURN DEFECTIVE. He couldn't just turn around and ship it to someone else because of the box markings but he had a box from an S1 or perhaps an S2 with its packing material. He then sold the return as new in the used box.
Slush always has consistent luck, about 6 blocks a day average. I think they got DDOS'd yesterday. They payouts are increasing back up to normal.
DDoS attack sounds like a good explanation to me. Very strange when I saw that happen (and one of my S1's had a best share of around 453,xxxx,xxxx).Anyhow, I have to see out my shift on the P2Pool node I switched to, plus that jump from 6PH to 9PH on the pool will definitely reduce my earnings .... so will see when we are done here.
p2pool is the right move; using is own p2pool node gets all the advantages of local mining, with the huge hashrate of all nodes.
Slush always has consistent luck, about 6 blocks a day average. I think they got DDOS'd yesterday. They payouts are increasing back up to normal.
DDoS attack sounds like a good explanation to me. Very strange when I saw that happen (and one of my S1's had a best share of around 453,xxxx,xxxx).Anyhow, I have to see out my shift on the P2Pool node I switched to, plus that jump from 6PH to 9PH on the pool will definitely reduce my earnings .... so will see when we are done here.
I heard recently Slush pool hashrate jumped from 6 PH/s to 9 PH/s, maybe this is your answer.
Too damn right! And they had a period about 7 hours back (just before that massive jump) when my rigs were not registering any shares. I had them pointing at slush and treble-checked that they were hashing, but nothing showed up on the pool!front end has little to do with backend
what you saw on front end
Jump to: