[ANN] US/North American Bitfury sales NEW STOCK ***NOW SHIPPING*** - page 3.

solarion

hero member

Activity: 966

Merit: 513

Quote from: allinvain on March 30, 2014, 07:41:32 PM

Cool, thanks for the tip. I shall give it a go.

Here is a quote from kano:

Quote

The BaB driver with 7 boards uses less than 10% CPU on RPI Arch - and for my 7 BA BaB boards, mines at over 270GH/s
It seems to be limited to 2 boards per SPI channel. More tends to get all sorts of errors.
Will look into resolving that ... one day.

Kind of a bummer Sad

Most of my rigs have more than 2 boards per SPI channel so :\ yeah..

After a few minutes of running with the bab-options set on my v1.2 rigs it still seems that performance is not consistently equivalent to that of chainminer. That may have something to do with the quote from kano above.

Another thing is I'm not sure if cgminer turns off dead or "zombie" chips like I would when manually editing the chainminer best.cnf file. By zombie chips I mean those that no matter what always hash at a pitifully low hashrate (0.05 to 0.10).

It does shut them down. Check the driver for BAB_BAD_DEAD. This is set to BAB_BAD_MIN * 2 by default. I have cgminer running on a full rig.

The display tells you exactly what's going on with your rig:

0: BaB 0 : 4.16.256 B:034 D:000

BaB 0 4(banks)16(cards)256(chips)34(bad_min)0(disabled)

Here's a very naughty rig:

0: BaB 0 : 4.13.200 B:008 D:025

Cgminer doesn't seem to like the cards set to .85v. The same cards freak out bfgminer.

You can also decrease the time necessary for testing by changing the history setting to something like 120(s) from the default 300(s).

allinvain

legendary

Activity: 3080

Merit: 1080

Cool, thanks for the tip. I shall give it a go.

Here is a quote from kano:

Quote

The BaB driver with 7 boards uses less than 10% CPU on RPI Arch - and for my 7 BA BaB boards, mines at over 270GH/s
It seems to be limited to 2 boards per SPI channel. More tends to get all sorts of errors.
Will look into resolving that ... one day.

Kind of a bummer Sad

Most of my rigs have more than 2 boards per SPI channel so :\ yeah..

After a few minutes of running with the bab-options set on my v1.2 rigs it still seems that performance is not consistently equivalent to that of chainminer. That may have something to do with the quote from kano above.

Another thing is I'm not sure if cgminer turns off dead or "zombie" chips like I would when manually editing the chainminer best.cnf file. By zombie chips I mean those that no matter what always hash at a pitifully low hashrate (0.05 to 0.10).

solarion

hero member

Activity: 966

Merit: 513

You might try 57:54:54:2:15 on v2 cards and see what you get.

allinvain

legendary

Activity: 3080

Merit: 1080

I think I may have gotten the hang of the bab-options startup variable. I'm now using the following for v1.2 h-card rigs

Code:

--bab-options 57:53:52:1:15

For v2.3 I use:

Code:

--bab-options 53:53:51:1:15

Now it remains to be seen if for the long term the pool side performance matches that of chainminer.

allinvain

legendary

Activity: 3080

Merit: 1080

For me the power efficiency is not so important yet, I merely want it to match or exceed the performance of chainminer. Should I also set the BAB_SPI_SPEED higher even on v1.2 cards, and could you give me an example of the bab-options you use or perhaps some more aggressive bab options?

lol, found a post on a different forum by you that could be beneficial:

Quote

I've been altering these lines in driver-bab.c

#define BAB_MAXSPEED 57
#define BAB_DEFMAXSPEED 55
#define BAB_DEFSPEED 53
#define BAB_MINSPEED 52
#define BAB_ABSMINSPEED 32

#define BAB_TUNEUP 1.0
#define BAB_TUNEDOWN 10.0

These are also the values that can be passed to cgminer on startup. The format was posted by kano in the cgminer thread...somewhere around pg 700 I believe.

solarion

hero member

Activity: 966

Merit: 513

Quote from: allinvain on March 30, 2014, 12:35:47 PM

Quote from: solarion on March 29, 2014, 09:19:42 PM

Quote from: btljuice on March 29, 2014, 10:11:31 AM

Quote from: solarion on March 28, 2014, 10:57:26 PM

True enough about the sd cards, sandisk + proper shutdown and they never seem to corrupt. I've yet to have one flake out on 12 rigs. The wobble thing is a very fair criticism though. Never should've been set up with that silly connector.

Quote from: btljuice on March 28, 2014, 10:27:36 PM

I just wish the stratum proxy worked as failover (if primary pool fails, go to backup, so on), instead of splitting work.

Just chuck chainminer and that proxy and run cgminer.

Can anyone confirm cgminer working with V2.2 H-cards? I followed instructions found elsewhere in the forum, compiled from a certain github repo (can't find link right now) with --enable-bab and running cgminer did not hash, just gave spi errors. If I could get cgminer going for my V3 m/V2.2 H rig, I'd be very very happy

All of my hcards are v2 and running cgminer. Just nano driver-bab.c and change this:

#define BAB_SPI_SPEED 96000

to this:

#define BAB_SPI_SPEED 625000

run make again and you're gold.

These options can be passed to cgminer on startup:

--bab-options Set BaB options max:def:min:up:down:hz:delay:trf

As mentioned above bfgminer also works with --enable-bfsb, but cgminer autotunes bitfury, uses far less of the rpi's weak cpu, and runs much better imo.

I tried that but it seems that hashrate is consistently lower than with chainminer. I've got v2.3 h-cards. The v1.2 h-cards run on average about the same as with chainminer - or so it seems. I should mention that I did not change the SPI SPEED value for the v1.2 h-cards rigs only for the v2.3.

Maybe I should let cgminer tune for a longer period of time?

Watch the hw error rate. Cgminer is set to 1.0% tuneup and 10.0% tunedown so it wipes out huge numbers of hw errors. The mechanism it uses to do this is the osc so it's tuning chips all the way down to speed 32 over time. This causes power efficiency to improve dramatically over time, but if you don't want it to do that or you want it to do it in moderation then simply pass different values to cgminer at startup via the --bab-options parameter mentioned above. It's extremely flexible and capable of matching chainminer's performance.

solarion

hero member

Activity: 966

Merit: 513

Quote from: daddyfatsax on March 30, 2014, 12:48:39 PM

I tried changing the SPI_SPEED on my v1.2 cards, and it just gives me "BaB delay getting work" when it starts up.

Change line 1663 in driver-bab.c from "false" to "true". Don't forget to run make again.

daddyfatsax

hero member

Activity: 857

Merit: 1000

Anger is a gift.

I tried changing the SPI_SPEED on my v1.2 cards, and it just gives me "BaB delay getting work" when it starts up.

allinvain

legendary

Activity: 3080

Merit: 1080

Quote from: solarion on March 29, 2014, 09:19:42 PM

Quote from: btljuice on March 29, 2014, 10:11:31 AM

Quote from: solarion on March 28, 2014, 10:57:26 PM

True enough about the sd cards, sandisk + proper shutdown and they never seem to corrupt. I've yet to have one flake out on 12 rigs. The wobble thing is a very fair criticism though. Never should've been set up with that silly connector.

Quote from: btljuice on March 28, 2014, 10:27:36 PM

I just wish the stratum proxy worked as failover (if primary pool fails, go to backup, so on), instead of splitting work.

Just chuck chainminer and that proxy and run cgminer.

Can anyone confirm cgminer working with V2.2 H-cards? I followed instructions found elsewhere in the forum, compiled from a certain github repo (can't find link right now) with --enable-bab and running cgminer did not hash, just gave spi errors. If I could get cgminer going for my V3 m/V2.2 H rig, I'd be very very happy

All of my hcards are v2 and running cgminer. Just nano driver-bab.c and change this:

#define BAB_SPI_SPEED 96000

to this:

#define BAB_SPI_SPEED 625000

run make again and you're gold.

These options can be passed to cgminer on startup:

--bab-options Set BaB options max:def:min:up:down:hz:delay:trf

As mentioned above bfgminer also works with --enable-bfsb, but cgminer autotunes bitfury, uses far less of the rpi's weak cpu, and runs much better imo.

I tried that but it seems that hashrate is consistently lower than with chainminer. I've got v2.3 h-cards. The v1.2 h-cards run on average about the same as with chainminer - or so it seems. I should mention that I did not change the SPI SPEED value for the v1.2 h-cards rigs only for the v2.3.

Maybe I should let cgminer tune for a longer period of time?

allinvain

legendary

Activity: 3080

Merit: 1080

Quote from: Gyrsur on March 30, 2014, 03:51:04 AM

6 of my 16 bitfury v1.2 H-CARD died over the time. October 2013 batch. no overclocking and no overheating! did someone face the same experience??

EDIT: seems to me quality of the bitfury v1.2 H-CARD (October 2013 batch) is not good enough to work with it 24/7 for a half year. some component on the card died. cards did not work again if I changed the slot on the bitfury v2.3 M-CARD.

I had the same problem, but luckily only 1 card died so far. Shame that they are so expensive to replace.

Gyrsur

legendary

Activity: 2856

Merit: 1520

Bitcoin Legal Tender Countries: 2 of 206

6 of my 16 bitfury v1.2 H-CARD died over the time. October 2013 batch. no overclocking and no overheating! did someone face the same experience??

EDIT: seems to me quality of the bitfury v1.2 H-CARD (October 2013 batch) is not good enough to work with it 24/7 for a half year. some component on the card died. cards did not work again if I changed the slot on the bitfury v2.3 M-CARD.

mb300sd

legendary

Activity: 1260

Merit: 1000

Drunk Posts

Use bfgminer and you won't have SD card issues anymore. I believe chainminer does a lot of writes, while bfgminer does none. Still using the crappy SD card supplied with my unit.

xstr8guy

hero member

Activity: 784

Merit: 1004

Glow Stick Dance!

Quote from: tom99 on March 29, 2014, 10:50:36 PM

Quote from: klondike_bar on March 29, 2014, 10:29:17 AM

Quote from: btljuice on March 28, 2014, 10:27:36 PM

Quote from: xzempt on March 28, 2014, 10:00:27 PM

if you use a good sd card, and shutdown the rpi properly you shouldnt have any issues.... my bitfury equip has been running non stop since january, once it was set up, ive never had to touch it, other that log in via pc and change pools....

I second that. I have a V3 m-board and V2.2 h-cards. I just keep some fans on them, make sure the cards don't wobble and they're good to go. I just wish the stratum proxy worked as failover (if primary pool fails, go to backup, so on), instead of splitting work.

I previously griped a dozen times because the machine would always orrupt SD cards and actually managed to turn two cards un-usable. (even when trying to format under a linux OS)

I upgraded to a Class 10, 16GB card and no more issues. I can unplug the machine hot, reboot it safely, no issues for a month or two now. Definitely an issue with using low-end SD cards.

what was brand name of this class 10 16GB card? I got problem again with sd card.

Patriot is a great premium brand. Be sure to get an rPi compatible SD card though. Check here first... http://elinux.org/RPi_SD_cards

Kingston are crap!

tom99

sr. member

Activity: 420

Merit: 250

Quote from: klondike_bar on March 29, 2014, 10:29:17 AM

Quote from: btljuice on March 28, 2014, 10:27:36 PM

Quote from: xzempt on March 28, 2014, 10:00:27 PM

if you use a good sd card, and shutdown the rpi properly you shouldnt have any issues.... my bitfury equip has been running non stop since january, once it was set up, ive never had to touch it, other that log in via pc and change pools....

I second that. I have a V3 m-board and V2.2 h-cards. I just keep some fans on them, make sure the cards don't wobble and they're good to go. I just wish the stratum proxy worked as failover (if primary pool fails, go to backup, so on), instead of splitting work.

I previously griped a dozen times because the machine would always orrupt SD cards and actually managed to turn two cards un-usable. (even when trying to format under a linux OS)

I upgraded to a Class 10, 16GB card and no more issues. I can unplug the machine hot, reboot it safely, no issues for a month or two now. Definitely an issue with using low-end SD cards.

what was brand name of this class 10 16GB card? I got problem again with sd card.

solarion

hero member

Activity: 966

Merit: 513

Quote from: btljuice on March 29, 2014, 10:11:31 AM

Quote from: solarion on March 28, 2014, 10:57:26 PM

True enough about the sd cards, sandisk + proper shutdown and they never seem to corrupt. I've yet to have one flake out on 12 rigs. The wobble thing is a very fair criticism though. Never should've been set up with that silly connector.

Quote from: btljuice on March 28, 2014, 10:27:36 PM

I just wish the stratum proxy worked as failover (if primary pool fails, go to backup, so on), instead of splitting work.

Just chuck chainminer and that proxy and run cgminer.

Can anyone confirm cgminer working with V2.2 H-cards? I followed instructions found elsewhere in the forum, compiled from a certain github repo (can't find link right now) with --enable-bab and running cgminer did not hash, just gave spi errors. If I could get cgminer going for my V3 m/V2.2 H rig, I'd be very very happy

All of my hcards are v2 and running cgminer. Just nano driver-bab.c and change this:

#define BAB_SPI_SPEED 96000

to this:

#define BAB_SPI_SPEED 625000

run make again and you're gold.

These options can be passed to cgminer on startup:

--bab-options Set BaB options max:def:min:up:down:hz:delay:trf

As mentioned above bfgminer also works with --enable-bfsb, but cgminer autotunes bitfury, uses far less of the rpi's weak cpu, and runs much better imo.

Taugeran

hero member

Activity: 658

Merit: 500

CCNA: There i fixed the internet.

Quote from: btljuice on March 29, 2014, 10:11:31 AM

Quote from: solarion on March 28, 2014, 10:57:26 PM

True enough about the sd cards, sandisk + proper shutdown and they never seem to corrupt. I've yet to have one flake out on 12 rigs. The wobble thing is a very fair criticism though. Never should've been set up with that silly connector.

Quote from: btljuice on March 28, 2014, 10:27:36 PM

I just wish the stratum proxy worked as failover (if primary pool fails, go to backup, so on), instead of splitting work.

Just chuck chainminer and that proxy and run cgminer.

Can anyone confirm cgminer working with V2.2 H-cards? I followed instructions found elsewhere in the forum, compiled from a certain github repo (can't find link right now) with --enable-bab and running cgminer did not hash, just gave spi errors. If I could get cgminer going for my V3 m/V2.2 H rig, I'd be very very happy

Bfgminer has excellent support that I can confirm works. Compile it on the Pi.

Have to add some modprobes to boot config then just sudo ./bfgminer -S bfsb:auto

klondike_bar

legendary

Activity: 2128

Merit: 1005

ASIC Wannabe

Quote from: btljuice on March 28, 2014, 10:27:36 PM

Quote from: xzempt on March 28, 2014, 10:00:27 PM

if you use a good sd card, and shutdown the rpi properly you shouldnt have any issues.... my bitfury equip has been running non stop since january, once it was set up, ive never had to touch it, other that log in via pc and change pools....

I second that. I have a V3 m-board and V2.2 h-cards. I just keep some fans on them, make sure the cards don't wobble and they're good to go. I just wish the stratum proxy worked as failover (if primary pool fails, go to backup, so on), instead of splitting work.

I previously griped a dozen times because the machine would always orrupt SD cards and actually managed to turn two cards un-usable. (even when trying to format under a linux OS)

I upgraded to a Class 10, 16GB card and no more issues. I can unplug the machine hot, reboot it safely, no issues for a month or two now. Definitely an issue with using low-end SD cards.

btljuice

member

Activity: 92

Merit: 10

Quote from: solarion on March 28, 2014, 10:57:26 PM

True enough about the sd cards, sandisk + proper shutdown and they never seem to corrupt. I've yet to have one flake out on 12 rigs. The wobble thing is a very fair criticism though. Never should've been set up with that silly connector.

Quote from: btljuice on March 28, 2014, 10:27:36 PM

I just wish the stratum proxy worked as failover (if primary pool fails, go to backup, so on), instead of splitting work.

Just chuck chainminer and that proxy and run cgminer.

Can anyone confirm cgminer working with V2.2 H-cards? I followed instructions found elsewhere in the forum, compiled from a certain github repo (can't find link right now) with --enable-bab and running cgminer did not hash, just gave spi errors. If I could get cgminer going for my V3 m/V2.2 H rig, I'd be very very happy

Soros Shorts

donator

Activity: 1617

Merit: 1012

Yeah, too bad he isn't selling anymore. I actually like my MBP rigs even though they take a long time to tune and require third party cases to properly secure and stabilize the cards. You can build them nice and quiet, unlike the other noisy offerings that need 2000+ RPM fans to operate.

I plan to keep mine running until 25 billion difficulty and beyond.

xstr8guy

hero member

Activity: 784

Merit: 1004

Glow Stick Dance!

Quote from: xzempt on March 28, 2014, 10:00:27 PM

Quote from: xstr8guy on March 28, 2014, 09:35:16 PM

Quote from: xzempt on March 28, 2014, 09:17:37 PM

Quote from: xstr8guy on March 28, 2014, 09:07:21 PM

Quote from: xzempt on March 28, 2014, 08:40:52 PM

:/

Lol, I remember when Dave was running customer support for Tom/BitcoinAsic. If I'm not mistaken, he was volunteering his time to help dig Tom out of his hopeless mess. He even helped me get my refund.

You've come a long way Dave!

Btw, has anyone heard what Tom is up to these days? I bet he wished he hadn't imploded so violently. He could have been at the top and Dave might have been just an employee instead of a BTC mogul.

dont get me wrong i have no hate for Dave... he should be very proud of what he has built so far.... just disappointed at a refusal to price in line with other manufacturers... the community helped finance his operation, and now he has made it, just feels like he is giving us a big F U since our money isnt needed any longer to keep them going.

Individual sales were never MGP's priority. He had his big-time buyers/investors. Dave just let us piggyback onto the hardware sales. This was known from the very beginning and shouldn't be a big surprise. Besides, there are many other miners to chose from now.

I'm personally running over 1.5THs of Bitfury boards and love my fickle little buggers. But I'm much more pleased running my KNC and BitMain machines. I don't have to worry about wiggling and swapping boards and constantly restarting. What you don't see in the video of Dave's datacenter is the army of interns running about wiggling boards and writing new SD cards, lol. Oh, and running to the store for new supplies of crappy rPi's.

if you use a good sd card, and shutdown the rpi properly you shouldnt have any issues.... my bitfury equip has been running non stop since january, once it was set up, ive never had to touch it, other that log in via pc and change pools....

I haven't had many SD card issues since I learned to shutdown properly. But occasionally I'll lose the ability to connect to a rig via SSH or the web interface and have to do a hard shutdown. I've scrambled a few SD cards that way.

Topic: [ANN] US/North American Bitfury sales NEW STOCK ***NOW SHIPPING*** - page 3. (Read 576785 times)

Topic: [ANN] US/North American Bitfury sales NEW STOCK NOW SHIPPING - page 3. (Read 576785 times)