New chipsets take time to be supported in *nix (and presumably libusb originates in *nix, translating to Windows).  It's unfortunate, but a reality.  That having been said, the easiest way to confirm a problem is a chipset vs libusb problem would be to try to run the cgminer binaries off of a live distro (presumably the same OS & version in use by the developers).  If cgminer doesn't detect the device there, it's definietly due to the version of libusb included with cgminer.  Also unfortunate, many other libusb versions cause mining problems as seen earlier in this thread, so even if the developer's OS of choice can detect the device on your machine, that doesn't mean cgminer can use it and be stable.  Presumably you would have to hack and compile on your own to be able to have cgminer use a newer libusb whilst not being stable.  Beyond that, all you can do in this scenario is hope that a future version of libusb comes out that is stable for mining, which also requires hoping the developers are trying new libusb versions.  However, the live distro test would at least allow you to know that so you don't waste additional time troubleshooting.

Was 3.1.1 the last version to support COM functionality?

Oh, and side note: mdude, your sig is out of date.

Unofficial Mac binaries updated to 3.4.3 at http://spaceman.ca/cgminer.

when using Zadig, do you select the winusb driver or one of the others?

Nothing, it's a normal part of the libusb check.

After having a similar issue (moving from 3.1.1 to 3.4.0) and cigminer not seeing devices, I formatted and reinstalled windows and installed the winusb driver only and the devices detected again.

Hello ck,
Hello Kano,

I've a question related to the identification of a device in cgminer and the a hardware device. As I'm currently about to develop a application that creates statistics for every device, it's essential to have a clear mapping between hardware device and the related device in cgminer for that. Previously I thought that the combination of the Device Type (GPU/BAS/AVA/....) and ID provided from cgminer could achieve that task, I had the hope it works as long the devices are connected to the same Port(USB/PCE...). Unfortunately I discovered that's not right. During the run of CGMiner I unplugged an Avalon from the USBPort and reconnected after a short time. After the reconnect the Id changed from AVA0 to AVA1. Now I'm questioning myself, how I can achieve the unique identification of a hardware device by reported data from CGMiner. I hope you can give me some advice!

Thany you very much in advance 

Avalon has no information in the device at all - I think that's something those guys like doing Icarus has nothing useful either.

Any device that has an iSerial that isn't constant would be one way to detect 2 devices being the same one that hotplugged later.

But with Avalon it's not possible - so if you unplug 2 and then plug them back in, there's no USB information to say which was which before.
The devices that don't have an iSerial, or have the same iSerial, are: AVA, AMU, BFL FPGA, MMQ
AsicMiner USBs can be reprogrammed to fix it
I've no idea what the ATI library supplies for GPUs but I'd guess nothing useful either.

These devices don't have this stupid problem: BFL SC, BLT, BTB

erm.. bump?

Running 3.4.3 but notice now (it seems this issue goes back a few versions) that the accepted blocks field now shows the latest difficulty (x number of blocks found it seems) instead of total block count? Anyone got a fix for this?



Heres another screnshot of cgminer with some weird ass numbers...