Yes I saw that thanks, it was about the BBB dhcp implementation. Didn't help me.

Think I should be satisfied that it's mining at all and leave it, but the hardware's too new to stop developing for it just yet 

Yep, didn't make a difference.

Calm down folks. I just posted it to let people know it happens even to developers, and have read what people suggested, but none of those fixed my particular issue. Every time I try one of those fixes things seem to just get a little worse so I'm afraid to touch it now...

I got an attack of the network lags after upgrading to 0.99 

Downgrading didn't help, powering down, restarting and rebooting didn't help. Even with cgminer not running ping times can take up to 2 seconds. SSH'ing in is excruciatingly slow. One time I couldn't even ssh in until I restarted it again. I just barely got it mining again. I saw others had gremlins that went away, but I can't seem to find any way to repair it.

USB 3 drivers on windows are inconsistent and have conflicts with the usb1.1 devices (like BEs) and the libusb library we use to talk to them. USB2 slots are infinitely more compatible (or use linux).

About 858,000,000,000

Based on your config file info, you seem to be running that binary on an RPi? The KnC devices come with a beaglebone built in, so what is this combination? Have you built a custom one plugging the GPIO pins of an RPi to the KnC hardware? There's an awful lot more to running those devices than just cgminer, if I'm not mistaken. The firmware does a lot more than just run cgminer on a beaglebone.

At least the claims don't sound unreasonable. They only have modest targets in mind.

Not really, 100GH is a trivial amount these days...

New version of cgminer out, 3.8.3 with minor improvements for these devices.

New release: Version 3.8.3, 23rd November 2013

Minor driver update and bugfixes.

Human readable changelog:

- Average hashrate shown for BF1 and BXF devices will now rise quickly on startup.
- The bi*fury device in its release form had different firmware from my development one so the driver has been updated to work with it.
- Fixed the bxf device to align in the display column if temperature went above 100 degrees.
- Don't keep displaying json auth failed on stratum pools that are misbehaving except at verbose logging level.
- Very small improvement in hardware error rate on some USB devices due to the way return messages are handled.
- Fix a memory leak when json is used to communicate with the RPC API
- Avalon improvements to fix the sudden drops in hashrate (these fixes are all already in the last avalon firmware I uploaded).
- Unlimited re-hotplugging of devices that have USB failures and turn into zombies but have had their USB reset by the operating system.


Full changelog:

- Set the bitfury device start times from when we first get valid work.
- Fix stack corruption of zeroing too much in bf1 driver.
- Make usb_detect return the cgpu associated with it to check if it succeeds to
decide on whether to increment the device count or not.
- Set tv work start time for bxf driver.
- Age the bxf work items over 90 seconds, not the bf1 work items.
- Zero the read buffer in _usb_read to avoid stale data and only use stack
memory instead of using the bulkbuf since it is only used in _usb_read.
- Leave room for temperatures above 100 degrees and pad consistently for bxf
statline.
- Drop json stratum auth failed message log level to verbose.
- Change the processed value not the bufsiz in response to an end of message
marker.
- Don't lose data beyond the end of message in a usb read.
- Silence irrelevant warning.
- Only check strlen on end if end exists.
- Simplify the end of message detection in _usb_read and allow it to return
without doing another read if the message is already in the buffer.
- Increase work ageing time to 90 seconds for bxf driver to account for firmware
changes.
- Use the age_queued_work function in the bitfury driver.
- Provide a function to discard queued work based on age.
- The json_val in api.c is a borrowed reference, not a new one so don't decref
it.
- Decrement json references in api.c to not leak memory.
- line 2913 added urlencode
- With reliable writes to the avalon there is no need for the sleep delays
between writes.
- There is no need to limit usb write transfers to maxpacketsize and it's
harmful for large transfers on slow devices such as wrt routers.
- Disable USB stats which were not meant to be enabled by default and add extra
memory for a memory error when stats are enabled.
- Set limit and count to integers to not overflow during failed hotplug attempts
and then not trying again.
- Update api example compilation instructions.

3.7.2, and it had red/blue fury support though not sure if the performance was down on that version.

You don't have any hardware for cgminer to mine with. It is no longer a cpu or gpu miner.

I'm not primarily a miner, I write mining software and it's in my interest to have more miners so I have no vested interest in having less people mining and keep trying to warn people not to waste their money.

No, the mining for profit era is over for the foreseeable future. Buy a few bitcoin instead if you wish to take the risk that it will keep rising.

I promised I'd keep you posted, and it's time for an update.

Nothing's happened.

Not sure where it went to then.

As promised, I'll keep you all posted.

Current cgminer has no GPU mining code so it will only mine on devices you consciously set up by associating the WinUSB driver with them.

Horse shit.

AMUs use a different driver (no idea what it's called on macosx), so if you have installed a driver for it, you will probably need to use the kextunload command but specify a different driver to unload than the AppleUSBCDC which is used by the BF1.

Virus checker, disable it