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

shawtux

newbie

Activity: 57

Merit: 0

Quote from: HellDiverUK on November 22, 2013, 06:13:47 AM

Quote from: shawtux on November 21, 2013, 06:11:51 PM

i updated to 3.6 and not my jalapeño is not detected as BFL but as AVA0 and AVA1... is there anything that i can do to fix this problem?

Is it mining? If it is, it's not a problem.

its not mining Sad

edit:

disabled avalon support and its mining

edit2:

its mining at a fraction of the speed that was on 3.0 Sad

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: shawtux on November 21, 2013, 06:11:51 PM

i updated to 3.6 and not my jalapeño is not detected as BFL but as AVA0 and AVA1... is there anything that i can do to fix this problem?

Is it mining? If it is, it's not a problem.

Taugeran

hero member

Activity: 658

Merit: 500

CCNA: There i fixed the internet.

Quote from: Luke-Jr on November 22, 2013, 02:31:32 AM

Quote from: Taugeran on November 22, 2013, 02:17:25 AM

how would one hot plug a nanofury NF1 through device manager on a windows 7 x32 machine. or can it only be located at startup with hidapi?

Plug it in, hit D M and type in nanofury:auto

the simplicity; it hurts my caffeine stuffed, sleep deprived brain! ty luke. troubleshooting a stubborn NF1 who doesn't like running at 52+ bits. it keeps bitfury_init_oldbuf: giving up after X tries

and does this until i drop it to under 52 :<

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: Taugeran on November 22, 2013, 02:17:25 AM

how would one hot plug a nanofury NF1 through device manager on a windows 7 x32 machine. or can it only be located at startup with hidapi?

Plug it in, hit D M and type in nanofury:auto

Taugeran

hero member

Activity: 658

Merit: 500

CCNA: There i fixed the internet.

how would one hot plug a nanofury NF1 through device manager on a windows 7 x32 machine. or can it only be located at startup with hidapi?

RicRock

sr. member

Activity: 290

Merit: 250

Quote from: crazyearner on November 21, 2013, 09:45:50 PM

Whats the best settings to use on bfg miner to use with blue furys and usb erupters as cant seem to get them working together on one instance of bfg miner having to use 2 different versions.

I list them all out on command line.

For example:

-S erupter:/dev/ttyUSB0 -S BF1:/dev/ttyACM0

etc. etc.

crazyearner

legendary

Activity: 1820

Merit: 1001

Whats the best settings to use on bfg miner to use with blue furys and usb erupters as cant seem to get them working together on one instance of bfg miner having to use 2 different versions.

shawtux

newbie

Activity: 57

Merit: 0

hi! i was on bfgminer 3.0.2 (if my memory serves me right) and i started my jalapeño and icarus with no problem... as an update freak that i am, i updated to 3.6 and not my jalapeño is not detected as BFL but as AVA0 and AVA1... is there anything that i can do to fix this problem?

bog1111

newbie

Activity: 10

Merit: 0

Quote from: Luke-Jr on October 20, 2013, 12:06:18 AM

Quote from: wmcorless on October 19, 2013, 11:59:12 PM

./bfgminer: --http-port: unrecognized option

This means libmicrohttpd wasn't found when you ran configure.

I'm an arse - doing it now!

xyzzy099

legendary

Activity: 1065

Merit: 1077

Quote from: bog1111 on November 21, 2013, 02:44:00 PM

Hi,

I have a new blade, and I'm having an issue getting it to work with BFGMiner.

When I add the --http-port 8332 bit to my existing command line, BFGMiner won't start, and gives an unrecognised option message.

Running on Raspbian for a while with no issues, got some BEs and Blue fury already.

When I built 3.5.1 on the Pi, I used the commands below.

./autogen.sh
./configure
make

Do I need to add anything after the configure command...? Do I need to run a apt-get install for anything beforehand?

I'm a bit confused by the read-me file - see link below

Thanks.

As long as you have libmicrohttpd-dev installed it should enable the proxy support by default. Maybe you need to install that package.

bog1111

newbie

Activity: 10

Merit: 0

Hi,

I have a new blade, and I'm having an issue getting it to work with BFGMiner.

When I add the --http-port 8332 bit to my existing command line, BFGMiner won't start, and gives an unrecognised option message.

Running on Raspbian for a while with no issues, got some BEs and Blue fury already.

When I built 3.5.1 on the Pi, I used the commands below.

./autogen.sh
./configure
make

Do I need to add anything after the configure command...? Do I need to run a apt-get install for anything beforehand?

