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

[aigeezer]

Thanks very much for trying all those, guys. I'll see what else I can come up with, but this will be the only way I'll be able to find it since you can reproduce it so easily.

Here's another please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-chop.exe

Starting "chop" test now. The "oh" version was still running fine with log/debug on after 4.25 hours. Looks like that pattern is holding.

I love the names for the various test versions - fun to imagine what they might stand for.

Edit: just 5 minutes into the "chop" test one LED came on for a couple of seconds but it didn't go zombie. I don't think I've ever seen that before - maybe one second at the most. May not be relevant, but it was unusual.

Edit: Breakthrough? LEDs are going on all over the place but then they go out again, often after 10 seconds or more. No zombies flagged. Every one recovers so far. Run is about 14 minutes old.

Edit: AMU 5 finally went zombie about 35 minutes into the run.

[kano]

I have a question because i dont get it to work.

I just setup some USB Erupters for mining PPC instead of PPC.

This is the command line i use right now:
cgminer -o http://stratum.d7.lt:3333 -u user -p pass

Everything runs ok but my GPU also starts to mine. What do i add to disable my GPU from mining ?

Try cgminer-nogpu instead of cgminer

Or add the -G option to the GPU version to disable GPU mining

[-ck]

Thanks very much for trying all those, guys. I'll see what else I can come up with, but this will be the only way I'll be able to find it since you can reproduce it so easily.

Here's another please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-chop.exe

Starting "chop" test now. The "oh" version was still running fine with log/debug on after 4.25 hours. Looks like that pattern is holding.

I love the names for the various test versions - fun to imagine what they might stand for.

Edit: just 5 minutes into the "chop" test one LED came on for a couple of seconds but it didn't go zombie. I don't think I've ever seen that before - maybe one second at the most. May not be relevant, but it was unusual.

Edit: Breakthrough? LEDs are going on all over the place but then they go out again, often after 10 seconds or more. No zombies flagged. Every one recovers so far. Run is about 14 minutes old.

Edit: AMU 5 finally went zombie about 35 minutes into the run.

Thanks a lot, it is suspicious that something's changing. Maybe we can combine some of these experiments then. More soon.

[-ck]

Thanks a lot, it is suspicious that something's changing. Maybe we can combine some of these experiments then. More soon.

Here's another:

http://ck.kolivas.org/apps/cgminer/temp/cgminer-cwa2.exe

Thanks!

[aigeezer]

Thanks a lot, it is suspicious that something's changing. Maybe we can combine some of these experiments then. More soon.

Here's another:

http://ck.kolivas.org/apps/cgminer/temp/cgminer-cwa2.exe

Thanks!

OK, I'll try cwa2 in a moment. "Chop" is still running. It only had two zombies despite all the bright lights. I could hot-swap both and it recovered. Run time about 1.5 hours.

Edit: the cwa2 test has been interesting. It ran for about 20 minutes with several heart-stopping LED incidents of 10-12 seconds each. All recovered though until one stayed on for even longer. I looked at the display expecting to see a zombie but instead saw the hashrate counter decrementing slowly. It took the poor thing about three minutes to get all the way down to zero, where it has stayed for a while. I'll see if I can hot-swap it now.

Edit: Yes, the display changed to zombie as soon as I unplugged it, the rate started to climb back up from zero and then the device got reallocated to AMU13. The test continues with no other quirks so far.

[-ck]

Thanks a lot, it is suspicious that something's changing. Maybe we can combine some of these experiments then. More soon.

Here's another:

http://ck.kolivas.org/apps/cgminer/temp/cgminer-cwa2.exe

Thanks!

OK, I'll try cwa2 in a moment. "Chop" is still running. It only had two zombies despite all the bright lights. I could hot-swap both and it recovered. Run time about 1.5 hours.

Edit: the cwa2 test has been interesting. It ran for about 20 minutes with several heart-stopping LED incidents of 10-12 seconds each. All recovered though until one stayed on for even longer. I looked at the display expecting to see a zombie but instead saw the hashrate counter decrementing slowly. It took the poor thing about three minutes to get all the way down to zero, where it has stayed for a while. I'll see if I can hot-swap it now.

Edit: Yes, the display changed to zombie as soon as I unplugged it, the rate started to climb back up from zero and then the device got reallocated to AMU13. The test continues with no other quirks so far.

Very interesting. Did you spot any displayed usb errors or warnings on the screen?

[aigeezer]

Very interesting. Did you spot any displayed usb errors or warnings on the screen?

Nothing at all - only the counter slowly decrementing. Since then the run continues with occasional long LED displays - about 10 seconds, but no failures. I'll probably leave it to run for about 10 more hours before I look at this thread again. It has run for about 2.25 hours so far.

Thanks!

[jmc1517]

Test results:

cgminer-chop : 2 zombies and one with zero hash count (light fully on) in about 30 minutes.

logfile (without --debug) here:
 https://dl.dropboxusercontent.com/u/44240170/logfile-chop.txt


I'll go on to cwa2 next...

Well that didn't take long. 1 zombie after only 6 minutes.

logfile (without --debug) here:
 https://dl.dropboxusercontent.com/u/44240170/logfile-cwa2.txt

Back to my "gold-standard" 3.3.1 for now then...

[aigeezer]

My cwa2 update: after 12.3 hours total run time I see two zombies and one AMU with hash-rate down to zero. No other messages. LEDs are on solid for three units, of course.

Edit: I hot-swapped all three and they all resumed hashing. The one that had been at zero changed to zombie status when it was first unplugged and recovered like the others when it was plugged back in. The run continues, looking normal now.

[-ck]

My cwa2 update: after 12.3 hours total run time I see two zombies and one AMU with hash-rate down to zero. No other messages. LEDs are on solid for three units, of course.

Thanks!

Next addition edition since both of those seemed to "help":

http://ck.kolivas.org/apps/cgminer/temp/cgminer-cwani.exe

[aigeezer]

My cwa2 update: after 12.3 hours total run time I see two zombies and one AMU with hash-rate down to zero. No other messages. LEDs are on solid for three units, of course.

Thanks!

Next addition edition since both of those seemed to "help":

http://ck.kolivas.org/apps/cgminer/temp/cgminer-cwani.exe

OK - cwani version started fine. Running now.

[jmc1517]

My cwa2 update: after 12.3 hours total run time I see two zombies and one AMU with hash-rate down to zero. No other messages. LEDs are on solid for three units, of course.

Thanks!

Next addition edition since both of those seemed to "help":

http://ck.kolivas.org/apps/cgminer/temp/cgminer-cwani.exe

I have had cgminer-cwani running for about 38 minutes, seemingly going OK.  One amu LED came on at 12:23 for a couple of seconds, then went out again (possibly due to a share taking too long to be found? AMU 4 perhaps?), so I wandered off for a while.  When I returned I had 4 zombies which appeared to all have occured at about the same time, so I have stopped the test.

logfile here (without --debug):
 https://dl.dropboxusercontent.com/u/44240170/logfile-cwani.txt

[aigeezer]

I just noticed a failure in my cwani test. One AMU unit has gone to zero hash rate and its LED is staying on. Not sure exactly when it first happened, but I'm 3.75 hours into the run.

Edit: I hot-swapped it and it's fine now. As before, the display reported a zombie as soon as I unplugged it, and it was reallocated (to AMU13) on restart. The run continues with only this one failure so far. LEDs still often come on for several seconds at a time.

Edit: A "real" zombie at last, 4.3 hours in. It happens to be the same physical AMU unit that went to zero before. Coincidence, perhaps. I'll hot swap it if I can.

[-ck]

I just noticed a failure in my cwani test. One AMU unit has gone to zero hash rate and its LED is staying on. Not sure exactly when it first happened, but I'm 3.75 hours into the run.

Edit: I hot-swapped it and it's fine now. As before, the display reported a zombie as soon as I unplugged it, and it was reallocated (to AMU13) on restart. The run continues with only this one failure so far. LEDs still often come on for several seconds at a time.

Edit: A "real" zombie at last, 4.3 hours in. It happens to be the same physical AMU unit that went to zero before. Coincidence, perhaps. I'll hot swap it if I can.

Hmm, still something I'm missing here. It's interesting that it's the same one so perhaps it's prone to some comm error which the code never recovers from.

Next please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-cwa8.exe

[PatMan]

ckolivas,

I gotta say, respect to you for the work & effort you're putting in with this winblows "buglet". I'm not a winblows user, but your efforts getting things right are highly admired my man.

Kudos.

[-ck]

Hmm, still something I'm missing here. It's interesting that it's the same one so perhaps it's prone to some comm error which the code never recovers from.

Next please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-cwa8.exe

And here's 2 more just in case you haven't played enough.

http://ck.kolivas.org/apps/cgminer/temp/cgminer-chop8.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-chop10.exe

[aigeezer]

ckolivas,

I gotta say, respect to you for the work & effort you're putting in with this winblows "buglet". I'm not a winblows user, but your efforts getting things right are highly admired my man.

Kudos.

I'm very impressed with ckolivas' patience also, and from the outset I've been afraid that it would turn out to be All My Fault. Luckily for me, jmc1517 is still in the game. Perhaps there's also a silent majority of Windows users out there somewhere watching and waiting.   
 

[aigeezer]

Hmm, still something I'm missing here. It's interesting that it's the same one so perhaps it's prone to some comm error which the code never recovers from.

Next please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-cwa8.exe

And here's 2 more just in case you haven't played enough.

http://ck.kolivas.org/apps/cgminer/temp/cgminer-chop8.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-chop10.exe

I just got back from dirtspace to find the same suspect AMU's LED on again and its hash rate reported as zero. I can't tell how long it was like that. Everything else looks OK. Total elapsed time for cwani is 8.75 hours. I'll try cwa8 in a moment and I think I'll swap "the suspect" with another to get a clue whether position on the hub is relevant.

Edit: Ten minutes into the new cwa8 run and I've noticed maybe a dozen of the 10ish-second LED-on incidents for various AMUs on each of my two daisy-chained hubs. In each case the hash rate display did not go down at all. The most recent one involved "the suspect" in its new position and it recovered like all the others. Throughout all these tests the last day or three my BAL unit has kept on hashing with no quirks.

Edit: Got the first zombie on cwa8 now about 1.5 hours into the run. Different hub than "the suspect" AMU, which happened to have two 10-ish second LED flares as I typed this, but is now back to normal. I'm getting several LED flares from random AMUs now, sort of like a meteor shower. Waited a while and they subsided. Now off to test chop8.

Edit: Grid power failure here now. Running on battery but I'll have to go offline. Back when I can.

Edit: Back after the power failure. Chop8 test has started. Looks normal so far.



 

[Karin]

Unofficial Mac binaries for 3.6.6 now posted.

cgminer for Mac OS X 3.6.6 (direct download link)
http://spaceman.ca/cgminer (website)

I haven't yet heard if this fixed BFL Jalapeños on Mac OS X 10.9, still awaiting feedback from Mac users.

[-ck]

ckolivas,

I gotta say, respect to you for the work & effort you're putting in with this winblows "buglet". I'm not a winblows user, but your efforts getting things right are highly admired my man.

Kudos.

I'm very impressed with ckolivas' patience also, and from the outset I've been afraid that it would turn out to be All My Fault. Luckily for me, jmc1517 is still in the game. Perhaps there's also a silent majority of Windows users out there somewhere watching and waiting.   
 

I'm more worried about losing my valuable victims testers before we resolve anything.