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

[Karin]

Unofficial Mac binaries have been updated for v3.11.0 and are available here.

These are precompiled universal binaries that support Mac OS X 10.5.8 through 10.9+.

[loshia]

Neither and it shouldn't matter to you since this is the first time I've seen your user name here. I made some changes to a how to guide and I was expecting some kind of thanks if I stumbled across something. If he really wanted help he'd have git hub open for reports and have a cleaner post.

The pipe error is new so I mentioned it. I help where I can and grump when I need it . Your making more mess responding to my entire post.

Have a nice e day and hope cK Olivias still see's what I posted.

%there is nothing wrong to expect something in return for time and efforts but as far as understand you are asking for it.so please take my apology I might get it wrong.
It is not my first time posting here
Besides in change log and source there is a word about pipe errors and no more lib USB resets if I remember correctly

[Buchi-88]

Thanks for the release, its possible the support the Antminer U1 in the next releases?

greets and thanks for your Hard work.

[-ck]

Pipe errors on usb reads that cgminer fails to clear are no longer treated as fatal (which would make them reset the usb device) and are passed back to the driver to decide what to do with them. Most drivers will still treat them as fatal but the hashfast driver will attempt to reread first and then drops the device itself, avoiding the usb reset which the HFA devices don't like.

[-ck]

Thanks for the release, its possible the support the Antminer U1 in the next releases?

greets and thanks for your Hard work.

I just received one in the mail (thanks Beastly) so I will get around to writing a driver for it at some stage. Understand that with someone dumping 3TH on my doorstep for me to work on another driver, you can see why a 2.5GH USB stick will get low priority.

[Buchi-88]

Thanks,  for your fast answer and it's OK for me, i'm waiting

greets

[techman05]

Pipe errors on usb reads that cgminer fails to clear are no longer treated as fatal (which would make them reset the usb device) and are passed back to the driver to decide what to do with them. Most drivers will still treat them as fatal but the hashfast driver will attempt to reread first and then drops the device itself, avoiding the usb reset which the HFA devices don't like.

Is there anyway to minimize having pipe errors. It seems like my drillbit devices and an amu labeled device have been reset a max of 156 times  since I updated to 3.11. Btc guild seems to be working since i haven't crashed all day, but I gotta wait and see if btcguild makes another post of "all clear" so I know its working properly.

I'm also seeing something called "high hash". What is that ? Am I ticking off a low difficulty coin?

Thanks

Edit tried to compile again. What am I missing? I'm getting the same compile errors  with winsock and winsock 2 header errors.

[techman05]

There wasn't any specifics in the windows compile guide of any special tweaks needed but I know that miniGW installed them with the basic install and that they are there. I have no idea other than that.

[-ck]

Pipe errors on usb reads that cgminer fails to clear are no longer treated as fatal (which would make them reset the usb device) and are passed back to the driver to decide what to do with them. Most drivers will still treat them as fatal but the hashfast driver will attempt to reread first and then drops the device itself, avoiding the usb reset which the HFA devices don't like.

Is there anyway to minimize having pipe errors. It seems like my drillbit devices and an amu labeled device have been reset a max of 156 times  since I updated to 3.11. Btc guild seems to be working since i haven't crashed all day, but I gotta wait and see if btcguild makes another post of "all clear" so I know its working properly.

I'm also seeing something called "high hash". What is that ? Am I ticking off a low difficulty coin?

Thanks

Edit tried to compile again. What am I missing? I'm getting the same compile errors  with winsock and winsock 2 header errors.

Pipe errors are hardware related, though far far less common on linux. Pick better hardware and get rid of all the usb1.1 crap (ie amu sticks). My compilation works perfectly fine picking up the correct headers all the time by default so there's something wrong with your build environment setup. What? I dunno, otherwise I would have told you by now since you've asked about 10 times.

[Takel]

Hello.
sorry for my bad english.

i've installed cgminer 3.11.0 and run ok, but now antminer (icarus) need theese setting:
#cgminer --icarus-options 115200:2:2 --icarus-timing short=90  (about 3,330 gh/s)

with cgminer 3.10 run with theese setting:
#cgminer --icarus-options 115200:1:1 --icarus-timing short=90  (about 3,180 gh/s)
where wrong ??
3.11 with --icarus-options 115200:1:1   run to low! about 500mh/s


i've arch linux

thx to all
Takel

[-ck]

Hello.
sorry for my bad english.

i've installed cgminer 3.11.0 and run ok, but now antminer (icarus) need theese setting:
#cgminer --icarus-options 115200:2:2 --icarus-timing short=90  (about 3,330 gh/s)

with cgminer 3.10 run with theese setting:
#cgminer --icarus-options 115200:1:1 --icarus-timing short=90  (about 3,180 gh/s)
where wrong ??
3.11 with --icarus-options 115200:1:1   run to low! about 500mh/s


i've arch linux

thx to all
Takel

There is no support for antminer U1 with cgminer yet, only with unofficial forks.

[Takel]

Ok sorry for the questions

[Buchi-88]

Hello.
sorry for my bad english.

i've installed cgminer 3.11.0 and run ok, but now antminer (icarus) need theese setting:
#cgminer --icarus-options 115200:2:2 --icarus-timing short=90  (about 3,330 gh/s)

with cgminer 3.10 run with theese setting:
#cgminer --icarus-options 115200:1:1 --icarus-timing short=90  (about 3,180 gh/s)
where wrong ??
3.11 with --icarus-options 115200:1:1   run to low! about 500mh/s


i've arch linux

thx to all
Takel

Hello Takel the Antminer run on the Original CgMiner only slow at 1,6 GH/s with "--icarus-timing long" it need a little bit time, to rund at Full speed 1,6 GH/s

At example by me the run:

Code:

cgminer -c /home/pi/cgminer.conf --icarus-timing long --quiet  --usb :5

greets

Edit: Or you use unofficial Cgminer, but there i very unstable:

Code:

http://sven-goessling.de/05/01/2014/antminer-auf-dem-raspberry-pi-04-01-14/

@cholivas

I hope this post is OK for you?

[Takel]

@BUchi-88
Thx for answers
 

[-ck]

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected.

I finally was able to reproduce this bug with nanofury usb sticks and have debugged it. The fix for this crash is now in git master and I suggest all users with these devices upgrade. Given the prevalence of these devices, I've also uploaded updated windows binaries denoted 3.11.0-1 with the bugfix.

[chek2fire]

I have problem with the last version of cgminer. When i start it and after a while some of my usb goes zombie or get off from programme. The previous version works without any problem and i run it for days only some rare crashes.
My usb is some icarus and some bitfury (bifury, nanofury, redfury)
For those that want to run antminers this fork version of cgminer works fine

https://github.com/fractalbc/cgminer

[techman05]

There wasn't any specifics in the windows compile guide of any special tweaks needed but I know that miniGW installed them with the basic install and that they are there. I have no idea other than that.

Post the relevant error messages then it may become clearer.

This is all the stuff I have on my problem in this post in this link including the frustrating banter. I don't think I did anything funny other than installing minGW though I had to fight my way through it to get to the "make" due to some non specifics like pthreads that didn't work by default and some versions used.
http://drillbitsystem.com/forum/index.php?topic=273.0

I can bet you, ckOlivias, built your own winsock files a while back and forgot about it   thats why I'm having greif  .

[techman05]

Funny thing is if you run my git hub with correct headers to the files specified in the errors added I still get a bunch of errors to the Same extent and if I do lean and mean it screws up some timer header.  If I ignore it it stops at the first driver since it has windows.h though at that point it breaks if I add the winsock 2 headers to that driver.

I can only swear minGW's current file version for these headers are fudged up [though they will say it's cK Olivias problem being the developer] since ckOlvivias can compile and continues to compile successfully.

[techman05]

So I should try just completely removing windows.h from the files from where they are and see what happens. I would have thought if that was the issue cK Olivias would have told me or changed it himself.

[techman05]

I replaced  all windows.h with the files set and then found myself removing ws2tcpip.h and got this error.  Every time I think I follow a fix a new thing comes out  . Any idea what this error means.

Code:

In file included from ./sha2.h:36:0,
                 from cgminer.c:53:
./miner.h:1180:18: error: field 'stratum_hints' has incomplete type
  struct addrinfo stratum_hints;
                  ^

line 1180 just says this "struct addrinfo stratum_hints;" and then its never used again in this file when I tried to ctl-f any others of it

line 18 says "#define curl_global_cleanup() {}" if that's what the 18 means