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

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

[jesse11]

Any update for the settings in cgminer for Klondike K16 mining unit? Some of the guys have got them running in Ubuntu but I'm running Win7. I've tried yet I'm missing something.
I tried: -0 http://stratum.btcguild.com:3333 -u username - p x -- usb KLN: 3 --enable-klondike16

[Askit2]

Any update for the settings in cgminer for Klondike K16 mining unit? Some of the guys have got them running in Ubuntu but I'm running Win7. I've tried yet I'm missing something.
I tried: -0 http://stratum.btcguild.com:3333 -u username - p x -- usb KLN: 3 --enable-klondike16

I would only use the following.  -0 http://stratum.btcguild.com:3333 -u username - p password
--enable-klondike16 is only for when building the cgminer. I would make sure you use a version that its enabled on. Not sure what version it starts on but hopefully that helps. Also --usb KLN:3 would only be if you wanted to limit it to Klondike boards and 3 of them. I suppose you want to limit it to 3 Klondike boards.

[jmc1517]

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.

Oh don't worry, I'm sticking around!  I admire your dogged determination ckolivas, and I think/hope that I would be the same if it were my software under test.  I'll try the remaining 3 builds today and post back.  There's one advantage if you can call it that, in running 34 erupters - any faults show up quite quickly      Later...

[-ck]

Any update for the settings in cgminer for Klondike K16 mining unit? Some of the guys have got them running in Ubuntu but I'm running Win7. I've tried yet I'm missing something.
I tried: -0 http://stratum.btcguild.com:3333 -u username - p x -- usb KLN: 3 --enable-klondike16

Here's an updated build (untested) containing the latest klondike support  build into the windows binary (do not use --enable-klondike16, that's a BUILD option, not a RUN option)

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

[os2sam]

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.

I'm in the process of completely reworking my mining rig and space for the the winter.  Once I get my configuration stabilized I'll be chiming back in.

For the time being I've been using 3.4.3 fairly reliably.  It will have a problem once in a great while, but never a zombie since I got my hubs daisy chained to their liking.  The new 49 port hub seems reliable too, but I'm not up to the 40's yet, baby steps.
Thanks,
Sam

[aigeezer]

Chop8 test results: elapsed time 9.5 hours, mainly unattended, led to three failures. Two are zombies and the third reports a zero hash rate and has the LED on solidly. The former "suspect" AMU was not one of the three. Neither was its former location on the hub.

I'll test chop10 shortly.