Author

Topic: BFL Singles and CGMiner 2.4.1 (Read 1660 times)

full member
Activity: 202
Merit: 100
June 05, 2012, 11:19:29 PM
#8
I'd bet money its your usb hub or cables.

I haven't had this issue yet, but i have been having issues with easyminer and singles appearing and disappearing. My solution was to use 1x6 port hub and 1x10 port hub instead of just the 10 port to run my 8 singles. This seems to have helped. The  hubs are el cheapo ones from Ben's outlet. I really do think that cheap hubs are causing some of these problems. I'm going to order a name brand hub in the future to see if that's the case.
member
Activity: 70
Merit: 10
June 05, 2012, 11:07:07 PM
#7
I'd bet money its your usb hub or cables.
legendary
Activity: 922
Merit: 1003
June 05, 2012, 10:10:04 PM
#6
Anyone have issue where all connected singles drop out of CGMiner after many hours of operation?  Restart of cgminer works fine.

Win7 32 bit.

 [2012-06-05 17:53:47] Error writing to BitForce ("ZFX")
 [2012-06-05 17:53:47] BFL 0 failure, disabling!
I've never had ALL connected Singles drop out, but I can confirm I've had a few drop out on a few occasions with 2.4.1 and 2.4.2 (Win7/64). When this happens the hashrate displays 'OFF' in the cgminer window. The dropout seems to be random; there is no pattern to it that I can see. I've had 2 Singles drop out within 24 hours; I've also gone a few days without any dropouts at all.

With the older 2.3.6 this problem did not seem to exist.  I was able to go for weeks (literally) without touching anything. I haven't been using 2.4.1/2.4.2 for that long yet, but so far it is not off to a good start.

Hopefully the BFL issues with the 2.4.x branch will be sorted out soon.
sr. member
Activity: 344
Merit: 250
June 05, 2012, 09:56:45 PM
#5
I received my two BFL singles 4 days ago and I've been running cgminer 2.4.1 and 2.4.2 (self-compiled from source) on Windows 7 64 bit, and haven't had them drop out that I've noticed, unless they lose power.

I made a small change so it will exit if they drop out (to deal with power outages), and then I start it with a .bat file that will restart cgminer if needed.  Seems to work fine, so far.

https://bitcointalksearch.org/topic/m.937742
hero member
Activity: 557
Merit: 500
June 05, 2012, 08:51:34 PM
#4
I've been running 2.4.1 since I've got my five singles running on 5/25.  Rock solid on all firmwares. Win 7 x64, I've been running a single instance of cgminer for each single.  Don't know if that makes a difference or not.
legendary
Activity: 1795
Merit: 1208
This is not OK.
June 05, 2012, 05:48:51 PM
#3
The BFL driver code isn't so great right now. At the slightest sign of a problem, the default action is to scream and die. There aren't any re-tries or timeouts. Hopefully that'll change soon.
full member
Activity: 196
Merit: 100
June 05, 2012, 05:07:18 PM
#2

Anyone have issue where all connected singles drop out of CGMiner after many hours of operation?  Restart of cgminer works fine.

Win7 32 bit.

 [2012-06-05 17:53:47] Error writing to BitForce ("ZFX")
 [2012-06-05 17:53:47] BFL 0 failure, disabling!

Already being discussed in the official cgminer thread as I do believe I have seen mention of this in the last couple of days in it.
sr. member
Activity: 252
Merit: 250
Inactive
June 05, 2012, 05:03:01 PM
#1

Anyone have issue where all connected singles drop out of CGMiner after many hours of operation?  Restart of cgminer works fine.

Win7 32 bit.

 [2012-06-05 17:53:47] Error writing to BitForce ("ZFX")
 [2012-06-05 17:53:47] BFL 0 failure, disabling!
Jump to: