Author

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

legendary
Activity: 2576
Merit: 1186
Is it possible to alter the difficulty target for the stratum proxy? I tried it with my BitFury ASIC, and it was getting flooded with diff 0 shares, and the miner's CPU became overloaded. I only got around 60GH/s hashrate when the real hashrate was 95GH/s. The proxy could be a nice alternative to get good backup pool support and the performance of chainminer, which still seems to be a bit faster than BFGMiner.
chainminer doesn't support stratum, so I don't think this will help. Sad
hero member
Activity: 518
Merit: 500
Like others, I have a couple Blue Fury units on order, so in anticipation I upgraded to 3.3.0.  It's working great with my Jalapeno and my USB Block Erupters under Windows.

From looking at others' posts, I wonder if my setup is using a different driver for my block erupters.  My erupters show up as ICAx instead of BESx.  Is that due to the USB driver I use for them, or do they always show up as ICA under Windows?

Is there something I should be doing different for these units?

I`m not sure it makes a great difference but I use
Code:
-s erupter:all
to get the "BES" showing instead of "ICA"
full member
Activity: 201
Merit: 100
Like others, I have a couple Blue Fury units on order, so in anticipation I upgraded to 3.3.0.  It's working great with my Jalapeno and my USB Block Erupters under Windows.

From looking at others' posts, I wonder if my setup is using a different driver for my block erupters.  My erupters show up as ICAx instead of BESx.  Is that due to the USB driver I use for them, or do they always show up as ICA under Windows?

Is there something I should be doing different for these units?
sr. member
Activity: 658
Merit: 250
Is it possible to alter the difficulty target for the stratum proxy? I tried it with my BitFury ASIC, and it was getting flooded with diff 0 shares, and the miner's CPU became overloaded. I only got around 60GH/s hashrate when the real hashrate was 95GH/s. The proxy could be a nice alternative to get good backup pool support and the performance of chainminer, which still seems to be a bit faster than BFGMiner.
sr. member
Activity: 658
Merit: 250
How is the BTC/hr number calculated?  It's a bit pointless for me, as I'm not mining BTC - I'm mining PPCoin. 

Similarly, the network hashrate is calculated wrong unless the altcoin happens to have 10 minute blocks.

If there was an option (for display purposes only) to set the network block rate, block reward and maybe even the name of the coin, these issues could be fixed.

Also, the hashrate counter based on accepted difficulty isn't working with scrypt, here's an example: 0.84/ 0.84/441.6Mh/s. I'm obviously not averaging 441.6MH/s mining scrypt.
hero member
Activity: 1246
Merit: 501
How is the BTC/hr number calculated?  It's a bit pointless for me, as I'm not mining BTC - I'm mining PPCoin. 
hero member
Activity: 725
Merit: 503
Finally got my BF1 to work with bfg, it seems the BF1 is very sensitive to "stuff".

I pulled my router to fix the wifi and then cgminer did not detect the BF1 anymore!?

Then after compiling 3.3.0; I tried everything, rebooting the raspberry, the usb hub and the BF1.

No go, then I tried to add it manually, not found, but after I removed it and put it back it was found, so was the BE.

All good for now... confused about the randomness.

Edit: btw HW seems way off the chart... Higher than A!? Seems to be hashing alright though...

Edit 2: Seems the BF1 doesn't get detected at startup, but it adds fine with M+ and bigpic:all if you cycle it after bfg is started...

Can you run bfg in nohup with logfile instead of the screen? would help alot!
sr. member
Activity: 270
Merit: 250
I'm running bfgminer on a Pi.
Thanks to the help of DrGuns4Hands, it can boot up and run unassisted.
However, when the pool was experiencing the recent DDoS attacks,
I heard the fan slow down for a long period but couldn't see the fault messages that would have been displayed if I had opened a terminal and started bfgminer manually.
So, how do I automatically start it with the output displayed or,
even better, how do I see the output messages using SSH?
legendary
Activity: 1066
Merit: 1098
I have a few Block Erupter USBs among my mining gear, and I find that they work great when I am pool mining - never see any problem at all - but if I use them for solo-mining, I will get something like this every now and then:

[2013-10-12 14:18:10] BES 3: Idle for more than 60 seconds, declaring SICK!
[2013-10-12 14:18:10] BES 3: Attempting to restart

It will then always recover very shortly.  It's not really a problem, but it's annoying.

I don't know if this is a bug, or just some timeout I need to set.  Any help?
hero member
Activity: 868
Merit: 1000
Nice changeset for 3.3.0. I am going to try it with my Erupters, while I am waiting for Blue Furies to be ready for shipping.

One thing I did not find in the changeslog was the ability to auto-rescan COM ports that had prior permissions errors. You remember that tiny UPS monitoring software conflict... Wink
Maybe in 3.4.0?
hero member
Activity: 868
Merit: 1000
Hi Luke-Jr

I'm currently waiting,( impatiently) for my BlueFury sticks to arrive.
I have just installed 3.3.0 on my pc and all seems to be ok. My erupters appear to settle down to their stable mining state faster than before.
GPU's are now retired to the box under the stairs, waiting for the day when BTc go into 4 figures and electricity is free.

When I receive my "Blues", is there anything extra I need to do before plugging them in?

I've looked through the "read notes" but to be fair, If I could understand all of this before next christmas, I could also learn to write my own Miner Grin Grin
The concern is the recent comments about "incorrect drivers" and "bricking"....................

that only applies to the Bitfurystrikesback/megabigpower and Metabank ßfury devices in the 25-400 Ghash range.

but as always regardless of device. take your time and double check everything.

-Taugeran

Thanks, this does settle my mind  a bit, They are expensive.
Then just plug in one, If it works, without "magic smoke" then the rest can follow.
legendary
Activity: 1680
Merit: 1014
Nice changeset for 3.3.0. I am going to try it with my Erupters, while I am waiting for Blue Furies to be ready for shipping.

One thing I did not find in the changeslog was the ability to auto-rescan COM ports that had prior permissions errors. You remember that tiny UPS monitoring software conflict... Wink
hero member
Activity: 658
Merit: 500
CCNA: There i fixed the internet.
Hi Luke-Jr

I'm currently waiting,( impatiently) for my BlueFury sticks to arrive.
I have just installed 3.3.0 on my pc and all seems to be ok. My erupters appear to settle down to their stable mining state faster than before.
GPU's are now retired to the box under the stairs, waiting for the day when BTc go into 4 figures and electricity is free.

When I receive my "Blues", is there anything extra I need to do before plugging them in?

I've looked through the "read notes" but to be fair, If I could understand all of this before next christmas, I could also learn to write my own Miner Grin Grin
The concern is the recent comments about "incorrect drivers" and "bricking"....................

that only applies to the Bitfurystrikesback/megabigpower and Metabank ßfury devices in the 25-400 Ghash range.

but as always regardless of device. take your time and double check everything.

-Taugeran
hero member
Activity: 868
Merit: 1000
Hi Luke-Jr

I'm currently waiting,( impatiently) for my BlueFury sticks to arrive.
I have just installed 3.3.0 on my pc and all seems to be ok. My erupters appear to settle down to their stable mining state faster than before.
GPU's are now retired to the box under the stairs, waiting for the day when BTc go into 4 figures and electricity is free.

When I receive my "Blues", is there anything extra I need to do before plugging them in?

I've looked through the "read notes" but to be fair, If I could understand all of this before next christmas, I could also learn to write my own Miner Grin Grin
The concern is the recent comments about "incorrect drivers" and "bricking"....................
member
Activity: 78
Merit: 10
Hey guys,  I'm currently running Linux Mint and have been struggling with CGMiner (note that it's CG and not BFG).  Reason I'm posting here:  Which one is better for mining.  Currently I'm using BFGminer to run my BFL Asic miner (running on a separate computer) and it's so similar to CGMiner that I kinda wanna try it.  I have 5 7970s and am using them to mine LTC.  Does anyone have a real answer (I don't care about your preference... not to sound rude or anything, I want to know which one is better)?
legendary
Activity: 2576
Merit: 1186
P.S. The MinePeon crowd are very excited to get fury support in bfgminer, I just wish I had one to test with (one is on its way, but not here yet).
Note that there have been some reports that using -S metabank:auto or -S bfsb:auto on the wrong device may brick the unit.
So be careful to only use those when it's actually known to be the real device.
legendary
Activity: 896
Merit: 1000
Right you are, I tried it with ozion and it worked as expected (I should have tried that furst but I had just done my cgminer test cases and it worked a few hours before), I was just a little thrown by the error, I had never seen that one before.

Nil

P.S. The MinePeon crowd are very excited to get fury support in bfgminer, I just wish I had one to test with (one is on its way, but not here yet).
legendary
Activity: 2576
Merit: 1186
Code:
 [2013-10-12 01:30:09] Switching to pool 1 stratum+tcp://stratum.btcguild.com:3333
 [2013-10-12 01:30:12] Stratum from pool 1 requested work update
 [2013-10-12 01:30:12] Pool 1 is hiding block contents from us
 [2013-10-12 01:30:12] Reconnect requested from pool 1 to stratum-lb-12j9j.btcguild.com:3333
 [2013-10-12 01:30:13] Pool 1 is issuing work for an old block: 000000000000000f32406b5c5eab162c30268d45Pool 1 is issuing work for an old block: 000000000000000f32406b5c5eab162c30268d
Pretty sure this is a known problem with BTCGuild right now.
Eleuthria said he was fixing it about an hour ago or so.
legendary
Activity: 896
Merit: 1000
Hi Luke, I am having a bit of a problem adding and setting pool priories via the api.  What I sam trying to do is;-

1. Add a new pool ( api command 'addpool' parameter 'stratum+tcp://stratum.btcguild.com:3333,User,Pass' )
2. Find the new pool id via the API (api command pools )
3. Switch to the new pool (api command switchpool)

I then get the following output from the running miner;-

Code:
 [2013-10-12 01:30:09] Switching to pool 1 stratum+tcp://stratum.btcguild.com:3333
 [2013-10-12 01:30:12] Stratum from pool 1 requested work update
 [2013-10-12 01:30:12] Pool 1 is hiding block contents from us
 [2013-10-12 01:30:12] Reconnect requested from pool 1 to stratum-lb-12j9j.btcguild.com:3333
 [2013-10-12 01:30:13] Pool 1 is issuing work for an old block: 000000000000000f32406b5c5eab162c30268d45Pool 1 is issuing work for an old block: 000000000000
000f32406b5c5eab162c30268d
 [2013-10-12 01:30:13] Stratum from pool 1 requested work update
 [2013-10-12 01:30:40] Stratum from pool 1 requested work update
 [2013-10-12 01:31:10] Stratum from pool 1 requested work update
 [2013-10-12 01:31:40] Stratum from pool 1 requested work update
 [2013-10-12 01:32:10] Stratum from pool 1 requested work update
 [2013-10-12 01:32:40] Stratum from pool 1 requested work update

... bla bla bla ...

Strange thing is, when I disable and remove the new pool via the api it successfully starts to work again with the old pool;-

Code:
 [2013-10-12 01:45:09] Switching to pool 0 http://stratum.bitcoin.cz:3333
 [2013-10-12 01:45:10] Stratum from pool 0 requested work update
 [2013-10-12 01:45:14] Stratum from pool 0 requested work update
 [2013-10-12 01:45:14] Stratum from pool 0 requested work update
 [2013-10-12 01:45:22] Stratum from pool 0 detected new block
 [2013-10-12 01:45:23] Staged work underrun; increasing queue minimum to 7
 [2013-10-12 01:45:23] Stratum from pool 0 requested work update
 [2013-10-12 01:45:26] Accepted 0d3a0a9f ICA 3  Diff 19/4
 [2013-10-12 01:45:26] Accepted 1844399b ICA 0  Diff 10/4
 [2013-10-12 01:45:28] Accepted 0fcb2216 ICA12  Diff 16/4
 [2013-10-12 01:45:35] Accepted 124bbf09 ICA12  Diff 13/4
 [2013-10-12 01:45:35] Accepted 035fa12a ICA 1  Diff 75/4
 [2013-10-12 01:45:38] Accepted 3bbf3051 ICA 7  Diff 4/4
 [2013-10-12 01:45:40] Accepted 1f310966 ICA 7  Diff 8/4

Any ideas?  The code works perfectly in cgminer and I am desperately trying to keep both miners working in my project (minepeon) to give people the choice as to what miner they want to run.  MinePeon uses the api allot to interact with the miner.

Thanks

Neil
sr. member
Activity: 658
Merit: 250
Another thing I've noticed with BFSB hardware and bfgminer is that the load average is always very high. Around 1.6 or so. This doesn't seem to be a problem, I'm just curious what could cause it, when CPU usage is less than 10%. I know that at least high I/O loads can cause high load averages even if the CPU is mostly idling. The load average is only 0.2-0.3 with chainminer, though, so this leads me to believe that bfgminer is doing something different. I'm also running the exact same binary on my other raspberry with 2 BFL Jalapenos, and its load average is always close to zero.
Jump to: