I have two deltas similar to the ones you have on an S5 that runs very quite. There is a link to a video here it has 15 seconds of SP20s and 15 seconds of the S5. Not a very scientific approach but a quick and dirty comparison: https://bitcointalk.org/index.php?topic=902305.1240. I like both unit types as they both serve me well. |
|
|
|
|
I have 43 hardware errors on one unit that has been running for over 3 days now and 0 on another that has been up for over 2 days. My minors restart on their own when they determine there is a problem. I like this feature since I can just let them run without having to continually monitor them.
|
|
|
|
If you have a server dedicated to P2P with bitcoind running and have your payouts going to another wallet on a different server why would you need to implement address rotation with bitcoind? I read the post on github and do not see why this would have been a benefit. Obviously I need a better education with this aspect. Can someone just point me in the right direction so I can read up on this please. You would have no need for this. Address reuse is generally frowned upon from both a security and privacy standpoint, if you were using the node bitcoind wallet this would be a big security improvement.
Privacy
Address reuse harms the privacy of not only yourself, but also others - including many not related to the transaction. In some cases, these risks are serious enough that they are likely in violation of reasonable consumer protection laws.
Security
Bitcoin does not, at a low level, have any concept of addresses, only individual coins. Address reuse, at this layer, requires producing multiple digital signatures when you spend bitcoins. Multiple situations have been found where more than one digital signature can be used to calculate the private key needed to spend bitcoins. Even if you spend all the bitcoins claimed by this private key at once, it is still possible to double-spend them in theft before they confirm. While the situations for finding the private key from signatures have been fixed, it is not prudent to assume there aren't more such situations yet unknown.
In the case of spending all the TXOs in a single transaction, there is an additional risk if someone is actively monitoring the network for vulnerable transactions: upon receiving such a transaction, they can split up their double spends such that there is only one ECDSA verification per transaction (making a single transaction for each TXO); this will cause the attacker's transactions to relay across the rest of the nodes faster than the legitimate one, increasing success of a double spend.
https://en.bitcoin.it/wiki/Address_reusePerfect, I was dumb in thinking that people were no longer using the node bitcoind for payouts, thank you. |
|
|
|
I see that the pinout information has been provided already so I can tell you that I used a scribe (pin will work too) to push in the locking tab to remove the pin the lifted it a little to lock in again. The locking tab is accessed in the rectangular opening of the connector. If you are uneasy about the change you can always try it out first to a power supply before connecting it to your miner. You will be very happy with these fans once you install them. |
|
|
|
If you have a server dedicated to P2P with bitcoind running and have your payouts going to another wallet on a different server why would you need to implement address rotation with bitcoind? I read the post on github and do not see why this would have been a benefit. Obviously I need a better education with this aspect. Can someone just point me in the right direction so I can read up on this please. |
|
|
|
@Ilan123, I put 2 delta fans on and it is rather quite now, running at 54-56c with an RPM at 2880 for both fans when I last looked. I don't have the P/N with me right now though. My SP20's are about 70db and the S5 about 60db with the new fans. It was louder than my other units before the change but I did not take a reading. Others have the stock db level from the S5 units here though. I will get particulars later like ambient room temp and the P/N for the fans later today.
Fan: Delta AFC1212DE, 12vdc, 1.6A, 3900 RPM, 192.96CFM, 51 dBA, 120mm x120mm x 38mm or equivalent. These came out of some old Dell desktops, Dell P/N: Y4574. Right now room temp 26.1C, blades at 57-55 with the fans at 3K and 3120. Here is a video with the delta fans installed on the S5. I am using my SP20s for reference. This video was taken with my phone. http://vid1284.photobucket.com/albums/a568/rponce454/MINER%20SOUND-Small_zpsyi3zjhtk.mp4 |
|
|
|
Wasn't aware of that Westhash status page but now have it up. I went through my S3s installing cgminer 4.7.0 aprox two weeks ago and yet the status page shows all red crosses. I'm running the Tues Aug 26 firmware release in each (original S3+ version) and just used PuTTY to recheck cgminer version ("cgminer-api version") and each reports 4.7.0. Any idea what the problem might be?
PS. Each S3 has had configuration modifications since then as well as having been rebooted, but normally the cgminer install isn't affected by that.
Did you append #xnsub at the end of your miner host configuration entry? TrevorS it should look like this: stratum+tcp://stratum.westhash.com:3334#xnsub Well, I'll be damned! Thanks very much kind sirs!  I see no apparent difference in behavior/performance. So, am I right in suspecting the only difference is a green check vs a red cross? Does using cgminer 4.7.0 solve the performance problem, whereas the #xnsub suffix merely provides visual acknowledgement? Just a question! The #xsub enables the extranonoce.subscribe subscription. That cgminer version from their website was compiled with this feature. The green check is there to indicate you have this feature enabled. I loaded it on my S3's and and enabled them, very little rejects. This is also supposed to help when they switch from using your miner or not (there is a blurb on the site about this). I no longer have my S3's or I would provide a screen shot. Are you getting a significant amount of rejects? EDIT: you could try setting up a proxy server as well. Here is the link to all of their S/W and the proxy https://www.nicehash.com/index.jsp?p=software#cgminer. I hope this sheds some light. |
|
|
|
Yes, I wonder what the new firmware will fix.
After running over night, I notice a large increase in rejects from my pool, Westhash. Any idea what if anything can be done?
Rejects are the red tips. You can see where I turned on the S5 and then later decommissioned the S3s.
Did you load your S3s with the cgminer 4.7/extranonoce.subscribe patch found on their website? If you did then that explains why the reject rate was almost nonexistent with those units. Without the patch (indicated with the green check on your Westhash status page) your miner will have a higher reject rate. I do not see a patch for the S5 units yet. Wasn't aware of that Westhash status page but now have it up. I went through my S3s installing cgminer 4.7.0 aprox two weeks ago and yet the status page shows all red crosses. I'm running the Tues Aug 26 firmware release in each (original S3+ version) and just used PuTTY to recheck cgminer version ("cgminer-api version") and each reports 4.7.0. Any idea what the problem might be? PS. Each S3 has had configuration modifications since then as well as having been rebooted, but normally the cgminer install isn't affected by that. Did you append #xnsub at the end of your miner host configuration entry? TrevorS it should look like this: stratum+tcp://stratum.westhash.com:3334#xnsub |
|
|
|
Now I am choosing between Chieftec GPM-850C (850 W, 80+ Gold, single 12V rail, but only 2 PCI-E power cables with 2 connectors each, totally 4, just what we need for S5) and Chieftec APS-850CB (same 850 W, 80+ Bronze, 2 12V rails, but it has 4 (!) separate PCI-E power cables). Both has the same price. I would like to combine them and buy a PSU with 850 W, 80+ Gold, Single 12V rail and 4 separate PCI-E power cables. For same price... But we are living in non-ideal world...
So the question is: will it be OK to use Chieftec GPM-850C with S5, keeping in mind that it has 2 PCI-E cables instead of 4?.. Cables looks solid, but...
Are you limited to what you can get at a decent cost there? I ask this because of information I read from a review that Chieftec does not manufacture the power supplies and they refer to this as a medium grade unit at best. I found some pictures of the circuit board and some of the capacitors look like they want to blow just sitting there. You don't want the power supply to takeout the miners so if you could find something a little better I would go that route. To answer your question though, the cables look adequate to handle the load but I could not find the specification of the wire gauge to verify this. |
|
|
|
Hello,
I've got eight of the SP20 now.
They all have fw version 2.5.64,
my first 6 have cgminer 4.8.0,
but my latest two that i got from the group buy have cgminer 4.7.0.
reasons?
concerns?
(i tried searching back through the thread but i didn't find anything)
I remember this one: You can also download pre-compiled binaries for Spondoolies SP20 with cgminer 4.8 and extranonoce.subscribe patch and replace stock Spondoolies SP20 cgminer (instructions included in README file): Spondoolies-SP20-cgminer-4.8.0.zip (MD5 checksum: 727bbea1dbee633a7f36825a06596c3a) found at https://www.nicehash.com/index.jsp?p=software#cgminerI have 4.7.0 on mine, that is interesting. This was used by some but not all on nice/west hash during the paycoin rush. EDIT: Some people used the proxy server for the SP units. The SP F/W does have an extranonoce flag in the settings tab now as well. |
|
|
|
The Delta fans I used both had 5-pin connectors with only 4 sockets used. They worked fine on the S1 units, only had to re-pin to match the standard pinout, I did this with a scribe, and remove the two raised barbs on the back of the connectors that were there to match the proprietary Dell computer connector. Those came off very easy with a blade. To put them on the S5, because of the location of the connectors, I had to shave the empty socket off of one of the connectors. I did this with a sharp box cutter but I am sure a xacto blade would work just as well. You can see the 5-pin connector as it hangs over the chassis connector.   |
|
|
|
@Ilan123, I put 2 delta fans on and it is rather quite now, running at 54-56c with an RPM at 2880 for both fans when I last looked. I don't have the P/N with me right now though. My SP20's are about 70db and the S5 about 60db with the new fans. It was louder than my other units before the change but I did not take a reading. Others have the stock db level from the S5 units here though. I will get particulars later like ambient room temp and the P/N for the fans later today.
Fan: Delta AFC1212DE, 12vdc, 1.6A, 3900 RPM, 192.96CFM, 51 dBA, 120mm x120mm x 38mm or equivalent. These came out of some old Dell desktops, Dell P/N: Y4574. Right now room temp 26.1C, blades at 57-55 with the fans at 3K and 3120. |
|
|
|
|
I throw this out there, did you just try a computer and a switch connected to them? You know just configure the NIC on the computer to see if you can get them on a standalone situation. Interested to find out what happened.
|
|
|
|
|
@Ilan123, I put 2 delta fans on and it is rather quite now, running at 54-56c with an RPM at 2880 for both fans when I last looked. I don't have the P/N with me right now though. My SP20's are about 70db and the S5 about 60db with the new fans. It was louder than my other units before the change but I did not take a reading. Others have the stock db level from the S5 units here though. I will get particulars later like ambient room temp and the P/N for the fans later today.
|
|
|
|
Why do I keep getting this error msg when trying to flash the Antminer s5 with the new Firmware? "tar: invalid magic tar: short read"
What am I doing wrong?
What is the name of the file you downloaded? If you download it and the name is different from SD-S5-20150107.tar.gz, it will not work. You may need to right click and save it a different way if the name is incorrect, depends on your browser. |
|
|
|
I can't resist... a bug you say, why it is "Ant" pool.  |
|
|
|
I have not seen this before and would like to know if anybody knows what this is. I did a search in this blog for any info but did not find any. I am running the Relay but did not see any association.  2015-01-07 06:43:15.305684 Sending 415 shares to 198.167.143.123:49545 It's a recently launched node updating its p2pool share chain. Thanks |
|
|
|
Yes, I wonder what the new firmware will fix.
After running over night, I notice a large increase in rejects from my pool, Westhash. Any idea what if anything can be done?
Rejects are the red tips. You can see where I turned on the S5 and then later decommissioned the S3s.
Did you load your S3s with the cgminer 4.7/extranonoce.subscribe patch found on their website? If you did then that explains why the reject rate was almost nonexistent with those units. Without the patch (indicated with the green check on your Westhash status page) your miner will have a higher reject rate. I do not see a patch for the S5 units yet. |
|
|
|
|
Show Posts
