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

[Illutian]

does it find your your BFL?

Yes, but because it's loading the Erupter driver (I assume) the BFL spits out a temperature string error and never begins hashing. I've also noticed that usually 1 or 2 Erupters remain offline (steady green light) using that switch and trying to add them inside BFGminer results in me going through all the 'ls /dev/*USB*' results and still not catching them.

Running them under the ICA driver tends to get all of them seen...with, usually, 3 being seen as 'BEE'.
--running the 'all' command to add devices while in BFGminer.

EDIT:

And it would appear that "erupter:/dev/ttyUSB##"; going the full range of 'lsusb' results, only adds 6 of the Block Erupters. The rest all result in a 'No device found'

[1714869649]

1714869649

[1714869649]

1714869649

[1714869649]

1714869649

[1714869649]

1714869649

[doctormandrake]

Where you can specific the COM ports. But for this it would be the ttyUSB ports.

I can't just use the 'erupter:all' because I also have a BFL unit and it will not start.

You can specify individual devices as well:

Code:

bfgminer -S erupter:\\.\COM3 -o -u etc

Thanks, hopefully this'll force BFGminer to see the BFL as what ever it sees it as. And the erupters as BEEs. ....really hate that 20% HW error rate.

you can specify com ports, or if you wanted you could also just run a seperate instance of antminer for the bfl and for the antminers. I find that works best in alot of instances (of course I even seperate individual ants that perform better to give them the 2.1gh clock speed etc lol) I have found bfgminer to be a champ with multiple instances, wherein cgminer simply crashed alot or created conflicts in most multiple instance scenarios.

[doctormandrake]

does it find your your BFL?

Yes, but because it's loading the Erupter driver (I assume) the BFL spits out a temperature string error and never begins hashing. I've also noticed that usually 1 or 2 Erupters remain offline (steady green light) using that switch and trying to add them inside BFGminer results in me going through all the 'ls /dev/*USB*' results and still not catching them.

Running them under the ICA driver tends to get all of them seen...with, usually, 3 being seen as 'BEE'.
--running the 'all' command to add devices while in BFGminer.

EDIT:

And it would appear that "erupter:/dev/ttyUSB##"; going the full range of 'lsusb' results, only adds 6 of the Block Erupters. The rest all result in a 'No device found'

I would try running the BE's and ants together, and a seperate instance for the bfl

[ZipTheRip]

ok so
 bfgminer -S antminer:all -S erupter:all -S all --set-device antminer:clock=x0981

works great  but now to add the nanofury yellowjacket.  I like these a lot  easy and cool 2.5 gh/s with lowest power draw of all my usb miners
anyone know what I need to do to get these to work at ~2.5gh/s?

[chiefstank]

ok so
 bfgminer -S antminer:all -S erupter:all -S all --set-device antminer:clock=x0981

works great  but now to add the nanofury yellowjacket.  I like these a lot  easy and cool 2.5 gh/s with lowest power draw of all my usb miners
anyone know what I need to do to get these to work at ~2.5gh/s?

is your nano working at all? 3.10.0 gives errors when detecting mine and no one has replied about what the problem may be.

[ZipTheRip]

ok so
 bfgminer -S antminer:all -S erupter:all -S all --set-device antminer:clock=x0981

works great  but now to add the nanofury yellowjacket.  I like these a lot  easy and cool 2.5 gh/s with lowest power draw of all my usb miners
anyone know what I need to do to get these to work at ~2.5gh/s?

is your nano working at all? 3.10.0 gives errors when detecting mine and no one has replied about what the problem may be.

yes my yellowjackets hash very well (2.5) running cgminer3.10 no commands
 but cgminer errors due to bfg drivers on the ants and block erupters
so I would like to get my yellowjackets running on bfg!

[sstark]

Hi everyone.

I have 5 red fury's, 2nd batch. But I can only get this driver to work for one of them.

win7 x64

trying to use bitminter client 1.4.3

It sees the one, and I have manually installed the driver ( many times ) for each device. uninstalled and reinstalled.

the other 4 it can't find. The scan times out with their red light on, or it errors saying 'cannot find port'

also I know they all work, they have been mining in cgminer with a different driver.

any ideas?

[dauntlessdivergent]

BFGMiner is throwing an error on my laptop. Yes I know it's not the greatest for mining but that's another story (this is mainly for testing out new pools) Anyhow I can very successfully mine with this GPU when I use BitMinter with the BitMinter client, but not when I use BFGMiner.

Here is the output.... any thoughts?

[2014-01-30 00:21:55] Started bfgminer 3.10.0
 [2014-01-30 00:21:55] Loaded configuration file multipoolgpu.conf
 [2014-01-30 00:21:56] CL Platform 0 vendor: NVIDIA Corporation
 [2014-01-30 00:21:56] CL Platform 0 name: NVIDIA CUDA
 [2014-01-30 00:21:56] CL Platform 0 version: OpenCL 1.0 CUDA 3.2.1
 [2014-01-30 00:21:56] Platform 0 devices: 1
 [2014-01-30 00:21:56]    0   NVS 4200M
 [2014-01-30 00:21:56] Unable to load ati adl library
 [2014-01-30 00:21:56] Probing for an alive pool
 [2014-01-30 00:21:56] Testing pool http://pool1.us.multipool.us:7777
 [2014-01-30 00:21:56] HTTP request failed: Empty reply from server
 [2014-01-30 00:21:56] HTTP request failed: Empty reply from server
 [2014-01-30 00:21:56] Stratum authorisation success for pool 0
 [2014-01-30 00:21:56] Pool 0 http://pool1.us.multipool.us:7777 alive
 [2014-01-30 00:21:56] Network difficulty changed to 1.11k ( 7.93Gh/s)
 [2014-01-30 00:21:56] New block: ...65ff3839 # 78543 diff 1.11k ( 7.93Gh/s)
 [2014-01-30 00:21:56] Stratum from pool 0 detected new block
 [2014-01-30 00:21:56] Pool 0 is hiding block contents from us
 [2014-01-30 00:21:57] Init GPU thread 0 GPU 0 virtual GPU 0
 [2014-01-30 00:21:57] CL Platform vendor: NVIDIA Corporation
 [2014-01-30 00:21:57] CL Platform name: NVIDIA CUDA
 [2014-01-30 00:21:57] CL Platform version: OpenCL 1.0 CUDA 3.2.1
 [2014-01-30 00:21:57] List of devices:
 [2014-01-30 00:21:57]    0   NVS 4200M
 [2014-01-30 00:21:57] Selected 0: NVS 4200M
 [2014-01-30 00:21:57] Error -11: Building Program (clBuildProgram)
 [2014-01-30 00:21:57] <program source>:678:10: error: no matching function for call to 'rotate'
                B = EndianSwap(tmp);
                       ^~~~~~~~~~~~~~~~~~
<program source>:128:24: note: instantiated from:
#define EndianSwap(n) (rotl(n & ES[0], 24U)|rotl(n & ES[1], 8U))
                       ^
<program source>:124:19: note: instantiated from:
#define rotl(x,y) rotate(x,y)
                  ^~~~~~
<built-in>:3025:26: note: candidate function
ulong16 __OVERLOADABLE__ rotate(ulong16, ulong16);
                         ^
<built-in>:3024:25: note: candidate function
ulong8 __OVERLOADABLE__ rotate(ulong8, ulong8);
                        ^
<built-in>:3023:25: note: candidate function
ulong4 __OVERLOADABLE__ rotate(ulong4, ulong4);
                        ^
<built-in>:3019:25: note: candidate function
ulong2 __OVERLOADABLE__ rotate(ulong2, ulong2);
                        ^
<built-in>:3018:25: note: candidate function
long16 __OVERLOADABLE__ rotate(long16, long16);
                        ^
<built-in>:3017:24: note: candidate function
long8 __OVERLOADABLE__ rotate(long8, long8);
                       ^
<built-in>:3016:24: note: candidate function
long4 __OVERLOADABLE__ rotate(long4, long4);
                       ^
<built-in>:3012:24: note: candidate function
long2 __OVERLOADABLE__ rotate(long2, long2);
                       ^
<built-in>:3011:25: note: candidate function
uint16 __OVERLOADABLE__ rotate(uint16, uint16);
                        ^
<built-in>:3010:24: note: candidate function
uint8 __OVERLOADABLE__ rotate(uint8, uint8);
                       ^
<built-in>:3009:24: note: candidate function
uint4 __OVERLOADABLE__ rotate(uint4, uint4);
                       ^
<built-in>:3005:24: note: candidate function
uint2 __OVERLOADABLE__ rotate(uint2, uint2);
                       ^
<built-in>:3004:24: note: candidate function
int16 __OVERLOADABLE__ rotate(int16, int16);
                       ^
<built-in>:3003:23: note: candidate function
int8 __OVERLOADABLE__ rotate(int8, int8);
                      ^
<built-in>:3002:23: note: candidate function
int4 __OVERLOADABLE__ rotate(int4, int4);
                      ^
<built-in>:2998:23: note: candidate function
int2 __OVERLOADABLE__ rotate(int2, int2);
                      ^
<built-in>:2997:27: note: candidate function
ushort16 __OVERLOADABLE__ rotate(ushort16, ushort16);
                          ^
<built-in>:2996:26: note: candidate function
ushort8 __OVERLOADABLE__ rotate(ushort8, ushort8);
                         ^
<built-in>:2995:26: note: candidate function
ushort4 __OVERLOADABLE__ rotate(ushort4, ushort4);
                         ^
<built-in>:2991:26: note: candidate function
ushort2 __OVERLOADABLE__ rotate(ushort2, ushort2);
                         ^
<built-in>:2990:26: note: candidate function
short16 __OVERLOADABLE__ rotate(short16, short16);
                         ^
<built-in>:2989:25: note: candidate function
short8 __OVERLOADABLE__ rotate(short8, short8);
                        ^
<built-in>:2988:25: note: candidate function
short4 __OVERLOADABLE__ rotate(short4, short4);
                        ^
<built-in>:2984:25: note: candidate function
short2 __OVERLOADABLE__ rotate(short2, short2);
                        ^
<built-in>:2983:26: note: candidate function
uchar16 __OVERLOADABLE__ rotate(uchar16, uchar16);
                         ^
<built-in>:2982:25: note: candidate function
uchar8 __OVERLOADABLE__ rotate(uchar8, uchar8);
                        ^
<built-in>:2981:25: note: candidate function
uchar4 __OVERLOADABLE__ rotate(uchar4, uchar4);
                        ^
<built-in>:2977:25: note: candidate function
uchar2 __OVERLOADABLE__ rotate(uchar2, uchar2);
                        ^
<built-in>:2976:25: note: candidate function
char16 __OVERLOADABLE__ rotate(char16, char16);
                        ^
<built-in>:2975:24: note: candidate function
char8 __OVERLOADABLE__ rotate(char8, char8);
                       ^
<built-in>:2974:24: note: candidate function
char4 __OVERLOADABLE__ rotate(char4, char4);
                       ^
<buil
 [2014-01-30 00:21:57] Failed to init GPU thread 0, disabling device 0
 [2014-01-30 00:21:57] Restarting the GPU from the menu will not fix this.
 [2014-01-30 00:21:57] Try restarting BFGMiner.
 [2014-01-30 00:21:57] Init GPU thread 1 GPU 0 virtual GPU 0
 [2014-01-30 00:21:57] CL Platform vendor: NVIDIA Corporation
 [2014-01-30 00:21:57] CL Platform name: NVIDIA CUDA
 [2014-01-30 00:21:57] CL Platform version: OpenCL 1.0 CUDA 3.2.1
 [2014-01-30 00:21:57] List of devices:
 [2014-01-30 00:21:57]    0   NVS 4200M
 [2014-01-30 00:21:57] Selected 0: NVS 4200M
 [2014-01-30 00:21:57] Error -11: Building Program (clBuildProgram)
 [2014-01-30 00:21:57] <program source>:678:10: error: no matching function for call to 'rotate'
                B = EndianSwap(tmp);
                       ^~~~~~~~~~~~~~~~~~
<program source>:128:24: note: instantiated from:
#define EndianSwap(n) (rotl(n & ES[0], 24U)|rotl(n & ES[1], 8U))
                       ^
<program source>:124:19: note: instantiated from:
#define rotl(x,y) rotate(x,y)
                  ^~~~~~
<built-in>:3025:26: note: candidate function
ulong16 __OVERLOADABLE__ rotate(ulong16, ulong16);
                         ^
<built-in>:3024:25: note: candidate function
ulong8 __OVERLOADABLE__ rotate(ulong8, ulong8);
                        ^
<built-in>:3023:25: note: candidate function
ulong4 __OVERLOADABLE__ rotate(ulong4, ulong4);
                        ^
<built-in>:3019:25: note: candidate function
ulong2 __OVERLOADABLE__ rotate(ulong2, ulong2);
                        ^
<built-in>:3018:25: note: candidate function
long16 __OVERLOADABLE__ rotate(long16, long16);
                        ^
<built-in>:3017:24: note: candidate function
long8 __OVERLOADABLE__ rotate(long8, long8);
                       ^
<built-in>:3016:24: note: candidate function
long4 __OVERLOADABLE__ rotate(long4, long4);
                       ^
<built-in>:3012:24: note: candidate function
long2 __OVERLOADABLE__ rotate(long2, long2);
                       ^
<built-in>:3011:25: note: candidate function
uint16 __OVERLOADABLE__ rotate(uint16, uint16);
                        ^
<built-in>:3010:24: note: candidate function
uint8 __OVERLOADABLE__ rotate(uint8, uint8);
                       ^
<built-in>:3009:24: note: candidate function
uint4 __OVERLOADABLE__ rotate(uint4, uint4);
                       ^
<built-in>:3005:24: note: candidate function
uint2 __OVERLOADABLE__ rotate(uint2, uint2);
                       ^
<built-in>:3004:24: note: candidate function
int16 __OVERLOADABLE__ rotate(int16, int16);
                       ^
<built-in>:3003:23: note: candidate function
int8 __OVERLOADABLE__ rotate(int8, int8);
                      ^
<built-in>:3002:23: note: candidate function
int4 __OVERLOADABLE__ rotate(int4, int4);
                      ^
<built-in>:2998:23: note: candidate function
int2 __OVERLOADABLE__ rotate(int2, int2);
                      ^
<built-in>:2997:27: note: candidate function
ushort16 __OVERLOADABLE__ rotate(ushort16, ushort16);
                          ^
<built-in>:2996:26: note: candidate function
ushort8 __OVERLOADABLE__ rotate(ushort8, ushort8);
                         ^
<built-in>:2995:26: note: candidate function
ushort4 __OVERLOADABLE__ rotate(ushort4, ushort4);
                         ^
<built-in>:2991:26: note: candidate function
ushort2 __OVERLOADABLE__ rotate(ushort2, ushort2);
                         ^
<built-in>:2990:26: note: candidate function
short16 __OVERLOADABLE__ rotate(short16, short16);
                         ^
<built-in>:2989:25: note: candidate function
short8 __OVERLOADABLE__ rotate(short8, short8);
                        ^
<built-in>:2988:25: note: candidate function
short4 __OVERLOADABLE__ rotate(short4, short4);
                        ^
<built-in>:2984:25: note: candidate function
short2 __OVERLOADABLE__ rotate(short2, short2);
                        ^
<built-in>:2983:26: note: candidate function
uchar16 __OVERLOADABLE__ rotate(uchar16, uchar16);
                         ^
<built-in>:2982:25: note: candidate function
uchar8 __OVERLOADABLE__ rotate(uchar8, uchar8);
                        ^
<built-in>:2981:25: note: candidate function
uchar4 __OVERLOADABLE__ rotate(uchar4, uchar4);
                        ^
<built-in>:2977:25: note: candidate function
uchar2 __OVERLOADABLE__ rotate(uchar2, uchar2);
                        ^
<built-in>:2976:25: note: candidate function
char16 __OVERLOADABLE__ rotate(char16, char16);
                        ^
<built-in>:2975:24: note: candidate function
char8 __OVERLOADABLE__ rotate(char8, char8);
                       ^
<built-in>:2974:24: note: candidate function
char4 __OVERLOADABLE__ rotate(char4, char4);
                       ^
<buil
 [2014-01-30 00:21:58] Failed to init GPU thread 1, disabling device 0
 [2014-01-30 00:22:12] Received kill message
 [2014-01-30 00:22:13] Killing OCL 0
 [2014-01-30 00:22:13] Killing OCL 0
 [2014-01-30 00:22:13]
Summary of runtime statistics:

 [2014-01-30 00:22:13] Started at [2014-01-30 00:21:57]
 [2014-01-30 00:22:13] Pool: http://pool1.us.multipool.us:7777
 [2014-01-30 00:22:13] Runtime: 0 hrs : 0 mins : 15 secs
 [2014-01-30 00:22:13] Average hashrate: 0.0 Megahash/s
 [2014-01-30 00:22:13] Solved blocks: 0
 [2014-01-30 00:22:13] Best share difficulty: 0
 [2014-01-30 00:22:13] Share submissions: 0
 [2014-01-30 00:22:13] Accepted shares: 0
 [2014-01-30 00:22:13] Rejected shares: 0 + 0 stale (nan%)
 [2014-01-30 00:22:13] Accepted difficulty shares: 0
 [2014-01-30 00:22:13] Rejected difficulty shares: 0
 [2014-01-30 00:22:13] Hardware errors: 0
 [2014-01-30 00:22:13] Network transfer:   1.3 /   1.1 kB  (109.8 /  94.1  B/s)
 [2014-01-30 00:22:13] Efficiency (accepted shares * difficulty / 2 KB): 0.00
 [2014-01-30 00:22:13] Utility (accepted shares / min): 0.00/min

 [2014-01-30 00:22:13] Unable to get work from server occasions: 0
 [2014-01-30 00:22:13] Work items generated locally: 3
 [2014-01-30 00:22:13] Submitting work remotely delay occasions: 0
 [2014-01-30 00:22:13] New blocks detected on network: 1

 [2014-01-30 00:22:13] Summary of per device statistics:

 [2014-01-30 00:22:13] OCL0       | 5s:  0.0 avg:  0.0 u:  0.0  h/s | A:0 R:0+0(none) HW:0/none
 [2014-01-30 00:22:13] 
Shutdown signal received.

[dmpotter]

I don't know if bfgminer is your best solution for mining with NVidia, shouldn't you try cudaminer?

[HellDiverUK]

I don't know if bfgminer is your best a solution for mining with NVidia, shouldn't you try cudaminer? getting an AMD GPU?

EFA.

[dauntlessdivergent]

I don't know if bfgminer is your best solution for mining with NVidia, shouldn't you try cudaminer?

Yep- I mentioned that it wasn't the best, but it's a machine that I use to stage my workers and try out different mining pools on. Cudaminer works fine, BitMinter works fine -it's just bfgminer that crashes. I just can't figure out why bfgminer is crashing. Since the other mining programs work I figured it may be something simple.

[rmolby]

Where you can specific the COM ports. But for this it would be the ttyUSB ports.

I can't just use the 'erupter:all' because I also have a BFL unit and it will not start.

You can specify individual devices as well:

Code:

bfgminer -S erupter:\\.\COM3 -o -u etc

Thanks, hopefully this'll force BFGminer to see the BFL as what ever it sees it as. And the erupters as BEEs. ....really hate that 20% HW error rate.

you can specify com ports, or if you wanted you could also just run a seperate instance of antminer for the bfl and for the antminers. I find that works best in alot of instances (of course I even seperate individual ants that perform better to give them the 2.1gh clock speed etc lol) I have found bfgminer to be a champ with multiple instances, wherein cgminer simply crashed alot or created conflicts in most multiple instance scenarios.

I can confirm that running multiple instance of BFGminer is very doable and stable... I have seperated my BEs from my ANTs (AMU) and BFL... now the BE's are actually submitting hashes since they are only running difficulty 4, when I had them mixed in with the other mining units and I was running difficulty 16, they were always taking too long to process and would submit stale shares

[Illutian]

you can specify com ports, or if you wanted you could also just run a seperate instance of antminer for the bfl and for the antminers. I find that works best in alot of instances (of course I even seperate individual ants that perform better to give them the 2.1gh clock speed etc lol) I have found bfgminer to be a champ with multiple instances, wherein cgminer simply crashed alot or created conflicts in most multiple instance scenarios.

Oh shoot. Does BEE relate to Antminers? I thought it was the Block Erupters.

I can confirm that running multiple instance of BFGminer is very doable and stable... I have seperated my BEs from my ANTs (AMU) and BFL... now the BE's are actually submitting hashes since they are only running difficulty 4, when I had them mixed in with the other mining units and I was running difficulty 16, they were always taking too long to process and would submit stale shares

The problem still exists that some of the Erupters won't activate (steady green light) and a 'No Device Found' "error" is thrown when you try and manually add them from within BFGminer.

But they are all found using: sudo ./bfgminer/bfgminer -o [redacted] -u [redacted] -p [redacted] -S -all --icarus-options 115200:1:1 --icarus-timing 3.0=100

Then BFGminer only sees the BFL unit. But going "M" -> "+" -> and typing 'all'

Adds the Erupters, usually ICA 0 to ICA 14 and then BEE 0 to BEE 2. For a total of 18 Erupters. Sometimes it does apply 'AMU' to at least one of them.

*Note: I used the Linux step, obviously, here: https://www.btcguild.com/index.php?page=support&section=blockerupter

[rriky92]

in my Raspberry with latest version i can see a usage of CPU about 100% why? :S

[rmolby]

you can specify com ports, or if you wanted you could also just run a seperate instance of antminer for the bfl and for the antminers. I find that works best in alot of instances (of course I even seperate individual ants that perform better to give them the 2.1gh clock speed etc lol) I have found bfgminer to be a champ with multiple instances, wherein cgminer simply crashed alot or created conflicts in most multiple instance scenarios.

Oh shoot. Does BEE relate to Antminers? I thought it was the Block Erupters.

I can tell you on Windows7 with BFGminer 3.9.0_nw_v3 and up, the following are the labels I have seen:

AMU = ANTminer U1
BES = Block Erupter USB
BFL = Butterfly Labs Jalapeno
ICA = Icarus device (Block Erupter USB when not running the -S erupter:all switch)

From what I have gleaned from the forums and I remember off my head,

BEE = also Block Erupter, but normally blade? Not sure...
NFY = Nano Fury

There are quite a few more but I just don't remember and I have no time right now to look...

[Luke-Jr]

Why on earth would you fork cgminer?

I have no  idea why people keep forking cgminer.
You'd think they'd help improve the original BFGMiner codebase!

[Cassey]

As I shift non-ASIC things over to Litecoins, I'm finding myself with a mix of GPUs in my system and wondering if there is a way to set parameters for each individually?

For instance, one poor machine has an APU, a 7870, and a R9-270x.

Note that I'm seriously impressed that it works as well as it does with just generic setting, but one is always trying to tweak a bit more out.

FYI using "-S opencl:auto --intensity 16 --temp-overheat 90 --temp-cutoff 100 --temp-target 80 --scrypt --gpu-fan 100 --auto-gpu" now.

Miner update:  Swapped cards around on another machine, running (2) XFX R9-270s at --intensity 20, rest left alone, and they are running at 465khs/ +/- 2.

[Luke-Jr]

Why on earth would you fork cgminer?

I have no  idea why people keep forking cgminer.
You'd think they'd help improve the original BFGMiner codebase!

So cgminer is a fork of BFGMiner?

More or less, though at this point it might be more accurate to say they have common roots: since forking, the cgminer devs have rewritten most of the BFGMiner code (for the worse, though).

[jedimstr]

Why on earth would you fork cgminer?

I have no  idea why people keep forking cgminer.
You'd think they'd help improve the original BFGMiner codebase!

So cgminer is a fork of BFGMiner?

More or less, though at this point it might be more accurate to say they have common roots: since forking, the cgminer devs have rewritten most of the BFGMiner code (for the worse, though).

I thought both you guys were forks of https://github.com/jgarzik/cpuminer

[Viceroy]

Hey Luke,

Are you going to stop supporting scrypt and GPU mining like the idiot that maintains cgminer?