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

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: alicea on January 17, 2014, 10:29:52 AM

Quote from: nwoolls on January 17, 2014, 10:21:30 AM

Quote from: alicea on January 17, 2014, 10:15:00 AM

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?

Quote from: nwoolls on January 17, 2014, 10:21:30 AM

Quote from: alicea on January 17, 2014, 10:15:00 AM

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.

alicea

hero member

Activity: 1050

Merit: 501

Quote from: nwoolls on January 17, 2014, 10:21:30 AM

Quote from: alicea on January 17, 2014, 10:15:00 AM

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?

Quote from: nwoolls on January 17, 2014, 10:21:30 AM

Quote from: alicea on January 17, 2014, 10:15:00 AM

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?

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: alicea on January 17, 2014, 10:15:00 AM

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.

Quote from: alicea on January 17, 2014, 10:15:00 AM

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

Quote from: alicea on January 17, 2014, 10:15:00 AM

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

Block Erupters do not report their temperature.

alicea

hero member

Activity: 1050

Merit: 501

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?

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: JBT on January 17, 2014, 07:16:40 AM

Quote from: WhiteBeard on January 17, 2014, 05:29:18 AM

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

JBT

full member

Activity: 165

Merit: 100

Quote from: WhiteBeard on January 17, 2014, 05:29:18 AM

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

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: WhiteBeard on January 17, 2014, 05:29:18 AM

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?

WhiteBeard

full member

Activity: 156

Merit: 102

Bean Cash - More Than a Digital Currency!

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

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: WhiteBeard on January 16, 2014, 09:34:57 PM

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.

Quote

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

full member

Activity: 156

Merit: 102

Bean Cash - More Than a Digital Currency!

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? Huh

Thanks for any help!! PLEASE!!! Undecided

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?

NecroBones

newbie

Activity: 58

Merit: 0

Quote from: NecroBones on January 16, 2014, 06:31:34 PM

Quote from: nwoolls on January 16, 2014, 06:29:33 PM

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!

NecroBones

newbie

Activity: 58

Merit: 0

Quote from: nwoolls on January 16, 2014, 06:29:33 PM

Quote from: NecroBones on January 16, 2014, 06:28:14 PM

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

Quote

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

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: NecroBones on January 16, 2014, 06:28:14 PM

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

Quote

"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

newbie

Activity: 58

Merit: 0

Quote from: nwoolls on January 16, 2014, 06:23:26 PM

Quote from: NecroBones on January 16, 2014, 06:01:21 PM

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:

Quote

"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"
}

NecroBones

newbie

Activity: 58

Merit: 0

Quote from: AbiTxGroup on January 16, 2014, 06:18:05 PM

The info is in the readme.txt

Quote

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:

Quote

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?

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: NecroBones on January 16, 2014, 06:01:21 PM

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?

AbiTxGroup

sr. member

Activity: 447

Merit: 250

Quote from: NecroBones on January 16, 2014, 06:01:21 PM

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?

image cut

The info is in the readme.txt

Quote

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

NecroBones

newbie

Activity: 58

Merit: 0

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?

https://i.imgur.com/JfXKAeO.jpg

wwwin

sr. member

Activity: 447

Merit: 250

Quote from: iglasses on January 16, 2014, 03:06:09 PM

Quote from: wwwin on January 16, 2014, 01:34:51 PM

Quote from: Laxe on January 16, 2014, 12:29:19 PM

Quote from: wwwin on January 16, 2014, 11:23:52 AM

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.

I have given a few minutes and stays there nothing other than "started bfminer 3.10.0"..If I run just --set-device antiminer:clock=x0981
then runs but does not recognize the Antminer. If I run just -S antminer:all --set-device antiminer:clock=x0981 then it hangs as before when I had the pool info...I am running from command prompt not batch file. Are you able to run the new 3.10.0 on Win 7 64? Thanks

I ran it for a while yesterday and went back to 3.9 today. I have three workers all Win7/64 and although it ran I was getting a ton of errors so not sure what that is about. Standard startup.
clocking @ 2ghs though not even trying 2.2 but that is even with 3.9 because I think my hub isn't throwing enough power into the sticks.

OK, will try 3.9 and see if that works. Thanks

iglasses

legendary

Activity: 1148

Merit: 1000

Quote from: wwwin on January 16, 2014, 01:34:51 PM

Quote from: Laxe on January 16, 2014, 12:29:19 PM

Quote from: wwwin on January 16, 2014, 11:23:52 AM

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.

I have given a few minutes and stays there nothing other than "started bfminer 3.10.0"..If I run just --set-device antiminer:clock=x0981
then runs but does not recognize the Antminer. If I run just -S antminer:all --set-device antiminer:clock=x0981 then it hangs as before when I had the pool info...I am running from command prompt not batch file. Are you able to run the new 3.10.0 on Win 7 64? Thanks

I ran it for a while yesterday and went back to 3.9 today. I have three workers all Win7/64 and although it ran I was getting a ton of errors so not sure what that is about. Standard startup.
clocking @ 2ghs though not even trying 2.2 but that is even with 3.9 because I think my hub isn't throwing enough power into the sticks.

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