Quote from: 303 on December 14, 2013, 01:09:02 AM

Quote from: jedimstr on December 14, 2013, 12:17:08 AM

I was able to finally get the Bi*Fury working on a Mac Pro using BFGMiner.

To top it all off, I did it alongside 44 Block Erupters, a GPU (5770), and a Red Fury, all in the same instance of BFGMiner.

There are two things that are key to getting this working (other than the already known need to kext load the Apple USB Modem drivers for the RedFury):
1. Use BFGMiner via sudo to bypass the permissions issues with the Bi*Fury.
2. Plugging the Bi*Fury and RedFury hot while loading each set of devices/drivers in succession while inside the App instead of all at once at the commandline or in the config.
I loaded the Block Erupters and GPU on startup of BFGMiner. Then I plugged the Bi*Fury into the my hub and used M and + to scan for the Bi*Fury (bifury:all). Then I plugged in the RedFury into the USB hub and did another scan for the RedFury (bigpic:all). I know that the RedFury scans tend to mess up other devices and the Block Erupter scans tend to mess up RedFury, but by staggering the driver loads within the BFGMiner and hotplugging before each scan for the two Bitfury based devices, I was successful in getting all these guys working together!!!

I may just stick with running it this way instead of separately on one of my dedicated RPi's because it seems somewhat unstable on the RPi. I had to go out to my mining room (separate garage room in the freezing cold) a few times today to hotplug the Bi*Fury into a hub because rebooting the Pi and restarting CGMiner didn't fix it, only unplugging/replugging worked with CGMiner on the Pi.

AWESOME! Thanks for the update. So you just ran bfgminer from CLI only specifying the pool address? Looking forward to trying this later tonight...

I have my pool info and some other settings for API and failover in my bfgminer.conf file. On the cli I have:

Code:

sudo bfgminer -S opencl:auto -S erupter:all -c bfgminer.conf

The sudo is important for the Bi*Fury to work or you'll get a segmentation fault.