[ANN] US/North American Bitfury sales NEW STOCK ***NOW SHIPPING***

[cypherdoc]

just to throw more crap variables into the mix; i had a bad Raspi.

bad enough only to take hashing sub 100's for several days making it all the more confusing.  thank goodness it fully failed allowing me to figure it wasn't so much the boards.  inserted a new one and am at least now up in the 400's now.

Chainminer doesn't match my pool readings either.  ugh.

Deleted my last post because I'm still needing to tune down two cards that go out to zero.  Did your Raspi give any symptoms?  

it was confusing b/c it didn't fail outright.  the rig would start out hashing around 300ish, then drift down to sub 100's.  then it wouldn't boot up at all with just a red light.  originally i thought it was the sd card as above posts will indicate but fortunately i have new raspi's laying around.  the fact that the card booted up on the new raspi told me it wasn't the card.  plus, it told me that the ip address was overlapping with one of the other rigs thus explaining why both went to 0 when trying to boot this one up.

inexplicably it started working again but still below 100's.  b/c of this erratic behavior and the fact that just earlier had given me a red light, i decided to swap out the raspi.  sure enough, now i'm hashing mid 400's during the day.  it even hit 640 last night on ozcoin!    these BF's, in general, are definitely doing much better at nighttime when it gets cold here.

it's a bite, at least for me, b/c there are so many possibilities where things can go wrong with these fragile units.  is it the chips, h boards, m boards, regulator, chainminer, or raspi?  my avalons, in contrast, are much more stable and consistent.

on a side note, has anyone noticed ozcoin is showing higher hashrates than what is displaying locally in chainminer?  are other pools doing the same?

[tacotime]

So, a couple of my cards started turning off permanently until reboot again and I cranked their voltage down to about 0.8 V.

Rig is hashing at about 352 GH/s now instead of 360, but it seems stable.

[cypherdoc]

So, a couple of my cards started turning off permanently until reboot again and I cranked their voltage down to about 0.8 V.

Rig is hashing at about 352 GH/s now instead of 360, but it seems stable.

so how do you "anticipate" the amount of counterclockwise turning of the trimpot nut needed to decrease voltage?

[tacotime]

So, a couple of my cards started turning off permanently until reboot again and I cranked their voltage down to about 0.8 V.

Rig is hashing at about 352 GH/s now instead of 360, but it seems stable.

so how do you "anticipate" the amount of counterclockwise turning of the trimpot nut needed to decrease voltage?

It seems like about a quarter turn or so is 0.050 V, but it's not consistent among cards I find

[cypherdoc]

So, a couple of my cards started turning off permanently until reboot again and I cranked their voltage down to about 0.8 V.

Rig is hashing at about 352 GH/s now instead of 360, but it seems stable.

so how do you "anticipate" the amount of counterclockwise turning of the trimpot nut needed to decrease voltage?

It seems like about a quarter turn or so is 0.050 V, but it's not consistent among cards I find

any response on the rma to return heatsinked defective h boards?

[tacotime]

So, a couple of my cards started turning off permanently until reboot again and I cranked their voltage down to about 0.8 V.

Rig is hashing at about 352 GH/s now instead of 360, but it seems stable.

so how do you "anticipate" the amount of counterclockwise turning of the trimpot nut needed to decrease voltage?

It seems like about a quarter turn or so is 0.050 V, but it's not consistent among cards I find

any response on the rma to return heatsinked defective h boards?

Nah, haven't heard anything one way or the other, but since I adjusted the trimpots everything has been running more or less okay.

Probably Dave is sitting around tweaking 8 bajillion of them in the TH/s mine at the moment

[salfter]

I Too compiled BFG miner and it only ran with 100% hw errors as well (after 15 minutes of running the timings never adjusted upward as they are expected.)  

Have you tried patching the bfgminer source to start at a slower speed, as I've done?  I have mine locked at 52, and it's been running for close to two days now.  The hardware error rate over that period has been about 0.25%...not as good as the BFL miners (one of those logged one error in the same period, while the other has zero), but still fairly low.  At 52, I'm getting 68-69 GH/s from two H-boards.

[salfter]

Anyone got bfg working with new v3 boards  as it cannot seem to see them with normal settings that work for v1-2 ?

Been working for me for the past couple of days, built from GitHub HEAD.  I posted build instructions earlier in this topic.

[Xian01]

Got my rigs in, and can't get chainminer connected to ghash.io at all Trying to build BFGMiner...

Poop.

EDIT: Fuck my ass. BFGMiner only picks up 4 of 16 boards on the first rig I'm trying to bring up... it's going to be a long night...

[kano]

I've written a cgminer driver (it's in the current cgminer 3.8.0/3.8.1) for the BlackArrow Bitfury V1 boards.
I've no idea if that is the same as a standard Bitfury board - I never had one and the twits would never sell me one either.
... maybe I should have put in the copyright header that Punin and Buzzdave aren't allowed to use the driver

Anyway, as I posted about it the other day:

For anyone who has a V1 BlackArrow Bitfury board - the latest cgminer 3.8.1 (3.8.0 also) has the RPi source for a driver now - consider it an early release since there are certain improvements I'll make to it that I've already sorted out what to do - in future versions - but it already runs with great performance.

The configure option is --enable-bab

It runs at 39.9GH/s valid shares with a bit under 10% HW errors above the 39.9GH/s on a standard board
i.e. if you were to also count bad nonces returned (which I prefer not to but I will mention in case anyone wishes to compare that number) it's returning 44GH/s of good+bad nonces.

I've run it with a single board on Raspbian to write and test it - it's based on the V1 initialisation of a single board.
I based the I/O code on the chainminer GPIO/SPI code as should be obvious for anyone who looks at my driver-bab.c and chainminer (as I also mention that at the top of driver-bab.c)

It's a bit CPU hungry so soon I'll be spending more effort on reducing that - 20% CPU with a single board - I've only tested with a single board.

It also doesn't tune the chip at all - so there is also assured performance improvement there - it runs at default settings at the moment.
That's the next effort I'll expend on the driver.

If anyone has a standard V1 BitFury board I'd also be curious to know if it works with them.

[ericdc30]

  Hi guys I have this card that keeps going to 0GH/s. I already used the last slot for a card with high miso error count. Any idea what procedure I should be following to get my rig working at 100% reliably?

[Doff]

Got my rigs in, and can't get chainminer connected to ghash.io at all Trying to build BFGMiner...

Poop.

EDIT: Fuck my ass. BFGMiner only picks up 4 of 16 boards on the first rig I'm trying to bring up... it's going to be a long night...

Odd I am using ghash.io with no issues. Make sure to cool it enough, but don't over-cool it! Haha.  The heatsinks on the back of the regulator help I have found as well.

[Doff]

I've written a cgminer driver (it's in the current cgminer 3.8.0/3.8.1) for the BlackArrow Bitfury V1 boards.
I've no idea if that is the same as a standard Bitfury board - I never had one and the twits would never sell me one either.
... maybe I should have put in the copyright header that Punin and Buzzdave aren't allowed to use the driver

Anyway, as I posted about it the other day:

For anyone who has a V1 BlackArrow Bitfury board - the latest cgminer 3.8.1 (3.8.0 also) has the RPi source for a driver now - consider it an early release since there are certain improvements I'll make to it that I've already sorted out what to do - in future versions - but it already runs with great performance.

The configure option is --enable-bab

It runs at 39.9GH/s valid shares with a bit under 10% HW errors above the 39.9GH/s on a standard board
i.e. if you were to also count bad nonces returned (which I prefer not to but I will mention in case anyone wishes to compare that number) it's returning 44GH/s of good+bad nonces.

I've run it with a single board on Raspbian to write and test it - it's based on the V1 initialisation of a single board.
I based the I/O code on the chainminer GPIO/SPI code as should be obvious for anyone who looks at my driver-bab.c and chainminer (as I also mention that at the top of driver-bab.c)

It's a bit CPU hungry so soon I'll be spending more effort on reducing that - 20% CPU with a single board - I've only tested with a single board.

It also doesn't tune the chip at all - so there is also assured performance improvement there - it runs at default settings at the moment.
That's the next effort I'll expend on the driver.

If anyone has a standard V1 BitFury board I'd also be curious to know if it works with them.

Id love to see this running on a V3 rig, I miss having fail-over. Its Cainsmore all over again for me.

[Xian01]

Odd I am using ghash.io with no issues. Make sure to cool it enough, but don't over-cool it! Haha.  The heatsinks on the back of the regulator help I have found as well.

 Did you have to preface the ghash.io url with "stratum+tcp://nl1.ghash.io" in Chainminer ?

EDIT: sshing into the pi gets me this;

Using username "pi".
pi@192.168.5.230's password:
Linux bf01 3.6.11+ #474 PREEMPT Thu Jun 13 17:14:42 BST 2013 armv6l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Nov 11 22:44:37 2013 from soundwave.home.lan
cat: .stat.log: No such file or directory
pi@bf01:/run/shm$

 Guess the .stat.log not being where it is might explain something wrong with why Chainminer isn't starting up....

[Doff]

Odd I am using ghash.io with no issues. Make sure to cool it enough, but don't over-cool it! Haha.  The heatsinks on the back of the regulator help I have found as well.

 Did you have to preface the ghash.io url with "stratum+tcp://nl1.ghash.io" in Chainminer ?

No, and make sure you use a password it doesn't like the blank one.

I just have nl1.ghash.io in all 3 boxes.

[tacotime]

Hi guys I have this card that keeps going to 0GH/s. I already used the last slot for a card with high miso error count. Any idea what procedure I should be following to get my rig working at 100% reliably?

You need to turn the voltage down, scroll back a few pages to see how to adjust the trimpots

[mb300sd]

Hi guys I have this card that keeps going to 0GH/s. I already used the last slot for a card with high miso error count. Any idea what procedure I should be following to get my rig working at 100% reliably?

If its one of the new m-boards, the cards are divided into groups of 4.

[mb300sd]

I have 1 bad H-card what will not hash at all... Waiting on RMA, how long does it usually take?

[Xian01]

If its one of the new m-boards, the cards are divided into groups of 4.

 Oh, I see, so 16 boards should appear as 4 miners to BFGMiner ?

[Doff]

If its one of the new m-boards, the cards are divided into groups of 4.

 Oh, I see, so 16 boards should appear as 4 miners to BFGMiner ?

Yes 4 banks of 4.
 
Bank 1
1: 39.084GH/s
2: 37.08GH/s
3: 37.366GH/s
4: 36.808GH/s
Bank 2
5: 36.808GH/s
6: 37.638GH/s
7: 35.935GH/s
8: 38.254GH/s
Bank 3
9: 36.808GH/s
10: 37.581GH/s
11: 34.66GH/s
12: 37.338GH/s
Bank 4
13: 34.675GH/s
14: 30.909GH/s
15: 33.887GH/s
16: 35.949GH/s