Blue Fury Support Thread.

[mcmike313]

thats what im running

MinePeon Version
MinePeon 0.2.4
Miner Version
bfgminer3.4.0

still ls /dev lists the device
but running minepeon wont

[1715280533]

1715280533

[1715280533]

1715280533

[1715280533]

1715280533

[Mudbankkeith]

thats what im running

MinePeon Version
MinePeon 0.2.4
Miner Version
bfgminer3.4.0

still ls /dev lists the device
but running minepeon wont

Mine is BFGminer3.3.0

You could always try the git pull for 3.5.1 (just out today for pc)

[mcmike313]

thats what im running

MinePeon Version
MinePeon 0.2.4
Miner Version
bfgminer3.4.0

still ls /dev lists the device
but running minepeon wont

Mine is BFGminer3.3.0

You could always try the git pull for 3.5.1 (just out today for pc)

ive only got macs and a raspberry pi that can only run eruptors
i have no way of getting the blue fury to work, 48 hours of collecting dust with a red light on and no gh's

[Mudbankkeith]

thats what im running

MinePeon Version
MinePeon 0.2.4
Miner Version
bfgminer3.4.0

still ls /dev lists the device
but running minepeon wont

Mine is BFGminer3.3.0

You could always try the git pull for 3.5.1 (just out today for pc)

ive only got macs and a raspberry pi that can only run eruptors
i have no way of getting the blue fury to work, 48 hours of collecting dust with a red light on and no gh's

log in to your Pi with ssh
then use git  pull to look for the latest BFGminer3.5.1


cd /opt/minepeon/

git pull



logon is:- minepeon
pasword is:- peon

My hdmi cable is occupied at the moment, the spare is in the post, so I cannot take a look today.

[mcmike313]

rebooted it and it works i think i love you

[FrontLineFodder]

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.  

same here, installed the required package ( on ubuntu, sudo apt-get install dfu-programmer )
ran the update script ( needed to run as root so, sudo ./dfu-prog.sh ) #spent 5 mins trying to work out why it wasnt finding the fury 
upgraded each of the BF's one at a time, all successful.

four of my five are acceptable (at 2.2-2.4GH/s)
The lazy one is still below 2.0

my buddies one refuses to work, it reports hashing at 2.3GH/s however does not get any results accepted (invalid nonce), when mining using just his bad BF, the difficulty at 1 there is the occasional accepted result but 98% hardware error (using bfgminer 3.5.1). I flashed it however no change.

[Zeek_W]

I'm at 2.28/2.27/2.17 averages after 2.5 days. 

At least I got mine working, no sign of compensation or even a reply from my group buy

[Beastlymac]

I'm at 2.28/2.27/2.17 averages after 2.5 days. 

At least I got mine working, no sign of compensation or even a reply from my group buy

Did you buy through Julz? His compensation has been sent. I think he is organising distributing it now.

[Zeek_W]

I'm at 2.28/2.27/2.17 averages after 2.5 days. 

At least I got mine working, no sign of compensation or even a reply from my group buy

Did you buy through Julz? His compensation has been sent. I think he is organising distributing it now.

Yes

[guyver]

beastlymac

when is this firmware update being released

[Beastlymac]

beastlymac

when is this firmware update being released

The update that was required to fix the hw error rate has actually been incorporated into the bfgminer 3.5.1 update.

[nite423]

I'm now running with BFGMiner 3.5.1 after running CGMiner for a few days. Looking at BFGminer, it looks like I have one miner that is actually kicking out about 35% hardware errors while the other four miners are less then 4.5%.  I guess I'll let it run for a day and see if it straightens out...if it doesn't maybe I can get it swapped out.

[winit]

Twice now I have ended up with 5 of 6 BF sticks showing either 'Sick' or 'Dead' after an hour of hashing. Running in BFGminer on Win 7.

[underachiever]

I'm using both block erupters and blue furies on the same instance of bfgminer.

Like previous posters have said, you just have to specify your devices.  It's pretty easy to do on Linux.  I'm using RedHat 6, but the process should be similar on Ubuntu.  To find out where your miners are, run:

Code:

ls /dev/tty*

Block erupters show up as /dev/ttyUSB# and blue furies are /dev/ttyACM#

