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

[ThinkFast]

Thanks for your response!
Ok. So you just chose a more verbose default setting than cgminer. That make sense now.

But what about throughput:
cg: WU: 1.1/m         HD4850
bfg: 0.00 BTC/hr      HD5570

I don't think this is a question of which client is better. I think I must have something configured wrong!
For these tests, I'm using the vanilla client for Win-32. No building from source. I was only doing that on the Arm platform.
I will keep looking. Maybe I will try debug mode.

[ThinkFast]

Summary of runtime statistics:
 [2013-10-27 22:45:30] Started at [2013-10-27 21:55:56]
 [2013-10-27 22:45:30] Pool: http://mint.bitminter.com:8332
 [2013-10-27 22:45:30] Runtime: 0 hrs : 49 mins : 30 secs
 [2013-10-27 22:45:30] Average hashrate: 71.7 Megahash/s
 [2013-10-27 22:45:30] Solved blocks: 0
 [2013-10-27 22:45:30] Best share difficulty: 27
 [2013-10-27 22:45:31] Share submissions: 49
 [2013-10-27 22:45:31] Accepted shares: 49
 [2013-10-27 22:45:31] Rejected shares: 0 + 0 stale (0.00%)
 [2013-10-27 22:45:31] Accepted difficulty shares: 49
 [2013-10-27 22:45:31] Rejected difficulty shares: 0
 [2013-10-27 22:45:31] Hardware errors: 0
 [2013-10-27 22:45:31] Network transfer: 208.2 /  15.9 kB  ( 70.1 /   5.3  B/s)
 [2013-10-27 22:45:31] Efficiency (accepted shares * difficulty / 2 KB): 0.45
 [2013-10-27 22:45:31] Utility (accepted shares / min): 0.99/min
 [2013-10-27 22:45:31] Unable to get work from server occasions: 0
 [2013-10-27 22:45:31] Work items generated locally: 952
 [2013-10-27 22:45:31] Submitting work remotely delay occasions: 0
 [2013-10-27 22:45:31] New blocks detected on network: 7
 [2013-10-27 22:45:31] Summary of per device statistics:
 [2013-10-27 22:45:31] OCL0 63.0C | 5s:  0.0 avg:  0.0 u:  0.0  h/s | A:0 R:0+0 none) HW:0/none
 [2013-10-27 22:45:31] OCL1 66.0C | 5s:71.68 avg:71.65 u:70.82 Mh/s | A:49 R:0+ (none) HW:0/none
 [2013-10-27 22:45:31] Shutdown signal received.

This indicates everything is fine! Hmm.

[ThinkFast]

Can't find "--quiet-work-updates" in the Readme files.
But I will try it.

[ThinkFast]

[Nevermind] I found the restart option in settings.  Doh!
Would it make sense to the developer(s) to have a option to re-read the config file without exiting and restarting?

[Taugeran]

Can't find "--quiet-work-updates" in the Readme files.
But I will try it.

OPT_WITHOUT_ARG("--quiet-work-updates|--quiet-work-update",
                        opt_set_bool, &opt_quiet_work_updates,
                        opt_hidden)

its a hidden option there are actually quite a few

[ThinkFast]

Got it. Thanks!

[Taugeran]

[Nevermind] I found the restart option in settings.  Doh!
Would it make sense to the developer(s) to have a option to re-read the config file without exiting and restarting?

should be doable but as with any feature, takes time. actually... @LJR should externally changing the config and using bfgminers restart functionality work?

[HellDiverUK]

Anyone else noticed the OpenWRT version causes a seg fault when quitting or restarting?  Happened on 3.3 and still happens on 3.4.

[Mudbankkeith]

Hi Luke-Jr

Is it possible to display the 'Time on Current Block' ?

[nwfella]

Hey Luke-jr,

So I finally got my twin turbo ii mounted on my first of two chilis. However, when I execute an instance of bfgminer it properly brings up my Icarus Block Eruptor, as well as the single BFL jally that I have connected, it is seemingly detecting the chili however I'm unable to see the individual chips under the [M]anage Devices section.  The error message that I keep receiving from the BFL 1 (chili) device is 'Failed to send queue, and queue empty; retrying after 1 second"

Any idea what might be causing this?

*Note: I am currently testing out version 3.4.0 (x86)

[jesse11]

Any update for the settings in BFGminer for Klondike K16 mining unit? I've tried yet I'm missing something. I tried: -0 http://stratum.btcguild.com:3333 -u username - p x -- usb KLN: 3 --enable-klondike16     no go  

[Luke-Jr]

it is seemingly detecting the chili however I'm unable to see the individual chips under the [M]anage Devices section.

This is due to Chili being based on a very old protocol.

The error message that I keep receiving from the BFL 1 (chili) device is 'Failed to send queue, and queue empty; retrying after 1 second"

This is due to bugs in the Chili firmware. I think they plan to release a fix at some point.
BFGMiner 3.4 has a workaround for it, but it needs to use more USB bandwidth than normal.

[jesse11]

Any update for the settings in BFGminer for Klondike K16 mining unit?

[Luke-Jr]

Any update for the settings in BFGminer for Klondike K16 mining unit?

Klondikes are, AFAIK, completely unsupported.
I'd be glad to add support, however I have nothing to work with.
Please ask your vendor if they can provide specifications and/or a sample unit.

[nwfella]

it is seemingly detecting the chili however I'm unable to see the individual chips under the [M]anage Devices section.

This is due to Chili being based on a very old protocol.

The error message that I keep receiving from the BFL 1 (chili) device is 'Failed to send queue, and queue empty; retrying after 1 second"

This is due to bugs in the Chili firmware. I think they plan to release a fix at some point.
BFGMiner 3.5 has a workaround for it, but it needs to use more USB bandwidth than normal.

Do you have a link handy? I'm only seeing version 3.4

[Luke-Jr]

it is seemingly detecting the chili however I'm unable to see the individual chips under the [M]anage Devices section.

This is due to Chili being based on a very old protocol.

The error message that I keep receiving from the BFL 1 (chili) device is 'Failed to send queue, and queue empty; retrying after 1 second"

This is due to bugs in the Chili firmware. I think they plan to release a fix at some point.
BFGMiner 3.5 has a workaround for it, but it needs to use more USB bandwidth than normal.

Do you have a link handy? I'm only seeing version 3.4

Sorry, typo. I meant 3.4.

[jesse11]

Will this help, http://projectklondike.org/
I use your miner for all my USB ASIC Miners and it does a fine job, I sure would like to use it for my K16's 

[Luke-Jr]

Will this help, http://projectklondike.org/
I use your miner for all my USB ASIC Miners and it does a fine job, I sure would like to use it for my K16's 

I sent LiquidSynDesigns a message, but it's probably more effective if existing or potential customers also request support.

[jesse11]

PM Sent to Steamboat      Thanks Luke

[nwfella]

it is seemingly detecting the chili however I'm unable to see the individual chips under the [M]anage Devices section.

This is due to Chili being based on a very old protocol.

The error message that I keep receiving from the BFL 1 (chili) device is 'Failed to send queue, and queue empty; retrying after 1 second"

This is due to bugs in the Chili firmware. I think they plan to release a fix at some point.
BFGMiner 3.5 has a workaround for it, but it needs to use more USB bandwidth than normal.

Do you have a link handy? I'm only seeing version 3.4

Sorry, typo. I meant 3.4.

Ok, installed 3.4 and it's apparently seeing the device but now declaring it sick. Debug output shows its stuck doing the following:
Re-initialize
Attempting to restart
Idle for more than 60 seconds, declaring SICK!

If you can provide any suggestions they would be much appreciated. Not particularly concerned about how high USB requirements are.