Topic: ANTMINER S3+ Discussion and Support Thread - page 380. (Read 710164 times)
Mine are running in a 30c ambient temp room! temps are not above 45c for the units! The miners can run up to 80c - not that you want them to run up that high!!
Ok thanks.
Whats the maximun temperature you recommend for S3?? My room is not a very cold one, i have to move units, but till then... i have temperatures of 45/46 both blades in my 2 S3. (that running them at 237,5 freq, if i use 218,75 they get 41-43 temperature
Whats the maximun temperature you recommend for S3?? My room is not a very cold one, i have to move units, but till then... i have temperatures of 45/46 both blades in my 2 S3. (that running them at 237,5 freq, if i use 218,75 they get 41-43 temperature
One of my S3's overclocks like a beast!
The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
Make sure to keep that beast cool (sub 35C pref), they really don't like getting warm when you run them at 237/250MHz (hash rate starts dropping and you might get and x or two after 10h+ of running)
Unfortunately I cannot get them running much lower temps! they run at 40/42 at stock! it's due to the room temp that I can't get them lower! here is an updated pic of how they look after running overnight!
Still going strong
how much Watts for those 494 GH/s ?
i have these values, which one is for 250?
first one?? and its values are ok?? (freq_value,chip_freq and timeout?)
The top one is for 250
All its numbers are fine.
One of my S3's overclocks like a beast!
The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
Make sure to keep that beast cool (sub 35C pref), they really don't like getting warm when you run them at 237/250MHz (hash rate starts dropping and you might get and x or two after 10h+ of running)
Unfortunately I cannot get them running much lower temps! they run at 40/42 at stock! it's due to the room temp that I can't get them lower! here is an updated pic of how they look after running overnight!
Still going strong
[IM]http://i57.tinypic.com/20adws9.jpg[/img]
Great, you got that odd device.
i'm going to have to run the 10hrs+ myself.
it's at 485gh/s average and 518gh/s current
impossible for me to keep the units sub 40C in the ambient temperature of the room though, so i'm not sure how it will hold up
also, I do not know if this is worth it. from 225 to 250 it added 75watts on the killawatt. So it's now pulling around >~450w for ~490-500gh/s ( with risk of dying after 10hrs of running as mentioned about )
Also, after changing queue to 0 and adding scan-time 1 and expiry 1, the unit has completely stopped having more discarded shares then accepted!
Right now I have two Gigampz pushing 900W HP server power supplies to 8 PCI connectors split between both. Each is pushing 440gh (At 218 and 250) and that's the best I can do no matter the frequency settings.
The unit running at 250 will hash at 500gh but only for about a half an hour before dropping off sharply.
The unit running at 250 will hash at 500gh but only for about a half an hour before dropping off sharply.
One of my S3's overclocks like a beast!
The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
Make sure to keep that beast cool (sub 35C pref), they really don't like getting warm when you run them at 237/250MHz (hash rate starts dropping and you might get and x or two after 10h+ of running)
Unfortunately I cannot get them running much lower temps! they run at 40/42 at stock! it's due to the room temp that I can't get them lower! here is an updated pic of how they look after running overnight!
Still going strong
[IM]http://i57.tinypic.com/20adws9.jpg[/img]
Great, you got that odd device.
One of my S3's overclocks like a beast!
The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
Make sure to keep that beast cool (sub 35C pref), they really don't like getting warm when you run them at 237/250MHz (hash rate starts dropping and you might get and x or two after 10h+ of running)
Unfortunately I cannot get them running much lower temps! they run at 40/42 at stock! it's due to the room temp that I can't get them lower! here is an updated pic of how they look after running overnight!
Still going strong
how much Watts for those 494 GH/s ?
i have these values, which one is for 250?
first one?? and its values are ok?? (freq_value,chip_freq and timeout?)
One of my S3's overclocks like a beast!
The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
The other sadly doesn't suffer the same fate! it's hashing at 430 at 218, any higher and the rate drops!
Make sure to keep that beast cool (sub 35C pref), they really don't like getting warm when you run them at 237/250MHz (hash rate starts dropping and you might get and x or two after 10h+ of running)
Unfortunately I cannot get them running much lower temps! they run at 40/42 at stock! it's due to the room temp that I can't get them lower! here is an updated pic of how they look after running overnight!
Still going strong
http://i57.tinypic.com/20adws9.jpg
can someone share what is a single S3 on a decent PSU pulling from the wall in terms of power ?
cheers
cheers
Corsair RM750, 354-377 depending on clock speeds is what I am getting @110VAC
thank you.
Hey,
have anyone a coupon for me. That's would great.
Please send me a PM.
ID Kidprodigy
have anyone a coupon for me. That's would great.
Please send me a PM.
ID Kidprodigy
I'm not so sure anymore. Faster S3 is starting to slow and the "slower" unit is catching up in accepted shares. Also worth noting is that the S3s never receieved ANY rejected shares when running stock options. I have no idea what to do. I can't get either unit to stabilize over 430 for more than two hours.
I'm going back to stock options. The tweaks were, seemingly, not making any significant difference after two hours of observation.
Spoke with some engineers at a large pool and they suggested --expiry 15 --scan-time 1 --queue 1. I am going to try that now.
Both of my Ants are all over the place. Just took a nap and woke up to both of them sub 400 at stock speeds.
Both of my Ants are all over the place. Just took a nap and woke up to both of them sub 400 at stock speeds.
I'm not so sure anymore. Faster S3 is starting to slow and the "slower" unit is catching up in accepted shares. Also worth noting is that the S3s never receieved ANY rejected shares when running stock options. I have no idea what to do. I can't get either unit to stabilize over 430 for more than two hours.
As you can see, temps are certainly not the issue.
Ant1 is running at 218, Ant2 at 250. (Ant2 runs at 470-490 for about 30-45 minutes)
It's looking like the extra invalids picked up by the scan, expiry and queue settings make any changes not worth it.
Also curious to know whether or not you guys are running 2x or 4x PCIe connections? I'm concerned that all of those DC/DC modules get warmer using the extra lines?
S1 DC/DC chips used to see small benefits (1GH+) from using heat-sinks...
can someone share what is a single S3 on a decent PSU pulling from the wall in terms of power ?
cheers
cheers
Corsair RM750, 354-377 depending on clock speeds is what I am getting @110VAC
can someone share what is a single S3 on a decent PSU pulling from the wall in terms of power ?
cheers
cheers
I am happy with my S3's. As an owner of bfl little singe(now not profitable), cointerra, and spondoolies s10(both perform great but are super noisy), I must say that Bitmain S3 is by far The Best Power Efficiency of the lot. Also the quietest (5 S3's same loudness as my pc).
I get sustained 444Gh/s at pool averaged per machine stock settings.
I get sustained 444Gh/s at pool averaged per machine stock settings.
Spoke with some engineers at a large pool and they suggested --expiry 15 --scan-time 1 --queue 1. I am going to try that now.
Both of my Ants are all over the place. Just took a nap and woke up to both of them sub 400 at stock speeds.
Both of my Ants are all over the place. Just took a nap and woke up to both of them sub 400 at stock speeds.
I am happy to contribute.
I wonder if kano is going take a look at the code and see what he could do as he for the S1 units.
I wonder if kano is going take a look at the code and see what he could do as he for the S1 units.
Hey Duce, could we get an update on your firmware adjustments?
Setting the Queue to anything but 0 increases both the Load and Discarded values. After another run with the Queue back to 0, accepted values are about the same as stock. My other unit is performing just like this except it likes a lower clock, such as 212.5 as others have identified. Again if you are on P2P then this should be good for you but the Queue value may interact different with your pool. The unit here is connected to a regular pool. Here is the same unit as before with the last run I started.
I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file.
***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***
***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***
Thanks for this post ! Going to try this on one of my units and see how it works out.
PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 4096"
I tried it on one by adding the --scan-time 1 --expiry 1 flags, but didn't see any difference in discards or load. Maybe some of you will have better luck.
Did you change the Queue to 0?
Since I've never SSH one of these, I don't want to risk bricking it.
If this fix turns out to be solid though, I hope Bitmain will include it in the next firmware release.
Or maybe I'll learn to SSH. On a side note. Does anyone know if you can get a better GHS/watt ratio by under-clocking the S1?
I'll tell you how to do it, but not going to go into every detail (how to SSH, sed, etc). Not responsible for you f'ing your stuff up.
1. SSH into the miner
2. cd /etc/init.d
3. cp cgminer cgminer.bak (in case you really muck it up, cgminer.bak will be your backup)
4. Enter this in the terminal: sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' cgminer
5. press enter
6. go to the web interface of the miner - Status > Miner Configuration > Save & Apply - this will restart cgminer with the new settings
7. go tip Duce for figuring this out for us
Duce, where's your tip jar? I owe you.
This is what you're changing:
Original --> PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 4096"
New & Improved --> PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 0 --scan-time 1 --expiry 1"
//S1 undervolt guide - https://bitcointalksearch.org/topic/m.5838713
I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file.
***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***
***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***
Thanks for this post ! Going to try this on one of my units and see how it works out.
PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 4096"
I tried it on one by adding the --scan-time 1 --expiry 1 flags, but didn't see any difference in discards or load. Maybe some of you will have better luck.
Did you change the Queue to 0?
Since I've never SSH one of these, I don't want to risk bricking it.
If this fix turns out to be solid though, I hope Bitmain will include it in the next firmware release.
Or maybe I'll learn to SSH. On a side note. Does anyone know if you can get a better GHS/watt ratio by under-clocking the S1?
Jump to: