Author

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

legendary
Activity: 1066
Merit: 1098
When I compile bfgminer on ubuntu and run configure the getwork proxy shows disabled.  All the dependencies are installed.  Any idea why its not working. 
compiled it and libmicrohttpd-dev is newest version, but how can I see if getwork proxy is active?
TIA

Start BFGMiner with --http-proxy 8330 (or whatever port you want), then point your blades at the IP of the machine running BFGM, using the port you specified on the command line.
sr. member
Activity: 342
Merit: 250
When I compile bfgminer on ubuntu and run configure the getwork proxy shows disabled.  All the dependencies are installed.  Any idea why its not working.  

You probably just need to install libmicrohttpd-dev.  If it's installed, the support should be enabled by default.

EDIT: If you DO have it installed, you should look through the configure log and see why it's failing to enable it.


It shows enabled.  Now when I go to start bfgminer I get error

./bfgminer: error while loading shared libraries: libmicrohttpd.so.10: cannot open shared object file: No such file or directory
legendary
Activity: 2955
Merit: 1049
When I compile bfgminer on ubuntu and run configure the getwork proxy shows disabled.  All the dependencies are installed.  Any idea why its not working. 
compiled it and libmicrohttpd-dev is newest version, but how can I see if getwork proxy is active?
TIA
legendary
Activity: 2955
Merit: 1049
Just install from Git.  Even a total linux noob like me can install it and have it going in less than 2 minutes, even from command line.
thx I have installed it from git...
legendary
Activity: 1066
Merit: 1098
When I compile bfgminer on ubuntu and run configure the getwork proxy shows disabled.  All the dependencies are installed.  Any idea why its not working.  

You probably just need to install libmicrohttpd-dev.  If it's installed, the support should be enabled by default.

EDIT: If you DO have it installed, you should look through the configure log and see why it's failing to enable it.
sr. member
Activity: 342
Merit: 250
When I compile bfgminer on ubuntu and run configure the getwork proxy shows disabled.  All the dependencies are installed.  Any idea why its not working. 
hero member
Activity: 1246
Merit: 501

Just install from Git.  Even a total linux noob like me can install it and have it going in less than 2 minutes, even from command line.
legendary
Activity: 2955
Merit: 1049
hero member
Activity: 868
Merit: 1000
32-bit apps just run on WoW64 (Windows on Windows).  They're not really running on Windows natively.

I don't know what the argument is anyway- Luke-Jr said it's 32-bit only due to the http server library that makes the Blade stuff work.  This is known, and has been for weeks.  The fact it works on Windows at all is fantastic work by Luke-Jr.


Thanks Luke for making this work, as I said earlier, when my blade arrives I will send a contribution. (running BFGminer 3.2.1 on a win 7 x86 zotac mini pc with a variety of devices)

P.S. I will still keep my Pi running cgminer (minepeon) (very low power) ideal for marginal/older devices.

Edit. BFG for serious use, cg for enhancing the toy..........
hero member
Activity: 518
Merit: 500
32-bit apps just run on WoW64 (Windows on Windows).  They're not really running on Windows natively.

I don't know what the argument is anyway- Luke-Jr said it's 32-bit only due to the http server library that makes the Blade stuff work.  This is known, and has been for weeks.  The fact it works on Windows at all is fantastic work by Luke-Jr.


+1 I think he has done extremely well to get it running.  For a non techie like me, to not have to deal with compiling this, downloading that and dealing with a stratum proxy AS WELL, its a real boon.  You cannot imagine the hoops I had to jump through to try and get cgminer to stop zombifying my BE.  And it still didn't work.



CGMiner is terrible - that messing about with those damned WinUSB drivers, and even then it still works like crap.  BFGMiner has come a long, long way recently. 

And all the devs can say is *rolls eyes* READ THE README.  I'm sure they will fix it, but I mean, come on, if com port contact works, blooming keep it!
hero member
Activity: 1246
Merit: 501
32-bit apps just run on WoW64 (Windows on Windows).  They're not really running on Windows natively.

I don't know what the argument is anyway- Luke-Jr said it's 32-bit only due to the http server library that makes the Blade stuff work.  This is known, and has been for weeks.  The fact it works on Windows at all is fantastic work by Luke-Jr.


+1 I think he has done extremely well to get it running.  For a non techie like me, to not have to deal with compiling this, downloading that and dealing with a stratum proxy AS WELL, its a real boon.  You cannot imagine the hoops I had to jump through to try and get cgminer to stop zombifying my BE.  And it still didn't work.



CGMiner is terrible - that messing about with those damned WinUSB drivers, and even then it still works like crap.  BFGMiner has come a long, long way recently. 
hero member
Activity: 518
Merit: 500
32-bit apps just run on WoW64 (Windows on Windows).  They're not really running on Windows natively.

I don't know what the argument is anyway- Luke-Jr said it's 32-bit only due to the http server library that makes the Blade stuff work.  This is known, and has been for weeks.  The fact it works on Windows at all is fantastic work by Luke-Jr.


+1 I think he has done extremely well to get it running.  For a non techie like me, to not have to deal with compiling this, downloading that and dealing with a stratum proxy AS WELL, its a real boon.  You cannot imagine the hoops I had to jump through to try and get cgminer to stop zombifying my BE.  And it still didn't work.

hero member
Activity: 1246
Merit: 501
32-bit apps just run on WoW64 (Windows on Windows).  They're not really running on Windows natively.

I don't know what the argument is anyway- Luke-Jr said it's 32-bit only due to the http server library that makes the Blade stuff work.  This is known, and has been for weeks.  The fact it works on Windows at all is fantastic work by Luke-Jr.
hero member
Activity: 1246
Merit: 501
Code?  Huh  I added the --http-port 8330 command to the shortcut, and pointed the blades at the IP of the machine. As it says in the README.ASIC


So thats all you have to do for bfg to recognise the cards (excluding set up of blade config page?)

Correct.  And let BFG through the firewall if you've got that turned on, too.
hero member
Activity: 868
Merit: 1000
Luke, wanted to give it a try with one blade... on 7x64 I must use 32bit since blades are not supported in x64... but something's wrong with --http-port option, here's what I get:


It only works on 32-bit.  As in, not on 64-bit.   Why are you running it on 64-bit and expecting it to work?  Huh

 Roll Eyes

Because x64 Win7 can run x86 apps Wink

You have answered the question yourself.

"Because x64 Win7 can run x86 apps"

BFGminer  is not really a Windows program, it is a DOS program.

When Win x64 arrived it needed programs to be re-written into x64 not "ported across"

If you really need a windows program, use GUIminer, it will run on x86 & x64

If the devices only look for x86, then programs on x64 will not communicate with it.
hero member
Activity: 547
Merit: 531
First bits: 12good
They may seem pointless to you, but it's the reason it's not working...

could it be a lack of motivation? one can easily find windows 7 in either 32 or 64 bit iso's. they are allover the interwebs free to download, even from microsofts own webs site. then you can you DAZ loader from anytorrent and you will have a genuine copy of windows 7 installed.


"genuine" is not the correct word for this, anyway thanks for the information in summary:

BFG 3.2.1 x86 is not working for Blades on x64 OS

I'll give it a try on ubunutu box.
hero member
Activity: 574
Merit: 501
They may seem pointless to you, but it's the reason it's not working...
newbie
Activity: 38
Merit: 0
Luke, wanted to give it a try with one blade... on 7x64 I must use 32bit since blades are not supported in x64... but something's wrong with --http-port option, here's what I get:


It only works on 32-bit.  As in, not on 64-bit.   Why are you running it on 64-bit and expecting it to work?  Huh

 Roll Eyes

Because x64 Win7 can run x86 apps Wink

Unfortunately, even though the app is 32 bit,  it's trying to connect to the 64 bit libraries because it's a 64 bit OS...

Oh yeah?! well i'd rather argue about pointless differences than ever discuss anything of serious merit.  Tongue
hero member
Activity: 574
Merit: 501
Luke, wanted to give it a try with one blade... on 7x64 I must use 32bit since blades are not supported in x64... but something's wrong with --http-port option, here's what I get:


It only works on 32-bit.  As in, not on 64-bit.   Why are you running it on 64-bit and expecting it to work?  Huh

 Roll Eyes

Because x64 Win7 can run x86 apps Wink

Unfortunately, even though the app is 32 bit,  it's trying to connect to the 64 bit libraries because it's a 64 bit OS...
hero member
Activity: 547
Merit: 531
First bits: 12good
Luke, wanted to give it a try with one blade... on 7x64 I must use 32bit since blades are not supported in x64... but something's wrong with --http-port option, here's what I get:


It only works on 32-bit.  As in, not on 64-bit.   Why are you running it on 64-bit and expecting it to work?  Huh

 Roll Eyes

Because x64 Win7 can run x86 apps Wink
Jump to: