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

[techman05]

when I get a latency warning I always thought it was a crappy share doing it. I've got/had 3.4.3 running in rotate mode since the pool I keep wanting to use forces a restart of all mining. When that happens my room glows like a scooby doo villan and though tje show is fine I WANT TO SLEEP. I then force switch with the switch pool option and let it do its work again.
I'm running windows 7 pc with only 6 eroupters so far.

[lano1106]

There is no way to link in your own libusb any more. You have to use the statically included libusb.

Well, technically, it is not totally exact. To be more accurate, there is no more official way to link with your own libs. However, I did just that by hacking a couple of lines in the configure script.

Unless Con resort to cryptography and obfuscation, there willl always be a way :-)

If I weren't sucking with automake and autoconf script syntax, I would offer you new configure switches ie:

--with-libusb=path_to_pc_file       Use system libusb libs

I have seen a couple of projects doing it like this. ie: Provide a safe version, let the flexibility to users willing to use their own version.

Firefox come to my mind.

[Askit2]

./autogen.sh fails with a can not find makefile.in.

Maybe you're missing some packages on your distro? Check you have autoconf automake and libtool at the very least

already installed says newest version when I try again.

I just git cloned on arch RPi and it built fine so not sure what's going on... Heck it even mines fine on the bitfury plugged straight into it.

Apparently I had a id10T error. It should have worked fine. I had run it so many times since I had used cflags blah blah blah ./autogen.sh blah blah.... I forgot to add the cflags on the start..... My first way was exactly how I had been running it to use the other libusb. copy the git, ./autogen.sh, CFLAGS configure, make clean, make. When I had issues I added to ./autogen.sh but forgot the cflags. So things didn't work. As I should have expected. I am still unsure about if the seg fault will come back but it seems able to build without me messing it up.

[-ck]

What a disgrace, we've been fighting with this issue for as long as I can remember and we went to all that effort to include the least worst version of libusb statically yet it still doesn't go away. <insert frustration tag>

Here try a build with statically linked version of the latest libusbx instead please since you have a way of reproducing the issue:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Sorry, I still get it.  I can reproduce it on demand by firing up my cgminer instance for LTC mining.

Thanks for trying. It was worth a try anyway but we think we had the least worst library in there already. At this rate I may end up having to write my own USB library. Rest assured we shall continue to bash our heads against brick walls on this one.

Out of sheer desperation, I have rewritten the usb transfer functions to use asynchronous communications and implemented our own timeout mechanism within the cgminer code to cancel transfers as an experiment instead of relying on libusb. Can you please try redownloading one of those binaries listed above again to see if it makes any difference?

[zamot]

Hello,

i have the same problem with Timeout messages for all BE.

AMU1: TIMEOUT GetResults took 1531ms but was 100ms
AMU0: TIMEOUT GetResults took 1531ms but was 100ms
AMU3: TIMEOUT GetResults took 1531ms but was 100ms
AMU2: TIMEOUT GetResults took 1531ms but was 100ms

Timeout variates from few 100ms to 2000ms or more. 
Till nowi used cgminer 3.3.0 and there was no problem, when i tried 3.4.0 and now currently 3.5.0 version i got this messagess.
I run cgminer in Windows XP SP2.
Zadig drivers are installed ( otherwise i couldn't run cgminer 3.3.0 ).
USB HUB has 3.5A max output, so there is no under power problem.
I also rebooted XP before i started cgminer 3.5.0.

A number of things potentially going on. We have problems with some usb implementations on certain OSs and the libusb library we use. 

How long does it normally take before you see these errors and do all of them have it at the same time?

XP is a bit limited for USB. Try starting with just 2 BEs and increase it by one at a time (waiting long enough for the errors to normally appear) till you see the errors reappear.
If possible, try windows7 or ideally a linux to see if they go away.

This timeout messages appears randomly time based, but around 10 - 15 seconds after starting of cgminer. I tried with one BE and then i added one per one other BE's, but timeout appears with one attached BE also.
I will try with cgminer that you posted link with next post.
Unfortunaly i can not try directly on Windows 7, because i do not have all privileges to install something into.
the next ry ist with linux, but i must first install it.

[CrazyGuy]

CentOS release 6.4 (Final) x64 - cgminer 3.5.0

segmentation fault trying to when trying to limit to 1 BAS device "--usb BAS:1" , no issues with "--usb :1"

Core was generated by `/home/crazyguy/cgminer/cgminer --usb BAS:1'.
Program terminated with signal 11, Segmentation fault.
#0  0x0000003dfb084f1d in __strcasecmp_l_sse2 () from /lib64/libc.so.6

[-ck]

CentOS release 6.4 (Final) x64 - cgminer 3.5.0

segmentation fault trying to when trying to limit to 1 BAS device "--usb BAS:1" , no issues with "--usb :1"

Core was generated by `/home/crazyguy/cgminer/cgminer --usb BAS:1'.
Program terminated with signal 11, Segmentation fault.
#0  0x0000003dfb084f1d in __strcasecmp_l_sse2 () from /lib64/libc.so.6

Need more of that dump backtrace to see where the crash happened.

[CrazyGuy]

#0  0x0000003dfb084f1d in __strcasecmp_l_sse2 () from /lib64/libc.so.6
#1  0x000000000043793c in usb_initialise () at usbutils.c:3216
#2  0x000000000041b2e2 in main (argc=1, argv=<value optimized out>) at cgminer.c:7826

[CrazyGuy]

This was a move from 3.4 to 3.5 for me and I had to install the libudev-devel package to get cgminer to compile again. Perhaps there's an issue with the centos implementation of libudev-devel.

[-ck]

This was a move from 3.4 to 3.5 for me. I had to install the libudev-devel package to get cgminer to compile again. Perhaps there's an issue with the centos implementation of libudev-devel.

No, probably a typo from me on some of the code cleanups in that area. Thanks for the bug report, I will investigate. 'bt full' on a binary built with -g and without optimisations gives me the most information, for reference in case you run into a bug again in the future.

[i3lome]

Im a fan of Cgminer, is there a way to get my blade working with it. Mining Proxy and Bfg keep loosing connection.

[-ck]

Im a fan of Cgminer, is there a way to get my blade working with it. Mining Proxy and Bfg keep loosing connection.

Unfortunately not. We've never been asked to or had anything to do with the blades.

[The00Dustin]

What a disgrace, we've been fighting with this issue for as long as I can remember and we went to all that effort to include the least worst version of libusb statically yet it still doesn't go away. <insert frustration tag>

Here try a build with statically linked version of the latest libusbx instead please since you have a way of reproducing the issue:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Code:

 cgminer version 3.5.0 - Started: [2013-09-30 20:32:53]
--------------------------------------------------------------------------------
 (5s):11.47G (avg):9.541Gh/s | A:92  R:0  HW:6  WU:135.8/m
 ST: 2  SS: 0  NB: 1  LW: 211  GF: 0  RF: 0
 Connected to xxxxxxx diff 8 with stratum as user xxxx
 Block: 0003f366a3179664...  Diff:149M  Started: [20:32:53]  Best share: 70
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 AMU  0:                | 242.6M/287.2Mh/s | A:16 R:0 HW:0 WU:  4.9/m
 AMU  1:                | 262.7M/293.0Mh/s | A: 4 R:0 HW:0 WU:  9.8/m
 AMU  2:                | 238.1M/247.4Mh/s | A: 7 R:0 HW:0 WU:  8.2/m
 AMU  3:                | 247.0M/348.7Mh/s | A: 0 R:0 HW:0 WU:  1.6/m
 AMU  4:                | 239.3M/268.3Mh/s | A: 9 R:0 HW:0 WU:  4.9/m
 AMU  5:                | 241.7M/292.8Mh/s | A: 0 R:0 HW:0 WU:  4.9/m
 AMU  6:                | 266.3M/325.9Mh/s | A: 9 R:0 HW:0 WU:  6.5/m
 AMU  7:                | 215.9M/246.0Mh/s | A: 0 R:0 HW:0 WU:  3.3/m
 AMU  8:                | 250.0M/346.2Mh/s | A: 1 R:0 HW:0 WU:  6.5/m
 AMU  9:                | 263.2M/318.2Mh/s | A: 1 R:0 HW:0 WU:  4.9/m
 AMU 10:                | 271.2M/327.2Mh/s | A: 2 R:0 HW:0 WU:  8.2/m
 AMU 11:                | 236.3M/316.1Mh/s | A: 8 R:0 HW:0 WU:  3.3/m
 AMU 12:                | 197.2M/239.0Mh/s | A: 0 R:0 HW:0 WU:  3.3/m
 AMU 13:                | 250.6M/351.1Mh/s | A: 8 R:0 HW:0 WU:  3.3/m
 AMU 14:                | 214.9M/311.1Mh/s | A: 0 R:0 HW:0 WU:  0.0/m
 AMU 15:                | 231.1M/275.7Mh/s | A: 1 R:0 HW:0 WU:  4.9/m
 AMU 16:                | 235.6M/311.5Mh/s | A: 1 R:0 HW:0 WU:  1.6/m
 AMU 17:                | 225.6M/260.5Mh/s | A: 1 R:0 HW:0 WU:  3.3/m
 AMU 18:                | 201.0M/242.8Mh/s | A: 0 R:0 HW:0 WU:  3.3/m
 AMU 19:                | 260.1M/332.6Mh/s | A: 1 R:0 HW:1 WU:  3.3/m
 AMU 20:                | 309.1M/427.4Mh/s | A: 1 R:0 HW:1 WU:  1.6/m
 AMU 21:                | 219.4M/290.3Mh/s | A: 1 R:0 HW:1 WU:  3.3/m
 AMU 22:                | 267.6M/338.2Mh/s | A: 0 R:0 HW:1 WU:  6.5/m
 AMU 23:                | 245.6M/331.1Mh/s | A: 0 R:0 HW:0 WU:  4.9/m
 AMU 24:                | 240.0M/336.9Mh/s | A: 1 R:0 HW:1 WU:  6.5/m
 AMU 25:                | 270.0M/346.5Mh/s | A: 1 R:0 HW:0 WU:  6.5/m
 AMU 26:                | 215.1M/311.4Mh/s | A: 0 R:0 HW:0 WU:  0.0/m
 AMU 27:                | 215.1M/311.3Mh/s | A: 0 R:0 HW:1 WU:  0.0/m
 AMU 28:                | 256.5M/239.1Mh/s | A: 0 R:0 HW:0 WU:  9.8/m
 AMU 29:                | 243.9M/317.1Mh/s | A: 1 R:0 HW:0 WU:  3.3/m
 AMU 30:                | 230.1M/302.0Mh/s | A:17 R:0 HW:0 WU:  6.5/m
 AMU 31:                | 248.6M/268.3Mh/s | A: 1 R:0 HW:0 WU:  6.5/m
 AMU 32:                | 215.3M/311.6Mh/s | A: 0 R:0 HW:0 WU:  0.0/m
--------------------------------------------------------------------------------

 [2013-09-30 20:33:10] AMU25: TIMEOUT GetResults took 892ms but was 100ms
 [2013-09-30 20:33:10] AMU19: TIMEOUT GetResults took 892ms but was 100ms
 [2013-09-30 20:33:10] AMU17: TIMEOUT GetResults took 892ms but was 100ms
 [2013-09-30 20:33:10] AMU24: TIMEOUT GetResults took 893ms but was 100ms
 [2013-09-30 20:33:10] AMU13: TIMEOUT GetResults took 893ms but was 100ms
 [2013-09-30 20:33:10] AMU1: TIMEOUT GetResults took 893ms but was 100ms
 [2013-09-30 20:33:10] AMU0: TIMEOUT GetResults took 893ms but was 100ms
 [2013-09-30 20:33:10] AMU16: TIMEOUT GetResults took 702ms but was 100ms
 [2013-09-30 20:33:10] AMU4: TIMEOUT GetResults took 894ms but was 100ms
 [2013-09-30 20:33:10] AMU26: TIMEOUT GetResults took 894ms but was 100ms
 [2013-09-30 20:33:10] AMU10: TIMEOUT GetResults took 834ms but was 100ms
 [2013-09-30 20:33:10] AMU27: TIMEOUT GetResults took 903ms but was 100ms
 [2013-09-30 20:33:16] Accepted 0d96b852 Diff 18/8 AMU 6 pool 0
 [2013-09-30 20:33:25] Accepted 0c337ca2 Diff 20/8 AMU 0 pool 0
 [2013-09-30 20:33:26] Accepted 17860599 Diff 10/8 AMU 30 pool 0
 [2013-09-30 20:33:28] Accepted 0c127d24 Diff 21/8 AMU 11 pool 0

Sorry, I still get it.  I can reproduce it on demand by firing up my cgminer instance for LTC mining.

M

An AMU can mine LTC?  I would've expected --scrypt to be the problem, but then I can't figure how there would be accepted shares...

[-ck]

Sorry, I still get it.  I can reproduce it on demand by firing up my cgminer instance for LTC mining.

An AMU can mine LTC?  I would've expected --scrypt to be the problem, but then I can't figure how there would be accepted shares...

He means a 2nd instance of cgminer, one for scrypt while the AMUs are still mining BTC.

...and I'm still waiting for feedback on those latest windows binaries.

[kano]

Im a fan of Cgminer, is there a way to get my blade working with it. Mining Proxy and Bfg keep loosing connection.

It requires a mining proxy, cgminer (or any other miner) wouldn't mine on it - it just simply acts as a proxy for it.
The blades have their own internal ancient crappy getwork miner that you can't override.

[os2sam]

Im a fan of Cgminer, is there a way to get my blade working with it. Mining Proxy and Bfg keep loosing connection.

Have you tried mining on getwork pools?

[vulgartrendkill]

Im a fan of Cgminer, is there a way to get my blade working with it. Mining Proxy and Bfg keep loosing connection.

Have you tried mining on getwork pools?

if you use --http-port 8332 in command line and point your blade to your pc under the server box on config page eg- 192.168.1.1,192.168.1.1  BFG should pick it up.  My blades have been up and running for about a week using this method.

[Photon939]

Initial results for 3.5.0 on Raspberry Pi with Bitfury BF1 and BFL gear are underwhelming. Running overnight I woke up to the BF1s running anywhere from 0 to about 1.2 Gh/s. I restarted cgminer and things seem to pick back up. Will report the status when I get home from work

The BF1 draws power entirely from USB. How are you connecting it to an RPi ?

It is running on a powered USB hub (albeit a cheap one) with an external 4A supply running five BF1s, it ran stable fine from Ubuntu and BFGminer for a few days so the hub shouldn't be a problem

Edit - Pi is running new Raspbian release

Well that sounds nasty and you should stop using cgminer for now with that combo.

After running another day this problem has happened again. I guess I'll switch to BFGminer for a bit and see if that works better. Also the system seems to crash quite frequently. My arduino watchdog has been doing its job but it seems sometimes the BF1s don't come back online after a reboot. The BFL gear has been running perfectly, only the BF1s seem to get stuck.

[Rant2112]

I'm still having trouble getting my Block Erupter to work on anything besides 3.1.1

With 3.5.0 I get:

AMU0: TIMEOUT GetResults took 659ms but was 100ms
...
AMU0: TIMEOUT GetResults took 659ms but was 100ms

AMU0: Comms error (werr=-7 amt=0)
...
AMU0: Comms error (werr=-7 amt=0)


I think this is a known problem but posting just to be sure.   I'll continue to use 3.1.1 as it is working fine.  


FYI - I'm mining using a recent Ubuntu release running under VMWare Fusion on a Mac.  The Block Erupter is plugged into a USB2 D-Link HUB.  It is connected to a 'high speed' USB port on the Mac which should mean it is USB2.

[zamot]

Hello,

i have the same problem with Timeout messages for all BE.

AMU1: TIMEOUT GetResults took 1531ms but was 100ms
AMU0: TIMEOUT GetResults took 1531ms but was 100ms
AMU3: TIMEOUT GetResults took 1531ms but was 100ms
AMU2: TIMEOUT GetResults took 1531ms but was 100ms

Timeout variates from few 100ms to 2000ms or more.  
Till nowi used cgminer 3.3.0 and there was no problem, when i tried 3.4.0 and now currently 3.5.0 version i got this messagess.
I run cgminer in Windows XP SP2.
Zadig drivers are installed ( otherwise i couldn't run cgminer 3.3.0 ).
USB HUB has 3.5A max output, so there is no under power problem.
I also rebooted XP before i started cgminer 3.5.0.

A number of things potentially going on. We have problems with some usb implementations on certain OSs and the libusb library we use.  

How long does it normally take before you see these errors and do all of them have it at the same time?

XP is a bit limited for USB. Try starting with just 2 BEs and increase it by one at a time (waiting long enough for the errors to normally appear) till you see the errors reappear.
If possible, try windows7 or ideally a linux to see if they go away.

This timeout messages appears randomly time based, but around 10 - 15 seconds after starting of cgminer. I tried with one BE and then i added one per one other BE's, but timeout appears with one attached BE also.
I will try with cgminer that you posted link with next post.
Unfortunaly i can not try directly on Windows 7, because i do not have all privileges to install something into.
the next ry ist with linux, but i must first install it.

So, i tried with cgminer-nogpu.exe from ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and i got this :

[2013-10-01 11:36:13] Started cgminer 3.5.0
[2013-10-01 11:36:13] Loaded configuration file cgminer.conf
[2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED
[2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED
[2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED
[2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED
[2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED
[2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED
[2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED
[2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED
[2013-10-01 11:36:16] No devices detected!
[2013-10-01 11:36:16] Waiting for USB hotplug devices or press q to quit
[2013-10-01 11:36:16] Probing for an alive pool

This was try with just one BE.