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

[-ck]

Hi

I'm running 2 cointerra miners and as the company cointerra has now filed for chapter 7 (bankruptcy) they will not support the hardware any more.

As of this I want to update the cgminer software on them. Currently running 4.3.5 on them.
I downloaded the source-tarball for 49.1 and want to cross compile it on a ubuntu X64 server and then move the binary over to the beaglebone controlling the boxes.

I have googled alot and can't find a good instruction on how to do this. Also tried to copy the source to the box itself and compile it there but it wouldn't even unpack from the tarball.
I got the error "tar: invalid tar magic"

So, does anyone have a good instruction or information on how to cross compile cgminer for me?

Right now I can get it compiled running on x64 but that's not a working solution for me.

Cross compiling is not for the inexperienced. I suggest you take the top off the cointerror, pull out the usb cables from the beaglebone controller and plug them into any pc running linux. The device works fine from any controller running cgminer.

[1714190586]

1714190586

[1714190586]

1714190586

[1714190586]

1714190586

[1714190586]

1714190586

[CrazyGuy]

I can't compile the latest git master branch.

Code:

hashtable.c:30:21: fatal error: lookup3.h: No such file or directory
 #include "lookup3.h"

Running

Code:

find ~/src/cgminer -name 'lookup3.h' 

returns nothing, but I see the include was added in the latest jansson updates (dd2738163dac0c974ceb8e05f03083d53f3c7e93).

Fixed in git, thanks.

Also missing hashtable_seed.c. I was able to pull it from the ckpool source to complete the build.

  CC     dump.lo
  CC     error.lo
  CC     hashtable.lo
make[2]: *** No rule to make target 'hashtable_seed.c', needed by 'hashtable_seed.lo'.  Stop.

[-ck]

Also missing hashtable_seed.c. I was able to pull it from the ckpool source to complete the build.

  CC     dump.lo
  CC     error.lo
  CC     hashtable.lo
make[2]: *** No rule to make target 'hashtable_seed.c', needed by 'hashtable_seed.lo'.  Stop.

Also fixed, thanks.

[Mike0029]

Don't hide your worker details. Promote them!  If someone uses them all they're doing is mining for you.

Everyone should mine on Slush using worker bigbitmine.donate

Every little helps!

Gotcha! I just blotched everything out, because that's what I have seen others do on these forums when they post pictures of their Antminer GUI... Here it is again, with my worker details, as you can see pool #1 and #2 are exactly the same...

http://s23.postimg.org/ruyc74m1j/Found_Block.jpg

So, yeah, I have no idea what is going on... then again I don't know if "LSTime" means "LastShareTime"... that was just a guess...

~Mike0029

I think you suspected right in the first instance. The "block" share was found on slush ..... but it was stale, i.e submitted after the work was timed-out (or after someone else had already submitted the same share)!

On the stale share being logged as a found block, I believe that is a bug in cgminer (or it may indeed be by design!), but the best place to ask that question would be in the cgminer thread. I say it may be a bug because despite clearly not being logged as your best share (and is definitely higher in size than your best share), it has been marked (and logged) as a found block, despite it being stale. So yeah, head over to ckolivas' thread and throw that his way ....

edit: Very strange as you seem to have good connectivity to the pool, aka only 1 stale share in 2 days + ...... very strange indeed that it had to be the found block that turned out to be timed-out!

I was told to bring my questions over here, so:

I still don't fully understand mining, so pardon my ignorance if this has been answered or addressed already, or if this is in the wrong thread. Thanks for any insight into the issue. I use Slush pool as my primary BTC mining pool, and I currently run 2 underclocked Antminer S1's on the pool at 130 GH/s. As far as I know, Slush pool DOES NOT merge mine any alt coin of sorts, so this is where my problem arises... I know that the Bitcoin network difficulty is at 47427554950 and I would need a "BestShare" greater than that number to find a block. One of my Antminer S1's report a "FoundBlock" and this isn't the first time this has happened at Slush pool for me, however my "BestShare" is only 66,379,851... My main questions are: Why does this happen? Does Slush actually merge mine and just not tell the users? Is my Antminer S1 just being glitchy? Does the "1" under "Stale" explain this? I did a little bit of research and the only altcoin that I found that can be merge mined with BTC AND has a difficulty below 66,379,851 is i0coin... Did my miner find an i0coin block, because it is possible to "merge mine" with Bitcoin? Here is an image for reference:

http://s21.postimg.org/9rdz8c737/Found_Block.jpg

Thanks again for any help!
~Mike

[-ck]

Slush only merge mines namecoin and that sort of merged mining wouldn't show any different diff to bitcoin. Cgminer never discards shares even if they're stale unless you enable the --no-submit-stale feature. On the other hand, bitmain's forked version of cgminer with their antminer driver throws out stale shares whether you ask it or not, so that's probably what happened. Being a fork, it could also be they screwed up the code too and it reports false positives.

[bitvinda]

Sorry if this has been covered before, but I can't seem to find anything and I am at my wit's end. I'm trying to set up 2 Antminer U2s on Windows 7. When I run cgminer with proper settings, I get one green light flashing on the device and no feedback in the command prompt other than that it couldn't find any devices. Sometimes, if I unplug and plug back in, I'll get the miners mining and it's really lucky for me to unplug the two and have both working when I plug back in. When I do 'List all devices' I get:

[timestamp] USB init, open device failed, err -3 you don't have privileges to access - AMU device 2:4
[timestamp] See README file included for help
[timestamp] Icarus detect <2:4> failed to initialise <incorrect device?>

Those 3 messages refresh every few seconds. Any help would be greatly appreciated.

[NathanB]

Sorry if this has been covered before, but I can't seem to find anything and I am at my wit's end. I'm trying to set up 2 Antminer U2s on Windows 7. When I run cgminer with proper settings, I get one green light flashing on the device and no feedback in the command prompt other than that it couldn't find any devices. Sometimes, if I unplug and plug back in, I'll get the miners mining and it's really lucky for me to unplug the two and have both working when I plug back in. When I do 'List all devices' I get:

[timestamp] USB init, open device failed, err -3 you don't have privileges to access - AMU device 2:4
[timestamp] See README file included for help
[timestamp] Icarus detect <2:4> failed to initialise <incorrect device?>

Those 3 messages refresh every few seconds. Any help would be greatly appreciated.

How to install an ASIC miner (USB)

Plug in your device. After a failed automatic installation go to:

http://zadig.akeo.ie/


1. download the program
2. run the program
3. select your device (list all devices), choose your ASIC and install the driver (WINUSB)
4. you can check your device manager if the ASIC is listed under USB
5. check with commandline cgminer  -n in standalone
6. run a short cgminer test if you can see a hashrate
7. if point 6 doesnt work try another USB ports
8. run cgminer 4.7.1

edit:

9. use a powered usb hub you will pull more power that your usb port on the computer can supply....

[kano]

Yeah most of that is in the README ... that's why the message says to read it

[LeviWalker]

Cross compiling is not for the inexperienced. I suggest you take the top off the cointerror, pull out the usb cables from the beaglebone controller and plug them into any pc running linux. The device works fine from any controller running cgminer.

I have two of these myself and was just thinking the same thing. Mine actually run fine (good actually) so I dont know if there would be anything to gain other than experience by doing this. I am running your CKPool in the same rack as the miners so what do you think about running these with cgminer on the server? Its a virtual environment so I can easily add another server for mining only if that would be better.

[-ck]

Cross compiling is not for the inexperienced. I suggest you take the top off the cointerror, pull out the usb cables from the beaglebone controller and plug them into any pc running linux. The device works fine from any controller running cgminer.

I have two of these myself and was just thinking the same thing. Mine actually run fine (good actually) so I dont know if there would be anything to gain other than experience by doing this. I am running your CKPool in the same rack as the miners so what do you think about running these with cgminer on the server? Its a virtual environment so I can easily add another server for mining only if that would be better.

Up until my cointerra turned into a blast furnace and tried to weld itself to my shelf, I ran it off a PC instead of the BBB built in and found the USB communications much more reliable where errors were virtually non existent and latency was lower, so I definitely think there's an advantage (provided you have ridiculously cheap electricity, otherwise these make great boat anchors).

[LeviWalker]

Up until my cointerra turned into a blast furnace and tried to weld itself to my shelf, I ran it off a PC instead of the BBB built in and found the USB communications much more reliable where errors were virtually non existent and latency was lower, so I definitely think there's an advantage (provided you have ridiculously cheap electricity, otherwise these make great boat anchors).

Thanks I think I will give that a shot today.

[opentoe]

My antminer S5's aren't shutting down when they hit 80C or above. Could this be a cgminer issue? The temps start runaway when you already have been mining and get disconnected from the pool/network. Even if the miner isn't hashing the fan will slow down and the temps will start to run away. Soon as I saw 90c I think it was I powered mine off right away. Now, if you turn on the miner from the start with no connection to a pool it will be fine. This only happens while you were hashing then get disconnected. What's really weird is my Dad also has an S5 and the same thing happened to him. He was hashing on the Guild and he heard the beeping, walked over to his miners and the fan was not spinning. Then he felt the heat coming off the top and smelled that metal heat type smell and quickly powered off both miners. If we both weren't home and this happened we'd be in trouble, possibly a fire? I also posted this on the Official S5 page, hopefully there will be some kind of fix. I tried using M's monitor program but that only gives you an alert if the temp goes over a certain amount. It doesn't power it off.

Was told this issue is probably in the bitmaintech driver code and they need to resolve it.

[-ck]

