Do not update to bfgminer 3.3.0.It breaks many things with MultiMiner. I'm working with Luke on it now.
Edit: Stick with 3.2.1 for now. There are several changes in 3.3.0 that I'll need to handle them in MultiMiner. Specifically:
- bfgminer no longer detects GPUs without using the -S opencl:auto argument
- bfgminer now lists GPUs after listing USBs which breaks things subtly
- bfgminer is no longer returning Intensity with the devs RPC API call
Edit 2: Here's some more information on why the order of the GPUs and USBs returned by bfgminer is causing such a problem. There were already some bugs and quirks in bfgminer prior to 3.3.0, but with this changing of the device orders it compounds things to the point of not being usable. I haven't found a solution yet.
Prior to 3.3.0, running bfgminer -d? would return GPUs first and then USBs. In 3.3.0, USBs are returned first and then GPUs. It seems like a small change until you factor in some other behaviors of bfgminer.
For instance, launching bfgminer --scrypt makes it ignore all USB devices. This was not a problem with GPUs returned first by the -d? argument. Now, however, if you try to launch bfgminer with the device index returned by -d? along with the --scrypt argument you get an invalid device error.
Pseudo Examples: #1 bfgminer -S all -S opencl:auto -d?
0 USB
1 GPU
bfgminer -S all -S opencl:auto -d 0 // succeeds
bfgminer -S all -S opencl:auto --scrypt -d 1 / fails, USB device in-use, -d 1 is no longer valid
#2 bfgminer -S all -S opencl:auto -d?
0 USB
1 GPU
bfgminer -S all -S opencl:auto --scrypt -d 1 / fails, USB devices ignored, -d 1 is no longer valid
#3 bfgminer -S all -S opencl:auto -d?
0 USB
1 GPU
bfgminer -S all -S opencl:auto -d 1 // succeeds, GPU mining only
bfgminer -S all -S opencl:auto -d?
1 GPU // where did the USB device go?
While I think this all seems like fairly odd and inconsistent behavior, Luke assures me that bfgminer was never designed to work the way it was up until 3.3.0. He indicates that the previous behavior, while it may have worked, was undefined.
I'll continue to look into this but, for now, stick with bfgminer 3.2.1 or cgminer.