OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[jmc1517]

Downloaded and started running cgminer-3.7.2

After about 40 minutes, 2 AMU LEDs (27/28) came on solid, but by the time I had checked the display only 1 was showing as zombie, then both LEDs went out and no zombies remained in the display. Yay!  Both AMUs had re-initialised as AMU 34/35.  This looks very promising

I hate to tempt fate, and I also hate quoting myself, but this baby's been running for 5 hours now with only the two temporary glitches reported above.  Nothing untoward in the logfile. Fingers and toes crossed.

[-ck]

Downloaded and started running cgminer-3.7.2

After about 40 minutes, 2 AMU LEDs (27/28) came on solid, but by the time I had checked the display only 1 was showing as zombie, then both LEDs went out and no zombies remained in the display. Yay!  Both AMUs had re-initialised as AMU 34/35.  This looks very promising

I hate to tempt fate, and I also hate quoting myself, but this baby's been running for 5 hours now with only the two temporary glitches reported above.  Nothing untoward in the logfile. Fingers and toes crossed.

Well, even if it isn't 100% and we still need to make changes, you can take part of the credit for your extensive testing.

Your failures were always still interesting because you routinely have one device disappear by itself followed by write errors on another device. I suspect ultimately there is a communication limitation/issue power issue or something after a fixed amount of time in your setup and only if things are running for an extended period does it reach a new steady state. The changes I made were to both increase reliability of communications on windows and to more gracefully handle failures.

[SpAcEDeViL]

Yeah.... Zombie Farm... only reboot helps to give the usb ports free....

[jmc1517]

Downloaded and started running cgminer-3.7.2

After about 40 minutes, 2 AMU LEDs (27/28) came on solid, but by the time I had checked the display only 1 was showing as zombie, then both LEDs went out and no zombies remained in the display. Yay!  Both AMUs had re-initialised as AMU 34/35.  This looks very promising

I hate to tempt fate, and I also hate quoting myself, but this baby's been running for 5 hours now with only the two temporary glitches reported above.  Nothing untoward in the logfile. Fingers and toes crossed.

Well, even if it isn't 100% and we still need to make changes, you can take part of the credit for your extensive testing.

Your failures were always still interesting because you routinely have one device disappear by itself followed by write errors on another device. I suspect ultimately there is a communication limitation/issue power issue or something after a fixed amount of time in your setup and only if things are running for an extended period does it reach a new steady state. The changes I made were to both increase reliability of communications on windows and to more gracefully handle failures.

Well I guess that did it. First permanent zombie AMU 20 after about 6 hours, and timeouts from AMU 0
Re-plugged AMU 20 (twice) but no hotplug message, and it's not being recognised, so AMU 20 remains a zombie.
Guess I'll kill it now and revert to 3.5.1 - which just to clarify does seem absolutely stable and will run for days without problems - but I'll stick a log on it anyway just to see if any temporary errors pop up.
Logfile for 3.7.2 here (without --debug):
 https://dl.dropboxusercontent.com/u/44240170/logfile-3.7.2.txt

[aneutronic]

3.7.2 ran a few minutes on the avalon at much lower hashrate then quit with a usb error.

http://pastebin.com/DQaP9S6Y

 

[SpAcEDeViL]

mh i become freeze crash, or USB crash... only a power off reboot helps... back to 3.1.1...

[-ck]

Well I guess that did it. First permanent zombie AMU 20 after about 6 hours, and timeouts from AMU 0
Re-plugged AMU 20 (twice) but no hotplug message, and it's not being recognised, so AMU 20 remains a zombie.
Guess I'll kill it now and revert to 3.5.1 - which just to clarify does seem absolutely stable and will run for days without problems - but I'll stick a log on it anyway just to see if any temporary errors pop up.
Logfile for 3.7.2 here (without --debug):
 https://dl.dropboxusercontent.com/u/44240170/logfile-3.7.2.txt

Yep same pattern. The libusb write errors are it failing to hotplug every single time. Weird fuckage but so be it.

Next test:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-allsync.exe

[techman05]

Sorry to add a new twist to cgminer but have a possible unrelated bug to play with when all is done. I tried load balancing between bitcoin and unobtainium pool and found even though I had set the unobtainium pool higher and was hashing higher, it got no shares back even though it was accepting all of them. Lesson learned for now "don't mix coin pools" even if there both compatible coins for my hardware.

Also I think the mixed difficulties fudged this up more as difficulty listed higher when trying to do both and dropped when I did just the Unobtainium(even bitcoin was the one that reported properly, the difficulty of the Unobtainium was the one shown as affected.

I'm hoping this is a bug and you can find a way for them to play together. Bitcoins fine ,but  I just want to have backup option to play with.

I'm currently running 3.6.6 on windows 7 (didn't see 3.7.2 yet but if you tripped over this and fixed it) send me a "fixed it" pm and I'll delete the post so you don't have others asking.

[Krak]

Sorry to add a new twist to cgminer but have a possible unrelated bug to play with when all is done. I tried load balancing between bitcoin and unobtainium pool and found even though I had set the unobtainium pool higher and was hashing higher, it got no shares back even though it was accepting all of them. Lesson learned for now "don't mix coin pools" even if there both compatible coins for my hardware.

