Blue Fury Support Thread. - page 21.

MaxGen

member

Activity: 79

Merit: 10

Just got my miner tonight, shutdown minepeon and connected the BF. Booted Mionepeon and it was mining at 145Mh. Gradually went up to 500Mhz, then started dropping until it was no longer detected.

I cannot get this thing to mine on Mineoepn, Win7 or Win8. Usign the WinUSB drivers on windows machines. Tried BFGMiner on Minepeon,

All systems just throwing 100% HW errors.

Tries the reset on Windows systems, but it isn't helping at all

Any suggestions?

Code:

 cgminer version 3.8.1 - Started: [2013-11-12 20:06:57]
--------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:660  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 69  GF: 0  RF: 0
 Connected to stratum.btcguild.com diff 2 with stratum as user User_2
 Block: 676b62e1...  Diff:511M  Started: [20:06:57]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BF1 0:                |  0.000/ 0.000h/s | A:0 R:0 HW:660 WU:0.0/m
--------------------------------------------------------------------------------

 [2013-11-12 20:06:50] Started cgminer 3.8.1
 [2013-11-12 20:06:56] Probing for an alive pool
 [2013-11-12 20:06:56] Pool 0 difficulty changed to 2
 [2013-11-12 20:06:57] Network diff set to 511M
 [2013-11-12 20:06:57] Pool 1 difficulty changed to 3

Code:

 bfgminer version 3.6.0 - Started: [2013-11-12 21:09:14] - [  0 days 00:00:20]
 [M]anage devices [P]ool management [S]ettings [D]isplay options  [H]elp [Q]uit
 Connected to stratum.btcguild.com diff 2 with stratum as user User_2
 Block: ...eb64e589 #269323  Diff:511M ( 3.66Ph/s)  Started: [21:09:14]
 ST:2  F:0  NB:1  AS:0  BW:[175/129 B/s]  E:0.00  I: 0.00 BTC/hr  BS:0
 1            |  1.35/ 1.62/ 0.00Gh/s | A:0 R:0+0(none) HW:137/100%
--------------------------------------------------------------------------------
 BPM 0:       |  1.31/ 1.59/ 0.00Gh/s | A:0 R:0+0(none) HW:153/100%
--------------------------------------------------------------------------------
ing():396
 [2013-11-12 21:09:13] Probing for an alive pool
 [2013-11-12 21:09:14] Pool 0 http://stratum.btcguild.com:3333 alive
 [2013-11-12 21:09:14] Network difficulty changed to 511M ( 3.66Ph/s)
 [2013-11-12 21:09:14] Pool 1 http://stratum.bitcoin.cz:3333 alive
 [2013-11-12 21:09:14] Pool 1 is hiding block contents from us

NocTurNalFX

member

Activity: 99

Merit: 10

Just started to get Comms errors on the block erupters. never had this problem before running them with the red furys. I have them running on 2 Anker 9+1 hubs if that makes a difference.

every few minutes the green light on the BE's will come on steady for about 5 or so seconds. not all of them at once, but half of them here and there. Never had this problem before.

Is there any commands I should be running with all of them running from the same cgminer instance ?

NocTurNalFX

member

Activity: 99

Merit: 10

Got 2 red furys in the mail today. Hashing away on cgminer with 15 be's. seem to be running good i suppose. one is about 2.2g's and the other hovering 2.0 both ~30% hardware errors. Is there something i can do to see less hardware errors? they have been hashing for about 3 hours now. one of them seems to be putting out a bunch of stale shares.

zamot

member

Activity: 122

Merit: 10

Quote from: -ck on November 10, 2013, 05:19:51 PM

I've put up a new version of cgminer, 3.8.1 with improvements to the blue/red fury devices.

Any idea why i get this errors on BF1s ?

Code:

 [2013-11-12 23:08:58] Hotplug: bitfury added BF1 5
 [2013-11-12 23:08:58] BF1 5 BF1RequestWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-11-12 23:08:58] BF1 5: Device disappeared, disabling thread
 [2013-11-12 23:08:58] BF1 5 failure, disabling!

And it is random on time and also on device.
I run cgminer 3.8.1 on Debian 7.1. It is not runing on RPi. There is no pencil mod.
There are 5 BEs and 5 BF1s, each od them on its own USB hub ( 3,5A powered).
It was try with connection of hubs into cascade ( BF1s hub connected to BEs hub and this to computer) and also try to connect hubs directly to computer and always the same result.
If i reset BF1s with reset switch on board it comes back.

Epinnoia

full member

Activity: 209

Merit: 100

Quote from: Mudbankkeith on November 12, 2013, 06:05:31 PM

I have a 10 port hub that craps out with only one device plugged in. The 4amp brick is now only feeding 0.4amp. (Binned the brick) The new brick fixed it.

try 2 erupters if it works:-
then 2 erupters + 1 BF if it works:-
then 2 erupters + the other BF if it works:-
then 2 BF "
then 2 BF + 1 erupter "
then 2 BF + the other erupter "
then 2 BF + 2 erupters "

Post your results, but it still shouts power problems.

Perhaps I was unclear.

2 erupters works. 2 erupters with 1 fury works. 2 erupters with 2 furies causes one, not both, of the erupters to go incommunicado -- regardless of where that erupter is (ie. on another hub completely). The 2 furies work with no erupters. The BEs are not being fed the same power as the furies. I have isolated the furies power from the erupters power. I get the same behavior when the BEs are on the same powered hub as the BFs as I get when the BEs are on a completely different hub. Both BEs look to be of the same type, with both saying rev 3.00.

I'll check on the USB version of the various ports being used, but I am pretty sure they're all 2.0. It's a fairly old msi g33m mobo.

ON EDIT: Yep. USB 1.1/2.0 | 6 x USB 2.0 (http://www.newegg.com/Product/Product.aspx?Item=N82E16813130120)

ON EDIT(2): With only 1 erupter, the results are actually interesting. I had both furies hashing. Added an erupter to another port/hub entirely, and the 2nd fury stops working. Bizarre. I'm back to my original determination: 1 fury works with erupters. More than 1 fury doesn't (in my Win7 x64, at least).

``cgminer.exe --usb "BF1:2"`` is what I am using to launch, since I have two furies.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: Epinnoia on November 12, 2013, 05:49:23 PM

Quote from: HellDiverUK on November 12, 2013, 05:14:23 PM

Quote from: Mudbankkeith on November 12, 2013, 05:10:48 PM

Quote from: Epinnoia on November 12, 2013, 05:04:53 PM

AS SOON as I put it into the HUB, my AMU 1 (BE) unit gets continuous HW errors, and reports speeds of like 500+ ghps.

Check the power output on your hub.

Agreed. This screams power issues.

I run my hubs off the same PSU I run my Blades off, so there's 80A getting rammed up the hub's chuff. Never any issues with power. Wink

I did have similar issues when I ran the hubs off the power bricks supplied with the hub.

It's a 10 port hub with only 2 erupters and 2 furies in it. And the erupters are the nearest to the power input, so likely to be getting their power before the BFs at the far end.

It doesn't feel like power issues. It feels like a hardware conflict. And I think I adequately isolated power as being the issue. I took the erupters out of the same hub, and put them onto a 4port unpowered usb hub plugged into the computer. The issue persists.

It seems that one of my BEs is unaddressable while this newest fury is plugged in. And it doesn't matter if they're even on the same root hub, or powered separately.

On a fresh reboot, BEs in one HUB, BFs in another, both lights on the BEs were on until I started bfgminer which is configured only to use the BFs. Once I started bfgminer, and the furies spun up, the light on one of the erupters turned OFF -- even though nothing was talking to it, and it's on another hub. I closed out bfgminer, so nothing is mining now. And now that light on the erupter is alternating between out and on for a little blink every so often (between 2 to 10 seconds).

And, as just I guessed it would do, as soon as I just removed the latest BF from it's completely different HUB, the BE's light (on another USB port completely) went solid green.

I have a 10 port hub that craps out with only one device plugged in. The 4amp brick is now only feeding 0.4amp. (Binned the brick) The new brick fixed it.

try 2 erupters if it works:-
then 2 erupters + 1 BF if it works:-
then 2 erupters + the other BF if it works:-
then 2 BF "
then 2 BF + 1 erupter "
then 2 BF + the other erupter "
then 2 BF + 2 erupters "

Post your results, but it still shouts power problems.

Edit:- USE ONLY YOUR USB2 PORTS on the PC

Epinnoia

full member

Activity: 209

Merit: 100

Quote from: HellDiverUK on November 12, 2013, 05:14:23 PM

Quote from: Mudbankkeith on November 12, 2013, 05:10:48 PM

Quote from: Epinnoia on November 12, 2013, 05:04:53 PM

AS SOON as I put it into the HUB, my AMU 1 (BE) unit gets continuous HW errors, and reports speeds of like 500+ ghps.

Check the power output on your hub.

Agreed. This screams power issues.

I run my hubs off the same PSU I run my Blades off, so there's 80A getting rammed up the hub's chuff. Never any issues with power. Wink

I did have similar issues when I ran the hubs off the power bricks supplied with the hub.

It's a 10 port hub with only 2 erupters and 2 furies in it. And the erupters are the nearest to the power input, so likely to be getting their power before the BFs at the far end.

It doesn't feel like power issues. It feels like a hardware conflict. And I think I adequately isolated power from being the cause/issue. I took the erupters out of the same hub, and put them onto a 4port unpowered usb hub plugged directly into the computer. The issue persists.

It seems that one, and only one, of my two BEs is unaddressable while this newest fury is plugged in. And it doesn't matter if they're even on the same root hub, or powered separately.

On a fresh reboot, BEs in one HUB, BFs in another (each hub plugged into the back of computer), both lights on the BEs were on until I started bfgminer which is configured only to use the BFs. Once I started bfgminer, and the furies spun up, the light on one of the erupters turned OFF -- even though nothing was talking to it, and it's on another hub. I closed out bfgminer, so nothing is mining now. And now that light on the erupter is alternating between out and on for a little blink every so often (between 2 to 10 seconds).

And, just as I guessed it would do, as soon as I just removed the latest BF from its completely different HUB, the BE's light (on another USB port completely) went solid green. It's just one of the two erupters, not both -- which baffles the hell out of me. I am sure there is a logical explanation, but I don't think it has to do with power. There's plenty of power. This is a USB conflict of some sort, I think.

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: Mudbankkeith on November 12, 2013, 05:10:48 PM

Quote from: Epinnoia on November 12, 2013, 05:04:53 PM

AS SOON as I put it into the HUB, my AMU 1 (BE) unit gets continuous HW errors, and reports speeds of like 500+ ghps.

Check the power output on your hub.

Agreed. This screams power issues.

I run my hubs off the same PSU I run my Blades off, so there's 80A getting rammed up the hub's chuff. Never any issues with power. Wink

I did have similar issues when I ran the hubs off the power bricks supplied with the hub.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: Epinnoia on November 12, 2013, 05:04:53 PM

I had 1 fury working seamlessly with 2 BEs on the same win7 x64 machine, running the most recent versions of cgminer. Got my replacement fury today (for a total of 2), and AS SOON as I put it into the HUB, my AMU 1 (BE) unit gets continuous HW errors, and reports speeds of like 500+ ghps. And neither BE produces any results with that 2nd fury in the hub. They just don't get along at all, and it seems more like a hardware conflict than code.

So, I figured, let's go back to running the BEs with cgminer and the BF with bfgminer. Still, same problem.

Why would 1 fury work just fine with the two BEs, but not 2 furies?

It's not a huge problem. I can move the BEs to another computer if I absolutely must. Is there's a special trick anyone has found to get more than one fury working with BEs in win7?

Check the power output on your hub.

Epinnoia

full member

Activity: 209

Merit: 100

I had 1 fury working seamlessly with 2 BEs on the same win7 x64 machine, running the most recent versions of cgminer. Got my replacement fury today (for a total of 2), and AS SOON as I put it into the HUB, my AMU 1 (BE) unit gets continuous HW errors, and reports speeds of like 500+ ghps. And neither BE produces any results with that 2nd fury in the hub. They just don't get along at all, and it seems more like a hardware conflict than code.

So, I figured, let's go back to running the BEs with cgminer and the BF with bfgminer. Still, same problem.

Why would 1 fury work just fine with the two BEs, but not 2 furies?

It's not a huge problem. I can move the BEs to another computer if I absolutely must. Is there's a special trick anyone has found to get more than one fury working with BEs in win7?

HellDiverUK

hero member

Activity: 1246

Merit: 501

Pencil trick working here too. Shame about the HW errors.

albon

legendary

Activity: 1750

Merit: 1407

So when might we get a better firmware?

Slesh

member

Activity: 103

Merit: 10

Hi
I just plugged 8 pcs. today.
1 of 8 do not use the Win driver as others (under WIn7) but shows me name of device "ATmega32U2 DFU".
And LED is not blinkinkg or shining ... seems to be death
Can someone help?

The others works around 2,4-2,5 in BFGMiner 3.2

thanks Slesh

ssinc

sr. member

Activity: 364

Merit: 250

Hash for Cash!

I just pencil modded a unit that was hashing around 500 MH/s... now it's running at 2.8-3 GH/s! Shocked

HW errors were about 20% at first and after 2 hours they're at 8%

Jeffrey

full member

Activity: 182

Merit: 100

Today I received my 5 Bluefury's. Happy yay.

I already had the latest zadig and cgminer 3.8.1.
First I plugged one in, installed it, ran cgminer and bam, 2.3ghs
Then I took my 49port hub (powered by a PSU which has 27a on 5v), plugged all 5 of them in in random slots, waited for them to be installed, ran cgminer and... sort of bam.
2.1 / 2.0 / 2.3 / 1.2 / 2.0

Oi, whats that, a 1.2?? It's also producing a lot more HW's than the others. So I pulled everything out, took the 1.2 one, tried it on the usb port directly, but still the same. Tried it via the hub without any other usb device plugged in, still the same. Tried a different system (same drivers, same miner) but still not more than 1.2

So... now what? Is it a faulty device? Is there anything I could try?

Any help is appreciated.

edit:
Just had a look at the average speed over a couple of hours
1.97 / 1.83 / 1.88 / 1.77 / 0.94
Feels way too low for devices being sold as 2.2 - 2.7... I should have a minimum of 11ghs but I'm only getting 8.39, that's nearly 3ghs difference

werauchimmer

member

Activity: 65

Merit: 10

You need a specialized tool:

(Joking aside: Do NOT use the blue side!)

mikejones

newbie

Activity: 59

Merit: 0

Quote from: bitterdog on November 12, 2013, 05:17:55 AM

Quote from: bitterdog on November 11, 2013, 07:44:48 PM

Quote from: bitterdog on November 11, 2013, 06:56:08 PM

2 of these are pencil modded at different resistances . Been running for 5.5 hrs now with a fan set to low blowing on them - cool to the touch

USING BFGminer 3.2 because it shows the serial #
Ill mod the other 3 and check back later so you can see the differances

http://i40.tinypic.com/2qsbhvb.png

here is the 10 min mark
I have the fan on medium now and I could stick my tongue on it if I was drunk
DO NOT DO THIS WITHOUT A FAN BLOWING ON THEM!
Id imagine if you submerge these in Mineral oil you could push 4.5GH/s if you swap that resistor to .65k

http://i39.tinypic.com/2ym8zue.png

After 1.5 hrs things settle down a little

http://i40.tinypic.com/xpwi3c.png

And here is 9 hours 40 mins. Next Im going to put back to stock and see where it came from

http://i41.tinypic.com/2qbumfq.png

How do you return to stock??

kabopar

hero member

Activity: 616

Merit: 500

Quote from: Mudbankkeith on November 12, 2013, 07:41:48 AM

Quote from: kabopar on November 12, 2013, 07:34:27 AM

Quote from: Atomar on November 12, 2013, 06:29:17 AM

How about to replace the restistor with an Ω:.85 instead of the pencil mod ?? Would that work to ??
Or what's the "best/savest" restistor to use and get the fastest speed ??

It would not be a ".85" but more likely a 10k instead of the present 22K, as per Beastlymac's earlier comment "from what the EE told me you want to replace the 22K resistor with a 10K one". (or maybe an added 18k in parallel with the present 22k to achieve the same 10k). The 0.85K reading during the 'pencil mod' is the observed 'in-circuit' resistance. I suspect that de-soldering the current SMD 22k resistor and replacing it with 10k is a high risk task that most of us do not have the tools and skills to perform. At the same time a few pencil lines are low risk and reversible...

Cheers

Or a 5K to 15K variable? set at nominal 10K for fine tuning?

Probably a good idea for the next batch, if the cost impact is not too high. The 'pencil mod' is simple and low risk, so far seems to be quite stable after about 14 hours.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: kabopar on November 12, 2013, 07:34:27 AM

Quote from: Atomar on November 12, 2013, 06:29:17 AM

How about to replace the restistor with an Ω:.85 instead of the pencil mod ?? Would that work to ??
Or what's the "best/savest" restistor to use and get the fastest speed ??

It would not be a ".85" but more likely a 10k instead of the present 22K, as per Beastlymac's earlier comment "from what the EE told me you want to replace the 22K resistor with a 10K one". (or maybe an added 18k in parallel with the present 22k to achieve the same 10k). The 0.85K reading during the 'pencil mod' is the observed 'in-circuit' resistance. I suspect that de-soldering the current SMD 22k resistor and replacing it with 10k is a high risk task that most of us do not have the tools and skills to perform. At the same time a few pencil lines are low risk and reversible...

Cheers

Or a 5K to 15K variable? set at nominal 10K for fine tuning?

inform

newbie

Activity: 42

Merit: 0

But how much volts this eat procedure your side

Topic: Blue Fury Support Thread. - page 21. (Read 89537 times)