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

[-ck]

So far it's running stable after 3+ hours.
Did I need to run with -D to see LOG_ERR messages like (Free|Discard) work called with null work from ..., or was there something else that enabled that?

Great thanks. You don't need to do anything to see error messages as they're high priority and show up under all circumstances.

[1532349191]

1532349191

[1532349191]

1532349191

[1532349191]

1532349191

[ahmi]

From where we can download this mining software!!!can any one tell me Please!!

[hurricandave]

From where we can download this mining software!!!can any one tell me Please!!

Go to Page 1 of this thread, all links are available there.

[MINX]

Hi everybody.

I recently bought a Rockminer R-Box (https://www.youtube.com/watch?v=qS70fGFimO0) that is working fine on Windows 7 x64 with CGMiner 4.9.0, Zadig 2.1.1 (lastest version: http://zadig.akeo.ie/).  It connects successfully with most of the available BTC pools.

My problem is when I trying to do SOLO mining and specifically with a SHA256 coin called Zetacoin by its low difficulty .  I setup the zetacoin-qt.exe core in server mode, downloaded the blockchain, and put a zetacoin.conf file with this:

server=1
gen=0
rpcuser=user
rpcpassword=password
rpcallowedip=127.0.0.1
rpcport=17333

The CGMiner command line is:

cgminer.exe --icarus-options 115200:1:1 --rock-freq 300 -o http://localhost:17333 -u user -p password --btc-address ZaPcdijw44kFXAYWHRWbZJfMJScir3ynX6

It connects and seems to work but all the shares are invalid and rejected with the message "share above target" that I can read every moment.  What I'm doing wrong?.  

Thanks

[LZ]

CGMINER 4.9.0 does not work with BFLSC.

Code:

$ cgminer -n
 [2015-01-28 07:04:04] USB all: found 10 devices - listing known devices
.USB dev 0: Bus 1 Device 6 ID: 0403:6014
  Manufacturer: 'Butterfly Labs'
  Product: 'BitFORCE SHA256 SC'                    
 [2015-01-28 07:04:04] 1 known USB devices

Code:

$ cgminer --benchmark -D -T
 [2015-01-28 07:06:55] Global quota greatest common denominator set to 1                    
 [2015-01-28 07:06:55] Generated target 00000000000000000000000000000000000000000000000000f8ff0700000000                    
 [2015-01-28 07:06:55] Started cgminer 4.9.0                    
 [2015-01-28 07:06:55] RES: thread starting                    
 [2015-01-28 07:06:55] USB scan devices: checking for BAS devices                    
 [2015-01-28 07:06:55] BAS looking for BAS 0403:6014 but found 8087:0024 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 8087:0024 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 8087:0024 instead                    
 [2015-01-28 07:06:55] BAS looking for BAS 0403:6014 but found 1d6b:0002 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 1d6b:0002 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 1d6b:0002 instead                    
 [2015-01-28 07:06:55] BAS looking for and found BAS 0403:6014                    
 [2015-01-28 07:06:55] USB lock BitForceSC 1-6                    
 [2015-01-28 07:06:55] RES: BitForceSC (1:6) lock=1                    
 [2015-01-28 07:06:55] USB res lock BitForceSC 1-6                    
 [2015-01-28 07:06:55] RES: BitForceSC (1:6) lock ok=1                    
 [2015-01-28 07:06:55] USB init, kernel attached ... - BAS device 1:6                    
 [2015-01-28 07:06:55] USB init, kernel detached ifinfo 0 interface 0 successfully - BAS device 1:6                    
 [2015-01-28 07:06:55] USB init, alternative iManufacturer match - BAS device 1:6                    
 [2015-01-28 07:06:55] Found BUTTERFLY LABS                    
 [2015-01-28 07:06:55] USB free BAS                    
 [2015-01-28 07:06:55] USB init, kernel attached ... - BMA device 1:6                    
 [2015-01-28 07:06:55] USB init, kernel detached ifinfo 0 interface 0 successfully - BMA device 1:6                    
 [2015-01-28 07:06:55] USB init, alternative iManufacturer match - BMA device 1:6                    
 [2015-01-28 07:06:55] Found BUTTERFLY LABS                    
 [2015-01-28 07:06:55] USB free BMA                    
 [2015-01-28 07:06:55] USB init, kernel attached ... - BMA device 1:6                    
 [2015-01-28 07:06:55] USB init, kernel detached ifinfo 0 interface 0 successfully - BMA device 1:6                    
 [2015-01-28 07:06:55] USB init, iProduct mismatch - BMA device 1:6                    
 [2015-01-28 07:06:55] Found BitFORCE SHA256 SC vs BitFORCE SHA256                    
 [2015-01-28 07:06:55] USB free BMA                    
 [2015-01-28 07:06:55] USB unlock BitForceSC 1-6                    
 [2015-01-28 07:06:55] BAS looking for BAS 0403:6014 but found 09da:9090 instead                    
 [2015-01-28 07:06:55] RES: BitForceSC (1:6) lock=0                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 09da:9090 instead                    
 [2015-01-28 07:06:55] USB res unlock BitForceSC 1-6                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 09da:9090 instead                    
 [2015-01-28 07:06:55] BAS looking for BAS 0403:6014 but found 045e:00dd instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 045e:00dd instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 045e:00dd instead                    
 [2015-01-28 07:06:55] BAS looking for BAS 0403:6014 but found 05e3:0716 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 05e3:0716 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 05e3:0716 instead                    
 [2015-01-28 07:06:55] BAS looking for BAS 0403:6014 but found 8087:0024 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 8087:0024 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 8087:0024 instead                    
 [2015-01-28 07:06:55] BAS looking for BAS 0403:6014 but found 1d6b:0002 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 1d6b:0002 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 1d6b:0002 instead                    
 [2015-01-28 07:06:55] BAS looking for BAS 0403:6014 but found 1d6b:0003 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 1d6b:0003 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 1d6b:0003 instead                    
 [2015-01-28 07:06:55] BAS looking for BAS 0403:6014 but found 1d6b:0002 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 1d6b:0002 instead                    
 [2015-01-28 07:06:55] BAS looking for BMA 0403:6014 but found 1d6b:0002 instead                    
 [2015-01-28 07:06:55] No devices detected!                    

OS is Gentoo. USE flags are bflsc, ncurses and udev. I downgraded to 4.8.0 and it works again.

[-ck]

CGMINER 4.9.0 does not work with BFLSC.
OS is Gentoo. USE flags are bflsc, ncurses and udev. I downgraded to 4.8.0 and it works again.

Recognised problem fixed in git. Try latest git.

[LZ]

Yes, the git version works. Thank you.

[minerbit hill]

something is strange here. CGMINER must be still doing something but I can't find it in task manager.

[tZKtdvt6]

ckolivas, thank you very much, now I have the newest cgminer to the machines, it works really good.

Thank you very much, again.

[vjl]

Are there known issues with the New R-Box and CGMINER 4.8.x and 4.9.0? I ask because both versions perform worse for me than version 4.7.1. With 4.7.1, my 2 New R-Boxes get 97-110 Gh/s and with the 4.8 and 4.9 versions, they are getting nearly half of that [about 55-60 Gh/s each].

I deleted 4.8.x but I still have 4.9.0 installed [Windows XP] as well as 4.7.1, if there are some ways I can help debug to find the cause of the slowdown. Would be more than willing to do whatever I can so I can get on the latest release with the "usual" speed that 4.7.1 has given me.

Thanks!

[-ck]

Are there known issues with the New R-Box and CGMINER 4.8.x and 4.9.0? I ask because both versions perform worse for me than version 4.7.1. With 4.7.1, my 2 New R-Boxes get 97-110 Gh/s and with the 4.8 and 4.9 versions, they are getting nearly half of that [about 55-60 Gh/s each].

I deleted 4.8.x but I still have 4.9.0 installed [Windows XP] as well as 4.7.1, if there are some ways I can help debug to find the cause of the slowdown. Would be more than willing to do whatever I can so I can get on the latest release with the "usual" speed that 4.7.1 has given me.

There was no specific rbox code that I can recall in the newer ones so I can't see an obvious reason for the slowdown. The only thing different in the new one is filtering out duplicates and not counting their shares in the hashrate so if you had an rbox which produced a lot of duplicates it may have appeared to be faster but did not match the upstream pool's estimate of your hashrate. Perhaps check the summary of rejected shares running the old version versus the new.

[-ck]

New release: Version 4.9.1 - 3rd February 2015

Stable minor update release.


Human readable changelog:

- If a pool supports full stratum resume (currently only ckpool pools do), which means an interrupted stratum connection can resume and submit any shares worked on in the interim without losing work, a message will now be displayed when the reconnect negotiated a resume.
- If a dead pool was removed previously there was still a thread in the background trying to connect to it. This has been fixed.
- Avalon 4 updates to use less power.
- Fix an intermittent crash with the BFL SC 28nm devices.
- Fix support for BFL SC 65nm devices failing on last release.
- Fix the BET driver not being able to restart a new instance when the first fails.
- Basic FreeBSD compilation support.
- Other minor build changes and fixes for potential issues.


Full changelog:

- Fix various unused warnings
- Fix avalon4 warnings
- Display notice if pool successfully negotiates stratum resume
- Support auto adjust voltage individually
- Don't keep retrying to connect to a pool that has been removed
- Null the actual pointer used to call discard and free_work and safely handle
being called with a null pointer, giving a verbose warning about the call site
- Fix off by one error when running out of queued IDs in bflsc28_queue_full
- Uninit BET driver when it fails to initialise any boards
- Fix detection of butterfly labs sc 65nm devices with the addition of the 28nm
device imanufacturers trumping their detection
- Remove compilation warnings. Cast overly-specific #def'd values to the
destination type, unsigned int.
- Basic ability to compile and run on FreeBSD 10.  Only tested compilation with
avalon, avalon2, bflsc, and icarus; only tested functionality of bflsc and
icarus.

[vjl]

Are there known issues with the New R-Box and CGMINER 4.8.x and 4.9.0? I ask because both versions perform worse for me than version 4.7.1. With 4.7.1, my 2 New R-Boxes get 97-110 Gh/s and with the 4.8 and 4.9 versions, they are getting nearly half of that [about 55-60 Gh/s each].

I deleted 4.8.x but I still have 4.9.0 installed [Windows XP] as well as 4.7.1, if there are some ways I can help debug to find the cause of the slowdown. Would be more than willing to do whatever I can so I can get on the latest release with the "usual" speed that 4.7.1 has given me.

There was no specific rbox code that I can recall in the newer ones so I can't see an obvious reason for the slowdown. The only thing different in the new one is filtering out duplicates and not counting their shares in the hashrate so if you had an rbox which produced a lot of duplicates it may have appeared to be faster but did not match the upstream pool's estimate of your hashrate. Perhaps check the summary of rejected shares running the old version versus the new.

Hi there,

Thanks for the info! So far my reject rate is 0.15% so I'm not sure that is the cause. I would expect to see "(duplicate)" 1/2 the time with a 50% rate deduction and I rarely see more than 1 "duplicate" show up in the line-by-line transactions. Is there any way I can get a look at the exact stats for how many duplicates that are produced?

TIA

[vjl]

Are there known issues with the New R-Box and CGMINER 4.8.x and 4.9.0? I ask because both versions perform worse for me than version 4.7.1. With 4.7.1, my 2 New R-Boxes get 97-110 Gh/s and with the 4.8 and 4.9 versions, they are getting nearly half of that [about 55-60 Gh/s each].

I deleted 4.8.x but I still have 4.9.0 installed [Windows XP] as well as 4.7.1, if there are some ways I can help debug to find the cause of the slowdown. Would be more than willing to do whatever I can so I can get on the latest release with the "usual" speed that 4.7.1 has given me.

There was no specific rbox code that I can recall in the newer ones so I can't see an obvious reason for the slowdown. The only thing different in the new one is filtering out duplicates and not counting their shares in the hashrate so if you had an rbox which produced a lot of duplicates it may have appeared to be faster but did not match the upstream pool's estimate of your hashrate. Perhaps check the summary of rejected shares running the old version versus the new.

I decided to run 4.9.0 for a couple of hours and what's happening seems to be that one New R-Box is running at full power, and the other at 1/2. Before both would be much closer to 100Gh/s. I've inserted a screenshot.

https://dl.dropboxusercontent.com/u/285874/XP%202015-02-04%2019-34-58.png

Any idea why this might be happening?

Thanks again!

[lxROKxl]

*** PLEASE HELP ***
WITH MONARCHS/CG-Miner

I have ordered 3 monarchs from BFL and when i run them on CG-miner only 2 of them run and the other simply idles, 0.00/0.00 g/h. I'm not sure what to do to fix it, I have converted all the drivers to WinUSB so that they will run on CG- Miner Also it says BMS, while the other two working ones are BMA. I'm not sure if that has anything to do with it, also under my Device Manager the one that doesn't work is labeled as Bitfoce SHA265 SC while the others don't have the SC at the end. Please help me, I don't know what to do.

http://postimg.org/image/at5n9s7qj/

http://postimg.org/image/t7g6drk17/

[matt4054]

I have ordered 3 monarchs from BFL and when i run them on CG-miner only 2 of them run and the other simply idles, 0.00/0.00 g/h. I'm not sure what to do to fix it, I have converted all the drivers to WinUSB so that they will run on CG- Miner Also it says BMS, while the other two working ones are BMA. I'm not sure if that has anything to do with it, also under my Device Manager the one that doesn't work is labeled as Bitfoce SHA265 SC while the others don't have the SC at the end. Please help me, I don't know what to do.

It seems to be a mixup between the older 65nm generation (Single SC) and the newer 28nm generation (Monarch). The fact that Windows Device Manager also recognizes one of them with "SC" at the end is intriguing to say the least, it seems that it's using a different USB device ID, suggesting a hardware problem. I guess (and hope for you) that it could also be driver related, as I don't know much about the USB subsystem implementation in MS Windows.

The BFL devices should come up as one of the following:

BAJ: BFL ASIC Jalapeño
BAL: BFL ASIC Little Single
BAS: BFL ASIC Single
BAM: BFL ASIC Minirig
BMA: BFL Monarch

According to your screenshot you are using cgminer version 4.9.1 (latest). The changelog for 4.9.1 mentions:

- Fix detection of butterfly labs sc 65nm devices with the addition of the 28nm device imanufacturers trumping their detection

So it looks like some changes were made to solve a related problem, but the other way around (not sure about this though). Anyway, I would suggest the following options:

• Try previous versions of cgminer, I would try from 4.9.0 downwards, version 4.6.0 seems to be the first with BMA support
• Try another host computer, preferably with another host OS (e.g. Linux instead of Windows)
• Wait for ckolivas to chime in and give you a better insider advice
• Obviously, if all else fails, then try to get lucky with BFL RMA...

[oneoff]

Hello

I have run my Antminer U2 smoothly until I upgraded to 4.9.1. Now CGMiner report "No Devices Detected"....

--usb-dump 0 finds:
14 devices... -listing known devices .USB dev 0: Bus 4 Device 4 ID: 10c4:ea60
Manufacturer: Silicon labs
Product: CP2102 USB to UART Bridge controller
1 known USB Devices
No devices Detected
Waiting for USB Hotplug.....


Some time when I have unplugged/plugged the antminer it has suddenly (complete random) started to mine. But this is lost once i restart cgminer or the computer.

I have installed CP210x_VCP_Windows and run zadig_2.1.1...

Pleace help, any advice is welcome. I have tried everything I can think of. Updated the motherboard chip firmware, USB firmware etc. Tried different --anu-freq values etc.

My string:
cgminer.exe --anu-freq 200 -o stratum+tcp://mine.xpool.ca:1111 -u 13Y4PwrjFdpK5JedGHt9GGABmJyPNMRR9K.ant -p x

[oneoff]

Hello

I have run my Antminer U2 smoothly until I upgraded to 4.9.1. Now CGMiner report "No Devices Detected"....

--usb-dump 0 finds:
14 devices... -listing known devices .USB dev 0: Bus 4 Device 4 ID: 10c4:ea60
Manufacturer: Silicon labs
Product: CP2102 USB to UART Bridge controller
1 known USB Devices
No devices Detected
Waiting for USB Hotplug.....

Downloaded the CGminer from Bitmain support page (cgminer-run-windows-20141027.rar): https://www.bitmaintech.com/support.htm?pid=007201404130633105772QFG6R2u0635

And got it working with the commands: --bmsc-options 115200:20 --bmsc-freq 0981

But why does it not work with 4.9.1?

[-ck]

I have run my Antminer U2 smoothly until I upgraded to 4.9.1. Now CGMiner report "No Devices Detected"....

But why does it not work with 4.9.1?

Don't know as the U1/U2 code hasn't been intentionally touched in many moons and my U2s died a long time ago so I can't test them. Presumably one of the new drivers (U3 maybe?) affected them. Stick to an older version if it works for you.

[matt4054]

Don't know as the U1/U2 code hasn't been intentionally touched in many moons and my U2s died a long time ago so I can't test them. Presumably one of the new drivers (U3 maybe?) affected them. Stick to an older version if it works for you.

For what it's worth, I can mine with my U1s on 4.9.1 without problems (tested: Windows binaries + compiled from github / Linux)