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

[kano]

It's a new rule in the latest gcc that fails the DRIVER_ADD_COMMAND macro in miner.h

A quick work around so you can compile miner.h and usbutils.c is to change 2 places in miner.h and 1 place in usbutils.c

Firstly:
https://github.com/ckolivas/cgminer/blob/master/miner.h#L236

Code:

#define FPGA_PARSE_COMMANDS(DRIVER_ADD_COMMAND) \
        DRIVER_ADD_COMMAND(bitforce) \
        DRIVER_ADD_COMMAND(modminer)

change the above #define to just be:

Code:

#define FPGA_PARSE_COMMANDS(DRIVER_ADD_COMMAND)

(note remove the '\' on the end also)

and Secondly:
https://github.com/ckolivas/cgminer/blob/master/miner.h#L236

Code:

#define ASIC_PARSE_COMMANDS(DRIVER_ADD_COMMAND) \
.
.
.

remove all the driver lines below it that you didn't include in your ./configure command.

e.g. if you
CFLAGS="-O2 -Wall -march=native" ./configure --enable-icarus

Then the changed result would just be:

Code:

#define ASIC_PARSE_COMMANDS(DRIVER_ADD_COMMAND) \
        DRIVER_ADD_COMMAND(icarus)

(a '\' after every line but the last line)

Thirdly in usbutils.c
https://github.com/ckolivas/cgminer/blob/master/usbutils.c#L3744

Remove all the "case DRIVER_*" lines but the ones you compiled in e.g. for only icarus, change it to just be:

Code:

               switch (cgpu->drv->drv_id) {
                        case DRIVER_icarus:
                                DEVWLOCK(cgpu, pstate);
                                release_cgpu(cgpu);
                                DEVWUNLOCK(cgpu, pstate);
                                count++;
                                break;
                        default:
                                break;
                }

[Polyatomic]

Could also try building with clang its available in EPEL.

Code:

milton@milton:~/temp/cgminer$ clang --version
clang version 3.8.0 (tags/RELEASE_380/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

buildlog here: http://dpaste.com/3Z7962Z
got it going with some old gear here:
 

Code:

cgminer version 4.9.2 - Started: [2016-07-16 12:24:27.338]
--------------------------------------------------------------------------------
 (5s):37.26G (1m):37.85G (5m):24.31G (15m):11.01G (avg):37.62Gh/s
 A:2000  R:0  HW:2  WU:525.1/m
 Connected to stratum.ckpool.org diff 1K with stratum as user 1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ.0
 Block: 4454ec80...  Diff:213G  Started: [12:25:55.222]  Best share: 1.71K
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
  0: ANU 0       : 250MHz                  | 3.301G / 1.926Gh/s WU:26.9/m
  1: ANU 1       : 250MHz                  | 3.030G / 2.105Gh/s WU:29.4/m
  2: ANU 2       : 250MHz                  | 1.461G / 2.270Gh/s WU:31.7/m
  3: ANU 3       : 250MHz                  | 2.177G / 1.678Gh/s WU:23.5/m
  4: ANU 4       : 250MHz                  | 2.614G / 2.174Gh/s WU:30.4/m
  5: ANU 5       : 250MHz                  | 1.917G / 1.912Gh/s WU:26.7/m
  6: ANU 6       : 250MHz                  | 2.579G / 2.022Gh/s WU:28.3/m
  7: ANU 7       : 250MHz                  | 1.733G / 1.555Gh/s WU:21.7/m
  8: ANU 8       : 250MHz                  | 950.8M / 1.926Gh/s WU:26.9/m
  9: ANU 9       : 250MHz                  | 3.413G / 1.857Gh/s WU:26.0/m
 10: ANU 10      : 250MHz                  | 2.224G / 2.174Gh/s WU:30.4/m
 11: ANU 11      : 250MHz                  | 2.550G / 2.022Gh/s WU:28.3/m
 12: ANU 12      : 250MHz                  | 1.348G / 1.857Gh/s WU:26.0/m
 13: ANU 13      : 250MHz                  | 5.615G / 2.201Gh/s WU:30.8/m
 14: ANU 14      : 250MHz                  | 2.573G / 2.009Gh/s WU:28.1/m
 15: ANU 15      : 250MHz                  | 2.950G / 1.775Gh/s WU:24.8/m
 16: ANU 16      : 250MHz                  | 2.231G / 1.981Gh/s WU:27.7/m
 17: ANU 17      : 250MHz                  | 2.598G / 1.981Gh/s WU:27.7/m
 18: ANU 18      : 250MHz                  | 2.181G / 2.174Gh/s WU:30.0/m
--------------------------------------------------------------------------------
 [2016-07-16 12:24:05.797] Started cgminer 4.9.2
 [2016-07-16 12:24:26.338] Probing for an alive pool
 [2016-07-16 12:24:26.912] Pool 0 difficulty changed to 1000
 [2016-07-16 12:24:27.182] Pool 0 message: Authorised, welcome to solo.ckpool.org 1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ!
 [2016-07-16 12:24:27.339] Network diff set to 213G
 [2016-07-16 12:25:55.222] Stratum from pool 0 detected new block at height 420910
 [2016-07-16 12:27:14.942] Pool 0 message: New best ever share for user: 1100.238928
 [2016-07-16 12:27:14.942] Stratum reconnect requested from pool 0 to stratum.ckpool.org:443
 [2016-07-16 12:27:15.873] Pool 0 difficulty changed to 1000
 [2016-07-16 12:27:16.100] Stratum from pool 0 requested work restart
 [2016-07-16 12:27:16.101] Pool 0 message: Authorised, welcome to solo.ckpool.org 1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ!
 [2016-07-16 12:27:50.230] Accepted 400ca180 Diff 1.02K/1000 ANU 13
 [2016-07-16 12:28:58.395] Pool 0 message: New best ever share for user: 1713.233558
 [2016-07-16 12:28:58.395] Accepted 264091fc Diff 1.71K/1000 ANU 4

[Buchi-88]

I have an problem with the cgminer and th U3, anyone have an idea?

cgminer version 4.9.2 - Started: [2016-07-30 23:57:50.402]
--------------------------------------------------------------------------------
 (5s):1.349M (1m):9.538G (5m):28.75G (15m):18.21G (avg):43.79Gh/s
 A:4898  R:0  HW:4  WU:612.0/m
 Connected to multiple pools with block change notify
 Block: 6084db13...  Diff:2.52M  Started: [00:03:33.486]  Best share: 16.1K
--------------------------------------------------------------------------------
 USB management Pool management Settings Display options Quit
 0: AU3 0       : 225MHz 775mV            | 1.349M / 43.79Gh/s WU:612.0/m
--------------------------------------------------------------------------------
 [2016-07-31 00:06:45.165] AU3 0: Idle for more than 60 seconds, declaring SICK!
 [2016-07-31 00:06:45.167] AU3 0: Attempting to restart

 

[-ck]

I have an problem with the cgminer and th U3, anyone have an idea?

cgminer version 4.9.2 - Started: [2016-07-30 23:57:50.402]
--------------------------------------------------------------------------------
 (5s):1.349M (1m):9.538G (5m):28.75G (15m):18.21G (avg):43.79Gh/s
 A:4898  R:0  HW:4  WU:612.0/m
 Connected to multiple pools with block change notify
 Block: 6084db13...  Diff:2.52M  Started: [00:03:33.486]  Best share: 16.1K
--------------------------------------------------------------------------------
 USB management Pool management Settings Display options Quit
 0: AU3 0       : 225MHz 775mV            | 1.349M / 43.79Gh/s WU:612.0/m
--------------------------------------------------------------------------------
 [2016-07-31 00:06:45.165] AU3 0: Idle for more than 60 seconds, declaring SICK!
 [2016-07-31 00:06:45.167] AU3 0: Attempting to restart

 

Looks typical of the U3, it's a steaming pile of shit and it's started failing for you.

[Buchi-88]

I have an problem with the cgminer and th U3, anyone have an idea?

cgminer version 4.9.2 - Started: [2016-07-30 23:57:50.402]
--------------------------------------------------------------------------------
 (5s):1.349M (1m):9.538G (5m):28.75G (15m):18.21G (avg):43.79Gh/s
 A:4898  R:0  HW:4  WU:612.0/m
 Connected to multiple pools with block change notify
 Block: 6084db13...  Diff:2.52M  Started: [00:03:33.486]  Best share: 16.1K
--------------------------------------------------------------------------------
 USB management Pool management Settings Display options Quit
 0: AU3 0       : 225MHz 775mV            | 1.349M / 43.79Gh/s WU:612.0/m
--------------------------------------------------------------------------------
 [2016-07-31 00:06:45.165] AU3 0: Idle for more than 60 seconds, declaring SICK!
 [2016-07-31 00:06:45.167] AU3 0: Attempting to restart

 

Looks typical of the U3, it's a steaming pile of shit and it's started failing for you.

THX, also no chance to a successful run?

[-ck]

THX, also no chance to a successful run?

Let it cool down, try a lower voltage and then start lowering the clock speed on each startup. You might find a speed where it works again, or half works, or it may never work again. They're just not very reliable and don't have much of a life expectancy.

[Buchi-88]

THX, also no chance to a successful run?

Let it cool down, try a lower voltage and then start lowering the clock speed on each startup. You might find a speed where it works again, or half works, or it may never work again. They're just not very reliable and don't have much of a life expectancy.

THX, i will test at next ry with this settings:

"au3-freq" : "200",
"au3-volt" : "750",

 

[KyrosKrane]

Just a quick compliment to CK, Kano, and the other cgminer devs. I recently rebuilt my mining rig based on a Raspberry Pi and a few Asicminer Block Erupters I still had. One compilation with appropriate flags later, and cgminer was happily chomping away and telling me I haven't found a block yet! It's pretty impressive to have software continue to work with ancient hardware in an environment as fast-moving as bitcoin. Major props and thanks!

[vayvanne]

Hi folks. In expect of bitcoin core v0.13 with segwit, will the cgminer be updated in part of solo mining? Guess that there may be also a changes in RPC part of bitcoin core.

[-ck]

Hi folks. In expect of bitcoin core v0.13 with segwit, will the cgminer be updated in part of solo mining? Guess that there may be also a changes in RPC part of bitcoin core.

Unlikely. The demand and utility for plain cgminer and the need for solo mining to work on it these days is somewhat pointless so there's no desire on my part to provide said update unless someone wants to contribute code pushes it to git and asks me to pull their request. The only new hardware coming out that will use official cgminer code will be upcoming avalon hardware and that will be running on low power controllers that won't be capable of solo mining in any meaningful capacity.

[andrew0187]

Hi. I am installing cgminer on my Pi and im following this guide: https://www.youtube.com/watch?v=a8kN9GDsB0U . I'm having some trouble when I run the "sudo ./autogen.sh" command. I get an error Any suggestions?

Code:

pi@raspberrypi:~/cgminer $ sudo ./autogen.sh
./autogen.sh: 6: ./autogen.sh: autoreconf: not found

[kano]

Hi. I am installing cgminer on my Pi and im following this guide: https://www.youtube.com/watch?v=a8kN9GDsB0U . I'm having some trouble when I run the "sudo ./autogen.sh" command. I get an error Any suggestions?

Code:

pi@raspberrypi:~/cgminer $ sudo ./autogen.sh
./autogen.sh: 6: ./autogen.sh: autoreconf: not found

We obviously have nothing to do with that video.

Read the README and it will tell you that you didn't install everything you need to install.

[CrystalmETH]

thanks for sharing, runs good. Will update tonight as I'm not known with this software.

[SmallVern]

Got it set up on my rig, thanks!

[michelem]

Anyone know how to send the API command to change miner frequency?

I'm trying sending the command "setconfig" with params like this "bitmain-freq,400", but it sends me an error config not found.

[kano]

Anyone know how to send the API command to change miner frequency?

I'm trying sending the command "setconfig" with params like this "bitmain-freq,400", but it sends me an error config not found.

That depends on the mining device and if there is implemented code to do that.
If it's someone else's driver they added to a fork of cgminer, I'd doubt it's been implemented.

[Rufus_Lenhador]

What should I do when I get this error?

Code:

[2016-09-28 14:04:13.329] Started cgminer 4.9.2
[2016-09-28 14:03:12.815] ICA 0 usb transfer err:(-9) LIBUSB_ERROR_PIPE
[2016-09-28 14:03:12.815] FAIL: USB get_lock not found (2:63)

Using an Avalon Nano miner.

[kano]

What should I do when I get this error?

Code:

[2016-09-28 14:04:13.329] Started cgminer 4.9.2
[2016-09-28 14:03:12.815] ICA 0 usb transfer err:(-9) LIBUSB_ERROR_PIPE
[2016-09-28 14:03:12.815] FAIL: USB get_lock not found (2:63)

Using an Avalon Nano miner.

Probably an incorrect libusb version rather than the libusb code we provide ...
Or an OS that doesn't support the USB locking we use ... or ... ?

[andreysmol]

Hello CGMiner!!!
I have mining "AntMiner U3"
I download and going mining on site very good and income bitcoin normal.
Now problem, what's error and problem. Maybe virus or not or others.
I download zadig and driver install good. But not receive, I don't know what's problem. How to fix error.
See Text document "logfile.txt" below.
Thanks, wait answer
Andrey

to see text document "logfile" error

Code:

[2016-10-18 08:32:52] Started cgminer 4.9.2
 [2016-10-18 08:32:52] Loaded configuration file cgminer.conf
 [2016-10-18 08:32:52] Fatal JSON error in configuration file.
 [2016-10-18 08:32:52] Configuration file could not be used.

 [2016-10-18 08:32:56] USB init, open device failed, err -12,
 [2016-10-18 08:32:56] You need to install a WinUSB driver for - AMU device 2:4
 [2016-10-18 08:32:56] And associate - AMU device 2:4 with WinUSB using zadig
 [2016-10-18 08:32:56] See README.txt file included for help
 [2016-10-18 08:32:56] Icarus detect (2:4) failed to initialise (incorrect device?)

 [2016-10-18 08:32:56] USB init, open device failed, err -12,
 [2016-10-18 08:32:56] You need to install a WinUSB driver for - AMU device 2:4
 [2016-10-18 08:32:56] And associate - AMU device 2:4 with WinUSB using zadig
 [2016-10-18 08:32:56] See README.txt file included for help
 [2016-10-18 08:32:56] Icarus detect (2:4) failed to initialise (incorrect device?)

 [2016-10-18 08:32:57] No devices detected!
 [2016-10-18 08:32:57] Waiting for USB hotplug devices or press q to quit
 [2016-10-18 08:32:57] Probing for an alive pool
 [2016-10-18 08:32:57] Pool 0 difficulty changed to 1024
 [2016-10-18 08:32:58] Network diff set to 259G

 [2016-10-18 08:33:06] USB init, open device failed, err -12,
 [2016-10-18 08:33:06] You need to install a WinUSB driver for - AMU device 2:4
 [2016-10-18 08:33:06] And associate - AMU device 2:4 with WinUSB using zadig
 [2016-10-18 08:33:06] See README.txt file included for help
 [2016-10-18 08:33:06] Icarus detect (2:4) failed to initialise (incorrect device?)

 [2016-10-18 08:33:06] USB init, open device failed, err -12,
 [2016-10-18 08:33:06] You need to install a WinUSB driver for - AMU device 2:4
 [2016-10-18 08:33:06] And associate - AMU device 2:4 with WinUSB using zadig
 [2016-10-18 08:33:06] See README.txt file included for help
 [2016-10-18 08:33:06] Icarus detect (2:4) failed to initialise (incorrect device?)

 [2016-10-18 08:33:15] USB init, open device failed, err -12,
 [2016-10-18 08:33:15] You need to install a WinUSB driver for - AMU device 2:4
 [2016-10-18 08:33:15] And associate - AMU device 2:4 with WinUSB using zadig
 [2016-10-18 08:33:15] See README.txt file included for help
 [2016-10-18 08:33:15] Icarus detect (2:4) failed to initialise (incorrect device?)

 [2016-10-18 08:33:16] USB init, open device failed, err -12,
 [2016-10-18 08:33:16] You need to install a WinUSB driver for - AMU device 2:4
 [2016-10-18 08:33:16] And associate - AMU device 2:4 with WinUSB using zadig
 [2016-10-18 08:33:16] See README.txt file included for help
 [2016-10-18 08:33:16] Icarus detect (2:4) failed to initialise (incorrect device?)

 [2016-10-18 08:33:25] USB init, open device failed, err -12,
 [2016-10-18 08:33:25] You need to install a WinUSB driver for - AMU device 2:4
 [2016-10-18 08:33:25] And associate - AMU device 2:4 with WinUSB using zadig
 [2016-10-18 08:33:25] See README.txt file included for help
 [2016-10-18 08:33:25] Icarus detect (2:4) failed to initialise (incorrect device?)

 [2016-10-18 08:33:25] USB init, open device failed, err -12,
 [2016-10-18 08:33:25] You need to install a WinUSB driver for - AMU device 2:4
 [2016-10-18 08:33:25] And associate - AMU device 2:4 with WinUSB using zadig
 [2016-10-18 08:33:25] See README.txt file included for help
 [2016-10-18 08:33:25] Icarus detect (2:4) failed to initialise (incorrect device?)

 [2016-10-18 08:33:34] USB init, open device failed, err -12,
 [2016-10-18 08:33:34] You need to install a WinUSB driver for - AMU device 2:4
 [2016-10-18 08:33:34] And associate - AMU device 2:4 with WinUSB using zadig
 [2016-10-18 08:33:34] See README.txt file included for help
 [2016-10-18 08:33:34] Icarus detect (2:4) failed to initialise (incorrect device?)

 [2016-10-18 08:33:34] USB init, open device failed, err -12,
 [2016-10-18 08:33:34] You need to install a WinUSB driver for - AMU device 2:4
 [2016-10-18 08:33:34] And associate - AMU device 2:4 with WinUSB using zadig
 [2016-10-18 08:33:34] See README.txt file included for help
 [2016-10-18 08:33:34] Icarus detect (2:4) failed to initialise (incorrect device?)

http://i83.fastpic.ru/big/2016/1019/8f/53d19c807a406d5a5a2ced415ccb9d8f.jpg
.
http://i84.fastpic.ru/big/2016/1019/85/e780a7feffac817d873999f925d38685.jpg
.

[Mikestang]

The best way to fix any problem with the U3 is to throw it in the trash; that's where they belong.