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

[OtaconEmmerich]

Also here's a debug log I get when I try out my old args.

Code:

 [2013-08-04 08:12:23] setrlimit: Soft fd limit already identical to hard limit         (1024)
 [2013-08-04 08:12:23] ft232r_scan: Found 10c4:ea60 - not a ft232r                      
 [2013-08-04 08:12:23] ft232r_scan: Found 13fe:3200 - not a ft232r                      
 [2013-08-04 08:12:23] ft232r_scan: Found 1d6b:0001 - not a ft232r                      
 [2013-08-04 08:12:23] ft232r_scan: Found 1d6b:0002 - not a ft232r

Seems like I'm missing something to detect the BE, Hmmm.

Quick update: I just checked dmesg and it says the BE is registering as a GSM MODEM, WHAT THE HELL?

Disable / remove modemmanager.  Unless of course you use it for some reason.

apt-get / aptitude purge modemmanager on debian/derived systems.  I did this on my ubuntu machine before my Jalapeños arrived.

This is a RT-N16 with ASUSWRT Merlin, I tried disabling the USB Modem feature in the web GUI but it still detects it as a Modem. Ugh. I'm pretty sure I can't remove it as it's part of the firmware package.

[OtaconEmmerich]

Quick update: I just checked dmesg and it says the BE is registering as a GSM MODEM, WHAT THE HELL?

Sounds like maybe a new model BE - although I'm not sure why it'd claim to be a modem.
Can you paste the exact lines from dmesg?

Code:

drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
option 2-1:1.0: GSM modem (1-port) converter detected
usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
usbcore: registered new interface driver option
drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.2
usb 2-1: USB disconnect, address 2
option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
option 2-1:1.0: device disconnected
usbcore: deregistering interface driver option
drivers/usb/serial/usb-serial.c: USB Serial deregistering driver GSM modem (1-port)
usbcore: deregistering interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial deregistering driver generic
usbcore: deregistering interface driver usbserial

[Luke-Jr]

Quick update: I just checked dmesg and it says the BE is registering as a GSM MODEM, WHAT THE HELL?

Sounds like maybe a new model BE - although I'm not sure why it'd claim to be a modem.
Can you paste the exact lines from dmesg?

Code:

drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
option 2-1:1.0: GSM modem (1-port) converter detected
usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
usbcore: registered new interface driver option
drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.2
usb 2-1: USB disconnect, address 2
option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
option 2-1:1.0: device disconnected
usbcore: deregistering interface driver option
drivers/usb/serial/usb-serial.c: USB Serial deregistering driver GSM modem (1-port)
usbcore: deregistering interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial deregistering driver generic
usbcore: deregistering interface driver usbserial

Are you using any special modprobe commands here?
What does lsusb -vv report?

[OtaconEmmerich]

Are you using any special modprobe commands here?
What does lsusb -vv report?

I ran nothing at all, I replugged in the BE before I ran this command.

Code:

Bus 002 Device 003: ID 10c4:ea60
Bus 001 Device 002: ID 13fe:3200
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 001: ID 1d6b:0002

[Luke-Jr]

Are you using any special modprobe commands here?
What does lsusb -vv report?

I ran nothing at all, I replugged in the BE before I ran this command.

Code:

Bus 002 Device 003: ID 10c4:ea60
Bus 001 Device 002: ID 13fe:3200
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 001: ID 1d6b:0002

Did you install kmod-usb-serial-cp210x from opkg?

[OtaconEmmerich]

Are you using any special modprobe commands here?
What does lsusb -vv report?

I ran nothing at all, I replugged in the BE before I ran this command.

Code:

Bus 002 Device 003: ID 10c4:ea60
Bus 001 Device 002: ID 13fe:3200
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 001: ID 1d6b:0002

Did you install kmod-usb-serial-cp210x from opkg?

AH HA! as I thought, the repo doesn't have that. I made a request for it, I guess I just gotta wait till someone compiles it and adds it. Thanks for clearing this up Luke-Jr.

[smscotten]

I'm having trouble building BFGminer on Angstrom (BeagleBone Black).

