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

drewage

member

Activity: 262

Merit: 10

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

eRRoRist

newbie

Activity: 19

Merit: 0

Quote from: PLaci1982 on November 21, 2013, 01:50:21 AM

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

I don't now the correct command or bfgminer does not allow connection to stratum via proxy?

Maybe your PROXY doesn't support stratum?

I can do it with cgminer though and it's mining without any issues.

On the same machine and network, I can use CGMiner -> stratum.btcguild.com:3333 going through my proxy.

cgminer -o "http:proxy.com:8080|stratum.btcguild.com:3333" -u xxx -p 111

PLaci1982

full member

Activity: 168

Merit: 100

Live long and prosper. \\//,

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

I don't now the correct command or bfgminer does not allow connection to stratum via proxy?

Maybe your PROXY doesn't support stratum?

eRRoRist

newbie

Activity: 19

Merit: 0

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?

PLaci1982

full member

Activity: 168

Merit: 100

Live long and prosper. \\//,

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

eRRoRist

newbie

Activity: 19

Merit: 0

Hello guys!!

I seem to be having problems connecting to a stratum server via a proxy server.

I'm mining behind a firewall and all my internet connections have to go through a proxy. I can use cgminer and stratum.btcguild.com:3333 via proxy without any problem. However I would like to use bfgminer instead as I have been hearing many good things about it.

I have tried all sorts of commands, however none of them seem to connect

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

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

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

This however would get me connected.

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

I'm mining at BTCguild, and you can only connect to them via stratum??

Any help will be greatly appreciated!! Thanks a lot!!

AbiTxGroup

sr. member

Activity: 447

Merit: 250

Quote from: Luke-Jr on November 12, 2013, 02:15:22 PM

Quote from: HellDiverUK on November 12, 2013, 01:38:42 PM

Edit: 3.5.2 is showing as the latest on OpenWRT...

I forgot to update the OpenWrt README... For 3.6, you'll need to change "testing" to "latest"

We now have 3 stages: stable, testing, and latest.

Stable (currently 3.0.x) is "no outstanding regressions from previous release, and probably any bugs found will also affect previous versions too".
Testing (currently 3.5.x) is "only applying bugfixes to make this the next stable"
Latest (currently 3.6.x) is "new code in the works; lolmaybeithascrashing"

That said, 3.5.2 should have had the bigpic fixes too... :/

Quote from: HellDiverUK on November 12, 2013, 02:06:28 PM

Set source manually to src/gz bfgminer http://luke.dashjr.org/programs/bitcoin/files/bfgminer/3.6.0/openwrt/12.09/ar71xx - it's still showing 3.5.2 as latest...

Did you opkg update?

Here is the post about the release versions.

arklan

legendary

Activity: 1778

Merit: 1008

Quote from: AbiTxGroup on November 20, 2013, 01:08:55 AM

Quote from: arklan on November 20, 2013, 12:56:37 AM

oh, right. it's just bfgminer.exe -G -S all

Hmmm. On win7x64 with intel chipset (laptop) and a workstation with AMD GPU's, that worked fine, well, I had to put a server/username/passwd also. I dont have a machine with nvidia gpu to test on.

Are you using the 64bit or 32bit bfgminer. Neither of my machines will work with the 64bit, but the 32bit starts up fine.

I like the 3.5.2 version best.

I went back to 3.5.2 as somewhere in these posts, ~~wizkid~~ Luke jr mentioned that the 3.5.2 was the stable and 3.6.0 was the latest testing, or something to that effect.

EDIT NOTE: mixed up reference to user

might be 64 bit... i'll try dropping back to suggested version.

AbiTxGroup

sr. member

Activity: 447

Merit: 250

Quote from: arklan on November 20, 2013, 12:56:37 AM

oh, right. it's just bfgminer.exe -G -S all

Hmmm. On win7x64 with intel chipset (laptop) and a workstation with AMD GPU's, that worked fine, well, I had to put a server/username/passwd also. I dont have a machine with nvidia gpu to test on.

Are you using the 64bit or 32bit bfgminer. Neither of my machines will work with the 64bit, but the 32bit starts up fine.

I like the 3.5.2 version best.

I went back to 3.5.2 as somewhere in these posts, ~~wizkid~~ Luke jr mentioned that the 3.5.2 was the stable and 3.6.0 was the latest testing, or something to that effect.

EDIT NOTE: mixed up reference to user

arklan

legendary

Activity: 1778

Merit: 1008

Quote from: AbiTxGroup on November 20, 2013, 12:55:59 AM

Quote from: arklan on November 20, 2013, 12:44:17 AM

having some problems with bfgminer 3.6.0, windows 7 x64.

after a fresh windows install it was fine, but after i installed my nvidia video driver and rebooted, bfgminer no longer launches, either outright freezing (and not allowing the window to be closed, even with ctrl alt del) or throwing the following error:

Failed to connect in util.c notifier_init():2686: The operation completed successfully.

after which it exits.

thoughts?

Its hard to tell without knowing what your startup command looks like. Can you list it for us to see?

Is it trying to start GPU mining? Add the "-G" to stop it.

oh, right. it's just bfgminer.exe -G -S all

AbiTxGroup

sr. member

Activity: 447

Merit: 250

Quote from: arklan on November 20, 2013, 12:44:17 AM

having some problems with bfgminer 3.6.0, windows 7 x64.

after a fresh windows install it was fine, but after i installed my nvidia video driver and rebooted, bfgminer no longer launches, either outright freezing (and not allowing the window to be closed, even with ctrl alt del) or throwing the following error:

Failed to connect in util.c notifier_init():2686: The operation completed successfully.

after which it exits.

thoughts?

Its hard to tell without knowing what your startup command looks like. Can you list it for us to see?

Is it trying to start GPU mining? Add the "-G" to stop it.

Alyce

newbie

Activity: 18

Merit: 0

Hello!
I can't compile bfgminer 3.6.0 on Raspbian linux. Version 3.4.0 compiled successful.
The error is:

Code:

CC bfgminer-miner.o
miner.c: In function '_probe_device_match':
miner.c:10358:11: error: dereferencing pointer to incomplete type
miner.c:10358:44: error: dereferencing pointer to incomplete type
miner.c:10359:11: error: dereferencing pointer to incomplete type
miner.c:10359:44: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c:10365:26: error: dereferencing pointer to incomplete type
miner.c: In function 'probe_device_thread':
miner.c:10405:34: error: dereferencing pointer to incomplete type
miner.c:10406:39: error: dereferencing pointer to incomplete type
miner.c:10411:36: error: dereferencing pointer to incomplete type
miner.c:10412:3: error: dereferencing pointer to incomplete type
miner.c:10425:3: error: dereferencing pointer to incomplete type
miner.c:10461:4: error: dereferencing pointer to incomplete type
miner.c:10478:4: error: dereferencing pointer to incomplete type
miner.c:10480:14: error: dereferencing pointer to incomplete type
miner.c:10480:25: error: 'lowl_vcom' undeclared (first use in this function)
miner.c:10480:25: note: each undeclared identifier is reported only once for each function it appears in
miner.c:10498:3: error: dereferencing pointer to incomplete type
miner.c: In function 'probe_device':
miner.c:10510:22: error: dereferencing pointer to incomplete type
make[2]: *** [bfgminer-miner.o] Error 1
make[2]: Leaving directory `/home/pi/bfgminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/pi/bfgminer'
make: *** [all] Error 2

I just make this step:
1. git clone https://github.com/luke-jr/bfgminer bfgminer
2. ./autogen.sh
3. ./configure --disable-opencl --disable-adl --disable-bigpic --disable-bitforce --disable-icarus --disable-avalon --disable-modminer --disable-x6500 --disable-ztex --disable-bfsb --disable-littlefury --enable-bitfury --enable-metabank
4. make

What wrong? How can i resolve problem?
Thanks.

arklan

legendary

Activity: 1778

Merit: 1008

having some problems with bfgminer 3.6.0, windows 7 x64.

after a fresh windows install it was fine, but after i installed my nvidia video driver and rebooted, bfgminer no longer launches, either outright freezing (and not allowing the window to be closed, even with ctrl alt del) or throwing the following error:

Failed to connect in util.c notifier_init():2686: The operation completed successfully.

after which it exits.

thoughts?

PLaci1982

full member

Activity: 168

Merit: 100

Live long and prosper. \\//,

I got my 1st ASIC, an USB Block Erupter.

At first time I did set it up on Windows w/ latest (3.6.0) BFG, works fine.

At second time I gave a try to my Ubuntu 12.04 LTS Precise Pangolin x64 (BFG from PPA).
I start BFG, and.... WTF?!? Something wrong!
Check, check, check.... BFG version, and see: 3.2.1-0precise1??
Checking updates: no update.
Checking PPA settings: correct.
Checking PPA content: OMFGWTF88MPH? Huh

? Latest build for any Ubuntu: 3.3.0... Still 3.2.1 < 3.3.0, so what? WHAT? Failed to build. Are unit3 still alive??

I was able to set it up on 3.2.1, but commands do differ from 3.6.0, it wasn't at that easy at 1st try like on windows.... And the hasrate are miserable... Shocked

PS: Sorry for my English! Grin

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: FaSan on November 19, 2013, 02:09:20 PM

Mr Wangchun have add with success the "momentum" protocol (ProtoShares) to the Minerd (cpu mining) software.

https://github.com/wangchun/cpuminer

Can is possibile to add it to BFGMiner ? Maybe with the GPU support too ? Roll Eyes

I don't have time for this at the moment.
Maybe if someone submits a pull request with code...

FaSan

hero member

Activity: 658

Merit: 502

Hi,
Mr Wangchun have add with success the "momentum" protocol (ProtoShares) to the Minerd (cpu mining) software.

https://github.com/wangchun/cpuminer

Can is possibile to add it to BFGMiner ? Maybe with the GPU support too ? Roll Eyes

Best Regards

qqqq

legendary

Activity: 1596

Merit: 1011

Quote from: xyzzy099 on November 19, 2013, 10:05:48 AM

Quote from: qqqq on November 19, 2013, 09:59:56 AM

Hello, what is actual queue for Little Single (30Gh\s) in solo? I'm tired of fighting with "Automatic queue" in 3.5.0 and 3.6.0 has the same problem. Now i set manually queue=60 and it still says that staged work underrun...

Do you have coinbase-addr and coinbase-sig set, as in the SOLO MINING section of the README? If not, I imagine you are connecting to bitcoin-qt/bitcoind with getwork which is just not fast enough for ASIC mining hardware.

If you set coinbase-addr and coinbase sig, BFGMiner will use GBT, which should solve your problem.

No, i'm not. i thought just adding http:// for ip or localhost allow use GBT. Ok i will try that way.

Seems to be solved, thanks.

xyzzy099

legendary

Activity: 1065

Merit: 1077

Quote from: qqqq on November 19, 2013, 09:59:56 AM

Hello, what is actual queue for Little Single (30Gh\s) in solo? I'm tired of fighting with "Automatic queue" in 3.5.0 and 3.6.0 has the same problem. Now i set manually queue=60 and it still says that staged work underrun...

Do you have coinbase-addr and coinbase-sig set, as in the SOLO MINING section of the README? If not, I imagine you are connecting to bitcoin-qt/bitcoind with getwork which is just not fast enough for ASIC mining hardware.

If you set coinbase-addr and coinbase sig, BFGMiner will use GBT, which should solve your problem.

qqqq

legendary

Activity: 1596

Merit: 1011

Hello, what is actual queue for Little Single (30Gh\s) in solo? I'm tired of fighting with "Automatic queue" in 3.5.0 and 3.6.0 has the same problem. Now i set manually queue=60 and it still says that staged work underrun...

vs3

hero member

Activity: 622

Merit: 500

Quote from: giorgiomassa on November 18, 2013, 11:31:51 AM

Dear all,

I'm trying to make an old, V1.0 board based on Intron's design which is very similar to BFSB's 450 GH/s miner. It has 16 Bitfury on a card and 16 card slots, the only difference is that instead of having an I2C selector for which card the SPI bus should talk to, it has a long chain of 16*16=256 Bitfury chips and it's attached to a RPI SPI port.

I modded the driver-bfsb.c file in order to scan only for one slot (the first and only, which is supposed to have 256 chips) but only 99 chips are detected! I tried to swap slots, use spare cards but nothing, the autodetection always stops at 99 chips. It is driving me crazy because there doesn't seem to be any "maximum chips" constant neither in the libbitfury.c nor in driver-bfsb.c, so I can't find where this limit comes from!

Can anybody help me or suggest me where to look at or had a similar problem?

Thanks in advance!

Giorgio - a few things from my recollection while reading the various forums - I think at some point Metabank and BFSB had issues with chains longer than 64 chips, which is why they ended up splitting them into smaller chains.

As for the limitation - I'm not sure which version and which branch are you using, but in the beginning Legkodymov (who did the first cgminer clone and most people have been starting from his version) had a limitation of 100 chips. Later that limitation became 200 chips. Look into miner.h:

Code:

struct cgpu_info {
	int cgminer_id;
	struct device_drv *drv;
...
#ifdef USE_BITFURY
	int chip_n;
	struct bitfury_device devices[200]; // TODO Move somewhere to appropriate place
#endif
...

Feel free to PM me if you have any questions as I don't want to pollute this thread with an unrelated discussion (we can continue in the one from bitfury - the FREE MONEY one and majority of the people who initially made their own boards still follow it and might be able to add more details).

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