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

[-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!

[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)

[-ck]

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)

Thanks for that. As I said the code for them wasn't directly touched so they should work the way they used to.

[Kx2000]

Anyone could help me ?

I Try to do working my antminer U3 on Cgminer on minepeon, i have updated 4.0.1 version included by a 4.9.1 version following a tutorial on internet. But cgminer don't start...

I go on SSH on opt/minepeon/bin/ and i launch cgminer with some arguments like -c /opt/minepeon/etc/miner.conf but nothing append.


Anybody could help me ?

Thanks.

[hurricandave]

You have no .conf file until you have successfully run cgminer or it is empty till it has been populated with pool, user, password info at the minimum.

[btcminer021]

* btcminer021 hugs ckolivas

Thanks for what you've done for the community. We're not worthy!

[o_solo_miner]

Hello Con,
Thank you for the new Version 

I managed to compile it under Raspian(Linux3.18.5-v7+) for the Raspi2 (with 4Core).

Anyway it works but looks quite different in output.
I am unable to select D for Display or U for USB and so on.
I am asking myself if i miss a step in compiling or configuring?
Or maybe i did it totaly wrong.

The miner (BFL Jalapeno 5 GHs) is mining and visible on your Solopool.
Only the menu look is not working.

[kano]

Hello Con,
Thank you for the new Version 

I managed to compile it under Raspian(Linux3.18.5-v7+) for the Raspi2 (with 4Core).

Anyway it works but looks quite different in output.
I am unable to select D for Display or U for USB and so on.
I am asking myself if i miss a step in compiling or configuring?
Or maybe i did it totaly wrong.

The miner (BFL Jalapeno 5 GHs) is mining and visible on your Solopool.
Only the menu look is not working.

You are missing curses

[o_solo_miner]

Hello Con,
Thank you for the new Version 

I managed to compile it under Raspian(Linux3.18.5-v7+) for the Raspi2 (with 4Core).

Anyway it works but looks quite different in output.
I am unable to select D for Display or U for USB and so on.
I am asking myself if i miss a step in compiling or configuring?
Or maybe i did it totaly wrong.

The miner (BFL Jalapeno 5 GHs) is mining and visible on your Solopool.
Only the menu look is not working.

You are missing curses

BIG THANX TO YOU KANO!

I didn't think of the library........
Installed the libncurses5-dev.
Now after quick recompiling (by the way, the PI2 is a Ferrarie now in compiling) it works great!

Puhh that was a "Problem by User" thing

[Mikestang]

New user here, just wanting to try mining for the "lottery" effect, as well as contribute to the bitcoin network.

My first piece of mining gear arrirved yesterday, an antminer U3.  I Installed and configured it correctly w/driver and zadig.  Downloaded latest cgminer (4.9.1), ran cgminer with the following: cgminer.exe -o stratum+tcp://solo.ckpool.org:3333 -u MYADDRESS.0 -p xx3

And I receive:
No Devices Detected!

Any suggestions?  Thank you.


And a separate issue with command line options (may be related to No Devices Attached?), I tried inserting a few of the U3 specific options at the command line, -au3-volt -au3-freq, but each returns the error:
cgminer.exe: -au3-volt: unrecognized option

If I try to insert any command line option that starts with '-s', -suggest-diff for example, I get this error:
cgminer.exe: -s: 'uggest-diff' is not a number

Please help this noob if you can, I'm anxious to get this going!  Thanks again in advance.

-mikestang

[-ck]

New user here, just wanting to try mining for the "lottery" effect, as well as contribute to the bitcoin network.

My first piece of mining gear arrirved yesterday, an antminer U3.  I Installed and configured it correctly w/driver and zadig.  Downloaded latest cgminer (4.9.1), ran cgminer with the following: cgminer.exe -o stratum+tcp://solo.ckpool.org:3333 -u MYADDRESS.0 -p xx3

And I receive:
No Devices Detected!

Any suggestions?  Thank you.


And a separate issue with command line options (may be related to No Devices Attached?), I tried inserting a few of the U3 specific options at the command line, -au3-volt -au3-freq, but each returns the error:
cgminer.exe: -au3-volt: unrecognized option

If I try to insert any command line option that starts with '-s', -suggest-diff for example, I get this error:
cgminer.exe: -s: 'uggest-diff' is not a number

Please help this noob if you can, I'm anxious to get this going!  Thanks again in advance.

-mikestang

The U3s are notoriously unreliable even out of the factory I'm afraid. Try a different cable than the one they gave you and make sure they're only connected to a USB2 slot or a separate hub with usb2 slots if you are trying in usb3 slots. Those commands are missing an extra hyphen: --au3-volt

[Mikestang]

The U3s are notoriously unreliable even out of the factory I'm afraid. Try a different cable than the one they gave you and make sure they're only connected to a USB2 slot or a separate hub with usb2 slots if you are trying in usb3 slots. Those commands are missing an extra hyphen: --au3-volt

Tried a different cable and no dice.  The little red light inside the U3 comes on when I plug in either cable, and my comp sees when I plug it in, so I think the cable is not an issue.  My computer is old, it doesn't have usb3, so no issue there.  Anything else I could try, besides contacting the seller for a replacement?

When I add the extra hyphen to --au3-volt --au3-freq --suggest-diff those options get accepted at the command line, thank you.  How would I set the baud rate and timeout for the U3, I do not see that option.  I see "--bitmain-options   Set bitmain options baud:miners:asic:timeout:freq", but not sure if that is the correct option, or what value I would use for miners, asic, or freq (since freq appears to be set by --au3-freq).

Additionally, when it says "press q to quit", pressing q doesn't do anything.

Thank you.

[-ck]

The U3s are notoriously unreliable even out of the factory I'm afraid. Try a different cable than the one they gave you and make sure they're only connected to a USB2 slot or a separate hub with usb2 slots if you are trying in usb3 slots. Those commands are missing an extra hyphen: --au3-volt

Tried a different cable and no dice.  The little red light inside the U3 comes on when I plug in either cable, and my comp sees when I plug it in, so I think the cable is not an issue.  My computer is old, it doesn't have usb3, so no issue there.  Anything else I could try, besides contacting the seller for a replacement?

When I add the extra hyphen to --au3-volt --au3-freq --suggest-diff those options get accepted at the command line, thank you.  How would I set the baud rate and timeout for the U3, I do not see that option.  I see "--bitmain-options   Set bitmain options baud:miners:asic:timeout:freq", but not sure if that is the correct option, or what value I would use for miners, asic, or freq (since freq appears to be set by --au3-freq).

Additionally, when it says "press q to quit", pressing q doesn't do anything.

Thank you.

Your U3 is probably stuffed if it doesn't show up but numerous goes at restarting the computer, unplugging and plugging it in again and doing the zadig dance or praying to certain gods might help. Baud rate is for hardware from the 1970s and is not used by cgminer though other software does because someone somewhere once used it on one of the first pieces of mining hardware and everyone just copied that command when they made their driver. Just ignore that. The q only really works once it's up and running properly but you have so far gotten nothing running.

[Mikestang]

but numerous goes at restarting the computer, unplugging and plugging it in again and doing the zadig dance or praying to certain gods might help.

Commencing dance, will report later on outcome.  I've contacted the reseller as well.  Thank you so much for your help.

And yes, I am quite familiar with baud ratings.  Only asked because it's a suggested setting in the U3 user guide.  My first modem was a 300/1200 baud.  When I got my 9600/14.4k with compression I couldn't believe how fast it was; hurray for the good ol' BBS days.