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

[Coinpicker]

I have a problem i will mine on a cpu pool and he is automatic mining whit gpu and i will get nothing.
How can i stop gpu and start whit cpu?

[1715425521]

1715425521

[1715425521]

1715425521

[1715425521]

1715425521

[1715425521]

1715425521

[1715425521]

1715425521

[1715425521]

1715425521

[drewage]

Is Bi•Fury gonna be supported in the next version?  I know it's in the pipeline, just curious.

In fact, you can try the "bifury" branch I pushed to git... It won't report hashrates, but it should mine...

I'll do that this weekend though I won't be able to actually 'try' it until Monday night.  

Did you have any heat issues with it? (I'm assuming, of course, that you received an engineering sample.)

[Luke-Jr]

Is Bi•Fury gonna be supported in the next version?  I know it's in the pipeline, just curious.

In fact, you can try the "bifury" branch I pushed to git... It won't report hashrates, but it should mine...

I'll do that this weekend though I won't be able to actually 'try' it until Monday night.  

Did you have any heat issues with it? (I'm assuming, of course, that you received an engineering sample.)

Plan on using oven gloves to unplug it...

[drewage]

Is Bi•Fury gonna be supported in the next version?  I know it's in the pipeline, just curious.

In fact, you can try the "bifury" branch I pushed to git... It won't report hashrates, but it should mine...

I'll do that this weekend though I won't be able to actually 'try' it until Monday night.  

Did you have any heat issues with it? (I'm assuming, of course, that you received an engineering sample.)

Plan on using oven gloves to unplug it...

I actually have kevlar gloves so I guess they'll come in handy.   

[juhakall]

Is there anything BFGMiner could do to fix these errors on BFSB hardware without restarting?

BSB 1e: bitfury_init_oldbuf: Giving up after 4 tries

I've noticed that a chip's frequency sometimes drops considerably and it starts spamming that error. Restarting BFGMiner fixes it, unlike when a whole card goes down. Since a simple BFGMiner restart is enough in this case, I'm wondering if this could be fixed automatically when it happens, without even having to restart?

[Taugeran]

Is there anything BFGMiner could do to fix these errors on BFSB hardware without restarting?

BSB 1e: bitfury_init_oldbuf: Giving up after 4 tries

I've noticed that a chip's frequency sometimes drops considerably and it starts spamming that error. Restarting BFGMiner fixes it, unlike when a whole card goes down. Since a simple BFGMiner restart is enough in this case, I'm wondering if this could be fixed automatically when it happens, without even having to restart?

i get this occasionally with a nanofury NF1 that i pencil modded. lowering the osc6 bits restarts it. i changed the volt mod slightly and it became stable again at the higher bits

[h3nkthesupertank]

I have a question i could not find so easely, so that's why im posting here. Sorry for bad English.

I'm using bfgminer 3.6.0 at this moment to mine some BTC.

Well, when i'm mining, i see this:

1:       xx/xx/xxMh/s
OCL 0: xx/xx/xxMh/s

I'm mining with my GPU, were is the 1 for and were is the OCL 0 for?
What XX's do i need to look for what my actual MH/s's are?

Thank you! God Bless

[Luke-Jr]

README

[HellDiverUK]

Is the Klondike K16 supported now in BFG?  I can't be sure looking at the readmes.

[Luke-Jr]

Is the Klondike K16 supported now in BFG?  I can't be sure looking at the readmes.

The driver is pretty poor code (almost verbatim import from cgminer), so I'll probably rewrite it when/if they get back to me with protocol specs (or maybe reverse engineer it from this code), but it should work as of 3.6.0...

[HellDiverUK]

Is the Klondike K16 supported now in BFG?  I can't be sure looking at the readmes.

The driver is pretty poor code (almost verbatim import from cgminer), so I'll probably rewrite it when/if they get back to me with protocol specs (or maybe reverse engineer it from this code), but it should work as of 3.6.0...

Cheers.  

I was bidding on a K16 on Fleabay, but it went for Silly Money^tm - someone was pretty keen to pay £280 for the thing...

[hhs99]

I have a machine with a quadcore and 2 nvidia video cards and I cant get bfgminer to run i get this error

clDevicesNum returned error, no GPUs usable

I'm trying to mine litecoins with it. the nvidia gpus are temporary until my 7900's get here. help please

[BRADLEYPLOOF]

I have a machine with a quadcore and 2 nvidia video cards and I cant get bfgminer to run i get this error

clDevicesNum returned error, no GPUs usable

I'm trying to mine litecoins with it. the nvidia gpus are temporary until my 7900's get here. help please

Your batch file to start bfgminer should look something like this:

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
bfgminer --scrypt -o host:port -u username -p password

And from there you can adjust the other GPU information such as
--lookup-gap <arg>  Set GPU lookup gap for scrypt mining, comma separated
--shaders <arg>     GPU shaders per card for tuning scrypt, comma separated
--thread-concurrency <arg> Set GPU thread concurrency for scrypt mining, comma separated

Then try running it

[hhs99]

I have a machine with a quadcore and 2 nvidia video cards and I cant get bfgminer to run i get this error

clDevicesNum returned error, no GPUs usable

I'm trying to mine litecoins with it. the nvidia gpus are temporary until my 7900's get here. help please

Your batch file to start bfgminer should look something like this:

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
bfgminer --scrypt -o host:port -u username -p password

And from there you can adjust the other GPU information such as
--lookup-gap <arg>  Set GPU lookup gap for scrypt mining, comma separated
--shaders <arg>     GPU shaders per card for tuning scrypt, comma separated
--thread-concurrency <arg> Set GPU thread concurrency for scrypt mining, comma separated

Then try running it

Same result.

[ikolubr]

Hi guys,
I'm new here. I was using CGminer on ubuntu and decided to change to BFGminer. I installed through the PPA. BFGMiner doesn't recognize my BFL's and recognize just one of my usb asicminers, I have 11 of them.
Anything I need to do extra? Do I need to install drivers for them or BFL like in Windows?!

Any ideas?

Thank you,
Igor

[Luke-Jr]

Hi guys,
I'm new here. I was using CGminer on ubuntu and decided to change to BFGminer. I installed through the PPA. BFGMiner doesn't recognize my BFL's and recognize just one of my usb asicminers, I have 11 of them.
Anything I need to do extra? Do I need to install drivers for them or BFL like in Windows?!

Any ideas?

Thank you,
Igor

From README:

Q: I ran cgminer, and now BFGMiner doesn't work!
A: cgminer has its own non-standard implementations of the drivers for most USB devices, and disables the official drivers (on Windows, you did this manually using Zadig). Before you can use BFGMiner, you will need to restore the original driver. With Linux, usually rebooting or re-plugging the device is sufficient.

[ikolubr]

Hi guys,
I'm new here. I was using CGminer on ubuntu and decided to change to BFGminer. I installed through the PPA. BFGMiner doesn't recognize my BFL's and recognize just one of my usb asicminers, I have 11 of them.
Anything I need to do extra? Do I need to install drivers for them or BFL like in Windows?!

Any ideas?

Thank you,
Igor

From README:

Q: I ran cgminer, and now BFGMiner doesn't work!
A: cgminer has its own non-standard implementations of the drivers for most USB devices, and disables the official drivers (on Windows, you did this manually using Zadig). Before you can use BFGMiner, you will need to restore the original driver. With Linux, usually rebooting or re-plugging the device is sufficient.

Thank you Sir. Very Appreciated!

[stridergt]

I posted the following on the cgminer thread, but since minepeon can utilize bfgminer too, I could use some of your help:

I am using minepeon (cgminer3.6.4) with a Jalapeno and observing that DAcc (Difficulty Accepted) is 60-85% when mining with the eligius pool and 100-105% when mining with BTCguild. (both pools had min difficulty set to auto, but even when I changed BTCguild to 8+GH/s, the difference in percentage roughly stayed the same)
Can someone elaborate a bit on the Dacc calculation and the difference I am observing between the two pools, does it affect my share contribution accordingly???
I checked github, but I was a bit lost. I also asked at the minepeon forum but the dev just parsed the DAcc value and could not elaborate on the calculation method.

Thank you in advance

[drewage]

Well, I can't wait for the next version to come out.  I have one of the bi-furies and I can't for the life of me get it recognized and running.  I've tried compiling BFGMiner from source and CGMiner from source on Ubuntu.  I've tried using precompiled binaries of CGMiner on OS X and I've gotten no love.  Mostly it's been unrecognized but when it has been recognized as a bitfury device it hasn't initialized.  It can just sit on it's hot little ass until I have more time to screw with it or 3.7 comes out.   There's no doubt though, this thing needs a fan.  It gets HOT just being plugged in. 

[Luke-Jr]

Well, I can't wait for the next version to come out.  I have one of the bi-furies and I can't for the life of me get it recognized and running.  I've tried compiling BFGMiner from source and CGMiner from source on Ubuntu.  I've tried using precompiled binaries of CGMiner on OS X and I've gotten no love.  Mostly it's been unrecognized but when it has been recognized as a bitfury device it hasn't initialized.  It can just sit on it's hot little ass until I have more time to screw with it or 3.7 comes out.   There's no doubt though, this thing needs a fan.  It gets HOT just being plugged in.  

Not sure when(if?) they'll be publishing the Windows INF file, but here's one that should work.

Edit: But do note that earlier Bi*furys shipped with buggy firmware and might not work very well until you upgrade the firmware (see BFGMiner README.ASIC for instructions.