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

[-Redacted-]

Under Windows, right click on your miner window header and go down to DEFAULTS.   Change the default window size.  Close and re-open your miner window.  Up and down arrows work to scroll the list if it's too long, too....

[Icon]

Ok looking for  an option to rescan my usb miners to start the miners that didn't start when i loaded bfgminer.. Kinda like a plug n mine option. and yes already looked over the readme file

Anyone know??


PS

Is there a program out there i can monitor my BTC balance without the need of my wallet.dat ? A nice gui program would work

[Icon]

Ya checked blockchain.info their posted balance for me is way off vs what fulled sync Bitcoin.Qt says

[ypsylon]

Out of curiosity. Is there option to manually pause work on all devices [Pause All/Unpause All]? For example when resetting router, so BFG won't start hooping to other (fail-over) pools.

[Luke-Jr]

Ok looking for  an option to rescan my usb miners to start the miners that didn't start when i loaded bfgminer.. Kinda like a plug n mine option. and yes already looked over the readme file

bfgminer-rpc "devscan|erupter:all"
Follow README.RPC for setup on the miner.

Is there a program out there i can monitor my BTC balance without the need of my wallet.dat ? A nice gui program would work

No. It's not possible to see a balance without wallet.dat (or equivalent, for other clients).

Thanks Luke.  It was bitminer, I removed it from my failover list.

Odd, I have BitMinter as my failover and it works just fine for me

Luke, is bfgminer throttling work based on BFL device temperature?

I'm seeing 85-86C on one BFL device and was wondering if bfgminer has a logic to throttle work, sort of like GPU
temp control.

The --temp-* options work fine for FPGAs/ASICs (with temperature support).

[mdopro1]

Under Windows, right click on your miner window header and go down to DEFAULTS.   Change the default window size.  Close and re-open your miner window.  Up and down arrows work to scroll the list if it's too long, too....

Thanks. I got it.

[Luke-Jr]

Luke, is bfgminer throttling work based on BFL device temperature?

I'm seeing 85-86C on one BFL device and was wondering if bfgminer has a logic to throttle work, sort of like GPU
temp control.

The --temp-* options work fine for FPGAs/ASICs (with temperature support).

Thanks Luke.

I've tried

"temp-cutoff" : "86",
"temp-target" : "79",
"temp-overheat" : "82",
"temp-hysteresis" : "3",

but when the temperature reached 86 C on one BFL device, that device was not disabled.  Do I have to setup any other "auto" parameters for temp-cutoff to work?

Shouldn't.. I'll make a note to test it.

[myporsche]

display bug
http://i39.tinypic.com/2u7rbs8.png

[Luke-Jr]

display bug

What font is your console using?

[Mudbankkeith]

Hi Luke-Jr
I've just migrated to BFGMiner 3.1.4 
Previously I was mining on GUIminer.
With one GPU miner on GUI my hash rate was 500 Mh/s
With 2 miners I had a combined hash of 550 Mh/s

Currently BFGMiner is giving me 520 Mh/s

Can BFGMiner run 2 miners in one process?

[myporsche]

What font is your console using?

Is it this？
http://i41.tinypic.com/2h3pixi.png

and my system is win7 64bit Simplified Chinese version

[Luke-Jr]

What font is your console using?

Is it this？


and my system is win7 64bit Simplified Chinese version

I'm sorry to say that I cannot read Chinese
Can you figure out what the font is, and whether I might be able to download it somewhere?
As a temporary workaround (but let's keep trying to get it fixed!), you can use --no-unicode

[myporsche]

What font is your console using?

Is it this？
http://i41.tinypic.com/2h3pixi.png

and my system is win7 64bit Simplified Chinese version

I'm sorry to say that I cannot read Chinese
Can you figure out what the font is, and whether I might be able to download it somewhere?
As a temporary workaround (but let's keep trying to get it fixed!), you can use --no-unicode

http://i39.tinypic.com/msyu68.png
The font title is Terminal （TrueType），the file name in the win folder is vga936.fon.
I found that I changed the settings such as GPU intensity this buy will appear.

[vulgartrendkill]

Hey there, I`m having a little issue with my block erupters on BFG 3.1.4.  I appears like BFG might be adding a phantom erupter, and so I have two number 9`s. 

Any ideas?

The only way i`ve managed to get rid of this is to restart bfg, but I`d like to keep it going.


Thanks.

[Luke-Jr]

Hey there, I`m having a little issue with my block erupters on BFG 3.1.4.  I appears like BFG might be adding a phantom erupter, and so I have two number 9`s. 

Any ideas?

The only way i`ve managed to get rid of this is to restart bfg, but I`d like to keep it going.


Thanks.

It's just a rendering glitch if they have the same id.

[vulgartrendkill]

Thanks   I thought I had some phantom block erupter problem.

[Spendulus]

Anyone else all of a sudden start having their ESET or other virus program start flagging BFG?  Was alwasy good, never had a problem before (but cgminer would get picked up).  Now here within the last week or so ESET is flagging BFG.

IMO, "antivirus" software that takes the easy way out by flagging commonly abused software as more than merely a warning, is itself malware.
They should be looking for the virus/trojan itself, not the common software they use.

Sadly i found many other private clients from being infected by a bfgminer/cgminer/minerd instance
Hidden in a self starting proces called adobe, so it looks some botnet builders are using the miner to run them illegal

These unknowing customers have no clue that its not normal that their gpu is blazing like mad so they complain and ofcourse some specialist find that its caused by the secretly installed miners.

If this is done by people they know or by botnet owners or usage of illegal software i do not know.
Ofcourse some of them report their findings to the av companies, and to be honest even though its annoying they are right

But fact is that this causes all anti virus makers to flag the miners as nasty software.

They aren't right. BFGMiner is not malware. The botnet is.
Flag that, not the legit software it's abusing.

There is a thing named adobe autodownloaded in the malware packages in "bfgminer dot org", that would likely be this item.

[Luke-Jr]

when the temperature reached 86 C on one BFL device, that device was not disabled.  Do I have to setup any other "auto" parameters for temp-cutoff to work?

After a careful review of the code in question:

• --temp-cutoff acts when the temperature exceeds the argument. This is how BFGMiner/cgminer have always interpreted the value, so this is a documentation error.
• While a device is resting, the hardware error counter continually increments. This is a regression in 3.1.4 (older versions worked correctly).
• It works for me, with the above in mind.

[Krellan]

I just upgraded to bfgminer 3.1.4, rather impressed by the new display layout, I like the summary line and blue highlight at top!

The program runs perfectly, hash rate is good, but should I be concerned about these compilation warnings?

util.c: In function ‘notifier_read’:
util.c:2564:2: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
util.c: In function ‘notifier_wake’:
util.c:2554:2: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
util.c: In function ‘json_rpc_call_completed’:
util.c:504:6: warning: call to ‘_curl_easy_getinfo_err_string’ declared with attribute warning: curl_easy_getinfo expects a pointer to char * for this info [enabled by default]

Josh

[Luke-Jr]

The program runs perfectly, hash rate is good, but should I be concerned about these compilation warnings?

Code:

util.c: In function ‘notifier_read’:
util.c:2564:2: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
util.c: In function ‘notifier_wake’:
util.c:2554:2: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
util.c: In function ‘json_rpc_call_completed’:
util.c:504:6: warning: call to ‘_curl_easy_getinfo_err_string’ declared with attribute warning: curl_easy_getinfo expects a pointer to char * for this info [enabled by default]

These are bugs in your compiler and libcurl, fixed in newer versions of such, and harmless in any case.