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

[2GOOD]

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.

[Mudbankkeith]

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? 

 

Because x64 Win7 can run x86 apps

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.

[HellDiverUK]

Code?    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.

[HellDiverUK]

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.

[vulgartrendkill]

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.

[HellDiverUK]

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. 

[vulgartrendkill]

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!

[Mudbankkeith]

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..........

[ewibit]

Latest release: 3.2.1

• Ubuntu: PPA maintained by "unit3"

there is only 3.1.4

[HellDiverUK]

Latest release: 3.2.1

• Ubuntu: PPA maintained by "unit3"

there is only 3.1.4

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.

[psjw4450]

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. 

[xyzzy099]

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.

[ewibit]

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...

[ewibit]

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

[psjw4450]

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

[xyzzy099]

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.

[psjw4450]

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.

I did and I get the same error.

[xyzzy099]

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

It appears that it is installed in a place where the linker can't find it,  if it is indeed installed anywhere.  It's not clear to me how it could be found by the build, but not found at run-time.

On my system, it is installed as /usr/lib/i386-linux-gnu/libmicrohttpd.so.10.

[Luke-Jr]

Got 3.2.1 running on Windows 7 Enterprise x86 last night.  As soon as the Blade connected to BFG, BFG just quit/disappeared.  Upon reopening BFG everything worked perfectly.  Connected the second Blade, and again BFG quits.  I've rebooted etc several times, and BFG is happy now. 

To me, it seems BFG quits on the very first instance on a Blade connecting to the HTTP port (perhaps something craps out creating the virtual device?). 

3.2.1 works OK on Linux, on the same machine (Intel NUC DCCP847DYE) with 4GB RAM and 30GB Kingston SSD).

Scratch that.  First time the Blade connects at each reboot, BFG quits.  It runs perfectly every time until the next reboot.

Blades aren't being restarted, just using the Switch Server function (the backup server are to a stratum_proxy running on my WHS.

I'll likely need the crash report (printed to standard error, or log file if one is configured) to do anything.

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

No, BFGMiner is a fully native Win32 and Win64 application.
I don't think it's even possible to build it for DOS.

[gmaxwell]

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

It's really not. When compiled for windows it's a windows program, just one that doesn't use the GUI.

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

Only if they're not portable. This miner software was primarily developed on x86_64 and most software from the gnu/linux and related ecosystems is highly portable.