Bitcoin Forum
July 20, 2018, 10:57:12 AM *
News: Latest stable version of Bitcoin Core: 0.16.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 [660] 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 ... 847 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.10.0  (Read 5756952 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
jmc1517
Jr. Member
*
Offline Offline

Activity: 56
Merit: 0


View Profile
October 31, 2013, 12:46:47 PM
 #13181

ckolivas, I think you may be on to something here with the "to" build.  It seems to be the best so far, but not stable like the 3.5.1 build.

I had it running for 1 hour 20 mins before a zombie AMU 29 appeared, which in itself is longer than the other tests have managed.  However, I checked the logfile and found that the zombie was preceded by LIBUSB_ERROR_TIMEOUTs from AMU 20 and it was followed by repeated LIBUSB_ERROR_TIMEOUTs from AMU 0.  Once the errors from AMU 0 start, there appears to be a permanent condition such they never stop.
Thanks. What was the initial timeout error? Did it say whether it was a write or a read?
All "write" errors in the whole log - including 10 from AMU 20 at 11:44 (probably a red-herring) then:

 [2013-10-31 11:46:28] AMU 29 SendWork usb write err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2013-10-31 11:46:28] AMU29: Comms error (werr=-4 amt=0)
 [2013-10-31 11:46:28] AMU 29 failure, disabling!
 [2013-10-31 11:46:28] Thread 29 being disabled

Edit: logfile here:
 https://dl.dropboxusercontent.com/u/44240170/logfile-to.txt
1532084232
Hero Member
*
Offline Offline

Posts: 1532084232

View Profile Personal Message (Offline)

Ignore
1532084232
Reply with quote  #2

1532084232
Report to moderator
1532084232
Hero Member
*
Offline Offline

Posts: 1532084232

View Profile Personal Message (Offline)

Ignore
1532084232
Reply with quote  #2

1532084232
Report to moderator
1532084232
Hero Member
*
Offline Offline

Posts: 1532084232

View Profile Personal Message (Offline)

Ignore
1532084232
Reply with quote  #2

1532084232
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1532084232
Hero Member
*
Offline Offline

Posts: 1532084232

View Profile Personal Message (Offline)

Ignore
1532084232
Reply with quote  #2

1532084232
Report to moderator
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2590
Merit: 1111


Ruu \o/


View Profile WWW
October 31, 2013, 12:49:22 PM
 #13182

ckolivas, I think you may be on to something here with the "to" build.  It seems to be the best so far, but not stable like the 3.5.1 build.

I had it running for 1 hour 20 mins before a zombie AMU 29 appeared, which in itself is longer than the other tests have managed.  However, I checked the logfile and found that the zombie was preceded by LIBUSB_ERROR_TIMEOUTs from AMU 20 and it was followed by repeated LIBUSB_ERROR_TIMEOUTs from AMU 0.  Once the errors from AMU 0 start, there appears to be a permanent condition such they never stop.
Thanks. What was the initial timeout error? Did it say whether it was a write or a read?
All "write" errors in the whole log - including 10 from AMU 20 at 11:44 (probably a red-herring) then:

 [2013-10-31 11:46:28] AMU 29 SendWork usb write err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2013-10-31 11:46:28] AMU29: Comms error (werr=-4 amt=0)
 [2013-10-31 11:46:28] AMU 29 failure, disabling!
 [2013-10-31 11:46:28] Thread 29 being disabled

-4 really is the system telling us the device has effectively gone. That's quite different to timeouts, and in fact has been in every one of your logs (appreciate you having posted them by the way). I honestly don't know what this means but it's a very different failure to some kind of runaway process that never times out.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
jmc1517
Jr. Member
*
Offline Offline

Activity: 56
Merit: 0


View Profile
October 31, 2013, 12:55:41 PM
 #13183

ckolivas, I think you may be on to something here with the "to" build.  It seems to be the best so far, but not stable like the 3.5.1 build.

I had it running for 1 hour 20 mins before a zombie AMU 29 appeared, which in itself is longer than the other tests have managed.  However, I checked the logfile and found that the zombie was preceded by LIBUSB_ERROR_TIMEOUTs from AMU 20 and it was followed by repeated LIBUSB_ERROR_TIMEOUTs from AMU 0.  Once the errors from AMU 0 start, there appears to be a permanent condition such they never stop.
Thanks. What was the initial timeout error? Did it say whether it was a write or a read?
All "write" errors in the whole log - including 10 from AMU 20 at 11:44 (probably a red-herring) then:

 [2013-10-31 11:46:28] AMU 29 SendWork usb write err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2013-10-31 11:46:28] AMU29: Comms error (werr=-4 amt=0)
 [2013-10-31 11:46:28] AMU 29 failure, disabling!
 [2013-10-31 11:46:28] Thread 29 being disabled

-4 really is the system telling us the device has effectively gone. That's quite different to timeouts, and in fact has been in every one of your logs (appreciate you having posted them by the way). I honestly don't know what this means but it's a very different failure to some kind of runaway process that never times out.
Yes it does seem strange.  There are timeouts from a device, then some *other* device goes AWOL without any notice whatsoever.  Anyway, I've now posted the entire logfile if you want to have a look at it.  See Edit* in previous post.
Karin
Member
**
Offline Offline

Activity: 109
Merit: 10



View Profile WWW
October 31, 2013, 02:18:19 PM
 #13184

I'm still getting reports from Mac users that 3.6.4 through 3.6.6 won't work with BFL Jalapeños, returning the following line:

Code:
BitForceSC detect (29:6) failed to initialise (incorrect device?)

This only occurs in the new operating system version, Mac OS X 10.9, aka Mavericks, which was a free upgrade for all Mac users.  OS 10.8 and lower work fine.

I wish I could do more to help test, but --usb-dump 0 and --verbose both do not return any additional information.  If there is anything else I can try, please let me know.  Perhaps I'll have them work back through cgminer releases and my Mac binaries (which had different libusb version up until recently when you started including them).

Easiest to use bitcoin/litecoin miner for Mac: AsteroidApp.com | @AsteroidApp | Bitcointalk forum thread
Unofficial cgminer for Mac OS X | sgminer for Mac OS X
forzendiablo
Legendary
*
Offline Offline

Activity: 1526
Merit: 1000


the grandpa of cryptos


View Profile
October 31, 2013, 08:20:19 PM
 #13185

the 3.6.6 versio nseems super buggy

yolo
Aggrophobia
Hero Member
*****
Offline Offline

Activity: 952
Merit: 1000



View Profile
October 31, 2013, 08:23:40 PM
 #13186

Are nanofurys supported by 3.6.6?
mdude77
Legendary
*
Offline Offline

Activity: 1540
Merit: 1001



View Profile
October 31, 2013, 09:20:50 PM
 #13187

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

I mine at Kano's Pool because it pays the best and is completely transparent!  Come join me!
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2590
Merit: 1111


Ruu \o/


View Profile WWW
October 31, 2013, 10:03:41 PM
 #13188

the 3.6.6 versio nseems super buggy
That's a super generalisation without details.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2590
Merit: 1111


Ruu \o/


View Profile WWW
October 31, 2013, 10:28:09 PM
 #13189

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.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
rav3n_pl
Legendary
*
Offline Offline

Activity: 1360
Merit: 1000


Don`t panic! Organize!


View Profile WWW
October 31, 2013, 10:46:48 PM
 #13190

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 Smiley

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
Some stuff on https://github.com/Rav3nPL/
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2590
Merit: 1111


Ruu \o/


View Profile WWW
October 31, 2013, 10:47:21 PM
 #13191

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 Smiley

What hardware would that be?

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
rav3n_pl
Legendary
*
Offline Offline

Activity: 1360
Merit: 1000


Don`t panic! Organize!


View Profile WWW
October 31, 2013, 10:59:47 PM
 #13192

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 Smiley

What hardware would that be?
2x usb erupter and 1x BFL 30GH/s directly to mobo.

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
Some stuff on https://github.com/Rav3nPL/
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2590
Merit: 1111


Ruu \o/


View Profile WWW
October 31, 2013, 11:25:57 PM
 #13193

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 Smiley

What hardware would that be?
2x usb erupter and 1x BFL 30GH/s directly to mobo.

How very odd, I don't think any of the code for those specifically was changed, nor for windows. You sure you're building it ok for your devices if you're building it yourself?

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2590
Merit: 1111


Ruu \o/


View Profile WWW
November 01, 2013, 02:54:11 AM
 #13194

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

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
jesse11
Sr. Member
****
Offline Offline

Activity: 327
Merit: 250


Ants Rock


View Profile
November 01, 2013, 04:16:25 AM
 #13195

Hey ckolivas, Thanks again  Grin   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  Grin
Win7  old server

 Yeah, I'm Happy  Grin

Mining with: BE's,BE Cubes, K16's, AntMiners U1's and AntMiners S1's
Xian01
Legendary
*
Offline Offline

Activity: 1386
Merit: 1005


Ø1Ø11ØØØ


View Profile
November 01, 2013, 05:53:36 AM
 #13196

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.

 
jmc1517
Jr. Member
*
Offline Offline

Activity: 56
Merit: 0


View Profile
November 01, 2013, 11:24:30 AM
 #13197

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...
 
aigeezer
Legendary
*
Offline Offline

Activity: 1426
Merit: 1009


Cryptanalyst castrated by his government, 1952


View Profile
November 01, 2013, 11:54:51 AM
 #13198

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: just noticed (2 hours in to "tob" run) that there is no LED on, even though AMU6 is still reported as zombie. That's a first, I think. Sorry - unit wasn't into socket far enough.

Weird - As I'm typing, all but one (see above) of the LEDs came on solid and the BAL fan has slowed. The display is still updating normally, it seems and everything claims to be hashing. I don't trust it though, so I'll restart it.

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.




ksenter
Member
**
Offline Offline

Activity: 90
Merit: 10


View Profile
November 01, 2013, 11:55:51 AM
 #13199

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.
P_Shep
Legendary
*
Offline Offline

Activity: 1176
Merit: 1000


View Profile
November 01, 2013, 02:34:16 PM
 #13200

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


Pages: « 1 ... 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 [660] 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 ... 847 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!