Bitminter client (Windows/Linux/Mac)

[kosmokramer]

I don't have a single Icarus compatible unit, Block Erupter or otherwise, so it's a little difficult to improve support.

There's an experimental version now at: http://bitminter.com/alpha/alpha.jnlp

I'd like to know how it runs (if at all) on block erupter, actual icarus, and any other icarus compatible devices. Does it work, does it show the correct hash rate, etc.

Howdy - just discovered BitMinter recently when I got my first few Block Erupters - love it! It's been working great, but recently I ran into an issue. I have one block erupter that works fine in cgminer, but when I attempt to mine with it in BitMinter, this is reported:

"Probe of port COM5 failed: timeout"

This happens every time I try to probe that port, but again, I open up cgminer and it starts mining just fine. Any ideas?

You need to install silabs drivers.

http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

Sorry, should have clarified - I have been using the silabs drivers. BitMinter works AWESOME with my erupters, but occasionally I get one that always throws those errors and never connects. Totally understand that it's hard to troubleshoot if you don't have one

[ewibit]

Running 1.3.2 and they are block erupters.

I have an experimental alpha version at http://bitminter.com/alpha/alpha.jnlp

Maybe that works better?

I have tried both versions with the same result...
after it has worked 3 days in this constellation without problems now I have only errors
I have done replugging a few times (and yes it is a powered USB HUB..)
(LEDs are green and on one item green LED is (was) blinking)  

Code:

Icarus (ttyUSB1) ERROR: Selftest error. Expected nonce 0xFFFFFEEA but got 0xB317598E.

 Icarus (ttyUSB1) ERROR: Too many errors, giving up 
2013.06.13 [17:42] Icarus (ttyUSB3): Not getting any results. Retuning timers. 
2013.06.13 [17:49] Icarus (ttyUSB3): Not getting any results. Retuning timers. 
2013.06.13 [17:49]  Icarus (ttyUSB3) ERROR: Selftest error. Expected nonce 0x00000112 but got 0x0171DF3B.

2013.06.13 [20:50]  Icarus detection failed. Expected nonce 0x00000109 but got 0xFBFBFBFB. 
2013.06.13 [20:50]  Probe of port ttyUSB6 failed: timeout 
2013.06.13 [20:50]  Icarus (ttyUSB9) ERROR: Selftest error. Timed out at 2001 ms. 
2013.06.13 [20:50] Icarus (ttyUSB9): Tuning timers. 
2013.06.13 [20:50]  Icarus (ttyUSB9) ERROR: Selftest error. Expected nonce 0x00000109 but got 0x0000393F.

Ubuntu 12.04
anyone know what to do?
TIA

edit:
one device running has 100% miscalculations

[DrHaribo]

Sorry, should have clarified - I have been using the silabs drivers. BitMinter works AWESOME with my erupters, but occasionally I get one that always throws those errors and never connects. Totally understand that it's hard to troubleshoot if you don't have one

Does it help to move it to a different USB port? If you mine on only that device does that work?

one device running has 100% miscalculations

Did you try mining on only that one, connected directly to the computer instead of the hub? Just to rule out the hub being bad.

You could also try a different miner (I believe bfgminer works with the silabs driver), but the way it finds the wrong nonces all the time, it doesn't look good.

[btceic]

DrHaribo,
I am planning on purchasing some of the k1, k16, k64 devices, is there any reason to believe that we will not be able to use these with your system?

[DrHaribo]

DrHaribo,
I am planning on purchasing some of the k1, k16, k64 devices, is there any reason to believe that we will not be able to use these with your system?

Any info on which protocol they use? If they need a computer with miner software to run, that is.

They will run fine with the pool. But probably not with BitMinter client, depending on which protocol they use.

[Palantir13]

Running 1.3.2 and they are block erupters.

I have an experimental alpha version at http://bitminter.com/alpha/alpha.jnlp

Maybe that works better?

I get a lot of crazy errors when running the alpha, such as: negative hash rates, some miners not actually finding any blocks when they can in the stable version, and a rough time "tuning timers".

[DrHaribo]

I get a lot of crazy errors when running the alpha, such as: negative hash rates, some miners not actually finding any blocks when they can in the stable version, and a rough time "tuning timers".

Could you cut'n'paste the messages and PM them to me here, or email at operator@bitminter.com ?

[Palantir13]

I get a lot of crazy errors when running the alpha, such as: negative hash rates, some miners not actually finding any blocks when they can in the stable version, and a rough time "tuning timers".

Could you cut'n'paste the messages and PM them to me here, or email at operator@bitminter.com ?

Running the newest version of the alpha (v1.4.0 alpha5) is actually stable. Seems to be running fine on my machine now. Would you recommend continuing to run the alpha? I've got 10 of these babies and a 7950 hashing away.

EDIT: Though, I am getting errors such as:

2013.06.14 [03:19]  Icarus (COM36) ERROR: Icarus (COM36) ran out of work. Idling...

[DrHaribo]

Running the newest version of the alpha (v1.4.0 alpha5) is actually stable. Seems to be running fine on my machine now. Would you recommend continuing to run the alpha? I've got 10 of these babies and a 7950 hashing away.

EDIT: Though, I am getting errors such as:

2013.06.14 [03:19]  Icarus (COM36) ERROR: Icarus (COM36) ran out of work. Idling...

If it works ok it will become the next beta, and hopefully soon the final 1.4.0.

Hmm, is the status line at the bottom showing zero queued work at the time? (grey boxes)

[Palantir13]

Running the newest version of the alpha (v1.4.0 alpha5) is actually stable. Seems to be running fine on my machine now. Would you recommend continuing to run the alpha? I've got 10 of these babies and a 7950 hashing away.

EDIT: Though, I am getting errors such as:

2013.06.14 [03:19]  Icarus (COM36) ERROR: Icarus (COM36) ran out of work. Idling...

Hmm, is the status line at the bottom showing zero queued work at the time? (grey boxes)

Yes, sometimes the work gets very low (I usually get more work when it gets down to the 50s though), and since I have 11 devices all on this one worker, I sometimes don't get enough new work queued up fast enough.

EDIT: Other type of error I get:

2013.06.14 [03:56] Icarus (COM34): Not getting any results. Retuning timers.
2013.06.14 [03:56] Icarus (COM34): Command response 10 ms, hash rate 335.8 Mhps.

Also, the software sometimes shows wildly inaccurate hashrates, such as a USB erupter at 2000 MH/s.

[DrHaribo]

Yes, sometimes the work gets very low (I usually get more work when it gets down to the 50s though), and since I have 11 devices all on this one worker, I sometimes don't get enough new work queued up fast enough.

I guess it drops to 0 for a short moment when there is a block change (long poll). Maybe I made the code for the Icarus a bit too sensitive to that and it complains quickly.

I'll add Stratum support soon, which will eliminate that moment of rushing to get new work after a block change.

[DrHaribo]

BitMinter client v1.4.0 beta2 is ready for testing.

New since beta1:

• Corrected hashrate and runs smoother on ASICMiner Block Erupter USB
• Fixed intermittent error messages on BFL ASICs
• Better Mac OS X integration (proper screen menu and dock icon)

Please check it out:

[ewibit]

BitMinter client v1.4.0 beta2 is ready for testing.

New since beta1:

• Corrected hashrate and runs smoother on ASICMiner Block Erupter USB
• Fixed intermittent error messages on BFL ASICs
• Better Mac OS X integration (proper screen menu and dock icon)

Please check it out:

Code:

2013.06.15 [10:16] Icarus (ttyUSB0): Tuning timers. 
2013.06.15 [10:16]  Icarus (ttyUSB2) ERROR: Selftest error. Timed out at 2000 ms. 
2013.06.15 [10:16]  Icarus (ttyUSB0) ERROR: Selftest error. Timed out at 2000 ms. 
2013.06.15 [10:16]  Icarus (ttyUSB2) ERROR: Selftest error. Timed out at 2000 ms. 
2013.06.15 [10:16]  Icarus (ttyUSB0) ERROR: Selftest error. Timed out at 2000 ms. 
2013.06.15 [10:16]  Icarus (ttyUSB2) ERROR: Selftest error. Timed out at 2000 ms. 
2013.06.15 [10:16]  Icarus (ttyUSB0) ERROR: Selftest error. Timed out at 2000 ms. 
2013.06.15 [10:16]  Icarus (ttyUSB2) ERROR: Selftest error. Timed out at 2001 ms. 
2013.06.15 [10:16]  Icarus (ttyUSB0) ERROR: Selftest error. Timed out at 2000 ms. 
2013.06.15 [10:16] Icarus (ttyUSB1): Command response 4 ms, hash rate 335,9 Mhps. 
2013.06.15 [10:16]  Icarus (ttyUSB2) ERROR: Selftest error. Timed out at 2000 ms. 
2013.06.15 [10:16]  Icarus (ttyUSB0) ERROR: Selftest error. Timed out at 2000 ms. 
2013.06.15 [10:16]  Icarus (ttyUSB0) ERROR: Selftest error. Timed out at 2000 ms. 
2013.06.15 [10:16]  Icarus (ttyUSB0) ERROR: Too many errors, giving up 
2013.06.15 [10:16]  Icarus (ttyUSB2) ERROR: Selftest error. Timed out at 25000 ms.

[DrHaribo]

Code:

2013.06.15 [10:16]  Icarus (ttyUSB0) ERROR: Too many errors, giving up 

That's a lot of errors. Could it be an issue with the USB hub? Have you tried whether it works with bfgminer?

[ewibit]

That's a lot of errors. Could it be an issue with the USB hub? Have you tried whether it works with bfgminer?

a few days it has run with 7 Block erupter without Problems, then it has begun to error
it is the same hub as before, (I have changed nothing), then I tried another hub, another port, cgminer, -> always errors
(Ubuntu 12.04)

with bfgminer I have not tried yet
 

[DrHaribo]

a few days it has run with 7 Block erupter without Problems, then it has begun to error
it is the same hub as before, (I have changed nothing), then I tried another hub, another port, cgminer, -> always errors

So different miner clients, different USB ports, different USB hubs, all result in lots of errors..

I guess you could try them on a different computer, but it sounds like the devices themselves are having issues. Are they overclocked? Do they get very hot?

Does it make any difference if you just try to run 1 or 2 instead of so many at once?

[ewibit]

So different miner clients, different USB ports, different USB hubs, all result in lots of errors..

I guess you could try them on a different computer, but it sounds like the devices themselves are having issues. Are they overclocked? Do they get very hot?

Does it make any difference if you just try to run 1 or 2 instead of so many at once?

I have tried it on a notebook and it works if I connect max. 3 Sticks there (Linux + Win); they are not overclocked; - I guess it has to do with the cheap HUB's and their PSU's that only give enough current at low temperatures?!
I hope I get next week the Anker USB 3.0 HUB and then this works correctly.

[DrHaribo]

I have tried it on a notebook and it works if I connect max. 3 Sticks there (Linux + Win); they are not overclocked; - I guess it has to do with the cheap HUB's and their PSU's that only give enough current at low temperatures?!
I hope I get next week the Anker USB 3.0 HUB and then this works correctly.

Could be a power issue, yes.

I guess the best thing to do is; find out which hubs are used by people mining with 50 of those sticks. Buy the same hub.

[lenny_]

Will EVER bitminter get sorted with stability problems?

Code:

0.00 TH/s

What a surprise.

[btceic]

Will EVER bitminter get sorted with stability problems?

Code:

0.00 TH/s

What a surprise.

doc tweeted that he is getting DDOS'ed at the moment.