Also I think the mixed difficulties fudged this up more as difficulty listed higher when trying to do both and dropped when I did just the Unobtainium(even bitcoin was the one that reported properly, the difficulty of the Unobtainium was the one shown as affected.

I'm hoping this is a bug and you can find a way for them to play together. Bitcoins fine ,but  I just want to have backup option to play with.

I'm currently running 3.6.6 on windows 7 (didn't see 3.7.2 yet but if you tripped over this and fixed it) send me a "fixed it" pm and I'll delete the post so you don't have others asking.

It's not a bug. It's covered right in the first few sentences of the readme.

[techman05]

Which read me? I didn't see it.

[Krak]

Which read me? I didn't see it.

The main one. The one that says "README." Second sentence on the third line.

Do not use on multiple blockchains at the same time!

[crazyates]

3.7.2 uploading as we speak/type. Besides, even numbers always sound more stable.

EDIT: And it's up.

I like even numbers. A lot.

Great work on this! 3.7.2 seems pretty stable.

[-ck]

Next test:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-allsync.exe

And here's the mother of all usb changes for testing:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-ymmv.exe

[-ck]

is this planed to add?

Not unless someone sends us developers one or more of them.

[Beastlymac]

is this planed to add?

Not unless someone sends us developers one or more of them.

I sent you a pm

[Jeffrey]

@ckolivas

any answer on this question? https://bitcointalk.org/index.php?topic=28402.msg3489847#msg3489847

A simple "yes" or "no" will suffice for now so at least I know where I should be looking for a solution

[-ck]

@ckolivas

any answer on this question? https://bitcointalk.org/index.php?topic=28402.msg3489847#msg3489847

A simple "yes" or "no" will suffice for now so at least I know where I should be looking for a solution

No limit except the one imposed by your operating system. On windows that's ~127. I know of someone with 2TH of erupters (yes that's not a typo) with ~208 on each linux box running them (ARM devices too so not even full power PCs).

[jmc1517]

Next test:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-allsync.exe

And here's the mother of all usb changes for testing:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-ymmv.exe

Right.  I'll get on the case!

Just for interest, the logfile from the evening/overnight run of 3.5.1 is here. No problems visible on screen and no zombies, but there are some different looking TIMEOUT messages in the log:
 https://dl.dropboxusercontent.com/u/44240170/logfile-3.5.1.txt

Just started "allsync" and I've got a zombie AMU 5 straight away, together with the usual timeouts from AMU 0.
Unplugged AMU 5 and left it out.  Now AMU 28 has gone zombie too.  I see different error messagaes in the log though (?)
I guess I'll move on to "ymmv" then...
Logfile here (without --debug):
  https://dl.dropboxusercontent.com/u/44240170/logfile-allsync.txt

[Askit2]

Hi,

Maybe a weird question, but is there a limit on the amount of Block Erupters cgminer is able to run? I'm asking this because I'm trying to set 98 up, (2x49port hubs) and it doesn't work.

When I connect hub 1 (with 49 BE's) it's fine. When I disconnect 1 and connect hub 2, it's fine. (so it's not a power issue, both are powered by an ATX supply with 30a on 5v) When I connect both of them at the same time, cgminer tells me it can't find any device and it's waiting for a hotplug.

When connect 1 full and a couple on the 2nd hub, it works. cgminer crashes on hotplug, so I have to close it, add more, and restart it. This works until I have 59. 59 is fine, 60 gives this error. I've tried putting the 60th in different usb ports (also on the laptop host itself), also other sticks, but it just won't accept  60 or more.

This is the behavior on cgminer 3.6.4, 3.7.0 and 3.7.2 (and often, 3.7.2 crashes after 1 or 2 minutes regardless of how many I've attached)

Using windows 7 64bit

Any advise?

Unless I misunderstand how you are wiring it up I would say maybe the Power supply doesn't like working at >100%.
I came to that number based on 60 erupters at .5 amp being 30A and I would have to guess the hub would waste some amount of power. I also have 0 idea how long your cables connecting to the power supply is but at 30A you should have a really short run and large cable.

But I can't figure out why one on the laptop port wouldn't work. I would have taken a shot at it earlier but I didn't see anything obvious unless you only use 1 power supply. Even then your laptop may not provide the full .5 amp without too much voltage sag. Laptops are usually not as powerful on the usb ports. But I know by spec it should work......

EDIT: by I misunderstand how you are wiring it up I mean that you say you have 2 hubs and one power supply. Possibly you wanted to convey a power supply per hub. I made the assumption that you had one power supply per hub the first time I read it as you would be woefully under powered otherwise.

[xyzzy099]

@ckolivas

any answer on this question? https://bitcointalk.org/index.php?topic=28402.msg3489847#msg3489847

A simple "yes" or "no" will suffice for now so at least I know where I should be looking for a solution

No limit except the one imposed by your operating system. On windows that's ~127. I know of someone with 2TH of erupters (yes that's not a typo) with ~208 on each linux box running them (ARM devices too so not even full power PCs).

The limit is 127 per host controller, not 127 per machine - right?  And that is not a Windows-specific limit...  It's a USB spec limit.