It was fixed by technique not by any actual driver fixes as far as I know... the problem is in the serial scanning especially if you specify :all.  Some of the drivers mess up other devices that aren't of that type whenever you scan:all.
One way around it is to specify with actual device paths...but for 43 BE's that can change over time? Forget about it...

What you have to do is attach each device in turn and add/scan all one group at a time.  Should also work for the BFL.

For instance in my case, startup with Erupters and GPU.
Then go to M & + in the menu to add new devices after plugging the device in while BFGMiner is running, one group at a time (i.e., bifury:all).

If you try to load all of these in order via the commandline or from the conf file, you'll get only the first group and it won't find the subsequent devices until you unplug-replug.

BTW- for any Bi*Fury users out there... the driver on the Mac requires you to startup BFGMiner via sudo or you won't be able to detect the device.

I use -S all with BE and BFL together OK - from nwoolls post it looks as though specifying them by group works so if nothing else I can update MacMiner to work around that - I was going to just add a 'use all devices' button but I suppose a button for each group wouldn't hurt.

I did try specifying a device individually though, just a BFL box and no luck with the little fury driver enabled - I suppose it needs to know the type of device it's connecting to.

Hi Bitbacco, sorry about the delay, I left the office once my stick was finally running in a cgminer window.

What is it that you needed me to do?

I am still having problems with specifying the bitfury device to cgminer, I cannot identify it from the list.

Anyways let me know if there was still some information you would like to see from my end.
Thanks

hmm.. ..all that is listed is below. I assumed the bluetooth things are what say they are…
and the usbserial are my jalapenos, and the others are the BEs…

Anyways the Bitfury is running at avg of ~2.5gh/s so it seems to be working.

crw-rw-rw-  1 root    wheel      18,  47 18 Dec 10:50dev/cu.Bluetooth-Modem
crw-rw-rw-  1 root    wheel      18,  49 18 Dec 11:02dev/cu.Bluetooth-PDA-Sync
crw-rw-rw-  1 root    wheel      18,  41 18 Dec 11:02dev/cu.Bluetooth-Serial-1
crw-rw-rw-  1 root    wheel      18,  43 18 Dec 11:02dev/cu.Bluetooth-Serial-2
crw-rw-rw-  1 root    wheel      18,  55 18 Dec 13:36dev/cu.SLAB_USBtoUART
crw-rw-rw-  1 root    wheel      18,  57 18 Dec 13:36dev/cu.SLAB_USBtoUART28
crw-rw-rw-  1 root    wheel      18,  59 18 Dec 13:36dev/cu.SLAB_USBtoUART29
crw-rw-rw-  1 root    wheel      18,  61 18 Dec 13:36dev/cu.SLAB_USBtoUART30
crw-rw-rw-  1 root    wheel      18,  63 18 Dec 13:36dev/cu.SLAB_USBtoUART31
crw-rw-rw-  1 root    wheel      18,  65 18 Dec 13:36dev/cu.SLAB_USBtoUART32
crw-rw-rw-  1 root    wheel      18,  73 18 Dec 13:36dev/cu.SLAB_USBtoUART36
crw-rw-rw-  1 root    wheel      18,  75 18 Dec 13:36dev/cu.SLAB_USBtoUART37
crw-rw-rw-  1 root    wheel      18,  77 18 Dec 13:36dev/cu.SLAB_USBtoUART38
crw-rw-rw-  1 root    wheel      18,  79 18 Dec 13:36dev/cu.SLAB_USBtoUART39
crw-rw-rw-  1 root    wheel      18,  81 18 Dec 13:36dev/cu.SLAB_USBtoUART40
crw-rw-rw-  1 root    wheel      18,  83 18 Dec 13:36dev/cu.SLAB_USBtoUART41
crw-rw-rw-  1 root    wheel      18,  85 18 Dec 13:36dev/cu.SLAB_USBtoUART42
crw-rw-rw-  1 root    wheel      18,  87 18 Dec 13:36dev/cu.SLAB_USBtoUART43
crw-rw-rw-  1 root    wheel      18,  89 18 Dec 13:36dev/cu.SLAB_USBtoUART44
crw-rw-rw-  1 root    wheel      18,  91 18 Dec 13:36dev/cu.SLAB_USBtoUART45
crw-rw-rw-  1 root    wheel      18,  93 18 Dec 13:36dev/cu.SLAB_USBtoUART46
crw-rw-rw-  1 root    wheel      18,  95 18 Dec 13:36dev/cu.SLAB_USBtoUART47
crw-rw-rw-  1 root    wheel      18,  97 18 Dec 13:36dev/cu.SLAB_USBtoUART48
crw-rw-rw-  1 root    wheel      18,  99 18 Dec 13:36dev/cu.SLAB_USBtoUART49
crw-rw-rw-  1 root    wheel      18,  67 18 Dec 13:36dev/cu.usbserial-FTWINKIX
crw-rw-rw-  1 root    wheel      18,  69 18 Dec 13:36dev/cu.usbserial-FTWMMYGN

Ya I'm not sure, I know its listed as device BF1 but with all the icarus errors, I cannot seem to find where it initially probes for the device.. just seems to start accepting from BF1 intermingled with all the icarus and bitforce errors.

I'll just wait it out, doesn't seem as though things are being affected!.. Thanks for all the help.

I should have documented this more and it'll work a lot smoother in the next version once API Output is separated from FPGA/ASIC miner and fed by everything - MobileMiner picks up any GPU or PGA devices that are showing up in API Output window

Not a KNC but it'll show in the next version, sorry about that!

Version 1.5.2 is up now but not replacing the download links for 1.5.1 until I've tested it a little bit more.

This update:

-Allows CGMiner window to feed the API Output window

-Allows the API Output window to function for your network miner regardless of whether you're mining on the machine running MacMiner

-Allows networked miners in API Output window to feed MobileMiner

-Removes spell-check lines from log views

http://downloads.fabulouspanda.co.uk/MacMiner.app-1.5.2.zip

No problem, I'm glad you've done all the hard work for me! At this point you can advertise it, I still haven't implemented the controls but it won't be long now. I've been using it for a day or so now and it seems stable.

I just had a couple of issues actually, one is more of a knc problem leading to a feature request - the 5s average hash is always over 33% higher than the total average so the representation in MobileMiner shows a speed much higher than reality - would it be possible to set which average to display, or to display one by the other?

Also, in the odd circumstances of development I fed my account fake machines and devices testing the mechanism and deleted a bunch but now I can't get the devices I deleted back in the devices list - even when removing a machine and letting it show up again - anything that can be done about that?

will do, thanks nwoolls!