Can you give some additional details or thread link about how to "replacing the 22k resistor with a 10k one"

I believe the last that was reported from Bitminter was that they were still working on it (can't remember who it is that maintains the bitminter code atm).

Received 2 today.

Starting bfgminer 3.5 with -S bitfury:/dev/ACM0 -S bitfury:/dev/ACM1

Recognized

[2013-11-06 12:51:49] lowlevel_scan: Found vcom device at dev_t:01a6000000000000 (path=/dev/ttyACM1, vid=0000, pid=0000, manuf=BFMG, prod=Bitfury BF1, serial=A4931313633351A01281)                   
[2013-11-06 12:51:49] lowlevel_scan: Found vcom device at dev_t:00a6000000000000 (path=/dev/ttyACM0, vid=0000, pid=0000, manuf=BFMG, prod=Bitfury BF1, serial=A4931313633351A01221)       

But never hash.

With erupters, I see something like this

[2013-11-06 12:55:41] Icarus Detect: Attempting to opendev/ttyUSB0                   
 [2013-11-06 12:55:41] Acquired exclusive advisory lock ondev/ttyUSB0                   
 [2013-11-06 12:55:41] Icarus Detect: Test succeeded atdev/ttyUSB0: got 000187a2                   
 [2013-11-06 12:55:41] Found BES 0 atdev/ttyUSB0                   
 [2013-11-06 12:55:41] BES 0: Init: baud=115200 work_division=0 fpga_count=0                   
 [2013-11-06 12:55:41] BES 0: Init: mode=default read_count=126 limit=0ms Hs=2.976100e-09                   


But after the initial line regarding ACM0/1 I see nothing further in the debug output.


Please advise

No joy with either BFGminer or CGminer on OSX. Simply will not pick up the device

CGminer 3.7+ on Windows 7 has had only had blinking Red lights no matter what.

just got the batch #2 and the heat sinks are difference  hoping this change will help with mining power

I am getting about spot on 2.0GH/s on two units using Debian 7.0 x64 with cgminer 3.7.2.


I have also noticed that the units are very temperamental with some USB hubs. Running even one unit in a USB hub (dlink) either one will eventually time out with an error about communication timeouts. If I connect them directly to the computer, they run fine with the numbers show above. I suspect that they are rather picky about power, but that is only a guess at this point.

Win7 64bit System

I just got the 2nd fury today with the scaled-back black heat sink (pictured above). It is very clearly running about twice as fast as the first one with the heavier heat sink that I received last week.

Something I noticed -- BFGminer shows the estimated hash rate (first and 2nd numbers) on the faulty one to be about 100MH/sec HIGHER than the one I got today (2.23GH/sec vs. 2.33GH/sec). The 3rd number in BFG, the effective rate, is where they differ drastically. Perhaps the firmware in the first one was a little too aggressive -- resulting in it being knocked back in stepping?  That's my feel of it after watching it rather closely these past few days.

Shouldn't I wait and see if BeastlyMac releases the firmware update?  SSINC has replacements in, but I have a sneaky suspicion that the one with the larger and better heatsink would perform the same if it had the same firmware as this more recent one.  I kind of like the ability to tell them apart so easily...  And if a firmware upgrade fixes the problem, that saves on shipping costs (both ways), as well as quite a bit of down mining time.

BFGminer does seem to squeeze about 10% more out of the newer fury, though.  1.97GH/sec in cgminer 3.7.2, and 2.17GH/sec in BFGminer 3.2.0.  That's nearly 200MH/sec difference in favor of BFGminer 3.2.0.  Maybe another 30min in each window would have brought the window narrower, but I don't think by very much.

I got my first HUGE problem solved with the help of Epinnoia, Thanks a bunch!  So bfgminer would not for the life of it be able to communicate on these, I'm on Win 7 and followed the op directions to the letter.  The problem was 2 fold, 1st the port had a bad default baud rate (9600 instead of the 115200 which Epinnoia recommended to me), second was even after this changed I had to make sure I pressed the "RST" button to make the change take effect (even unplugging/replugging these in did not cause the change to help).

Now for my next HUGE problem..... 60% + HW error rates an all of these devices....

Thanks for the help in advance!