Blue Fury Support Thread.

[kabopar]

The main aim of 3.5.1 is to correct the hw error count. It will give a tiny bit extra hash rate but nothing overly significant.

The ever increasing HW error rate may still be a concern (and reduces the submitted shares...)

[1713883587]

1713883587

[kabopar]

For those of you that want to run both BE's and BF on same pc (Win 7):

BE's (Block Eruptors) running under an instance of bfgminer 3.2.1, with the following shortcut (text in Target field of shortcut)
C:\temp\bfgminer-3.2.0-win64\bfgminer.exe -o [pool url] -u [user name] -p [password] -G -S erupter:all --icarus-options 115200:1:1 --icarus-timing 3.0=100

(change to suit the location of your executable)

Once the BE's are running, run a separate instance of bfgminer for BF.  I used
either bfgminer 3.2.0 ('special', with the BF driver installed per the support thread)
using bfgminer32 ver 3.2.0 and the batch file of the style
bfgminer.exe -S "BF1:all" -o [pool url] -u [user name] -p [password] 
(this works ok w/o H errors)

or 3.5.1, using a batch file with the content:
bfgminer.exe -S bigpic:all -o [pool url] -u [user name] -p [password]
(works ok but with increasing H errors)

Had both running on the same old laptop for a few days now (with BF going on and off for different tests and s/w configurations).

Cheers

[Epinnoia]

I've downloaded the drivers, they work flawlessly, these seem to self-install, just make sure that the driver install program that pops up recognises all your Blue Furies...

Zadig doesn't install drivers.  It associates drivers with devices.  When you run Zadig, you're binding the USB device with USB drivers.  

In brief, if the device shows up as a USB device, it's probably configured for CGMiner.  If it shows up as a COM port, it's probably configured for BFGMiner.  I switch between them quite often for testing.  

[Beastlymac]

Second post updated with instructions on how to flash your device on ubuntu. Please bare in mind that it is at your own risk.

[HellDiverUK]

I'm hoping to run these things on OpenWRT.  It'll need a USB to serial driver, most likely.  Which one?

[FrontLineFodder]

Second post updated with instructions on how to flash your device on ubuntu. Please bare in mind that it is at your own risk.

Hi BeastlyMac,

Is there any changelog for the firmware file ?

I have one BF hashing at under 2GH/s that I'll run it on regardless but what changes are there I should look out for ?

Thanks

[Taugeran]

I have 50 running at 90Gh/s total. Two throw tons of hardware errors. Shares found on same two are very low even though hashrate is reported normal.

These things run very cool. Begging to to overclocked. Hoping to be able to tweak in the future.

Pictures?  I posted above how it is possible to hardware overclock. Firmware over clocking might be available in the future I just don't want to cause more issues that would then need to be fixed.

which post on oc'ing


probably tarding and can't find it

[FrontLineFodder]

which post on oc'ing


probably tarding and can't find it

https://bitcointalk.org/index.php?topic=319419.msg3486886#msg3486886

[Taugeran]

which post on oc'ing


probably tarding and can't find it

https://bitcointalk.org/index.php?topic=319419.msg3486886#msg3486886

ty

[Zeek_W]

Seems to be a general lack of QA on these

[Epinnoia]

Second post updated with instructions on how to flash your device on ubuntu. Please bare in mind that it is at your own risk.

There's another Amtel package that needs to be installed, from repository.  

Unfortunately, the re-flash did nothing to help my 1.4GH/sec fury.  It's still only getting 1.4GH/sec.

I appreciate your efforts, Beastlymac.  Looks like I am going to have to box this thing up and send it to SSINC for replacement. 

[mcmike313]

I am having problems with my minepoen

i can run eruptors fine i have the latest version of minepeon (Linux minepeon 3.6.11-18-ARCH+ armv6l])

when i connect the blue fury device in i see it show up in
ls /dev

ive tried every combination from forums and yet i still cannot use it to mine

do i need to do something with the buttons on it?
the device is just constant red light

[Mudbankkeith]

I am having problems with my minepoen

i can run eruptors fine i have the latest version of minepeon (Linux minepeon 3.6.11-18-ARCH+ armv6l])

when i connect the blue fury device in i see it show up in
ls /dev

ive tried every combination from forums and yet i still cannot use it to mine

do i need to do something with the buttons on it?
the device is just constant red light

Runs great on minepeon 0.2.4    "  -S BPM:all   "

Hash rate 2432Mh on minepeon,  error rate 59.33%,  pool shows 2252Mh,  reject 0.87%,  total losses 60.2%

The 59% error cannot be true figure. I suspect the first 50% is due to the chip running at half speed, the correct error rate is then circa 9.26%

5000Mh * 50% = 2500Mh,    less circa 9% =  2275Mh,   less circa 1% = 2252Mh  this must be too close for coincidence?

Not tried it yet with erupters in the mix.

Edit:- add a good fan and the hashrate goes up

[mcmike313]

#!/bin/bash
sleep 10
/usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer -S BPM:all -c /opt/minepeon/etc/miner.conf


no luck
am i on the wrong version?

[Mudbankkeith]

#!/bin/bash
sleep 10
/usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer -S BPM:all -c /opt/minepeon/etc/miner.conf


no luck
am i on the wrong version?

There are problems with BFG 3.5.0
If your build uses this version then you need also to specify the port number.
I am using minepeon 0.2.4 with BFG 3.3.0   .............  there is a patch version of BFG 3.5.1(not tried it yet)

[mcmike313]

How would I downgrade to make it work or what is the command for the port? I tried the patched version I think it was bfgminer-fury but still no luck

[Jeffrey]

For those of you that want to run both BE's and BF on same pc (Win 7):

BE's (Block Eruptors) running under an instance of bfgminer 3.2.1, with the following shortcut (text in Target field of shortcut)
C:\temp\bfgminer-3.2.0-win64\bfgminer.exe -o [pool url] -u [user name] -p [password] -G -S erupter:all --icarus-options 115200:1:1 --icarus-timing 3.0=100

(change to suit the location of your executable)

Once the BE's are running, run a separate instance of bfgminer for BF.  I used
either bfgminer 3.2.0 ('special', with the BF driver installed per the support thread)
using bfgminer32 ver 3.2.0 and the batch file of the style
bfgminer.exe -S "BF1:all" -o [pool url] -u [user name] -p [password] 
(this works ok w/o H errors)

or 3.5.1, using a batch file with the content:
bfgminer.exe -S bigpic:all -o [pool url] -u [user name] -p [password]
(works ok but with increasing H errors)

Had both running on the same old laptop for a few days now (with BF going on and off for different tests and s/w configurations).

Cheers

Sir, this post was most helpful! I'm still waiting for my BF's to arrive, but when they do I'm planning to run them together with my current BE setup. I was already looking for information to prepare it so they could be up and running as soon as they arrived.

So thanks to you I can make sure I have the right miners and command lines ready.

Thank you!

[kabopar]

For those of you that want to run both BE's and BF on same pc (Win 7):

BE's (Block Eruptors) running under an instance of bfgminer 3.2.1, with the following shortcut (text in Target field of shortcut)
C:\temp\bfgminer-3.2.0-win64\bfgminer.exe -o [pool url] -u [user name] -p [password] -G -S erupter:all --icarus-options 115200:1:1 --icarus-timing 3.0=100

(change to suit the location of your executable)

Once the BE's are running, run a separate instance of bfgminer for BF.  I used
either bfgminer 3.2.0 ('special', with the BF driver installed per the support thread)
using bfgminer32 ver 3.2.0 and the batch file of the style
bfgminer.exe -S "BF1:all" -o [pool url] -u [user name] -p [password] 
(this works ok w/o H errors)

or 3.5.1, using a batch file with the content:
bfgminer.exe -S bigpic:all -o [pool url] -u [user name] -p [password]
(works ok but with increasing H errors)

Had both running on the same old laptop for a few days now (with BF going on and off for different tests and s/w configurations).

Cheers

Sir, this post was most helpful! I'm still waiting for my BF's to arrive, but when they do I'm planning to run them together with my current BE setup. I was already looking for information to prepare it so they could be up and running as soon as they arrived.

So thanks to you I can make sure I have the right miners and command lines ready.

Thank you!

You are welcome, good luck
Let us know what performance are your BF's getting

Cheers

[Mudbankkeith]

How would I downgrade to make it work or what is the command for the port? I tried the patched version I think it was bfgminer-fury but still no luck

Just download minepeon 0.2.4 onto a spare SD card.

https://bitcointalk.org/index.php?topic=251675.msg2672927#msg2672927


http://rdmsnippets.com/2013/07/24/mining-bitcoins-with-usb-block-erupters-a-raspberry-pi-and-minepeon/

[zyk0]

Weird, switched to bfgminer 3.5.1 and the reported error rate was way down:

Code:

 BPM0       | 5s: 2.21 avg: 2.21 u: 2.09 Gh/s | A:2431 R:16+1(.69%) HW:350/3.5%    
 BPM1       | 5s: 2.30 avg: 2.30 u: 2.17 Gh/s | A:2407 R:17+0(.70%) HW:382/3.7%    
 BPM2       | 5s: 2.29 avg: 2.29 u: 2.16 Gh/s | A:2465 R:12+0(.48%) HW:408/4.0%    
 BPM3       | 5s: 1.99 avg: 1.99 u: 1.88 Gh/s | A:2148 R:19+0(.88%) HW:312/3.5%    

but now after flashing the firmware on the furies, they're back up again

Code:

 BPM 0:       |  2.29/ 2.29/ 2.18Gh/s | A: 81 R:0+0(none) HW: 26/7.0%
 BPM 1:       |  2.21/ 2.21/ 2.19Gh/s | A: 79 R:0+0(none) HW: 72/ 17%
 BPM 2:       |  1.99/ 1.99/ 1.89Gh/s | A: 70 R:1+0(1.4%) HW: 44/ 13%
 BPM 3:       |  2.31/ 2.30/ 0.51Gh/s | A: 18 R:0+1(5.3%) HW:265/ 76%

and one of them is again being stubborn about giving good performance... I need to learn to leave well-enough alone.