My antminer S5's aren't shutting down when they hit 80C or above.

Was told this issue is probably in the bitmaintech driver code and they need to resolve it.

This.

[opentoe]

10-4

[opentoe]

What does this mean? I'm grabbing it from the output of cgminer. I only have two pools setup and the third one is a blank. Is that what it is trying to test, the third one that has nothing in it?



 [2015-03-20 23:16:33] (5s):1.426T (1m):669.1G (5m):482.2G (15m):230.1G (avg):1.132Th/s
[2015-03-20 23:16:34] Testing pool
 [2015-03-20 23:16:34] HTTP request failed: <url> malformed
 [2015-03-20 23:16:34] Failed to getaddrinfo for stratum+tcp://:(null)
[2015-03-20 23:16:36] Submitting share 00000000 to pool 0
 [2015-03-20 23:16:36] Accepted 000000e0 Diff 0/1024 BTM 0 pool 0
 [2015-03-20 23:16:38] (5s):1.399T (1m):656.7G (5m):480.3G (15m):229.8G (avg):1.129Th/s

[Mikestang]

My antminer S5's aren't shutting down when they hit 80C or above.

Was told this issue is probably in the bitmaintech driver code and they need to resolve it.

This.

Isn't that a safety feature?  Aren't they supposed to shut down around 80*C?

[os2sam]

I've just received to BFL Monarch's.  They identify themselves to Windoze as BitFORCE SHA256 SC and CGMiner 4.9.1 identifies them as a BAS.  Then I get a steady stream of errors saying "RequestQueJobStatus failed <err=0 amt=20>.
Thanks,
Sam

[-ck]

They identify themselves to Windoze as BitFORCE SHA256 SC and CGMiner 4.9.1 identifies them as a BAS. 

What a pain. That's the identifier for their 65nm hardware. No idea why they put it on mofarchs as well

65nm so far showed up as:
"BitFORCE SHA256 SC"

while 28nm as:
"BitFORCE SC-28nm"

The old FPGA showed up as:
"BitFORCE SHA256"
and then 28nm started showing up as this too.

Now they're mixing the 65nm identifiers with their "new"er hardware. If BFL didn't have bigger problems, I'd say they were doing it deliberately, but this is probably just plain screwup on their part I guess.

What does the iManufacturer field list?

[os2sam]

They identify themselves to Windoze as BitFORCE SHA256 SC and CGMiner 4.9.1 identifies them as a BAS.  

What does the iManufacturer field list?

Is this what your asking for?

Code:

C:\cgm491>CGMINER -D -T
 [2015-03-21 17:30:07] Started cgminer 4.9.1

snip

[2015-03-21 17:30:08] USB scan devices: checking for BAS devices
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27ca instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27ca instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27ca instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27c9 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c9 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c9 instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27cb instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cb instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cb instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27c8 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c8 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c8 instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27cc instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cc instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cc instead
[2015-03-21 17:30:08] BAS looking for and found BAS 0403:6014
[2015-03-21 17:30:08] USB lock BitForceSC 5-1
[2015-03-21 17:30:08] RES: BitForceSC (5:1) lock=1
[2015-03-21 17:30:08] USB res lock BitForceSC 5-1
[2015-03-21 17:30:08] RES: BitForceSC (5:1) lock ok=1
[2015-03-21 17:30:08] USB init - BAS device 5:1 usbver=0200 prod='BitFORCE SHA256 SC' manuf='BUTTERFLY LABS' serial='FTYM9T5M'
[2015-03-21 17:30:08] BAS0: reset got err 0
[2015-03-21 17:30:08] BAS: cgid 0 SetLatency got err 0
[2015-03-21 17:30:08] BAS0: setdata got err 0
[2015-03-21 17:30:08] BAS0: setbaud got err 0
[2015-03-21 17:30:08] BAS0: setflowctrl got err 0
[2015-03-21 17:30:08] BAS0: setmodemctrl got err 0
[2015-03-21 17:30:08] BAS0: purgetx got err 0
[2015-03-21 17:30:08] BAS0: purgerx got err 0
[2015-03-21 17:30:08] BitForceSC detect (5:1) Warning unknown firmware ' 1.4.30x00' using Ver2
[2015-03-21 17:30:08] BAS: cgid 0 SetLatency got err 0
[2015-03-21 17:30:08] BitForceSC (5:1) identified as: 'BAS'
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 058f:6377 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 058f:6377 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 058f:6377 instead

[-ck]

Is this what you're asking for?

Code:

C:\cgm491>CGMINER -D -T
 [2015-03-21 17:30:07] Started cgminer 4.9.1
[2015-03-21 17:30:08] USB init - BAS device 5:1 usbver=0200 prod='BitFORCE SHA256 SC' manuf='BUTTERFLY LABS' serial='FTYM9T5M'

Yes that's it.

Try this:

http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe