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

[NecroBones]

The info is in the readme.txt

The totals line shows the following:
 6/32   75.0C | 171.3/170.8/171.2Gh/s | A:729 R:8+0(.01%) HW:0/.81%

Each column is as follows:
  The number of devices and processors currently mining
  Hottest temperature reported by any processor
  5 second exponentially decaying average hash rate
  An all time average hash rate
  An all time average hash rate based on actual nonces found, adjusted for pool
      reject and stale rate
  The number of Accepted shares
  The number of Rejected shares and stale shares discarded (never submitted),
      and the percentage these are of total found.
  The number of HardWare errors, and percentage invalid of nonces returned

Awesome thanks, I must have missed that.

But that doesn't explain to me why there would be such a huge difference. For instance, I see a line like this:

AMU 3: | 0.59/ 1.06/ 2.00Gh/s

How does the "all time" average end up being about half of the one that is based on nonces found?

[NecroBones]

What do the three speeds for each device mean, relative to each other? I just updated to 3.10.0, and plugged in the antminers that arrived today, and I see the third speed reported as 2GH, but the other numbers are half that. Is this normal?

What arguments are you using to launch bfgminer? Are you specifying manual Icarus timings?

Actually yes, I copied someone's settings from a couple pages back in this thread:

"scan" : [
   "erupter:all",
   "antminer:all",
   "all"
],
"set-device" : [
   "antminer:clock=x0981"
],
"icarus-options" : "115200:2:2",
"icarus-timing" : "2.5=90",
"klondike-options" : "362:65"
}

[nwoolls]

Actually yes, I copied someone's settings from a couple pages back in this thread:

"scan" : [
   "erupter:all",
   "antminer:all",
   "all"
],
"set-device" : [
   "antminer:clock=x0981"
],
"icarus-options" : "115200:2:2",
"icarus-timing" : "2.5=90",
"klondike-options" : "362:65"
}

That's why. The first two numbers, for Icarus-based devices, are essentially estimates based on an internal # that is different for each device, e.g. Erupter is ABC, Antminer is XYZ, etc. The third number is your effective hashrate based on actual work you are doing.

When you start to override the Icarus timings using arguments on the command line or config file it throws off those first two numbers, but not the real work done.

[NecroBones]

Actually yes, I copied someone's settings from a couple pages back in this thread:

"scan" : [
   "erupter:all",
   "antminer:all",
   "all"
],
"set-device" : [
   "antminer:clock=x0981"
],
"icarus-options" : "115200:2:2",
"icarus-timing" : "2.5=90",
"klondike-options" : "362:65"
}

That's why. The first two numbers, for Icarus-based devices, are essentially estimates based on an internal # that is different for each device, e.g. Erupter is ABC, Antminer is XYZ, etc. The third number is your effective hashrate based on actual work you are doing.

When you start to override the Icarus timings using arguments on the command line or config file it throws off those first two numbers, but not the real work done.

OK, that's good to know. So I either need to ignore the other averages, or ditch the custom settings. I'm not sure how those settings are affecting performance anyway, so I might remove them.

[NecroBones]

That's why. The first two numbers, for Icarus-based devices, are essentially estimates based on an internal # that is different for each device, e.g. Erupter is ABC, Antminer is XYZ, etc. The third number is your effective hashrate based on actual work you are doing.

When you start to override the Icarus timings using arguments on the command line or config file it throws off those first two numbers, but not the real work done.

OK, that's good to know. So I either need to ignore the other averages, or ditch the custom settings. I'm not sure how those settings are affecting performance anyway, so I might remove them.

It looks like overall performance is better with the defaults. Thanks guys!

[WhiteBeard]

I just upgraded to bfgminer 3.9.0 and now it can't find my bfl miners... I have   '-S all' in the command line.  It finds the AsicMiner Erupters, but none of the BFL stuff.  What am I doing wrong?  Did I lose something when I removed version 3.1.4?

Thanks for any help!!  PLEASE!!!  

EDIT:  there was a file called 'bitforce-firmware-flash' in the working directory of the previous version that I do not see anywhere now.  Could that be the problem?

[HellDiverUK]

I just upgraded to bfgminer 3.9.0 and now it can't find my bfl miners... I have   '-S all' in the command line.  It finds the AsicMiner Erupters, but none of the BFL stuff.  What am I doing wrong?  

Should still work fine. 

EDIT:  there was a file called 'bitforce-firmware-flash' in the working directory of the previous version that I do not see anywhere now.  Could that be the problem?

Nothing to do with it.

[WhiteBeard]

But it's still not working...  I've been working on it for hours.  Any ideas?   

[HellDiverUK]

But it's still not working...  I've been working on it for hours.  Any ideas?   

Need more info.  What OS are you running on?  What way is the BFL attached?  Hubs?  What sort of USB port?

[JBT]

But it's still not working...  I've been working on it for hours.  Any ideas?   

check in windows device manager if they actually show up there presuming it's windoze.....

[Mudbankkeith]

But it's still not working...  I've been working on it for hours.  Any ideas?   

check in windows device manager if they actually show up there presuming it's windoze.....

Start from the beginning.  unplug everything.
Install the latest version 3.10.0

restart the PC, I assume its windows.

plug in your erupters, when they have been accepted by windows, start your BFG.

power up one BFL.

then plug in the USB cable. watch for the port to be accepted. The first one may take a few minutes to install.

Start a new session of BFG.
Because the erupters are already running, the new session should just see your BFL.

Then add the others one at a time and watch for the ports to be accepted again. They should be quicker the second time and onwards.

Then just stop The sessions of BFG and wait a few seconds.

Then start a new session of BFG. It should then find everything.

The command line should only need               -S all      or         -S:all

[alicea]

Hello
1. What intensity is the best to be set on Usb Block Erupters? What intensity is being set by default?
2. Is it normal that they show as Icarus?
3. BFGminer doesn't show me the temperature, what to do to have it shown?

[nwoolls]

1. What intensity is the best to be set on Usb Block Erupters? What intensity is being set by default?

No concern - intensity is for GPUs only. Nothing to do with ASICs.

2. Is it normal that they show as Icarus?

Yes, you need to pass in -S erupter:all in order to have them detected as a Block Erupter

3. BFGminer doesn't show me the temperature, what to do to have it shown?

Block Erupters do not report their temperature.

[alicea]

2. Is it normal that they show as Icarus?

Yes, you need to pass in -S erupter:all in order to have them detected as a Block Erupter

Must I do it or may I leave them being recognised as Icarus? Does it change anything from practical point of view?

3. BFGminer doesn't show me the temperature, what to do to have it shown?

Block Erupters do not report their temperature.

Ok... I have a radiator and it is a bit warm in the place it touches erupters (not hot) - I hope it's sufficient cooling?

[Mudbankkeith]

2. Is it normal that they show as Icarus?

Yes, you need to pass in -S erupter:all in order to have them detected as a Block Erupter

Must I do it or may I leave them being recognised as Icarus? Does it change anything from practical point of view?

3. BFGminer doesn't show me the temperature, what to do to have it shown?

Block Erupters do not report their temperature.

Ok... I have a radiator and it is a bit warm in the place it touches erupters (not hot) - I hope it's sufficient cooling?

erupter or icarus its only a name at this level.    If you have any other devices then you can name them, but then you need      -S erupter all -S otherdevice all

A small USB fan for some cooling is helpful.

[Xbits]

Has anybody gotten BFG 3.10 working with antminer in Win 7 64bit....mine gets stuck at "started bfminer 3.10.0" and nothing else.
I tried removing Zadig and reinstalling the driver thru windows without changing with Zadig and still it does not work. I am running the command line shown in these thread.

bfgminer  -o stratum+tcp://us1.ghash.io:3333 -u XXXX -p XXX -S antminer:all --set-device antiminer:clock=x0981

the antminer is working with cgminer but cant get it to work with bfg. Thanks

How long do you give it?  Try giving it a minute or two to load.  Are you running it in a command prompt or a shortcut/.bat file?  If it's the latter try using the command prompt directly since the window closes if the shortcut or .bat file runs into an error.  Using a command prompt lets you see what the error message is.

You could try to start BFG Miner with just the '--set-device antiminer:clock=x0981' command and see if that works or with no commands at all.

Also make sure the pool details are correct as it will auto close the window if it is not.

At the end of your .bat file start a new line and put:

pause

instead of closing out, this will keep the window open when there is a problem so you can see what the problem is.

[AbiTxGroup]

How long do you give it?  Try giving it a minute or two to load.  Are you running it in a command prompt or a shortcut/.bat file?  If it's the latter try using the command prompt directly since the window closes if the shortcut or .bat file runs into an error.  Using a command prompt lets you see what the error message is.

You could try to start BFG Miner with just the '--set-device antiminer:clock=x0981' command and see if that works or with no commands at all.

Also make sure the pool details are correct as it will auto close the window if it is not.

At the end of your .bat file start a new line and put:

pause

instead of closing out, this will keep the window open when there is a problem so you can see what the problem is.

Its easier to use windows explorer to go to you miners directory and click on the path to highlight it, then type in "CMD" and press enter.  This will open a command prompt, you can start your batch file in this window.  If the miner stops or if you stop the miner, the window will stay open.

[voingiappone]

Hello everybody, I dare to ask here a small question that is driving me nuts!

I am using 4 Antminers U1 on a 32bit Linux machine (my laptop). No problems here but I need to move them on my mining server (linux 64bit) but if I try to compile and install BFGMiner it cannot detect any miner. No matter how I try... even if I get root privileges.
No problem when installing on any 32bit machine but not working on any 64bit.

I have all the dependencies installed (compiles fine) and I also tried to change libudev0-dev with libudev1-dev, updated libc6 etc. Last thing I can do is to run a virtualized 32 bit machine but I think that's a last resort (dumb) solution.

Can somebody point me to a solution? Or at least explain me where the problem is....

Thank you all,

Luca

[nwoolls]

I am using 4 Antminers U1 on a 32bit Linux machine (my laptop). No problems here but I need to move them on my mining server (linux 64bit) but if I try to compile and install BFGMiner it cannot detect any miner. No matter how I try... even if I get root privileges.

Run the following and report the output back here:

Code:

bfgminer -d? -D -S antminer:all

[Luke-Jr]

Yes, you need to pass in -S erupter:all in order to have them detected as a Block Erupter

Must I do it or may I leave them being recognised as Icarus? Does it change anything from practical point of view?

Using the erupter driver gives you: correct hashrate, timings, and identify function.
With icarus timings, you might lose some hashing time until it calibrates, but I've tried to minimise that.