Do you think an EVGA 1300G2 will run one of these?
Also how loud is it? Say compared to those Dell 750's (God Damn hair dryers) you are using to power them? My girlfriend may be upset when she hears them.
GrapeApe: Easily, with a little room for OC'ing and the 1300's are quiet/silent. CG: Those Prisma's are sexy beautiful. Can't wait to get mine in house. Did ya' get my email? |
|
|
|
|
Well I hope they get off their ass and update ya'
|
|
|
|
Dear Community, Our truly apologies for the mis-understanding reported in this Support Thread. We are very willing to share the cgminer code to the Community. Just reviewed our internal resource again, there is a little mis-communicaton between Customer Service Team and R&D Department. We thought this task was done 3 weeks ago.. However, R&D Department is repacking the cgminer code and will upload it to GitHub.com in 3 hours. Any advice from the Community and Global Customers is appreciated, feel free to contact us via PM or info@bitmaintech.com. Thank you! "Fool me once, foo on you. Fool me twice, foo on me". When CK posts that he has access to the code and it's what runs in the S3 then I'm a believer. |
|
|
|
Does anyone know how Kano was able to write his own version for the S1? Does he have supporting documents? Or did he just come up with a work around? They had released the code for the driver for the S1. With a lot of polling from a big customer they eventually released the S2 driver. The S3 driver we've had no luck getting out of them. To whom it may concern: We WERE loyal BITMAIN customers owing to their shipping model, quality of product, and expeditious order fulfillment. We WERE gearing up to place a large S3+ order. That capex expenditure is now on hold.We are now investigating a large purchase of BTC Garden AM-V2's instead. 2 of which are under going testing as I type this and, so far, we are impressed. BITMAIN's illegal refusal to release current driver code for their S3 product line places the viability of mining with S3's in jeopardy. BITMAIN's current "version" of the S3 code "has more bugs than a bait store". This is exemplified by the activity in this thread. The S3's are not the profitable "plug-n-play" S1 miners we came to so dearly love. Additionally, we support the tireless, largely uncompensated, professional work done by CK and Kano. We intend on voicing our discontent with BUTMAIN's pre-order business model (and yes we got taken by BFL), illegal refusal to release code as mandated by the GPL License, and buggy S/W by exercising our purchasing dollars/BTC elsewhere. Wake up BITMAIN "you're not the only game in town". PlanetCrypto |
|
|
|
HELP! My Antminer S3's suddenly stopped. I just received them three days ago. I got them configured and running easily. (I replaced an S1, so I was already familiar with the set-up). They worked fine for the last couple of days. Today they started beeping. When I go to the GHash.IO page, I can see the pool is still up and mining away. But for some reason, I'm no longer mining. When I log into each miner, and check the miner status tab, there are no stats. I already tried to power down and re-start them. What do you recommend I look at next to trouble shoot this? Thanks.
Ghash US1 went down, don't panic. Yep, that was it. Not sure why my back-up didn't kick in (Slush pool). Maybe I had the wrong URL for that. So now I have us1.ghash.io:3333 as my first pool, and nl1.ghash.io:3334 as my second pool. The miners are buzzing again  Thanks Ghash is our first "failover" pool (i.e. Pool #2). Rather than using the URL for Ghash's US1 we use the IP. We do this because in the past DNS (google 8.8.8.8 and 8.8.4.4) have had issues correctly supplying the IP for that URL. This makes the pool appear unavailable or "dead". Below is a snapshot of our Worker #22's Miner status page and is an example of what to expect for hash rate when OC'ing to 237.5MHz with a customized Stratum Difficulty of 915.  Ghash's Netherlands server is on port 3334? Best of luck. |
|
|
|
I have a question about the stratum difficulty. I have two Antminer S3s, and I'm using the GHash.IO mining pool. Their FAQ says: The optimal settings of the stratum difficulty depends on your hash-rate:
16+ GH/s - 16 difficulty
32+ Gh/s - 32 difficulty
64+ GH/s - 64 difficulty
128+ GH/s - 128 difficulty
256+ GH/s - 256 difficulty
512+ GH/s - 512 difficulty
1 TH/s - 1024 difficulty So based on that, the setting would be 256 for each miner. Does anyone actually alter this setting in their mining pool? Or do you just keep the default setting? thank you. I don't think it's for each miner ( unless you have them as different workers). If they're set as one worker, then set it to 512 (or 1TH if you can get it stable over 1000 GH/s). If they're separate workers then yea, 256 should be fine. But Yes it works in every pool I've tried (4 or 5 different pools) They are set up with different worker IDs. I thought that was required. I didn't know I could have two miners in the same pool with the same worker ID. Does that work? Is there an advantage to doing that? No... It's hard to see/track your individual S3's performance... I'm using separate workers for each of mine S3's ...256 diff...  ZiG But Yes it works in every pool I've tried (4 or 5 different pools) Stratum difficulty can be "forced" on some pools (Ghash for instance) on others it typically is calculated and/or set by the pool (Eligius). This is normally set on an even bit boundry (16, 32, 64, 128, etc. . . .) We are currently hashing on a pool that calculates, over time, a precise difficulty for each worker that does not necessarily fall on an even bit boundry. We are seeing Stratum difficulty raging from 281.07 to 454.57 on our 12 S1's and 796.60 to 1084.24 on our 12 S3's. We see, when implementing a new miner, this pool defaults to 512 and adjusts that value over time. I think I'm seeing less stale, Dup, and low difficulty rejects as a result. But am reticent to make a definitive statement as too the observation. Does this makes sense, Oh Great and Knowledgeable Stratum Guru's? |
|
|
|
The point is, the "pool" is paying out more than it can ever take in on a PPS model so somethings up somewhere.
Trying to build a bitcoin affiliate network is what they are saying, also they claim the payout of bonus may last up until 5TH. This suggests they could end it sooner if they reach the goals for the pool. If something is to good to be true it usually is. But on the other hand, if I had the resources, and could afford it, I would do the exact same thing to promote my own business, though perhaps not as aggresive as 12.5% *Edit I am on the NY server, I only had a few minor disconnects, which may have to do with the fact the pool / company is in process of being built.stratum+tcp://east2.bitcoindigger.com:3333 STILL dead ! I'll let test miner run for 10 minutes to see if it corrects but I doubt it. Edit: Seems it was a worker issues _ instead of . I am running 1 s-3 on it seems okay. I did the VA server as I may be closer to it then the NY one. I am in the Midwest and run all 12 miners (9-S1's and 3-S3's) on the VA server. My 2 S1's are on the VA server. Did a ping to all of them and east1 (VA) had the lowest times (~80ms). I'm in Minnesota. Didn't read the previous post about not posting about pools in this thread. Won't happen again. Sorry. |
|
|
|
For a limited time this pool is currently open to the public mining community. There are no fees and a 12.5% bonus is paid out on all bitcoins mined. Totally not a scam. Yup not a scam at all, 12.5 % bonus AND there is also a tread that he says he`s giving away 1 free S3 every day for august. ya right. Is it a scam or? I mine there and the BTC payments have hit my wallet. Edit: Paying PPS now with auto payouts. Also the bonus has been paid. My buddy has won 2 of the S3 miners and should take delivery this weekend or next week. Will see if they show. Signed up. Rolled 2 S1's to test. |
|
|
|
So I got my antminer s3 running..
Its doing about 500GH/s which isn't bad..
Do you all mine with ghash.io or?
try eligius  i dont know why, but lately ghash paying a bit lower than what we estimated (calculator) or just try p2pool 8%-12% lower to be precise. Might just be bad round luck. Continuing to monitor. |
|
|
|
When your done OC'ing (editing the file) it says to reboot the system.
When back at the command line in PuTTy, can you do like a sudo reboot to reboot the system ?
I don't know in Putty (could be the same), but in Terminal, if you are still at the root prompt, type reboot, then hit enter/return. sudo not required because your logged in as root after wq in vi and back at command prompt type "reboot" and hit enter/return. |
|
|
|
Something to brighten everyones day/evening. Think this is a good sign. Difficulty w/8 period moving average.  You obviously haven't seen the projected numbers for the next difficulty adjustment. Doom AND gloom! And it's really going to screw up that nice chart. I have and watch it pretty close. Betting it'll look like that spike at the end of June then continue downward to bottom out in the single digit %'s over the next several months. One anomalous spike does not a trend make. % Difficulty increases are on and have been on a downward trend since last December (as the chart depicts and the numbers don't lie). As total network hash rate increases the manufacturing production hashing capacity becomes an ever decreasing % of total network hash rate. This will limit or throttle difficulty increases. This limit is dictated or caused by the rate that chip foundries can produce extremely custom chips (as the name implies Application Specific Integrated Chip). Now if Intel decided to jump on the bandwagon all bets are off. But the probability of that happening is lower than the quantum possibility that 1+1=3. |
|
|
|
Something to brighten everyones day/evening. Think this is a good sign. Difficulty w/8 period moving average. |
|
|
|
I predict the next difficulty increase will be 20%
I predict it to be 11% I predict 11.11% jokes aside, it will be less than 20%, but higher than 11%, I choose 14-15% I'm going with 13%-15% averaged out over time. |
|
|
|
I've yet to get one PBMining referral lol
And I guess that speaks volumes for the worth of having that in your signature. |
|
|
|
I'm home for the summer??? I never said I took the pic at my university.. Lol
I love how you all try to play detective.
Dude, give it up man. No one believes you and now youre just embarrassing yourself. I don't care if you think I'm female or male.. Lol I don't care either , but it is a very good way to do referrals. So if you are the young lady in the photo or if you took the photo of your girl friend I don't mind since I won't be using your referral link either way. Still a nice way to market pbmining Or posting that referral link might just solicit a DDOS or SSH flood attack with JennaK as the referrer. Just sayin' |
|
|
|
If anyone is interested, I'm posting the stats on my two B3 units where one is slightly over clocked and the other is stock. I picked which unit to over clock based on the fact that it had the lowest hardware errors after running for several days. Note that both units are running at a colo facility with 208 volt power and temperature control. The stock unit runs about 38 degrees and the over clocked one between 38 and 39. I'm using 2 CX750M PSUs, one per S3. I know it's overkill, but I bought them before we all found out that the S3s are not over clock friendly. I used all 4 power connectors because I wanted to experiment with over clocking from a distance without having to go to colo and move plugs around. FYI, none of the plugs or cables have ever felt warm to the touch. Here are the stats after running for almost 6 days with the above configuration: | Frequency | GH/s | HW | DiffA | DiffR | Error Rate % | | 218.75 | 441.44 | 1,732 | 50,942,208 | 63,488 | 0.00339558387456823 | | 225 | 453.36 | 8,056 | 52,252,928 | 71,680 | 0.0153938274573601 |
The delta is that the over clocked unit is providing about 2.7% more accepts with about 3.5 times more hardware errors. Prior to over clocking the hardware errors were quite a bit less than the current stock unit. But the nearly 3% increase in accepts seems worth it to me. Note that I also tried a frequency of 237.5 on the over clocked unit, but I got 824 HW errors after 20 minutes. This seemed like an insane error rate, so I backed it off to 225. Yes am interested, thanks. Especially for the stat analysis and logic behind it. On a different note, eMule has be a close friend of mine for years. Are you related? |
|
|
|
I'm guessing this is not normal?   There is Magic Smoke that is trapped inside all electronics devices. The Magic Smoke has escaped those components. You must replace those components with new components that have the Magic Smoke still imprisoned in them. Then your S3 will function again. Seriously, from your pics, looks like a couple of SMD (Surface Mount Device) resistors/capacitors experienced an excessive over current condition. Can't read the litho on the card next to the components in your pics. RXXX = a resistor, CXXX = a capacitor where XXX is the component number. Take a que-tip dipped in iso-propol alcohol and clean off the charring next to those components to be able to read the litho on the circuit card. Make sure you're well grounded when doing this, else static electricity might toast something else. To read the markings on the components that identify their values you'll likely have to look at another undamaged machine. This type of component is dirt cheap, shipping on new parts will likely exceed the cost of all those components combined. We're talking a total order $$$ amount under $25. They can be ordered from a plethora of online sources. I order a lot from Digikey cuz' they're nearby and shipping times are brief. Once obtained and still being well grounded, de-solder the burnt parts and solder in the new. Identifying why the Magic Smoke escaped those components is of particular interest to me and likely to others. |
|
|
|
What 7.5-8.0 TH/s looks like. Dissipating ~24,000 BTU. Most PSU's = EVGA 1300's, powers 3 S3's each with current to spare. Bitmain Rocks! Awesome work planet, when I saw the red cables I thought that looks familiar as I am using the same EVGA 1300 to power 3 S3's each (they fit perfectly 3 per shelf in my 42U cabinet vented to the attic ), I only have 7 units and just checked the power at the wall all 7 use almost exactly 2400watts combined. Thanks, we'll be adding more in the near future. But not until the power company runs in another 400A@240V. @ stock freq, feed by the EVGA 1300's I measure exactly 325W each. Each "rack" (purchased @ Menards ~$50) has 12 S3's. So power consumption of a single rack ends up being 3900W. The equation to convert watts to BTU is: watts * 3.15 = BTU So each rack is dissipating 12,285 BTU. 2x racks = 24,570 BTU So your 7 are dissipating 7,560 BTU or about what 2 Walmart space heaters would do. If you live in a place that has cold winters (like us in Minnesota) vent that heat in to your house and get paid to heat the house. Regarding the power discussion, as you can see in the picture only 4 of the S3's are using 4 Pcie connectors (Cuz' they were there I used'em). All but one of the S3's are clocked @ 237.5 and running just fine. |
|
|
|
What 7.5-8.0 TH/s looks like. Dissipating ~24,000 BTU. Most PSU's = EVGA 1300's, powers 3 S3's each with current to spare. Bitmain Rocks!Awesome work planet, when I saw the red cables I thought that looks familiar as I am using the same EVGA 1300 to power 3 S3's each (they fit perfectly 3 per shelf in my 42U cabinet vented to the attic ), I only have 7 units and just checked the power at the wall all 7 use almost exactly 2400watts combined. Thanks, we'll be adding more in the near future. But not until the power company runs in another 400A@240V. @ stock freq, feed by the EVGA 1300's I measure exactly 325W each. Each "rack" (purchased @ Menards ~$50) has 12 S3's. So power consumption of a single rack ends up being 3900W. The equation to convert watts to BTU is: watts * 3.15 = BTU So each rack is dissipating 12,285 BTU. 2x racks = 24,570 BTU So your 7 are dissipating 7,560 BTU or about what 2 Walmart space heaters would do. If you live in a place that has cold winters (like us in Minnesota) vent that heat in to your house and get paid to heat the house. |
|
|
|
|
Show Posts
