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
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 139. (Read 5806015 times)
January 26, 2014, 07:48:28 AM
January 26, 2014, 06:34:05 AM
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. 
January 26, 2014, 05:21:14 AM
@BUchi-88
Thx for answers
Thx for answers
January 26, 2014, 05:05:25 AM
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
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?
January 26, 2014, 04:40:06 AM
Ok sorry for the questions
January 26, 2014, 04:33:34 AM
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. 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
January 26, 2014, 04:32:18 AM
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
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
January 25, 2014, 10:50:29 PM
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.
January 25, 2014, 09:59:41 PM
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.
January 25, 2014, 08:29:31 PM
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.
January 25, 2014, 04:48:19 PM
Thanks, for your fast answer and it's OK for me, i'm waiting 
greets
greets
January 25, 2014, 04:19:51 PM
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. greets and thanks for your Hard work.
January 25, 2014, 04:12:36 PM
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.
January 25, 2014, 03:09:43 PM
Thanks for the release, its possible the support the Antminer U1 in the next releases?
greets and thanks for your Hard work.
greets and thanks for your Hard work.
January 25, 2014, 02:45:08 PM
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.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.
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
January 25, 2014, 12:59:19 PM
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+.
These are precompiled universal binaries that support Mac OS X 10.5.8 through 10.9+.
January 25, 2014, 12:55:51 PM
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.
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.
January 25, 2014, 10:52:56 AM
Not sure what I saw but I saw a new error flash on the screen "-pipe" and I think it was tied to lib usb.
Any idea if that still means I should be using an alternate btcguild or is that something else.
I'm going to try compiling later and see if I can get past where I was having trouble now. Just make sure if any thing I posted about it in my fork I get some credit since I did the searching.
Are you here to beg or to help to community? whatever you find please keep it secret not to get disappointed for the lack of creditsAny idea if that still means I should be using an alternate btcguild or is that something else.
I'm going to try compiling later and see if I can get past where I was having trouble now. Just make sure if any thing I posted about it in my fork I get some credit
since I did the searching.In genal you can not do much about USB pipe errors unless you are writing USB dev firmware. what needs to be done is done already from cgminer developers.
January 25, 2014, 08:40:46 AM
Not sure what I saw but I saw a new error flash on the screen "-pipe" and I think it was tied to lib usb.
Any idea if that still means I should be using an alternate btcguild or is that something else.
I'm going to try compiling later and see if I can get past where I was having trouble now. Just make sure if any thing I posted about it in my fork I get some credit since I did the searching.
Any idea if that still means I should be using an alternate btcguild or is that something else.
I'm going to try compiling later and see if I can get past where I was having trouble now. Just make sure if any thing I posted about it in my fork I get some credit
since I did the searching. 
January 25, 2014, 06:18:02 AM
BaB driver changes are:
Support for both V1 and V2 controller (automatically)
Automatic tuning of all the chips performance.
Redesign of nonce reply handling to remove all the problems I copied from chainminer (there were a few)
Dramatic drop in HW errors due to a few things: not corrupting the replies, ignoring raw E0 replies and of course (not new) checking the nonces more extensively
A bucket load of statistics in the API stats that will tell you what's going on with each chip
Included is a 5 minute history that is used for performance tuning (all fields that have "History" in the name)
Here's an example with a single 16 chip board:
The last 8 are the parameters you can supply with --bab-options to tune it (see ASIC-README)
I've run it fine with 1 board and with 6 boards (I have both)
I am still tuning it and it may need some adjustment to handle the large setups of 24 boards - but I've not had access to one since before the last lot of changes.
Support for both V1 and V2 controller (automatically)
Automatic tuning of all the chips performance.
Redesign of nonce reply handling to remove all the problems I copied from chainminer (there were a few)
Dramatic drop in HW errors due to a few things: not corrupting the replies, ignoring raw E0 replies and of course (not new) checking the nonces more extensively
A bucket load of statistics in the API stats that will tell you what's going on with each chip
Included is a 5 minute history that is used for performance tuning (all fields that have "History" in the name)
Here's an example with a single 16 chip board:
Code:
[STATS] => 0
[ID] => BaB0
[Elapsed] => 458
[Calls] => 0
[Wait] => 0.000000
[Max] => 0.000000
[Min] => 99999999.000000
[Version] => 2
[Chips] => 16
[Boards] => 1
[Banks] => 1
[Chips Per Bank] => 0 16 0 0 0
[Missing Chips Per Bank] => 0 0 0 0 0
[Device Elapsed] => 459
[History Enabled] => true
[Chip History Limit] => 300
[Nonces 0-15] => 322 286 260 268 283 288 296 263 278 258 312 306 283 257 257 238
[Good 0-15] => 305 265 238 242 261 267 272 238 259 237 284 287 263 234 234 218
[Bad 0-15] => 2 6 7 11 7 6 9 10 4 6 13 4 5 8 8 5
[Conf 0-15] => 0x1b 0x1b 0x1b 0x1b 0x1b 0x1b 0x1b 0x1b 0x1b 0x1b 0x1b 0x1b 0x1b 0x1b 0x1b 0x1b
[Fast 0-15] => 54 54 54 54 54 54 54 54 54 54 54 54 54 54 54 54
[Spie 0-15] => 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0
[Miso 0-15] => 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[HW% 0-15] => 0.651 2.214 2.857 4.348 2.612 2.198 3.203 4.032 1.521 2.469 4.377 1.375 1.866 3.306 3.306 2.242
[GHs 0-15] => 2.852 2.478 2.225 2.263 2.441 2.497 2.543 2.225 2.422 2.216 2.656 2.684 2.459 2.188 2.188 2.038
[Sum GHs 0-15] => 38.376
[Cont-Bad 0-15] => 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[Max-Bad 0-15] => 1 2 1 2 1 1 2 2 1 1 2 1 2 1 1 1
[History Good 0-15] => 209 177 166 154 171 170 172 154 187 162 193 203 164 152 142 143
[History Bad 0-15] => 1 4 1 4 7 4 6 9 3 6 8 3 5 6 7 4
[History HW% 0-15] => 0.476 2.210 0.599 2.532 3.933 2.299 3.371 5.521 1.579 3.571 3.980 1.456 2.959 3.797 4.698 2.721
[History GHs 0-15] => 2.998 2.521 2.370 2.198 2.435 2.436 2.457 2.198 2.664 2.321 2.758 2.902 2.335 2.163 2.026 2.040
[Sum History GHs 0-15] => 38.821
[Total History GHs] => 38.821
[Total History HW%] => 2.789
[History Speed 0.0 Dead] => 0
[History Speed 0.8 V.Slow] => 0
[History Speed 1.6 Slow] => 0
[History Speed 2.2 OK] => 5
[History Speed 2.8 Good] => 9
[History Speed >2.8 Fast] => 2
[History Dead] => None
[History V.Slow] => None
[Nonce Offset 0xff800000] => 2137
[Nonce Offset 0x00000000] => 1407
[Nonce Offset 0xffc00000] => 560
[Discarded E0s] => 7777
[Tested] => 4455
[OK] => 4104
[Total Tests] => 11835
[Max Tests] => 13
[Avg Tests] => 2.884
[Untested] => 0
[Work Links] => 6260
[Work Processed Links] => 3396
[Max Links] => 6
[Max Processed Links] => 6
[Total Work Links] => 31025
[Avg Links] => 1.525
[Avg Proc Links] => 0.827
[Avg Work Links] => 7.560
[Fail] => 111
[Fail Total Tests] => 1600
[Fail Avg Tests] => 14.414
[Fail Work Links] => 950
[Fail Total Work Links] => 950
[Initial Ignored] => 240
[Ign Total Tests] => 454
[Ign Work Links] => 0
[Ign Total Work Links] => 0
[WFree Total] => 1024
[WFree Count] => 859
[Available Work] => 16
[SPI Work] => 0
[Chip Work] => 133
[SFree Total] => 8
[SFree Count] => 2
[SPI Waiting] => 0
[SPI Sent] => 5
[RFree Total] => 256
[RFree Count] => 256
[Result Count] => 0
[NFree Total] => 102400
[NFree Used] => 2797
[Delay Count] => 490
[Delay Min] => 0.899001
[Delay Max] => 1.019091
[Delay Bands] => <0.5=0 <0.7=0 <0.9=242 <1.1=248 <1.3=0 <1.5=0 <1.7=0 <1.9=0 <2.1=0 <2.3=0 <2.5=0 >=2.7=0
[Send Count] => 491
[Send Total] => 24.646958
[Send Avg] => 0.050
[Send Min] => 0.045762
[Send Max] => 0.086118
[MaxSpeed] => 55
[DefaultSpeed] => 54
[MinSpeed] => 52
[TuneUp] => 1.000000
[TuneDown] => 10.000000
[SPISpeed] => 1000000
[SPIDelayuS] => 0
[TransferDelayuS] => 0
I've run it fine with 1 board and with 6 boards (I have both)
I am still tuning it and it may need some adjustment to handle the large setups of 24 boards - but I've not had access to one since before the last lot of changes.
Jump to: