OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 101.

juhakall

sr. member

Activity: 658

Merit: 250

In this paste the summary 5s hashrate is zero because of a pool outage:

Code:

 bfgminer version 3.4.0 - Started: [2013-11-04 20:06:54] - [  0 days 04:29:32]
 [M]anage devices [P]ool management [S]ettings [D]isplay options  [H]elp [Q]uit
 Connected to nl1.ghash.io diff 128 with stratum as user juhakall.bfsb
 Block: ...ba64262f33dfbc74  Diff:391M ( 2.80Ph/s)  Started: [00:34:48]
 ST:0  F:0  NB:34  AS:0  BW:[117/ 44 B/s]  E:505.54  I: 9.25mBTC/hr  BS:2.95M
 4/80         |  0.10/185.3/171.1Gh/s | A:5074 R:13+0(.26%) HW:42536/6.2%
--------------------------------------------------------------------------------
 BSB 0:       | 37.69/37.43/34.62Gh/s | A:1040 R: 2+0(.19%) HW:10338/7.3%
 BSB 1:       | 38.66/38.48/35.02Gh/s | A:1039 R: 5+0(.48%) HW: 8681/6.1%
 BSB 2:       | 74.69/74.36/67.23Gh/s | A:1981 R: 3+0(.15%) HW:20221/7.4%
 BSB 3:       | 35.22/35.03/34.27Gh/s | A:1014 R: 3+0(.29%) HW: 3296/2.5%
--------------------------------------------------------------------------------

However, the device 5s hashrates are still normal, even though they aren't really hashing.

I have two questions about this. Why not include the summary 5s hashrate in the API response? And what's up with the 5s device hashrates not dipping at all during an outage?

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: jesse11 on November 04, 2013, 02:39:52 PM

Luke, Are you checking your PM's?

I already replied to yours earlier... O.o

jesse11

sr. member

Activity: 333

Merit: 250

Ants Rock

Luke, Are you checking your PM's?

drewage

member

Activity: 262

Merit: 10

Quote from: Mudbankkeith on November 03, 2013, 01:28:25 PM

Quote from: drewage on November 03, 2013, 01:09:48 PM

Hey, sorry if this has already been covered but I just got a jalapeno and I'm running it under BFGMiner 3.3.0 along with 14 BEs. It's on a MacMini running Ubuntu 12.04 i386. The setup will run fine for anywhere from 2-3 hours to 20+ hours but then the jalapeno will report as sick. The jalapeno is plugged directly into the MacMini and the BEs are in 2 Anker hubs that are plugged into another hub and from there into the mini. Once I shutdown BFGMiner and restart everything works again. The temps look fine, 38-41, and I'm just wondering if anyone has a suggestion.

move the jalapeno into your master hub.

Awesome! Thanks for the quick reply.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: drewage on November 03, 2013, 01:09:48 PM

Hey, sorry if this has already been covered but I just got a jalapeno and I'm running it under BFGMiner 3.3.0 along with 14 BEs. It's on a MacMini running Ubuntu 12.04 i386. The setup will run fine for anywhere from 2-3 hours to 20+ hours but then the jalapeno will report as sick. The jalapeno is plugged directly into the MacMini and the BEs are in 2 Anker hubs that are plugged into another hub and from there into the mini. Once I shutdown BFGMiner and restart everything works again. The temps look fine, 38-41, and I'm just wondering if anyone has a suggestion.

move the jalapeno into your master hub.

drewage

member

Activity: 262

Merit: 10

Hey, sorry if this has already been covered but I just got a jalapeno and I'm running it under BFGMiner 3.3.0 along with 14 BEs. It's on a MacMini running Ubuntu 12.04 i386. The setup will run fine for anywhere from 2-3 hours to 20+ hours but then the jalapeno will report as sick. The jalapeno is plugged directly into the MacMini and the BEs are in 2 Anker hubs that are plugged into another hub and from there into the mini. Once I shutdown BFGMiner and restart everything works again. The temps look fine, 38-41, and I'm just wondering if anyone has a suggestion.

BitMinerN8

hero member

Activity: 626

Merit: 500

Mining since May 2011.

Quote from: i3lome on November 03, 2013, 01:11:33 AM

How hard is it to use bfg in unbunto. Im a windows guy ready for a change.

If you are looking into reducing your overhead even more, you might want to checkout http://minepeon.com
It's a mining distro that runs off a Raspberry Pi.

ktbken

full member

Activity: 158

Merit: 100

Quote from: i3lome on November 03, 2013, 01:11:33 AM

How hard is it to use bfg in unbunto. Im a windows guy ready for a change.

Hi my setup doc for xubuntu should help you http://tinyurl.com/cboxzdy

i3lome

full member

Activity: 210

Merit: 100

How hard is it to use bfg in unbunto. Im a windows guy ready for a change.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: igormkd on November 02, 2013, 03:58:48 PM

Why is not possible to Install it on CENTOS and REDHAT Huh

Pretty sure a number of people use it on RedHat/CentOS.
It's my understanding they'll soon have a package in the official repositories.

igormkd

newbie

Activity: 27

Merit: 0

Why is not possible to Install it on CENTOS and REDHAT Huh

vulgartrendkill

hero member

Activity: 518

Merit: 500

Quote from: Mudbankkeith on October 29, 2013, 04:13:20 PM

Quote from: vulgartrendkill on October 29, 2013, 03:39:54 PM

I`ve tried switching from .3 to .4, carried over the bat file, and started 3.4, added a pool pressed enter and...it froze. did nothing for 10 mins.

Any ideas?

My bat file works perfectly on 3.3, and thats the only thing i`ve added.

Does the old 3.3.0 bat file still work on version 3.3.0?

If so start version 3.4.0 with the old bat file.

Then if you want to change or add another pool, just work on a spare copy of the file.

it does work indeed. i`ve swtched back to .3 for the moment. I also get a Error failed to wake notifier spam the window. Like i said 3.3 works like a dream

bitlock

newbie

Activity: 20

Merit: 0

Watch the miner logs - bfgminer display up to ica14 by default - not sure how to reset it.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: HellDiverUK on November 01, 2013, 04:16:03 PM

Quote from: madcratebuilder on November 01, 2013, 02:26:38 PM

Quote

I recently began building up my mini-wannabe army of Erupters: only 18 so far. All into USB 3.0 ports.

9 Erupters per 10 port, powered, USB3.0 Dyconn hub[10th is fan]. The specs i read say this hub can power whats in it.

However, BFGminer wont run more than 15 of these ASIC Erupters. At least, it only shows 0-14 and associated info(hasrates etc)

Sometimes it will only run half my Erupters, 9, but random ones from each hub, not just 9 from one and none from the other.

This acts like you do not have a full 0.5 amps to each usb port. I know Dyconn claims .900mA per port, that means it must have a 9 amp power supply. I bet if you measured the amp out put it well be less than 9 amps. A good Fluke meter can measure up to 10 amps dc with out a external shunt.

Doesn't need to be 9A if the PSU is outputting 12v. Only needs to be a 4-5A 12v to provide 9A of 5v.

It does sound like a power problem.
Take a read through this thread:- https://bitcointalksearch.org/topic/m.2700634
Lots of hub information.

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: madcratebuilder on November 01, 2013, 02:26:38 PM

Quote

I recently began building up my mini-wannabe army of Erupters: only 18 so far. All into USB 3.0 ports.

9 Erupters per 10 port, powered, USB3.0 Dyconn hub[10th is fan]. The specs i read say this hub can power whats in it.

However, BFGminer wont run more than 15 of these ASIC Erupters. At least, it only shows 0-14 and associated info(hasrates etc)

Sometimes it will only run half my Erupters, 9, but random ones from each hub, not just 9 from one and none from the other.

This acts like you do not have a full 0.5 amps to each usb port. I know Dyconn claims .900mA per port, that means it must have a 9 amp power supply. I bet if you measured the amp out put it well be less than 9 amps. A good Fluke meter can measure up to 10 amps dc with out a external shunt.

Doesn't need to be 9A if the PSU is outputting 12v. Only needs to be a 4-5A 12v to provide 9A of 5v.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: Luke-Jr on October 31, 2013, 11:23:39 AM

Quote from: Nemo1024 on October 31, 2013, 06:15:32 AM

Luke, can you comment on the following, regarding BlueFuries:

Quote from: Beastlymac on October 31, 2013, 06:04:42 AM

Quote from: Nemo1024 on October 31, 2013, 05:54:51 AM

Quote from: Beastlymac on October 31, 2013, 05:43:10 AM

They draw 0.5A from what the EE has told me.
The command would be along the lines of.

Code:

bfgminer -S bigpic:all -o pool -u user -p pass

Also if you are using bfgminer from Luke's build you won't be able to probe for both block eruptor and blue fury as both probes will break each other. If that makes sense?

Hmm. I plan to run two separate instances of bfgminer, where one instance would only control/probe for Erupters (-S erupter:all), and the other - only BFs (-S bigpic:all). Hope this works. If not, I'd need to plan for all BlueFuries running from a separate machine. Huh

I don't think cgminer has the same issue. One option would be use a old version of bfgminer sub 3.3.0 so it is only compatiable with the block eruptors and then use our version of bfgminer. Theoretically that should work. Luke might know a better idea or he might have some kind of fix in the works I am not sure.

Just don't use -S :all
This tells BFGMiner to probe every port for the device.
Erupters can't handle BigPic probes, and BigPic can't handle Icarus probes.

Hi Luke-Jr
So does this mean I need to specify all the com ports, if I am mixing Erupters and BlueFurys?

I use -S all for my erupters, when I added a Fury I used the :\\.\COMn. but the Fury was not found.
If I run the Fury on its own then it works ok.

madcratebuilder

member

Activity: 70

Merit: 10

Quote

I recently began building up my mini-wannabe army of Erupters: only 18 so far. All into USB 3.0 ports.

9 Erupters per 10 port, powered, USB3.0 Dyconn hub[10th is fan]. The specs i read say this hub can power whats in it.

However, BFGminer wont run more than 15 of these ASIC Erupters. At least, it only shows 0-14 and associated info(hasrates etc)

Sometimes it will only run half my Erupters, 9, but random ones from each hub, not just 9 from one and none from the other.

This acts like you do not have a full 0.5 amps to each usb port. I know Dyconn claims .900mA per port, that means it must have a 9 amp power supply. I bet if you measured the amp out put it well be less than 9 amps. A good Fluke meter can measure up to 10 amps dc with out a external shunt.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: Nemo1024 on October 31, 2013, 06:15:32 AM

Luke, can you comment on the following, regarding BlueFuries:

Quote from: Beastlymac on October 31, 2013, 06:04:42 AM

Quote from: Nemo1024 on October 31, 2013, 05:54:51 AM

Quote from: Beastlymac on October 31, 2013, 05:43:10 AM

They draw 0.5A from what the EE has told me.
The command would be along the lines of.

Code:

bfgminer -S bigpic:all -o pool -u user -p pass

Also if you are using bfgminer from Luke's build you won't be able to probe for both block eruptor and blue fury as both probes will break each other. If that makes sense?

Hmm. I plan to run two separate instances of bfgminer, where one instance would only control/probe for Erupters (-S erupter:all), and the other - only BFs (-S bigpic:all). Hope this works. If not, I'd need to plan for all BlueFuries running from a separate machine. Huh

I don't think cgminer has the same issue. One option would be use a old version of bfgminer sub 3.3.0 so it is only compatiable with the block eruptors and then use our version of bfgminer. Theoretically that should work. Luke might know a better idea or he might have some kind of fix in the works I am not sure.

Just don't use -S :all
This tells BFGMiner to probe every port for the device.
Erupters can't handle BigPic probes, and BigPic can't handle Icarus probes.

Nemo1024

legendary

Activity: 1680

Merit: 1014

Quote from: ?? on ??

edit: also, when BFGminer starts, it often says i cannon access certain COM ports. Seems to be different ones each time.

I experienced this problem when UPS controller software would hi-jack random COM ports. I had to uninstall UPS monitor, but I am petitioning for Luke to include a delayed automatic re-scan of COM ports that failed to initialise. Wink

Nemo1024

legendary

Activity: 1680

Merit: 1014

Luke, can you comment on the following, regarding BlueFuries:

Quote from: Beastlymac on October 31, 2013, 06:04:42 AM

Quote from: Nemo1024 on October 31, 2013, 05:54:51 AM

Quote from: Beastlymac on October 31, 2013, 05:43:10 AM

They draw 0.5A from what the EE has told me.
The command would be along the lines of.

Code:

bfgminer -S bigpic:all -o pool -u user -p pass

Also if you are using bfgminer from Luke's build you won't be able to probe for both block eruptor and blue fury as both probes will break each other. If that makes sense?

Hmm. I plan to run two separate instances of bfgminer, where one instance would only control/probe for Erupters (-S erupter:all), and the other - only BFs (-S bigpic:all). Hope this works. If not, I'd need to plan for all BlueFuries running from a separate machine. Huh

I don't think cgminer has the same issue. One option would be use a old version of bfgminer sub 3.3.0 so it is only compatiable with the block eruptors and then use our version of bfgminer. Theoretically that should work. Luke might know a better idea or he might have some kind of fix in the works I am not sure.

Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 101. (Read 1193219 times)