I started trying to build 2.10.11 because that was what was listed as "stable." When building I was told that I needed jansson. I build jansson fine and the whole ./configure, make, make install process appeared to go through with no trouble (Success!). Except that when I tried to run the executable:

bfgminer: error while loading shared libraries: libjansson.so.4: cannot open shared object file: No such file or directory

libjansson.so.4 is right in the same place (/usr/local/lib) it was when I ran make and make install. So, not sure what that's about.

At that point I figured that I ought to just try the 3.1.4 version. There configure reported:

checking whether HASH_ITER is declared... no
configure: error: Could not find HASH_ITER - please install uthash-dev 1.9.2+


Ok, so I went looking for uthash and here is where I'm probably handicapped by not being a C guy. (My first language was Fortran, then TCL, Rexx, and Perl, and now I write PHP because that's what they pay me to do). Anyway, the only uthash distribution out there says only this:

USAGE
============
The only file you need to use uthash in your own application is

    src/uthash.h

These bonus headers are also included:

    src/utlist.h
    src/utarray.h
    src/utstring.h

OK, header files. There are a number of them in the directory where I untarred the 3.1.4 distribution, and where I was trying to build bfgminer. So I tried copying uthash.h into the bfgminer distribution folder, but configure reported the same "Could not find HASH_ITER - please install uthash-dev 1.9.2+" message. I tried the same after copying the other three "bonus" header files in as well.

At this point it appears that I don't just need the uthash header files; I need the debian package uthash-dev. Which I don't have because I'm not running Debian.

Searching didn't yield any answers to these, so I'm a bit stuck and back to mining with cgminer. Might anyone have suggestions about what my next steps should be?

[Luke-Jr]

I'm having trouble building BFGminer on Angstrom (BeagleBone Black).

I started trying to build 2.10.11 because that was what was listed as "stable." When building I was told that I needed jansson. I build jansson fine and the whole ./configure, make, make install process appeared to go through with no trouble (Success!). Except that when I tried to run the executable:

bfgminer: error while loading shared libraries: libjansson.so.4: cannot open shared object file: No such file or directory

libjansson.so.4 is right in the same place (/usr/local/lib) it was when I ran make and make install. So, not sure what that's about.

Check that /usr/local/lib is listed in /etc/ld.so.conf and that you ran ldconfig after installing it (this is standard procedure for library installs)

At that point I figured that I ought to just try the 3.1.4 version. There configure reported:

checking whether HASH_ITER is declared... no
configure: error: Could not find HASH_ITER - please install uthash-dev 1.9.2+


Ok, so I went looking for uthash and here is where I'm probably handicapped by not being a C guy. (My first language was Fortran, then TCL, Rexx, and Perl, and now I write PHP because that's what they pay me to do). Anyway, the only uthash distribution out there says only this:

USAGE
============
The only file you need to use uthash in your own application is

    src/uthash.h

These bonus headers are also included:

    src/utlist.h
    src/utarray.h
    src/utstring.h

OK, header files. There are a number of them in the directory where I untarred the 3.1.4 distribution, and where I was trying to build bfgminer. So I tried copying uthash.h into the bfgminer distribution folder, but configure reported the same "Could not find HASH_ITER - please install uthash-dev 1.9.2+" message. I tried the same after copying the other three "bonus" header files in as well.

At this point it appears that I don't just need the uthash header files; I need the debian package uthash-dev. Which I don't have because I'm not running Debian.

Searching didn't yield any answers to these, so I'm a bit stuck and back to mining with cgminer. Might anyone have suggestions about what my next steps should be?

It won't look in the bfgminer directory for the uthash headers by default.
Try using: ./configure CFLAGS="-I$PWD"

[smscotten]

Check that /usr/local/lib is listed in /etc/ld.so.conf and that you ran ldconfig after installing it (this is standard procedure for library installs)

Arrgh. Yes, I did run ldconfig, but /etc/ld.so.conf is a zero-length file. That's troubling. And now fixed.

It won't look in the bfgminer directory for the uthash headers by default.
Try using: ./configure CFLAGS="-I$PWD"

Beauty. Thank you!

luckydog:~$ bfgminer -V
bfgminer 3.1.4
luckydog:~$

 

[smscotten]

Sorry to be a pest. One more thing.

# bfgminer -D -T -d? -S all
 [2013-08-05 15:27:43] setrlimit: Increased soft fd limit from 1024 to hard limit of 4096                   
 [2013-08-05 15:27:43] Timers: Using clock_gettime(CLOCK_MONOTONIC_RAW)                   
 [2013-08-05 15:27:43] Started bfgminer 3.1.4                   
 [2013-08-05 15:27:43] ft232r_scan: Found "FT232R USB UART" serial "A90ZF159"                   
 [2013-08-05 15:27:43] ft232r_scan: Found 1d6b:0002 - not a ft232r                   
 [2013-08-05 15:27:43] ft232r_scan: Found 1d6b:0002 - not a ft232r                   
 [2013-08-05 15:27:43] Not a ZTEX device 0403:6001                   
 [2013-08-05 15:27:43] Not a ZTEX device 1d6b:0002                   
 [2013-08-05 15:27:43] Not a ZTEX device 1d6b:0002                   
 [2013-08-05 15:27:43] Devices detected:                   
0 devices listed

A90ZF159 is a Lancelot FPGA. I've done 'modprobe ftdi_sio vendor=0x0403 product=0x6001' but I don't have any /dev/ttyusb*. bfgminer appears to be detecting the device but determining that it isn't something it can use.

I'm already chagrinned for finding one of my earlier questions in the README after you answered it (thank you for being so gracious) but I'm stumped again. Any ideas?

[Luke-Jr]

Sorry to be a pest. One more thing.

# bfgminer -D -T -d? -S all
 [2013-08-05 15:27:43] setrlimit: Increased soft fd limit from 1024 to hard limit of 4096                   
 [2013-08-05 15:27:43] Timers: Using clock_gettime(CLOCK_MONOTONIC_RAW)                   
 [2013-08-05 15:27:43] Started bfgminer 3.1.4                   
 [2013-08-05 15:27:43] ft232r_scan: Found "FT232R USB UART" serial "A90ZF159"                   
 [2013-08-05 15:27:43] ft232r_scan: Found 1d6b:0002 - not a ft232r                   
 [2013-08-05 15:27:43] ft232r_scan: Found 1d6b:0002 - not a ft232r                   
 [2013-08-05 15:27:43] Not a ZTEX device 0403:6001                   
 [2013-08-05 15:27:43] Not a ZTEX device 1d6b:0002                   
 [2013-08-05 15:27:43] Not a ZTEX device 1d6b:0002                   
 [2013-08-05 15:27:43] Devices detected:                   
0 devices listed

A90ZF159 is a Lancelot FPGA. I've done 'modprobe ftdi_sio vendor=0x0403 product=0x6001' but I don't have any /dev/ttyusb*. bfgminer appears to be detecting the device but determining that it isn't something it can use.

I'm already chagrinned for finding one of my earlier questions in the README after you answered it (thank you for being so gracious) but I'm stumped again. Any ideas?

Please paste output from

Code:

lsusb -vv
ls /dev/ttyUSB*

Also, be sure you haven't run cgminer, as that corrupts the drivers (re-plugging the device should fix it though).

[smscotten]

Sorry to be a pest. One more thing.

# bfgminer -D -T -d? -S all
 [2013-08-05 15:27:43] setrlimit: Increased soft fd limit from 1024 to hard limit of 4096                   
 [2013-08-05 15:27:43] Timers: Using clock_gettime(CLOCK_MONOTONIC_RAW)                   
 [2013-08-05 15:27:43] Started bfgminer 3.1.4                   
 [2013-08-05 15:27:43] ft232r_scan: Found "FT232R USB UART" serial "A90ZF159"                   
 [2013-08-05 15:27:43] ft232r_scan: Found 1d6b:0002 - not a ft232r                   
 [2013-08-05 15:27:43] ft232r_scan: Found 1d6b:0002 - not a ft232r                   
 [2013-08-05 15:27:43] Not a ZTEX device 0403:6001                   
 [2013-08-05 15:27:43] Not a ZTEX device 1d6b:0002                   
 [2013-08-05 15:27:43] Not a ZTEX device 1d6b:0002                   
 [2013-08-05 15:27:43] Devices detected:                   
