I find that I am unable to run both Erupters and Red Fury on the some RPi using  ID 0e8f:0016 GreenAsia Inc. 4 port USB 1.1 hub UH-174 (this is actually a 10-port hub manufactured from 3 ea of the 4-port chips)

I am running bfgminer-3.8.0 on rasbpian , still with usb2. Have not forced usb-1 yet. I have no NanoFury for which that is required.

I got some Red Furies a couple of weeks ago and was able to run one with Erupters for a couple of hours. I was not able to run 2-Red Fury for more than a few minutes. I eventually gave up running any Red Furies with Erupters. As a result, I run the erupters on raspberrypi-2 and Red Furry on raspberrypi-1., GreenAsia hubs on both. I used -S erupter:all and -S bigpic:all to bring them on line.

While playing around today with cascading 10-port hubs (GreenAsia) from a 4-port hub on raspberryp-4 , I repeated the exeriment. I was unable to run both Erupter and Red Fury from the same Pi. However, I was able to run either Erupters or Red Fury, thought not together.

I believe, I have read similar reports on one of these forums concerning the incompatibility of Erupters and Red Furies on the Pi

Now to thoroughly confuse the issue:  On rapsberrypi-3 with a 7-port hub, ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub, I was able to run a Red Fury with a couple of Erupters, for a couple weeks. Same   bfgminer-3.8.0 (and -3.0.7).  The only reason it is not still running is that I consolidated the Red Furies and Erupters on the two dedicated single type Pi miners.

I suppose the conclusion to be drawn is that compatibility is hub chip set sensitive. And, others see this problem.

I have no experience with FreeBSD.  However I had trouble (they say rasbpian's libusb is not useable) compiling for raspberrypi. The suggested solution was to provide libusb from compiled source. See https://bitcointalk.org/index.php?topic=338938.msg3634958#msg3634958 for how this was done for pi. Maybe you can adapt it to your situation.

Reference:  https://bitcointalk.org/index.php?topic=291456.msg3632179#msg3632179


This sounds like a similar problem on compiling bfgminer for raspberrypi.  I was advised to provide libusb because the one provided by rasbpian was not appropriate. It would compile, but the result was not useable.

The solution may be as follows: cd into your bfgminer-x.y.x and make a directory libusb for the purpose of compiling the libusb.

I used an earier version of the source. However, I suggest using the latest bfgminer source; then unzip and change iinto the directory.


 wget the libusb source from sourceforge.net .  Extract the .tar.bz2 source. cd into the resulting directory.
Execute commands ./configure and make. Note that I do NOT do a "make install".



cd up a couple levels back to your bfgminer directory.  The apt-get commands will no doubt be different for FreeBSD. Moreover, the libjason-dev may not be necessary, or you may already have it. Take a close look at the ./configure comand with the LIBUSB_CFLAGS= and LIBUSB_LIBS= . This is the next to last line. The purpose is to pass the path to the usb libraries previously compiled to the ./configure command. I have no experience with BSD and don't know if this will work.


The only claim that I can make is that this worked for rasbpian (debian for raspberrypi). Keep in mind that I am running a red furry rather than a nanofury on a raspberrypi.