Would static linking a fixed libusb also work for producing a Raspian version?   I'm, umm, not particularly fond of the Arch distro...

As my build environment had to be rebuilt from scratch when I returned from overseas, I was missing some stuff which accidentally built the windows binary without GPU support. I've reuploaded a new binary which should work now.

No, no one could afford to pay me to do that.

I tried building the newest git version, and noticed that my linux scrypt miners no longer worked properly. Hashrates were minimal because intensity was only 8. cgminer was complaining about the config being broken, and after starting with -T I saw the error was "Invalid config option --intensity: Invalid value passed to set intensity". This was introduced in commit 2b171f7fae19a451abefd5189ecad64fbd08d8a0, everything still works fine with commit cb6d62de08995cb3ce2ae906dfa629f42d382c21. I'm using intensity 17 on the linux rigs, I don't have the problem on my Windows rigs with a lower intensity.

Nope, that didn't help. The windows rigs also have intensity set before scrypt in the config, and it works.

EDIT: --scrypt on the command line makes it works on linux too, though. So you seem to be on the right track. The intensity sanity check just doesn't detect that scrypt is being enabled from the config on linux.

Check all your peripherals , USB hub/s , USB cables , power supply etc . Its probably not the miner client. Try swapping out a USB cable or try just one erupter and see if u can get just one to mine at 335 Mh/s.

Cairnsmore1 (yeah. I know...):

I have hold off to upgrade to 3.x from 2.11.3, but today the temptation was too big ;-)

Upgrading etc. all went fine on Ubuntu 12.04.2, worked through the READMEs, did the libusb-1.0.16-rc10, disconnect USB, removed all --scan serial (ttyUSB*) from config file, restart everything, reconnect USB, did NOT issue the modprobe command...

Out of the 6x CM1s, cgminer only detects CMR0, 1 and 2. I let them run for a while with no problems, but of course I'm missing the rest of the boards.

Anyone tried the latest version with CM1s? Any other pointers?

Well, in my SW development practice this is called a "regression" as it broke prior existing behaviour. Good enough reason for me to call it a bug.

Exactly. It's actually impossible now to specify all scrypt settings using solely the config file, since the intensity sanity check doesn't detect "scrypt" : true from the config file.

OK, fine,  I'm just expressing my opinion a bit and attempting to apply common sense.

It would just seem to make sense to me to tell the the mining software what type of mining I want it to do before telling it how I want it to mine that specific coin.

The previous posters remark about regression is very valid too, it seems to me.
Later,
Sam