I'm a bit confused by the read-me file - see link below

https://i.imgur.com/z0HL8hW.jpg

Thanks.

Trance104

full member

Activity: 206

Merit: 100

BFG miner is no longer recognizing my Jally. It only picks up my SC single.

How do I make it recognize both?

*edit*

Easy miner is garbage.

jedimstr

hero member

Activity: 798

Merit: 1000

Quote from: Luke-Jr on November 21, 2013, 06:03:18 AM

Quote from: Notanon on November 21, 2013, 05:52:55 AM

How far off until BFGMiner supports the Drillbit thumbs? Just got mine today and want to start running them on my Pi with BFGMiner as soon as possible to keep power consumption down, as CGMiner is too unstable on the Pi at the moment.

I've not heard anything from Drillbit in a while...

Per James the Drillbit firmware guy, you should get contacted "soon": http://drillbitsystem.com/forum/index.php?topic=184.msg625#msg625

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: Notanon on November 21, 2013, 05:52:55 AM

How far off until BFGMiner supports the Drillbit thumbs? Just got mine today and want to start running them on my Pi with BFGMiner as soon as possible to keep power consumption down, as CGMiner is too unstable on the Pi at the moment.

I've not heard anything from Drillbit in a while...

Notanon

sr. member

Activity: 388

Merit: 250

How far off until BFGMiner supports the Drillbit thumbs? Just got mine today and want to start running them on my Pi with BFGMiner as soon as possible to keep power consumption down, as CGMiner is too unstable on the Pi at the moment.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

I've noticed a number of things in README have fallen out of date.
If you see any of these and feel like helping out, please just pastebin your modified version and PM me a link to it.
Please include in your PM a name and email address for attribution.

Thanks,

Luke

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: purelithium on April 06, 2013, 05:51:04 PM

How can I get crash logs to you from windows?

Ideally, use --debuglog --log-file someuniquefilenameyouwillremember.log
Paste the backtrace here (the very bottom of the log); if I need the full file, I will ask for it.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: drewage on November 21, 2013, 02:58:31 AM

Is Bi•Fury gonna be supported in the next version? I know it's in the pipeline, just curious.

In fact, you can try the "bifury" branch I pushed to git... It won't report hashrates, but it should mine... Wink

eRRoRist

newbie

Activity: 19

Merit: 0

Quote from: Luke-Jr on November 21, 2013, 03:31:21 AM

This is a bug in libcurl for HTTP proxies when combined with CURLOPT_CONNECT_ONLY (needed for stratum).
I've found a workaround, and will put it in the next release.

Cool!! If that's the case I will stop trying now. I was trying all sorts of combinations like adding sock4...and stuff like that. Looking forward to the next release!! Thank you and all the guys who tried to help!!

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: eRRoRist on November 20, 2013, 08:54:12 PM

Quote from: PLaci1982 on November 20, 2013, 02:33:24 PM

Quote from: eRRoRist on November 20, 2013, 11:11:29 AM

bfgminer -o stratum.bitcoin.cz:3333 -x http://proxy.com:8080 -u xxx -p 111

Maybe you should try to connect to stratum+tcp://stratum.btcguild.com:3333 instead of bitcoin.cz.........

Code:

bfgminer -o stratum+tcp://stratum.btcguild.com:3333 -x http://proxy.com:8080 -u xxx -p 111

oops. I made a mistake in my post. Yes, I was using stratum.btcguild.com:3333.

These are the commands that don't work.
bfgminer -o stratum.btcguild.com:3333 -x http://proxy.com:8080 -u xxx -p 111
bfgminer -o stratum+tcp://stratum.btcguild.com:3333 -x http://proxy.com:8080 -u xxx -p 111
bfgminer -o http://stratum.btcguild.com:3333 -x http://proxy.com:8080 -u xxx -p 111

These are the commands that work.
bfgminer -o http://api.bitcoin.cz:8332 -x http://proxy.com:8080 -u xxx -p 111
cgminer -o "http:proxy.com:8080|stratum.btcguild.com:3333" -u xxx -p 111

At least I know that I can do it behind my firewall, it's just that I don't now the correct command or bfgminer does not allow connection to stratum via proxy?

This is a bug in libcurl for HTTP proxies when combined with CURLOPT_CONNECT_ONLY (needed for stratum).
I've found a workaround, and will put it in the next release.

Quote from: drewage on November 21, 2013, 02:58:31 AM

Is Bi•Fury gonna be supported in the next version? I know it's in the pipeline, just curious.

Yes.

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