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

[Nemo1024]

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

[Mudbankkeith]

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

[Mudbankkeith]

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

Maybe in 3.4.0?

[xyzzy099]

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?

[village.idiot]

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?

[rupy]

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!

[HellDiverUK]

How is the BTC/hr number calculated?  It's a bit pointless for me, as I'm not mining BTC - I'm mining PPCoin. 

[juhakall]

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.

[juhakall]

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.

[NorbyTheGeek]

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?

[vulgartrendkill]

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"

[Luke-Jr]

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.

[juhakall]

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.

I tried it with the slush stratum proxy, of course. Yes, two proxies there. As I said, it did produce valid shares at around 60GH/s, and was only limited by the CPU because BFGMiner's proxy didn't set a higher diff target. Another solution I've tried is BFGMiner's getwork proxy, but that won't work because it doesn't support RollNTime.

These kludges would be useful only because BFGMiner still is around 1% slower than chainminer with BFSB miners.

What does this mean exactly?: "Third hashrate displayed is now based on nonces found, adjusted for pool rejected/stale shares. It should still be approximately equivalent to your effective/earning hashrate, but with better accuracy."

At first I thought it was purely based on difficulty accepted ((difficulty_accepted/seconds_elapsed*2^32) hashes per second), but the numbers don't match.

[Luke-Jr]

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.

I tried it with the slush stratum proxy, of course. Yes, two proxies there. As I said, it did produce valid shares at around 60GH/s, and was only limited by the CPU because BFGMiner's proxy didn't set a higher diff target. Another solution I've tried is BFGMiner's getwork proxy, but that won't work because it doesn't support RollNTime.

These kludges would be useful only because BFGMiner still is around 1% slower than chainminer with BFSB miners.

What does this mean exactly?: "Third hashrate displayed is now based on nonces found, adjusted for pool rejected/stale shares. It should still be approximately equivalent to your effective/earning hashrate, but with better accuracy."

At first I thought it was purely based on difficulty accepted ((difficulty_accepted/seconds_elapsed*2^32) hashes per second), but the numbers don't match.

That's what it used to be. Now it's based on (good_nonces * (difficulty_accepted / difficulty_submitted)) for better resolution.

[Mudbankkeith]

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"

This is only needed when you have a mix of devices and need them to show in the process window.
mostly -S all  Is good enough to hash.

[HellDiverUK]

3.3.0 is running well here, Win32 version running on Windows 8.1 Ent.  Currently only controlling a few Block Erupters and two Blades.

[vulgartrendkill]

3.3.0 is running well here, Win32 version running on Windows 8.1 Ent.  Currently only controlling a few Block Erupters and two Blades.

Yep same here. 10 BE and 2 Gen 2 blades running a total of 24.50 ghs.

I have noticed that rejects are about 3 %.  Any idea how I can reduce these or is that acceptable?  Hw errors at .98 %.

[HellDiverUK]

My 1st Gen Blades are sitting at 2.6% and 3.4% HW errors.  It's pretty normal for them.  The Block Erupters are all sitting between 0.5-0.7% HW errors.  Again, normal.

[Zammo]

I have 3.3.0 running on Win7 x64. I haven't had any issues. I have 28 USB erupters, 3.3.0 seems to detect the erupters perfectly. When I used 3.2.1, I often needed to restart BFGMiner several times before all the erupters were detected

[aspirez]

Hi,
can someone explain me how to build BFG miner for windows with static libralies, like that in the win32/64 prebuilded zip's?