So your basic bfgminer command for 3 erupters and 2 blue furies would be:

Code:

bfgminer -c bfgminer.conf -S erupter:/dev/ttyUSB0 -S erupter:/dev/ttyUSB1 -S erupter:/dev/ttyUSB2 -S bigpic:/dev/ttyACM0 -S bigpic:/dev/ttyACM1

note that I've defined the blue furies as "bigpic".  On Ubuntu I had to use "bitfury" but on Windows it was "BF1".  I actually run 21 erupters and 2 furies.  It makes for a very long command line, but I launch with a shell script so it's no more difficult than specifying 'all'.

[mchu168]

I put a "-S noauto" ahead of my "-S /dev/x" string and solved a lot of problems..

[tk1337]

beastlymac

when is this firmware update being released

The update that was required to fix the hw error rate has actually been incorporated into the bfgminer 3.5.1 update.

3.5.1 definitely is improved over 3.5.0, however I'm showing a typical 3%-5% HW errors across all Fury miners (where as my 3.2.0 BFGMiner build had none, not sure how accurate that was though) and one at 43%, the one at 43% I believe is bad, as this is the same one that usually goes 'SICK' or 'DEAD' within 10hrs of mining, also, I've never seen it above 1.5x GH/s. Right now it's at 1.18GH/s; I've already spoken to my group buy leader about a replacement for this one.

OS: Arch Linux (MinePeon 0.2.4.1)


Hopefully this BFGMiner 3.5.1 will stay stable, as I'll be gone for two days *crosses fingers*.

[nhminer]

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.

I went back and reread this whole thread.  Maybe I'm just blind, but could you help out with a link to where you have the OC info?

Back in https://bitcointalk.org/index.php?topic=319419.msg3486886#msg3486886 you wrote "Edit. It is possible to overclock the units and push them to potentially 2.7 by replacing the 22k resistor with a 10k one."
but a little more info would be helpful...


BTW: I'm currently running 7 (thanks ssinc)  with w7x64, cgminer 3.7.2; 10 port cheap powered hub with max of 4 units in each hub
RESULTS: avg 2.3 per unit

~nh

[tk1337]

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.

I went back and reread this whole thread.  Maybe I'm just blind, but could you help out with a link to where you have the OC info?

Back in https://bitcointalk.org/index.php?topic=319419.msg3486886#msg3486886 you wrote "Edit. It is possible to overclock the units and push them to potentially 2.7 by replacing the 22k resistor with a 10k one."
but a little more info would be helpful...


BTW: I'm currently running 7 (thanks ssinc)  with w7x64, cgminer 3.7.2; 10 port cheap powered hub with max of 4 units in each hub
RESULTS: avg 2.3 per unit

~nh

Anyone that *should* be over-clocking these, would have the knowledge to look at the board and see which resistors are 10k; However, with that being said there are two resistors on the board at 10k, R8 & R11 (R8 next to PRG button, R11 next to RST button), so I'm assuming by Beastlymac's statement that both 10k resistors would need to be swapped out to 22k, but would like confirmation that it would be both, if not both which, R8 or R11?

EDIT:
Also, you would be replacing it with a SMD 1206 22k ohm 1/8w resistor (Beastlymac, correct me if I'm wrong please), which seem to be pricey at DigiKey at the moment due to stock shortages it looks like. However Mouser does have a good amount in stock at the moment and are much cheaper than DigiKey.

[will_a]

I read that to be replacing the 22k resister with the 10k one.  Mine are due to arrive today so can't check myself.

[nhminer]

Anyone that *should* be over-clocking these, would have the knowledge to look at the board and see which resistors are 10k; However, with that being said there are two resistors on the board at 10k, R8 & R11 (R8 next to PRG button, R11 next to RST button), so I'm assuming by Beastlymac's statement that both 10k resistors would need to be swapped out to 22k, but would like confirmation that it would be both, if not both which, R8 or R11?

EDIT:
Also, you would be replacing it with a SMD 1206 22k ohm 1/8w resistor (Beastlymac, correct me if I'm wrong please), which seem to be pricey at DigiKey at the moment due to stock shortages it looks like. However Mouser does have a good amount in stock at the moment and are much cheaper than DigiKey.

Agreed, issue is replace both, or one, just wanted direction before playing with the board

~nh