By the way, my power blinked for a second, the UPS kept the computer on, and cgminer started saying:
[2013-11-01 17:58:14] BAL 0 usb write err:(-7) LIBUSB_ERROR_TIMEOUT
[2013-11-01 17:58:14] BAL0: RequestQueJob failed (err=-7 amt=0)
Guess it lost the connection to the Little Single. So I hotplugged the usb cable to it, and it recovered.
Wasn't sure if it was supposed to be able to recover without having to unplug/replug the usb cable, so I thought I'd mention it. But it probably had more to do with windows losing the device than cgminer, just mentioning it in case.
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 188. (Read 5805670 times)
November 01, 2013, 06:47:48 PM
November 01, 2013, 05:06:18 PM
I think I've misunderstood. Are you asking if the pool stats show ping times to the pools? If so, they don't.
Right, a round trip time from request to response.
OK, I might add that stat. Somehow.
November 01, 2013, 05:02:23 PM
Do the pool stats have a 'ping' like time to them? Or are my stats not working... I'm getting this all the time:
[Calls] => 0
[Wait] => 0
[Max] => 0
[Min] => 99999999
[Pool Calls] => 0
[Pool Attempts] => 0
[Pool Wait] => 0
[Pool Max] => 0
[Pool Min] => 99999999
[Pool Av] => 0
No delay. Backup pools often stay unset because they're never talked to after the initial testing they're alive.[Calls] => 0
[Wait] => 0
[Max] => 0
[Min] => 99999999
[Pool Calls] => 0
[Pool Attempts] => 0
[Pool Wait] => 0
[Pool Max] => 0
[Pool Min] => 99999999
[Pool Av] => 0
There's got to be some round-trip delay though? 20ms at least!
I'd like to keep an eye on ping times and swap pools if they start getting silly.
November 01, 2013, 04:59:12 PM
Do the pool stats have a 'ping' like time to them? Or are my stats not working... I'm getting this all the time:
[Calls] => 0
[Wait] => 0
[Max] => 0
[Min] => 99999999
[Pool Calls] => 0
[Pool Attempts] => 0
[Pool Wait] => 0
[Pool Max] => 0
[Pool Min] => 99999999
[Pool Av] => 0
No delay. Backup pools often stay unset because they're never talked to after the initial testing they're alive.[Calls] => 0
[Wait] => 0
[Max] => 0
[Min] => 99999999
[Pool Calls] => 0
[Pool Attempts] => 0
[Pool Wait] => 0
[Pool Max] => 0
[Pool Min] => 99999999
[Pool Av] => 0
There's got to be some round-trip delay though? 20ms at least!
I'd like to keep an eye on ping times and swap pools if they start getting silly.
November 01, 2013, 04:37:45 PM
cgminer hangs when it looses Internet connection to the pool. Even when the connection comes back cgminer wont continue, it wont even respond to key presses, you have to kill the window. This has happened with several versions currently running 3.6.1 on window 7 32bit. Is there a work around, I just lost 7hrs of mining?
November 01, 2013, 04:24:16 PM
Do the pool stats have a 'ping' like time to them? Or are my stats not working... I'm getting this all the time:
[Calls] => 0
[Wait] => 0
[Max] => 0
[Min] => 99999999
[Pool Calls] => 0
[Pool Attempts] => 0
[Pool Wait] => 0
[Pool Max] => 0
[Pool Min] => 99999999
[Pool Av] => 0
No delay. Backup pools often stay unset because they're never talked to after the initial testing they're alive. [Calls] => 0
[Wait] => 0
[Max] => 0
[Min] => 99999999
[Pool Calls] => 0
[Pool Attempts] => 0
[Pool Wait] => 0
[Pool Max] => 0
[Pool Min] => 99999999
[Pool Av] => 0
November 01, 2013, 09:34:16 AM
Do the pool stats have a 'ping' like time to them? Or are my stats not working... I'm getting this all the time:
[Calls] => 0
[Wait] => 0
[Max] => 0
[Min] => 99999999
[Pool Calls] => 0
[Pool Attempts] => 0
[Pool Wait] => 0
[Pool Max] => 0
[Pool Min] => 99999999
[Pool Av] => 0
[Calls] => 0
[Wait] => 0
[Max] => 0
[Min] => 99999999
[Pool Calls] => 0
[Pool Attempts] => 0
[Pool Wait] => 0
[Pool Max] => 0
[Pool Min] => 99999999
[Pool Av] => 0
November 01, 2013, 06:55:51 AM
May have been a coincidence but yesterday I finally updated from 3.6.4 to 3.6.6. A few hours later I found my PC was locked up, had to hold down the power button. I switched back to 3.6.4 just in case because I'm going to be away today.
Running windows 8 x64 with a BFL little single.
Running windows 8 x64 with a BFL little single.
November 01, 2013, 06:54:51 AM
Edit: Since the restart, the "to" candidate has run for seven hours with no errors or anomalies, still going strong.
Here's some more, trying to narrow it down further then please.http://ck.kolivas.org/apps/cgminer/temp/cgminer-tob.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-tor.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-tow.exe
As an aside: I've been running 3.5.1 since yesterday midday. No errors, so I'm still happy with it.
So, I've trialled the new 3 above. Got zombies fairly quickly on all of them so terminated the tests soon after they occurred (I can leave them running longer if it would help prove anything).
Results as follows:
cgminer-tob started at 09:33, first zombie at 09:37, 2nd at 9:43. Stopped at 09:44.
cgminer-tor started at 09:48, first zombie at 10:00, 2nd at 10:23. Stopped at 10:41.
cgminer-tow started at 10:45, first zombie AMU 32 after 2 minutes, but must have failed and auto-replugged (?)
as AMU 32 is now showing after AMU 33 in the table.
Logfiles here (without --debug):
https://dl.dropboxusercontent.com/u/44240170/logfile-tob.txt
https://dl.dropboxusercontent.com/u/44240170/logfile-tor.txt
https://dl.dropboxusercontent.com/u/44240170/logfile-tow.txt
Currently running cgminer-tow with --debug. Just on the off-chance of capturing an error...
Just starting to catch up to you. "tob" crashed within seconds. That unhelpful Windows message "cgminer-nogpu has stopped working". On to "tor".
Edit: AMU7 has gone zombie about 15 minutes in to "tor". I'll try "tow" now.
Edit: "cgminer-nogpu.exe has stopped working" after about 15 seconds in "tow". Back to "tob" for a while, I guess.
Edit: "tob" has a zombie on AMU6 for this run about 20 minutes in. Last time it crashed early. Tough stuff to track down.
Edit:
Weird - As I'm typing, all
Edit: Several more zombies from time to time. Another interesting pattern, unique to "tob" perhaps - I usually get the "cgminer-nogpu has stopped working" crash now when I try to restart a zombie by disconnecting either just it or its whole hub and replugging.
November 01, 2013, 06:24:30 AM
Edit: Since the restart, the "to" candidate has run for seven hours with no errors or anomalies, still going strong.
Here's some more, trying to narrow it down further then please.http://ck.kolivas.org/apps/cgminer/temp/cgminer-tob.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-tor.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-tow.exe
As an aside: I've been running 3.5.1 since yesterday midday. No errors, so I'm still happy with it.
So, I've trialled the new 3 above. Got zombies fairly quickly on all of them so terminated the tests soon after they occurred (I can leave them running longer if it would help prove anything).
Results as follows:
cgminer-tob started at 09:33, first zombie at 09:37, 2nd at 9:43. Stopped at 09:44.
cgminer-tor started at 09:48, first zombie at 10:00, 2nd at 10:23. Stopped at 10:41.
cgminer-tow started at 10:45, first zombie AMU 32 after 2 minutes, but must have failed and auto-replugged (?)
as AMU 32 is now showing after AMU 33 in the table.
Logfiles here (without --debug):
https://dl.dropboxusercontent.com/u/44240170/logfile-tob.txt
https://dl.dropboxusercontent.com/u/44240170/logfile-tor.txt
https://dl.dropboxusercontent.com/u/44240170/logfile-tow.txt
Currently running cgminer-tow with --debug. Just on the off-chance of capturing an error...
November 01, 2013, 12:53:36 AM
I'm getting a lot of;
KLNx:0 went idle before work was sent
... spam running the 3.6.6 nogpu test executable for Windows. Mining at ghash.io FWIW.
KLNx:0 went idle before work was sent
... spam running the 3.6.6 nogpu test executable for Windows. Mining at ghash.io FWIW.
October 31, 2013, 11:16:25 PM
Hey ckolivas, Thanks again 
no zombie's, I had to unplug and plug in each ASIC USB Miner till all were up and running, no problem. The K16's are Rocking
Win7 old server
Yeah, I'm Happy
no zombie's, I had to unplug and plug in each ASIC USB Miner till all were up and running, no problem. The K16's are Rocking Win7 old server
Yeah, I'm Happy
October 31, 2013, 09:54:11 PM
Edit: Since the restart, the "to" candidate has run for seven hours with no errors or anomalies, still going strong.
Here's some more, trying to narrow it down further then please.http://ck.kolivas.org/apps/cgminer/temp/cgminer-tob.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-tor.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-tow.exe
October 31, 2013, 06:25:57 PM
Latest git is not mining on my machine at all. It is detecting hardware, connecting to pools and just quit.
Good I have working exe from previous build
What hardware would that be?Good I have working exe from previous build
October 31, 2013, 05:59:47 PM
Latest git is not mining on my machine at all. It is detecting hardware, connecting to pools and just quit.
Good I have working exe from previous build
What hardware would that be?Good I have working exe from previous build
October 31, 2013, 05:47:21 PM
Latest git is not mining on my machine at all. It is detecting hardware, connecting to pools and just quit.
Good I have working exe from previous build
What hardware would that be? Good I have working exe from previous build
October 31, 2013, 05:46:48 PM
Latest git is not mining on my machine at all. It is detecting hardware, connecting to pools and just quit.
Good I have working exe from previous build
Good I have working exe from previous build
October 31, 2013, 05:28:09 PM
Are nanofurys supported by 3.6.6?
No, none of the developers have one and no one has tried to offer us one or contribute any code for one so there's no sign of there being any support for them forthcoming in cgminer. October 31, 2013, 05:03:41 PM
the 3.6.6 versio nseems super buggy
That's a super generalisation without details. 
October 31, 2013, 04:20:50 PM
the 3.6.6 versio nseems super buggy
It's working great for me and others. But not everyone. There's some factor about these machines that have problems that the authors haven't been able to pinpoint yet.
M
Jump to: