Can You explain for me please  Sure, That is the priority level for the pool, when pool 0 fail you switch to pool 1 and if pool 1 fail you and pool 0 always ko you switch to pool 2 If you set only eligius and eligius fail you switch to nothing and you burn power  Eligius failed august the 14th, the 15th and the 18th and I switch to westlach and automatically when eligius come back the btcgarden return mining with eligius.    I hope that it helps you as well as the other forumers. @9600 : I set 340, I want a safety margin I have a CS750M PSU, I don't try over. I've been well over 1.3TH for about a half hour now. Accepted looks to be about right, my pool's front-end is down at the moment so I can't report on pool-side yet. Man I wish these miners had temp sensors. |
|
|
|
|
Because the miners are priced to fiat values over here in the US, the S3+ just became the less expensive miner to operate. This was not the case when BTC was $650 and US distributors were selling at $549/AMV2. At current prices, the S3+ shipping on the 20th is still much less expensive if you stick to the standard exponential diff. growth of 20%.
The lost revenue over the next month is null.
That said, I love my AMV2s and would love to see them come down a bit, though at this price point it may be better for BTCGarden to mine for themselves! Those BE200s were all bought when BTC was above $600, that has to effect their production cost. Even if foundries/fabs only take fiat, BTC is still being converted.
|
|
|
|
What frequency ended up being most stable at 680? I'm clocking my 8 blades tomorrow and am curious to know where you finally settled. |
|
|
|
I wonder how long we have as individuals before it doesn't make sense to hash...
It hasn't made sense to hash SCRYPT for quite some time now... |
|
|
|
|
Just received and redeemed mine! Perfect!
|
|
|
|
|
If you've still got em! Claimed!
|
|
|
|
Hi, I have set to 340  1 You must use the older firmware 1rst of july 2014 2 I use winscp to connect the RPI  3 You must edit run.sh (I use winscp)  4 You change 310 in --btcg-clks 310:3000 by something fun, I have chosen 340 5 enjoy And what are the V2 specifications, we need information please Do you know where we can get ahold of the 7/1 firmware? |
|
|
|
Does anyone have the older firmware?
I'm also looking. 7-19 does not allow for any overclock. |
|
|
|
|
Just got my AMV2x2 kit shipped and setup from Minersource. Looking to these as a more stable alternative to the S3 at the moment. 1.25th out of the box with barely any heat. What kinds of speeds are you guys seeing at 320 and 330?
|
|
|
|
Does anyone know if the --no submit stale cgminer flag works as a BMT cgminer param?
Well I've tested and it certainly works as a flag. Testing 24-hour results now. |
|
|
|
|
Does anyone know if the --no submit stale cgminer flag works as a BMT cgminer param?
|
|
|
|
Has anyone seen the next estimated next est diff level..? Next difficulty retarget occurs at block 316511.0 (eta 12.4 days): 24080944291.1 / +22.1% [est.]I know it's only estimated but even so, yikes...!  Where the hell are you seeing 22%? Even so, you can't really make any predictions on the next jump immediately after the current jump. This is when the large DCs and manufactures ramp up their farms. They inevitably turn down the their hardware about 7 days prior to the change to average out the next jump. My bet is 8-10%. |
|
|
|
So! All units are hashing over 440gh (Two over 490), but only when using a cronjob to restart the cgminer service every 1/2 hour - 1hr depending on the miner.
Regardless of how long I leave any of these guys up to "stabilize", they always fall to 390-398 after 48 hours.
There's only one thing. I am noticing a rather high number of duplicate shares poolside since starting this restart routine. (surprise)
Is there a cgminer flag among the bitmain options to clear the asic of all work upon a cgminer restart? I know the A1 miners have a similar command with '--hwreset'
Restarting every 30 minutes is a bad practice. Try replacing thermal paste grease and I think the issue will be solved. I'm pretty aware how just how shitty it is, but unfortunately after re-pasting two units I saw a decrease in running temperatures but was still experiencing a steep drop off in hash after about 25-35 minutes. One of the units will spike back up to about 470 but never enough to average out to 440 without cgminer restarts. I wish I could attribute this to poor labor skill on my part, but I'm just about 100% certain I don't suck at apply thermal paste. =/ what kind of thermal paste did u use ?? Ceramique ok.. do not use AS5 thermal paste and do not place the plate upside down like this idiot tried to do below: http://i62.tinypic.com/k9bapy.jpg[/img] check your heat sink is placed right way: http://i59.tinypic.com/2l9nubs.jpg[/img] with all those "-" it looks like you have a cooling issue on that blade. look at your plate did you place it upside down by accident ?? Hahaha, no no definitely didn't remount the plate upside down. However, if my heatsinks were machined/cast anywhere NEAR as well as the ones in that unit I probably wouldn't have any problems. |
|
|
|
Ok, so I posted a few days ago about my batch 2 S3. At stock clocks I get a huge hash drop at 2-3 hours and one chip is showing a "-" where the "O" should be. I contacted bitmain and they said to re-paste, which I did. The paste seems do have done absolutely nothing. I would rather not run it at 212 but that what it is at now, has anyone found a reproducible solution for the underperforming miners?
I have one in the same situation, it just does not like anything higher than 212. I know there are others in the same situation. On the positive side they consume less power. I did everything possible to remove thermal problems and none help. Mine is a B1 so I would just let it run. The amount of time working on them takes away from production. If you are like me you just want to get it up to speed but sometimes you just have to let one go. Look at my previous posts on this thread, you can follow my saga. My personal solution has been to institute scheduled restarts. I am now between 460-490 for about 3 days now and have the accepted shares to show. Dupes are a bit high, but that's to be expected with this config. |
|
|
|
So! All units are hashing over 440gh (Two over 490), but only when using a cronjob to restart the cgminer service every 1/2 hour - 1hr depending on the miner.
Regardless of how long I leave any of these guys up to "stabilize", they always fall to 390-398 after 48 hours.
There's only one thing. I am noticing a rather high number of duplicate shares poolside since starting this restart routine. (surprise)
Is there a cgminer flag among the bitmain options to clear the asic of all work upon a cgminer restart? I know the A1 miners have a similar command with '--hwreset'
Restarting every 30 minutes is a bad practice. Try replacing thermal paste grease and I think the issue will be solved. I'm pretty aware how just how shitty it is, but unfortunately after re-pasting two units I saw a decrease in running temperatures but was still experiencing a steep drop off in hash after about 25-35 minutes. One of the units will spike back up to about 470 but never enough to average out to 440 without cgminer restarts. I wish I could attribute this to poor labor skill on my part, but I'm just about 100% certain I don't suck at apply thermal paste. =/ what kind of thermal paste did u use ?? Ceramique |
|
|
|
So! All units are hashing over 440gh (Two over 490), but only when using a cronjob to restart the cgminer service every 1/2 hour - 1hr depending on the miner.
Regardless of how long I leave any of these guys up to "stabilize", they always fall to 390-398 after 48 hours.
There's only one thing. I am noticing a rather high number of duplicate shares poolside since starting this restart routine. (surprise)
Is there a cgminer flag among the bitmain options to clear the asic of all work upon a cgminer restart? I know the A1 miners have a similar command with '--hwreset'
Restarting every 30 minutes is a bad practice. Try replacing thermal paste grease and I think the issue will be solved. I'm pretty aware how just how shitty it is, but unfortunately after re-pasting two units I saw a decrease in running temperatures but was still experiencing a steep drop off in hash after about 25-35 minutes. One of the units will spike back up to about 470 but never enough to average out to 440 without cgminer restarts. I wish I could attribute this to poor labor skill on my part, but I'm just about 100% certain I don't suck at apply thermal paste. =/ |
|
|
|
|
So! All units are hashing over 440gh (Two over 490), but only when using a cronjob to restart the cgminer service every 1/2 hour - 1hr depending on the miner.
Regardless of how long I leave any of these guys up to "stabilize", they always fall to 390-398 after 48 hours.
There's only one thing. I am noticing a rather high number of duplicate shares poolside since starting this restart routine. (surprise)
Is there a cgminer flag among the bitmain options to clear the asic of all work upon a cgminer restart? I know the A1 miners have a similar command with '--hwreset'
|
|
|
|
|
Quick question, in the cgminer stats, there are a few different difficulty values. Diff, Diff1#, DiffA#, and DiffR#. I think I've got them all figured except for DiffR#, suggestions?
|
|
|
|
|
Is anyone experiencing an abnormally high amount of duplicate shares? I'm still seeing performance as stated, but I'm seeing a huge number of duplicates (Tens of thousands more) as compared to my S1 units.
|
|
|
|
I have a Corsair 1200W Power supply. I used to load below 1000W on +12V rails.
Recently I noticed that one of the PCI-E power supply cable overheat a lot than all the other 5 PCI-E power cables.
I tried removing all other loads and justed tried with this overheating cable for various loads in this PSU.
Did what ever swapping and switchings I could do and found it as a cable problem.
I thoroughly inspected this faulty cable for any physical damages but couldn't find any.
This cable is only started using 2 months ago and its overheating from the first moment itself.
I suspect it as a clear case for warranty claim, looking for comments regarding this or your experience if any.
Use a multi meter and check it for high resistance. edit- If its a modular cable that is. What kind of overheating are you seeing? Exactly how hot is it getting? If its only getting warm to the touch then I wouldn't worry too much. If your PSU has split rails you probably just have one that's loaded down close to max or that particular cable has different gauge wire. This is why I always cut and splice all of the connectors from any ATX or server PSU for my miners. Get rid of what I don't need, weed out the low gauge wire, keep what I want. Helps with multiple 12+ rails as you can more easily load balance between them when you're literally picking which wires you want. I know it seems like a pain in the ass, but I feel like most of you miners should have the electrical competency to cut, splice and test a 12+ power source. |
|
|
|
|
Show Posts