0 devices listed

A90ZF159 is a Lancelot FPGA. I've done 'modprobe ftdi_sio vendor=0x0403 product=0x6001' but I don't have any /dev/ttyusb*. bfgminer appears to be detecting the device but determining that it isn't something it can use.

I'm already chagrinned for finding one of my earlier questions in the README after you answered it (thank you for being so gracious) but I'm stumped again. Any ideas?

Please paste output from

Code:

lsusb -vv
ls /dev/ttyUSB*

Also, be sure you haven't run cgminer, as that corrupts the drivers (re-plugging the device should fix it though).

Oh! i didn't know that I'd have to re-plug the device between running cgminer and running bfgminer. I've got cgminer running—of course I've stopped it before trying to run bfgminer (I'm not quite *that* thick!) but lets see.

I restarted the BBB and power-cycled the Lancelot. Here is the output:

luckydog:~$ lsusb -vv
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Seria
l (UART) IC
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6001 FT232 USB-Serial (UART) IC
  bcdDevice            6.00
  iManufacturer           1 FTDI
  iProduct                2 FT232R USB UART
  iSerial                 3 A90ZF159
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower               90mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 FT232R USB UART
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x1d6b Linux Foundation
  idProduct          0x0002 2.0 root hub
  bcdDevice            3.08
  iManufacturer           3
  iProduct                2
  iSerial                 1
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0004  1x 4 bytes
        bInterval              12

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x1d6b Linux Foundation
  idProduct          0x0002 2.0 root hub
  bcdDevice            3.08
  iManufacturer           3
  iProduct                2
  iSerial                 1
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0004  1x 4 bytes
        bInterval              12
luckydog:~$ ls /dev/ttyUSB*
/dev/ttyUSB0
luckydog:~$ bfgminer -D -T -d? -S all
 [2013-08-05 17:34:34] scan-serial: /dev glob all-adding /dev/ttyUSB0                   
 [2013-08-05 17:34:34] setrlimit: Increased soft fd limit from 1024 to hard limit of 4096                   
 [2013-08-05 17:34:34] Timers: Using clock_gettime(CLOCK_MONOTONIC_RAW)                   
 [2013-08-05 17:34:34] Started bfgminer 3.1.4                   
 [2013-08-05 17:34:35] ft232r_scan: Found "FT232R USB UART" serial "A90ZF159"                   
 [2013-08-05 17:34:35] ft232r_scan: Found 1d6b:0002 - not a ft232r                   
 [2013-08-05 17:34:35] ft232r_scan: Found 1d6b:0002 - not a ft232r                   
 [2013-08-05 17:34:35] Icarus Detect: Attempting to open /dev/ttyUSB0                   
 [2013-08-05 17:34:35] Icarus Read: No data in 0.10 seconds                   
 [2013-08-05 17:34:35] Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 000187a2                   
 [2013-08-05 17:34:35] BFL: Attempting to open /dev/ttyUSB0                   
 [2013-08-05 17:34:36] BFL: Error reading/timeout (ZGX)                   
 [2013-08-05 17:34:38] ModMiner detect: no response to version request from /dev/ttyUSB0                   
 [2013-08-05 17:34:38] Not a ZTEX device 0403:6001                   
 [2013-08-05 17:34:38] Not a ZTEX device 1d6b:0002                   
 [2013-08-05 17:34:38] Not a ZTEX device 1d6b:0002                   
 [2013-08-05 17:34:38] Devices detected:                   
0 devices listed
luckydog:~$
 

Well, this is at least different output to bfgminer -D -T -d? -S all than I was getting before. Maybe I'm almost all the way there.

Thank you!

[HellDiverUK]

Just posting to say I'm loving the new layout.  Seems a bit more stable with my Block Erupters, too (no manic hash rates).  Nice one.

Little donation sent to Luke-Jr.

[jml]

I can confirm that having the cm1 miners and BE within the same host (raspberry pi) causes the pi to hang requiring power cycling to reset the unit with bfgminer 3.14. I cannot ssh back to the pi after it has crashed requiring a power cycle to reboot.

 Would this problem be addressed on the next software version?

[mrrad]

I got my jalapeno hashing on bfgminer 3.1.4 with the host pc gpu disabled but the gpu temp. does not return to the normal idle temp. How can I take it completely out of the equation so it doesn't leech for want of a better word.. Obliviously I want to still have the gpu enabled on the pc to play games etc..  Thanks..................... I tried the bitminter client and the gpu is completely idle , before with the BFGminer I was using an extra 50 watts from the leeching gpu.........I'm sure there is a way around this.........

[bronan]

Anyone else all of a sudden start having their ESET or other virus program start flagging BFG?  Was alwasy good, never had a problem before (but cgminer would get picked up).  Now here within the last week or so ESET is flagging BFG.

IMO, "antivirus" software that takes the easy way out by flagging commonly abused software as more than merely a warning, is itself malware.
They should be looking for the virus/trojan itself, not the common software they use.

Sadly i found many other private clients from being infected by a bfgminer/cgminer/minerd instance
Hidden in a self starting proces called adobe, so it looks some botnet builders are using the miner to run them illegal

These unknowing customers have no clue that its not normal that their gpu is blazing like mad so they complain and ofcourse some specialist find that its caused by the secretly installed miners.

If this is done by people they know or by botnet owners or usage of illegal software i do not know.
Ofcourse some of them report their findings to the av companies, and to be honest even though its annoying they are right

But fact is that this causes all anti virus makers to flag the miners as nasty software.

[Luke-Jr]

Anyone else all of a sudden start having their ESET or other virus program start flagging BFG?  Was alwasy good, never had a problem before (but cgminer would get picked up).  Now here within the last week or so ESET is flagging BFG.

IMO, "antivirus" software that takes the easy way out by flagging commonly abused software as more than merely a warning, is itself malware.
They should be looking for the virus/trojan itself, not the common software they use.

Sadly i found many other private clients from being infected by a bfgminer/cgminer/minerd instance
Hidden in a self starting proces called adobe, so it looks some botnet builders are using the miner to run them illegal

These unknowing customers have no clue that its not normal that their gpu is blazing like mad so they complain and ofcourse some specialist find that its caused by the secretly installed miners.

If this is done by people they know or by botnet owners or usage of illegal software i do not know.
Ofcourse some of them report their findings to the av companies, and to be honest even though its annoying they are right

But fact is that this causes all anti virus makers to flag the miners as nasty software.

They aren't right. BFGMiner is not malware. The botnet is.
Flag that, not the legit software it's abusing.

[HellDiverUK]

Or use a decent AV program (not ESET).  I've never had an issue with Microsoft Security Essentials, and I've been using it since beta.

[Luke-Jr]

Since you have a Mini Rig SC, I was wondering if it has a built in router/Linux like Avalon or you connect the 8 long boards to an internal USB hub and then connect that hub to a PC?

It has a Nexus7 builtin, but you can plug the USB into a Windows system just fine.

Can one PC handle three mini rigs?

If it's powerful enough (which really isn't that much).

Thanks Luke.  I got it up and running with 3.1.4.  Disconnected Nexus 7 and hooked it up to an Anker hub.
Used the same SiLabs drivers as I used for Erupters

Well, that's not possible.. BFL devices use FTDI chips, not SiLabs
I'd guess it autoinstalled the driver.

1) API returns 128 PGA devices (~4GH/s each).  I guess that is each BFL asic chip.  Is this right?  I expected 8 devices ~60 GH/s each.
    Just like the ones displayed in the main window.

That's correct.
You can change the display to show all the processors too (D, M keystroke)

2) The hardware errors counts for each device might be incorrect. HW > Accepted

I'd guess you're mining at a difficulty higher than 1.
Use the % shown to see rate of bad nonces.

[2013-08-08 00:37:45] pool 2 JSON stratum auth failed: [
  20,
  "Unknown method",
  null

This looks like an incomplete response from a pool that doesn't support transparent/secure stratum.
Pretty normal, in that case, and shouldn't be displayed higher than debug mode...

[mdopro1]

This could be a silly question but how do I make my bfgminer screen bigger to accommodate for a few new added erupters?