Author

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

hero member
Activity: 1246
Merit: 501
windows 8 is probably the problem


No, it isn't.  Windows 8.1 isn't a problem either, as that's what I'm using.  Roll Eyes
legendary
Activity: 2576
Merit: 1186
Doing my test run on the main git branch now.
Should be ready for 3.3 within a day or two, assuming no surprises.
Does this support bitfury chips under the main bfg once you are done?
Yes, here are the WIP release notes:
  • New drivers for bitfury-based devices: BFSB/MegaBigPower kits, Big Picture Mining USB, LittleFury, and Metabank.
  • Support for proxy virtual devices has been extended to include the stratum protocol when the upstream pool selected is also stratum and supplies sufficient extranonce2 space. If the upstream pool does not meet this criteria, stratum clients will be disconnected and new ones will fail to subscribe. You can take advantage of this to failover to the getwork proxy. Support for upstream getwork pools is impossble, but GBT is planned.
  • opencl: Driver is disabled by default if FPGAs or ASICs are detected. To enable, use -S opencl:auto
  • Third hashrate displayed is now based on nonces found, adjusted for pool rejected/stale shares. It should still be approximately equivalent to your effective/earning hashrate, but with better accuracy.
  • Utility on the TUI status line has been replaced with expected Income, measured as 100% PPS BTC per hour for easy comparison with electric costs.
  • RPC: Methods shared with cgminer now only consider entire devices, to be more compatible. A set of new processor-detail methods have been added to get full information per-processor.
  • RPC: Old devdetail method has been made compatible with cgminer devdetails and renamed.
  • New options --chroot-dir and --setuid on POSIX systems (thanks Ricardo!).
hero member
Activity: 518
Merit: 500
Doing my test run on the main git branch now.
Should be ready for 3.3 within a day or two, assuming no surprises.

Does this support bitfury chips under the main bfg once you are done?


Thanks
legendary
Activity: 2576
Merit: 1186
Doing my test run on the main git branch now.
Should be ready for 3.3 within a day or two, assuming no surprises.
sr. member
Activity: 447
Merit: 250
windows 8 is probably the problem

Not sure what you are replying to, but my post was in reply to settings that are currently working. 

I posted that I was using win8 to run bfgminer.

I have 2x 7950's and 2x 7850's running with cgminer and the bfgminer running the remote blades.  All are running great under win8, just trying to help others out.

Originally, I used the same bfgminer startup on my win7 laptop when I setup my first blade.  Once I had ran that for a couple of days, I then ran bfgminer on my win8 miner so that I could shutdown my laptop.

If anyone uses the startup that I posted, make sure you open port 8332 with your firewall software to allow the blades to connect.
hero member
Activity: 910
Merit: 550
windows 8 is probably the problem
sr. member
Activity: 447
Merit: 250
win7 64bit,     cant get bfgminer to load properly and recognize my blades,


anyone have the the text of their batch file that would get me going in the right direction?
I am using bfgminer-3.2.1-win32 on Win8 64bit

bfgminer -G --http-port 8332 -o stratum+tcp://stratum.mining.eligius.st:3334 -O btc_address

Blades are configured to connect to IP of the win8 machine.  I am running my blades by themselves with paperclipped psu.

Just in case, use the blade config util to setup to connect to bfgminer machine. Util is at http://192.168.1.254:8000 by default.
hero member
Activity: 1246
Merit: 501
win7 64bit,     cant get bfgminer to load properly and recognize my blades,



Be aware only the 32-bit version of bfgminer supports the Blades.  You can of course run 32-bit bfgminer on 64-bit Windows.

hero member
Activity: 518
Merit: 500
win7 64bit,     cant get bfgminer to load properly and recognize my blades,


anyone have the the text of their batch file that would get me going in the right direction?


Code:
bfgminer --http-port 8332 -o us2.eclipsemc.com:3333 -u your username -p your password -L logfinal.txt -G 

Is what I use.
hero member
Activity: 504
Merit: 500
win7 64bit,     cant get bfgminer to load properly and recognize my blades,


anyone have the the text of their batch file that would get me going in the right direction?
full member
Activity: 246
Merit: 100
im trying to go back to bfgminer from easyminer to see if there is a better performance and less hardware errors. When I open up bfgminer it says something about faild to soething opencl library. then the getcomport comes up 2 times.

then I putin url, user and pass. after hitting enter the mining software pauses for a second like its trying to write the cfg file and then I get a error that says this program has stopped responding.

I am on a 64 bit version of windows but have tried both versions, is there any idea what might cause this error?

I have tried running as admin but that did not seem to help.
hero member
Activity: 1246
Merit: 501
As promised.  BFG crapped out three times before it worked with both Blades at the same time.

As said, it's Win7 Exnterprise x86 on a Celeron 847 NUC.  No other software on the machine, other the BFGMiner 3.2.1.


During bitcointroll's outage, I have identified the cause of this crash (a bug in PDCurses), submitted a patch upstream to fix it that will hopefully be merged at some point, and implemented a workaround that will be included in the next release of BFGMiner.

Awesome.  Smiley

Another issue has cropped up.  You'll like this one (not a lot).

On a machine with an AMD APU (E2-2000/A50M), once the AMD drivers are installed, BFGMiner's 'status' display isn't displaying anything (the bit where it says Share Accepted, etc).  It's just blank.  The TUI menus work OK, and it's hashing away like a good one, but nothing comes up to say shares accepted/rejected, new block found, etc.  This is under Windows 8.1 x64 Enterprise.  Exact same install transferred from an Intel machine which worked OK.  If I remove the AMD drivers and go back to the Microsoft Basic Display driver, the text works OK.  

legendary
Activity: 2576
Merit: 1186
As promised.  BFG crapped out three times before it worked with both Blades at the same time.

As said, it's Win7 Exnterprise x86 on a Celeron 847 NUC.  No other software on the machine, other the BFGMiner 3.2.1.

Crash was at log time 15:09:49

Code:
Failed to init bfd from (C:\bfgminer321\pdcurses.dll)
0x66e43b50 : C:\bfgminer321\pdcurses.dll : wclrtoeol
Failed to init bfd from (C:\Windows\system32\msvcrt.dll)
0x762aa442 : C:\Windows\system32\msvcrt.dll : unlock
Failed to init bfd from (C:\Windows\system32\msvcrt.dll)
0x762ba490 : C:\Windows\system32\msvcrt.dll : getenv
Failed to init bfd from (C:\Windows\system32\msvcrt.dll)
0x762ba462 : C:\Windows\system32\msvcrt.dll : getenv
Failed to init bfd from (C:\bfgminer321\pdcurses.dll)
0x66e41408 : C:\bfgminer321\pdcurses.dll : waddch
During bitcointroll's outage, I have identified the cause of this crash (a bug in PDCurses), submitted a patch upstream to fix it that will hopefully be merged at some point, and implemented a workaround that will be included in the next release of BFGMiner.
hero member
Activity: 1246
Merit: 501
Works OK for me with both 8 and 8.1 - I'm running 8.1 Enterprise on my main miner, and just needed the VCP drivers and everything worked first time.
hero member
Activity: 868
Merit: 1000
I'm using this Zotac machine for some of my miners, FWIW.

Same here. Zotac with win7x86 drawing 65W

64 BE's connected with no problem. and BFGMiner 3.2.1
(It looks like it will take close to the maximum usb of 127 for those who can afford that many devices)
Also hosting Bitcoin-Qt

I have a Pi with minepeon. drawing 6W. This starts to become unstable with more than 20 BE's
(Overheating and cpu load of 160%)

Edit:- Also I have a spare Pi in the system programmed, tested, and ready to run. Just for the day when S*** happens.

2nd edit:- the primary Pi will take over the hosting for BlueFury when they arrive in 10 days
(I still need assurance that minepeon will run them)


I wonder if a can try to get a little advice. Im running Win8 64bit, I have 3x10 tecknet (48w per ten psu) hubs powering 30 ports for 30 BE`s, yet windows reports an error after 27 approx. ERROR USB controller does not have enough resources. Im guessing its a com port allocation issue, but I cant see why windows just wont make some more ports, as its a fair high spec PC (cost £1.8k) with i7, 16GB fast RAM, SSD etc etc. Ive tried to Google it but no help found yet.

I gave up trying to get win8 x64 to allocate any usb ports to com ports, and went back to win7 x86
I will be polite and say win 8 is "different"

si-labs told me to re-program my erupters with unique id numbers, at that point win 7 went back online.

win 7 worked first time

win 8 still flags com ports not found   

its the same pc with 2 hard drives.
full member
Activity: 126
Merit: 100
I'm using this Zotac machine for some of my miners, FWIW.

Same here. Zotac with win7x86 drawing 65W

64 BE's connected with no problem. and BFGMiner 3.2.1
(It looks like it will take close to the maximum usb of 127 for those who can afford that many devices)
Also hosting Bitcoin-Qt

I have a Pi with minepeon. drawing 6W. This starts to become unstable with more than 20 BE's
(Overheating and cpu load of 160%)

Edit:- Also I have a spare Pi in the system programmed, tested, and ready to run. Just for the day when S*** happens.

2nd edit:- the primary Pi will take over the hosting for BlueFury when they arrive in 10 days
(I still need assurance that minepeon will run them)


I wonder if a can try to get a little advice. Im running Win8 64bit, I have 3x10 tecknet (48w per ten psu) hubs powering 30 ports for 30 BE`s, yet windows reports an error after 27 approx. ERROR USB controller does not have enough resources. Im guessing its a com port allocation issue, but I cant see why windows just wont make some more ports, as its a fair high spec PC (cost £1.8k) with i7, 16GB fast RAM, SSD etc etc. Ive tried to Google it but no help found yet.
legendary
Activity: 2576
Merit: 1186
3.3 will be released as soon as it's ready...

In the meantime, Windows binaries of the latest bitfury code are here:
http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bitfury
hero member
Activity: 1246
Merit: 501

I must have installed winusb 5 times and it still didn`t work.  Then I was told there is a problem with usb3 hubs. so the 100 gbp anker hub i`d bought was useless because they hadn`t got round to fixing it

I have an Anker USB3 hub, and it works perfectly with BFGMiner - it works with BFG on USB3 on three different PCs (AsMedia USB3, Intel USB3, NEC USB3), and USB2 on all the computers I've tried.  It also works on a TPLink 703N micro-router running OpenWRT with the Anker hub, which also powers the router.
hero member
Activity: 518
Merit: 500
I'd rather not use my 3 Bluefurys than use cgminer again, it sucks pretty hard when compared to bfgminer - no built-in proxy, poor BlockErupter support, the retarded need for fucking about with WinUSB drivers, terrible interface...  BFG also has and a developer who has a personality and is happy to help with issues rather than saying "README  Roll Eyes" in response to any questions.

But, hey, horses for courses.

+1

Cgminer`s main downfall is that its main developers don`t seem to understand that not everyone can code\compile linux\compile anything.

I must have installed winusb 5 times and it still didn`t work.  Then I was told there is a problem with usb3 hubs. so the 100 gbp anker hub i`d bought was useless because they hadn`t got round to fixing it
hero member
Activity: 1246
Merit: 501
I'd rather not use my 3 Bluefurys than use cgminer again, it sucks pretty hard when compared to bfgminer - no built-in proxy, poor BlockErupter support, the retarded need for fucking about with WinUSB drivers, terrible interface...  BFG also has and a developer who has a personality and is happy to help with issues rather than saying "README  Roll Eyes" in response to any questions.

But, hey, horses for courses.
Jump to: