I just received my miners and am very excited.
I was able to connect them to my network and I am able to access the web interface.
I only changed the WAN settings to:
IP Address: 192.168.0.250
subnet: 255.255.255.0
gateway: 192.168.0.1
broadcast: 192.168.0.255
(I did not modify my LAN settings from DHCP)
I added eligius to my #1 pool and removed the others...
Pool 1: stratum+tcp://stratum.mining.eligius.st:3334 stratum+tcp://stratum.mining.eligius.st:3334
Worker: Wallet ID
Password: N/A
Click Apply & Save...
Now when I view the Miner Status, everything says "This section contains no values yet"... and is empty.
Any idea why my pool is not being displayed here? Previously, it had Antminer's pool there and it looked fine...
Topic: ANTMINER S3+ Discussion and Support Thread - page 406. (Read 710164 times)
The chip is spec'd at 9.33W @ 7.5 0.75V - you can do the math on that amiright?
hah!@
Edit: fixed, and thanks for pointing that out.
The chip is spec'd at 9.33W @ 7.5 0.75V - you can do the math on that amiright?
From the datasheet:
Note the line for natural convection, and how current begins to drop off as ambient temperature rises.
So opening them, putting a box fan behind them in a AC room, should help them alot being stable, and better OC performance if possible. right .?
Your chart is meaningless unless we know the devices current requirement.
The chip is spec'd at 9.33W @ .75V - you can do the math on that amiright?
I fixed the x on the asic in the gui by removing the heatsink and reapplying thermal paste. However I had the opposite issue others have reported. There was not enough paste. Looks like someone got a talking to about using too much and is now being too conservative. There were large areas of pretty much every chip that had clearly not had any paste on them at all. I applied paste with an exacto blade to all the chips on both blades and put it back together and now the x is gone. I'm not sure the hashrate is any better though, still only doing about 430 but its only been a few minutes.
On the bright side it saved you the time of cleaning them up. That took a bit of time for me the other day. Hopefully they will get to 441 for you.
Aah I spoke too soon. The x is back. Same chip.
first what clock?
second what psu?
I tried OC on both but too many HW errors. So they were both back to stock. Since this one that had the x went to a - I tried OCing it again and it seems to work at 225 with zero HW but still can't even pull 430 hashrate. These are both duds.
Forgot to mention the PSU. Corsair CX750M. One per miner.
did you re-flash the firmware it brought my 420 up to the 440's with stock setting?
I did. I just edited a post above since I had 3 in a row and didn't want to make it 4. These things take a lot longer than the S1's to settle into an average hash rate so it's hard to tell how a change does right away. But I have to leave it as is for tonight since I am taking off. It's at 225 and not throwing any HW in the first 6 minutes and the average hashrate is 440 at the moment so maybe this one will reach advertised rates. Overall much less impressed by these than the S1.
I fixed the x on the asic in the gui by removing the heatsink and reapplying thermal paste. However I had the opposite issue others have reported. There was not enough paste. Looks like someone got a talking to about using too much and is now being too conservative. There were large areas of pretty much every chip that had clearly not had any paste on them at all. I applied paste with an exacto blade to all the chips on both blades and put it back together and now the x is gone. I'm not sure the hashrate is any better though, still only doing about 430 but its only been a few minutes.
On the bright side it saved you the time of cleaning them up. That took a bit of time for me the other day. Hopefully they will get to 441 for you.
Aah I spoke too soon. The x is back. Same chip.
first what clock?
second what psu?
I tried OC on both but too many HW errors. So they were both back to stock. Since this one that had the x went to a - I tried OCing it again and it seems to work at 225 with zero HW but still can't even pull 430 hashrate. These are both duds.
Forgot to mention the PSU. Corsair CX750M. One per miner.
the psu should be good. before you flash firmware swap the psu. maybe you have 2 good psu's and a poor one.
If psu switch is done and the problem follows the psu it is a psu issue.
if the miner still sucks. try freq 212.5
before you flash!
flashing should not get done until you check out everything.
I fixed the x on the asic in the gui by removing the heatsink and reapplying thermal paste. However I had the opposite issue others have reported. There was not enough paste. Looks like someone got a talking to about using too much and is now being too conservative. There were large areas of pretty much every chip that had clearly not had any paste on them at all. I applied paste with an exacto blade to all the chips on both blades and put it back together and now the x is gone. I'm not sure the hashrate is any better though, still only doing about 430 but its only been a few minutes.
On the bright side it saved you the time of cleaning them up. That took a bit of time for me the other day. Hopefully they will get to 441 for you.
Aah I spoke too soon. The x is back. Same chip.
first what clock?
second what psu?
I tried OC on both but too many HW errors. So they were both back to stock. Since this one that had the x went to a - I tried OCing it again and it seems to work at 225 with zero HW but still can't even pull 430 hashrate. These are both duds.
Forgot to mention the PSU. Corsair CX750M. One per miner.
did you re-flash the firmware it brought my 420 up to the 440's with stock setting?
I fixed the x on the asic in the gui by removing the heatsink and reapplying thermal paste. However I had the opposite issue others have reported. There was not enough paste. Looks like someone got a talking to about using too much and is now being too conservative. There were large areas of pretty much every chip that had clearly not had any paste on them at all. I applied paste with an exacto blade to all the chips on both blades and put it back together and now the x is gone. I'm not sure the hashrate is any better though, still only doing about 430 but its only been a few minutes.
On the bright side it saved you the time of cleaning them up. That took a bit of time for me the other day. Hopefully they will get to 441 for you.
Aah I spoke too soon. The x is back. Same chip.
first what clock?
second what psu?
I tried OC on both but too many HW errors. So they were both back to stock. Since this one that had the x went to a - I tried OCing it again and it seems to work at 225 with zero HW but still can't even pull 430 hashrate. These are both duds.
Forgot to mention the PSU. Corsair CX750M. One per miner.
I fixed the x on the asic in the gui by removing the heatsink and reapplying thermal paste. However I had the opposite issue others have reported. There was not enough paste. Looks like someone got a talking to about using too much and is now being too conservative. There were large areas of pretty much every chip that had clearly not had any paste on them at all. I applied paste with an exacto blade to all the chips on both blades and put it back together and now the x is gone. I'm not sure the hashrate is any better though, still only doing about 430 but its only been a few minutes.
On the bright side it saved you the time of cleaning them up. That took a bit of time for me the other day. Hopefully they will get to 441 for you.
Aah I spoke too soon. The x is back. Same chip.
Did you re-flash firmware?
Oh you know what, not on this one. I did on the other one but it didn't seem to improve anything. I can try it on this one.
EDIT: Flashed the firmware. Still got a dash on that chip. Have to watch and see what the hashrate does. Still looks like its not doing any HW though at 225 freq. Maybe that specific chip was throwing all the HW when I OC'd before.
I fixed the x on the asic in the gui by removing the heatsink and reapplying thermal paste. However I had the opposite issue others have reported. There was not enough paste. Looks like someone got a talking to about using too much and is now being too conservative. There were large areas of pretty much every chip that had clearly not had any paste on them at all. I applied paste with an exacto blade to all the chips on both blades and put it back together and now the x is gone. I'm not sure the hashrate is any better though, still only doing about 430 but its only been a few minutes.
On the bright side it saved you the time of cleaning them up. That took a bit of time for me the other day. Hopefully they will get to 441 for you.
Aah I spoke too soon. The x is back. Same chip.
first what clock?
second what psu?
I tried OC on both but too many HW errors. So they were both back to stock. Since this one that had the x went to a - I tried OCing it again and it seems to work at 225 with zero HW but still can't even pull 430 hashrate. These are both duds.
I fixed the x on the asic in the gui by removing the heatsink and reapplying thermal paste. However I had the opposite issue others have reported. There was not enough paste. Looks like someone got a talking to about using too much and is now being too conservative. There were large areas of pretty much every chip that had clearly not had any paste on them at all. I applied paste with an exacto blade to all the chips on both blades and put it back together and now the x is gone. I'm not sure the hashrate is any better though, still only doing about 430 but its only been a few minutes.
On the bright side it saved you the time of cleaning them up. That took a bit of time for me the other day. Hopefully they will get to 441 for you.
Aah I spoke too soon. The x is back. Same chip.
Did you re-flash firmware?
As to the beeping issue when the share difficulty changes, don't most P2Pools allow you to set a user defined share difficulty via the password? The one I use for scrypt mining does anyway.
Yes you can. Add /1024 I believe to end of your payout address. That'll force it to the highest difficulty supported by the current version of p2pool.
Note this won't at all affect your payout, as this is just the psuedoshare difficulty. The "real" difficulty is much much higher.
M
Anyone using their S3 on P2Pool? I am mining on GHash right now and it makes me hate myself. If P2Pool worked for you guys, I'll switch them as soon as I get back.
use Eligius man
S3s are working great with P2Pool, here are 4 stock S3s running on a single address:
http://minefast.coincadence.com/miner.php?id=19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj
this pool? http://www.p2pool.org/
how much BTC are you earning / day with your miners?
p2pool.org is NOT directly affiliated with p2pool, it is a p2pool node operated by an individual.
http://minefast.coincadence.com is my p2pool node, if you click the link you quoted above you will see exactly what I'm earning.
The official homepage for the p2pool project is:
http://p2pool.in/
Not only that, p2pool.org unfortunately has a deservedly bad reputation.
M
As to the beeping issue when the share difficulty changes, don't most P2Pools allow you to set a user defined share difficulty via the password? The one I use for scrypt mining does anyway.
Got my two last evening.
Both hashed all night about 440gh/s-450gh/s @pool.
No problem with beeping, they're in the basement.
Both hashed all night about 440gh/s-450gh/s @pool.
No problem with beeping, they're in the basement.
I fixed the x on the asic in the gui by removing the heatsink and reapplying thermal paste. However I had the opposite issue others have reported. There was not enough paste. Looks like someone got a talking to about using too much and is now being too conservative. There were large areas of pretty much every chip that had clearly not had any paste on them at all. I applied paste with an exacto blade to all the chips on both blades and put it back together and now the x is gone. I'm not sure the hashrate is any better though, still only doing about 430 but its only been a few minutes.
On the bright side it saved you the time of cleaning them up. That took a bit of time for me the other day. Hopefully they will get to 441 for you.
Aah I spoke too soon. The x is back. Same chip.
first what clock?
second what psu?
I fixed the x on the asic in the gui by removing the heatsink and reapplying thermal paste. However I had the opposite issue others have reported. There was not enough paste. Looks like someone got a talking to about using too much and is now being too conservative. There were large areas of pretty much every chip that had clearly not had any paste on them at all. I applied paste with an exacto blade to all the chips on both blades and put it back together and now the x is gone. I'm not sure the hashrate is any better though, still only doing about 430 but its only been a few minutes.
On the bright side it saved you the time of cleaning them up. That took a bit of time for me the other day. Hopefully they will get to 441 for you.
Aah I spoke too soon. The x is back. Same chip.
bitmain has gained greatly in value from yesterday up to today. the sp30 is a bust. no one knows had big of a bust yet but it is a bust. the ceo the the company admitted so on the sp30 thread.
so will it hash at 4th and pull 2400 watts.
it is not going to do the promised 6th.
we also do not know what the efficiency will drop to. .6 watts .7 watts?
this means the s-3 has jumped up in value. How big a jump depends on how bad the sp30 turns out to be.
As a s-3 owner this will also help with the diff.
Tell them to take their time and work it out for a few more months so we can ROI so will it hash at 4th and pull 2400 watts.
it is not going to do the promised 6th.
we also do not know what the efficiency will drop to. .6 watts .7 watts?
this means the s-3 has jumped up in value. How big a jump depends on how bad the sp30 turns out to be.
As a s-3 owner this will also help with the diff.
bitmain has gained greatly in value from yesterday up to today. the sp30 is a bust. no one knows had big of a bust yet but it is a bust. the ceo the the company admitted so on the sp30 thread.
so will it hash at 4th and pull 2400 watts.
it is not going to do the promised 6th.
we also do not know what the efficiency will drop to. .6 watts .7 watts?
this means the s-3 has jumped up in value. How big a jump depends on how bad the sp30 turns out to be.
As a s-3 owner this will also help with the diff.
so will it hash at 4th and pull 2400 watts.
it is not going to do the promised 6th.
we also do not know what the efficiency will drop to. .6 watts .7 watts?
this means the s-3 has jumped up in value. How big a jump depends on how bad the sp30 turns out to be.
As a s-3 owner this will also help with the diff.
Jump to: