[1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff]

[pcecycle]

I am using the Beta client.

[1713579636]

1713579636

[1713579636]

1713579636

[1713579636]

1713579636

[1713579636]

1713579636

[DrHaribo]

I am using the Beta client.

And there are no errors about the Antminer producing wrong nonces or being disconnected?

[irrational]

Starting to think paying 3% to BTCGuild isn't for me (I never make use of their notifications, etc).

I was curious how everyone likes it over here at BitMinter? Especially interested in opinions from those who've mined both here and BTC Guild for a good comparison.

[pcecycle]

Yes there was an error about wrong nonce. I did go into settings and disabled rescan and so far it has been running about 11 hours without stopping.

[DrHaribo]

Yes there was an error about wrong nonce. I did go into settings and disabled rescan and so far it has been running about 11 hours without stopping.

There's probably also a "too many errors, giving up", in the logs. Meaning it began consistently producing wrong nonces or timing out, without any valid results. Perhaps it got too hot?

[Cascaders28]

I've been tinkering with the auto start features available to hopefully reduce my downtime and I have a question. My Chili miners require two starts, they error out spectacularly the first time then they'll hash just fine on the second start.

Is there any way to schedule a run once task to start them as automated devices a second time? I was able to have them auto start with the client, then start 20 seconds later, but then it tries to send them a start command every 20 second which seems less than ideal. Any help would be appreciated!

[theweiss]

Hey, is anyone on here mining in Bitminter with a Rasberry Pi?  They seem pretty awesome and it would be nice to save some power and free up the laptop I've been mining through. 

I have 3  30gh/s Butterfly Lab ASICS, a ton of Block Erupters/powered hubs and one Antminer u1.

I've read that you can mine in the Bitminter pool on these using a program called Minepeon.  Beyond that I don't know too much, I'm just reading around to see what information I can find.  I definitely want to continue mining here on Bitminter both because the DR. has been so helpful, proactive and communicative, and because its a really, pleasantly transparent pool.

Any advice is appreciated and any good threads that deal with the Rasberry Pi and Bitminter specifically would be great too.


DOC,
Any advice or warnings for mining through a Rasberry Pi?

[DrHaribo]

I've been tinkering with the auto start features available to hopefully reduce my downtime and I have a question. My Chili miners require two starts, they error out spectacularly the first time then they'll hash just fine on the second start.

Is there any way to schedule a run once task to start them as automated devices a second time? I was able to have them auto start with the client, then start 20 seconds later, but then it tries to send them a start command every 20 second which seems less than ideal. Any help would be appreciated!

It doesn't actually send any commands to the devices if they are already running. But it does print "Executing scheduled action: Start automated devices" every time in the log which is annoying.

I have attempted to fix the problem with having to start Chili devices twice in the beta. Could you try that and see if it has worked? The beta is available under the "tools" menu on the website.

DOC,
Any advice or warnings for mining through a Rasberry Pi?

I did try once on the old (256 MB memory) Rasberry Pi and I think it took about 1 minute just to start Bitminter client. But after it was running it seemed to work ok. CPU mining wasn't very fast though. I haven't tested ASIC mining - not sure if it works or not. It might start faster on the later Raspberry Pi version with more memory (512 MB).

[matrix961]

Hey, is anyone on here mining in Bitminter with a Rasberry Pi?  They seem pretty awesome and it would be nice to save some power and free up the laptop I've been mining through. 

I have 3  30gh/s Butterfly Lab ASICS, a ton of Block Erupters/powered hubs and one Antminer u1.

I've read that you can mine in the Bitminter pool on these using a program called Minepeon.  Beyond that I don't know too much, I'm just reading around to see what information I can find.  I definitely want to continue mining here on Bitminter both because the DR. has been so helpful, proactive and communicative, and because its a really, pleasantly transparent pool.

Any advice is appreciated and any good threads that deal with the Rasberry Pi and Bitminter specifically would be great too.


DOC,
Any advice or warnings for mining through a Rasberry Pi?

My one rig mining at bitminter is a raspberry pi setup with minepeon installed and running very well.

Raspberry pi version B with 512 ram
minepeon 0.2.4.5
2 x USB 2.0 high power hubs
10 x Antminer U2's, 5 on each hub (20 ghps total)

Boots up quick and starts mining automatically once configured.

The default bfgminer config runs the U2's well but I had to use the same OC settings used for the U1 to get them all runnung at the default of 2.0 ghps each consistently. Other than that all is good and the setup runs great.

[EWold]

Hey Dr,

I'm new to mining (well, off for about 6 months, now trying it again with an RPi), so I'm really not that knowledgeable about some things and I have searched this thread however my thread results were not by date, so I may not be aware of chronological updates and this thread is massive.  So, I have a few questions.  

When I resumed BTC mining I turned a perk off (the pre-pay perk) and the payouts seem to just trickle in, before they seemed to flow into my account like nuts.  I think I understand that it takes a while (in the past you said it took about 20 hours) for confirmations to confirm something, but the logged entries of deposits in my log 'seem' to be quite infrequent.  For the past 7 days I've received a total of 10 BTC deposits.  In the past, according to the logs on the website, it was not uncommon that I was getting up to 7 BTC deposits each day. In any 2 consecutive day window in the past that I sampled, I had received 10 payouts.  This week I've had this thing running for 6 of the past 7 days according to my minepeon (RPi) graphs, on one day, off one day, on for 5 straight days. I would have though that running for 5 straight days would have returned a regular deposit cycle (I'm well beyond the 20 hour window being on for 5 days) like I got 6 months ago.  Is this the nature of not using the prepay perk, fewer deposits?  (the deposits are much smaller than in the past, so its not a matter of them building up for larger but fewer deposits, OTOH, I don't know how often the BTC algorithm has halved the payouts in the past six months, maybe several times)

You had also said something else about the pre-pay perk off in regards to confirmations.  You said if and when a block get confirmed.  The 'if' caught my attention.  Is it possible that some work parts/blocks fall through the cracks or something and don't get pooled up to someone else to confirm?  That if and when caught my interest.

Thanks.

[Isuearl]

to be honest, I haven't used the client since when I started late last year....I use BFG miner to mine....it runs my blades through the proxy built in, and my USB miners in another instance....so if you want to mine with a rasberry pi you could go that route.... my caveat, I havent used a pi yet but I do know there is a BFG miner version for the pi....

[smooth]

to be honest, I haven't used the client since when I started late last year....I use BFG miner to mine....it runs my blades through the proxy built in, and my USB miners in another instance....so if you want to mine with a rasberry pi you could go that route.... my caveat, I havent used a pi yet but I do know there is a BFG miner version for the pi....

I built bfgminer for the RPi from the github source last year, and updated it a few times. No problems at all. Worked great as a proxy for my blades (until I sold them off and upgraded to newer mining gear).

[DrHaribo]

the payouts seem to just trickle in, before they seemed to flow into my account like nuts.

You get paid when blocks are found. We are a smaller part of the global hashpower now and find blocks less frequently than when you were mining previously. On average your payout is not affected by that, but there is higher variance. The difficulty is much higher than when you mined before though and that does affect everyone. Some additional info on how payouts work: https://bitcointalk.org/index.php?topic=27062.msg2769824#msg2769824

[philipma1957]

Hey Dr,

I'm new to mining (well, off for about 6 months, now trying it again with an RPi), so I'm really not that knowledgeable about some things and I have searched this thread however my thread results were not by date, so I may not be aware of chronological updates and this thread is massive.  So, I have a few questions.  

When I resumed BTC mining I turned a perk off (the pre-pay perk) and the payouts seem to just trickle in, before they seemed to flow into my account like nuts.  I think I understand that it takes a while (in the past you said it took about 20 hours) for confirmations to confirm something, but the logged entries of deposits in my log 'seem' to be quite infrequent.  For the past 7 days I've received a total of 10 BTC deposits.  In the past, according to the logs on the website, it was not uncommon that I was getting up to 7 BTC deposits each day. In any 2 consecutive day window in the past that I sampled, I had received 10 payouts.  This week I've had this thing running for 6 of the past 7 days according to my minepeon (RPi) graphs, on one day, off one day, on for 5 straight days. I would have though that running for 5 straight days would have returned a regular deposit cycle (I'm well beyond the 20 hour window being on for 5 days) like I got 6 months ago.  Is this the nature of not using the prepay perk, fewer deposits?  (the deposits are much smaller than in the past, so its not a matter of them building up for larger but fewer deposits, OTOH, I don't know how often the BTC algorithm has halved the payouts in the past six months, maybe several times)

You had also said something else about the pre-pay perk off in regards to confirmations.  You said if and when a block get confirmed.  The 'if' caught my attention.  Is it possible that some work parts/blocks fall through the cracks or something and don't get pooled up to someone else to confirm?  That if and when caught my interest.

Thanks.

stale blocks are blocks that never confirm.  basically they are an f you the btc is lost  for this  block. that happens once in a while .

[Cascaders28]

I've been tinkering with the auto start features available to hopefully reduce my downtime and I have a question. My Chili miners require two starts, they error out spectacularly the first time then they'll hash just fine on the second start.
Is there any way to schedule a run once task to start them as automated devices a second time? I was able to have them auto start with the client, then start 20 seconds later, but then it tries to send them a start command every 20 second which seems less than ideal. Any help would be appreciated!

It doesn't actually send any commands to the devices if they are already running. But it does print "Executing scheduled action: Start automated devices" every time in the log which is annoying.
I have attempted to fix the problem with having to start Chili devices twice in the beta. Could you try that and see if it has worked? The beta is available under the "tools" menu on the website.

I tried the beta this morning. On starting Chili 1 I got
2014.03.18 [8:05] Device detected on COM29: BitFORCE SC 1.0

Then this, repeated probably 30 times
2014.03.18 [8:05] BitFORCE (COM29) ERROR: Unexpected response to stage 1 or 2- stage command: ERROR: UNKNOWN

Then it ended on
2014.03.18 [8:05] BitFORCE (COM29) ERROR: BFL-incompatible Chili firmware? Retrying without ZWX command
2014.03.18 [8:05] BitFORCE (COM29) ERROR: Unexpected response to queue job pack command: INPROCESS:0

Text is the same for Chili 2 (COM31) but they did both start hashing. However for some reason it seems like the server stopped giving me work very quickly and eventually both ended on
2014.03.18 [8:05] BitFORCE (COMXX) ERROR: BitFORCE (COMXX) ran out of work. Idling…

I tried it again a bit later and this time it seems to be working. Only running for about 3 minutes but it didn’t stall out immediately either. I still get hit with the above mess in the log but they do start hashing without any additional clicking from me. I tried to set COM29 and COM31 as automated, and set the client to auto start them and while it hits both it only manages to actually start one of them when I try it that way. I may tinker with the scheduled tasks to see about getting around that.

[DrHaribo]

I was curious how everyone likes it over here at BitMinter? Especially interested in opinions from those who've mined both here and BTC Guild for a good comparison.

Best option may be to try it for a couple weeks and see how you like it.

[Grayson5]

Hi,

I just installed an Antminer S1 on my home network.  Since then I have seen my network slow significantly impacting browser, email, etc...  Has anyone else seen an impact on network performance after installing an S1?

Thanks.

[SgtMoth]

nope, i have 6 and no issues.  Do you have a wallet open?

[Amahastpl]

I have a total of 46 Antminers S1 connected to a Cisco 2960 switch and a regular $50 Netgear router.

Funny thing is my Explorer and Chrome are just fine, Opera seems to lag a little as far as browsing websites go.

Have to figure this one out one day...

[Jayjay04]

Can anyone help me setting up my antminers.
Just received supposedly 2 x U2, but they are hashing at 1.6Gh/s on the bitminter client.
How do I overclock them to at least 2Gh/s ?!
It's written everywhere that there are easy to overclock but nothing on HOW !!!

Thanks for your help.