Bitminter client (Windows/Linux/Mac) - page 31.

DrHaribo

legendary

Activity: 2730

Merit: 1034

Needs more jiggawatts

BitMinter client version 1.4.0 is out.

Changes from 1.3.2 to 1.4.0:

Added support for BFL SC (Butterfly Labs ASIC)
Fix hashrate measurements for ASICMiner Block Erupter USB
Fix hashrate gauge being stuck on non-zero value when you stop mining while
in performance mode, then leave performance mode
Mac OS X: Fix "probe all ports" to find ASICMiner Block Erupter USB
Mac OS X: Use screen menu and dock icon, like other Mac apps
Default to scanning all ports for external devices on startup
Remove yellow and red zones and warning light on gauges
Remove green zone on gauges for devices where we can't determine stock
hashrate. BFL FPGA, BFL ASIC, Icarus-compatible devices (hashrate varies).
Recognize more devices

Try it out:

If you have issues with 1.4.0 then you can still get the previous release (1.3.2) at http://bitminter.com/client/1.3.2/bitminter.jnlp

Next up will be Stratum and backup pools.

hakock

newbie

Activity: 27

Merit: 0

Quote from: lenny_ on June 16, 2013, 02:24:23 PM

Quote from: btceic on June 16, 2013, 02:22:03 PM

Quote from: lenny_ on June 16, 2013, 02:19:35 PM

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.

Ouch...
Maybe it's time to invest some money for better service?

Or, FINALLY, implement an optional backup-pool in the software.
(Waiting for this for a long time...)(don't know if this was discussed lately, sorry if so)

Nobody can or should demand a 100% stable service. The miner and the pool are terrific enough! Nothing to complain about.
But just the opportunity to add a backup pool for these short periods with problems would be an enormous bonus for all of us.
PLEASE!!! Cry

lenny_

legendary

Activity: 1036

Merit: 1000

DARKNETMARKETS.COM

Quote from: btceic on June 16, 2013, 02:22:03 PM

Quote from: lenny_ on June 16, 2013, 02:19:35 PM

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.

Ouch...
Maybe it's time to invest some money for better service?

btceic

sr. member

Activity: 392

Merit: 250

♫ A wave came crashing like a fist to the jaw ♫

Quote from: lenny_ on June 16, 2013, 02:19:35 PM

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.

lenny_

legendary

Activity: 1036

Merit: 1000

DARKNETMARKETS.COM

Will EVER bitminter get sorted with stability problems?

Code:

0.00 TH/s

What a surprise.

DrHaribo

legendary

Activity: 2730

Merit: 1034

Needs more jiggawatts

Quote from: ewibit on June 15, 2013, 07:05:50 PM

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. Wink

ewibit

legendary

Activity: 2955

Merit: 1049

Quote from: DrHaribo on June 15, 2013, 05:19:48 PM

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

legendary

Activity: 2730

Merit: 1034

Needs more jiggawatts

Quote from: ewibit on June 15, 2013, 03:09:54 PM

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

legendary

Activity: 2955

Merit: 1049

Quote from: DrHaribo on June 15, 2013, 02:21:26 PM

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

legendary

Activity: 2730

Merit: 1034

Needs more jiggawatts

Quote from: ewibit on June 15, 2013, 03:16:41 AM

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

legendary

Activity: 2955

Merit: 1049

Quote from: DrHaribo on June 14, 2013, 05:49:49 PM

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

legendary

Activity: 2730

Merit: 1034

Needs more jiggawatts

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:

DrHaribo

legendary

Activity: 2730

Merit: 1034

Needs more jiggawatts

Quote from: Palantir13 on June 14, 2013, 05:48:39 AM

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.

Palantir13

newbie

Activity: 38

Merit: 0

Quote from: DrHaribo on June 14, 2013, 05:29:13 AM

Quote from: Palantir13 on June 14, 2013, 05:16:07 AM

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

legendary

Activity: 2730

Merit: 1034

Needs more jiggawatts

Quote from: Palantir13 on June 14, 2013, 05:16:07 AM

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

newbie

Activity: 38

Merit: 0

Quote from: DrHaribo on June 13, 2013, 06:47:00 PM

Quote from: Palantir13 on June 13, 2013, 06:11:04 PM

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 [email protected] ?

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

legendary

Activity: 2730

Merit: 1034

Needs more jiggawatts

Quote from: Palantir13 on June 13, 2013, 06:11:04 PM

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 [email protected] ?

Palantir13

newbie

Activity: 38

Merit: 0

Quote from: DrHaribo on June 11, 2013, 04:07:48 PM

Quote from: Palantir13 on June 11, 2013, 02:10:03 PM

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

legendary

Activity: 2730

Merit: 1034

Needs more jiggawatts

Quote from: btceic on June 13, 2013, 05:39:03 PM

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.

btceic

sr. member

Activity: 392

Merit: 250

♫ A wave came crashing like a fist to the jaw ♫

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?

Topic: Bitminter client (Windows/Linux/Mac) - page 31. (Read 654946 times)