And you might give a try stepping through the USB ports one at a time as an icarus worker.

Though I doubt that is the problem of the moment since you are getting a failure to open port.
Not some sort of 'unexpected reply'.

And the python --version:

Python 2.7.3

Well that looks effectively the same as mine.

My BFL Single is on another machine ATM doing some testing, so 0 - 7 is both my CM1's.

AH, here's a thought, with my flash each FPGA chip gets its own comm line / USB port. But, IIRC, with the standard flash things are substantially different.

Have you tried stepping through one at a time?

I.e., try only one worker at /dev/ttyUSB0 .
If no joy, delete that worker and try /dev/ttyUSB1 .
etc.

Also, are you creating icarus workers or cairnsmore in mpbm?

-- edit

Got the image. Looks as I would expect.

Here is my "uname -a" output:
Linux xxxxx 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux

In my last post I have an alias for ll='ls -la', if that wasn't obvious.

If you put a screen cap in your last post, I'm not seeing it.

In the "Worker editor" you are supplying the "Port:" as "/dev/ttyUSB1", etc.?

-- edit

Also, I'm sure you remembered to stop any executing instances of cgminer or bfgminer which were previously running.

-- edit

And let's double check those permissions down in /dev

xx@xxxx ~ $ ll /dev/ttyUSB*
crw-rw---T 1 root dialout 188, 0 Jun  4 23:49 /dev/ttyUSB0
crw-rw---T 1 root dialout 188, 1 Jun  4 23:49 /dev/ttyUSB1
crw-rw---T 1 root dialout 188, 2 Jun  4 23:49 /dev/ttyUSB2
crw-rw---T 1 root dialout 188, 3 Jun  4 23:49 /dev/ttyUSB3
crw-rw---T 1 root dialout 188, 4 Jun  4 23:49 /dev/ttyUSB4
crw-rw---T 1 root dialout 188, 5 Jun  4 23:49 /dev/ttyUSB5
crw-rw---T 1 root dialout 188, 6 Jun  4 23:49 /dev/ttyUSB6
crw-rw---T 1 root dialout 188, 7 Jun  4 23:50 /dev/ttyUSB7

Well now you've gone past where I can be helpful since I'm using neither cgminer nor bfgminer.

You'll need to start searching to find more info about those specifically.   

Lots of people have been having problems with cgminer 3.2.x. Hope you're using something slightly older than that.

--

I'm using Modular Python Bitcoin Miner (MPBM) since I found it does better with the dynamic clocking flash on the CM1's than bfgminer did. I also have a BFL FPGA hooked up in the mix driven with MPBM.

BUT, since you don't have the dynamic clock flash on your CM1, I assume - they don't ship that way, you will probably get slightly better performance with cgminer or bfgminer.

[edit] Looks like you're making good progress then.

The CM1 still doesn't get an assigned /dev/ttyUSBxx   ?

Does it show up with an "lsusb" command?

And I'm not sure from your statement above, but do you have the CM1 plugged into the USB before the modprobe and "echo ..." commands are issued?

In my /etc/rc.local file I have this:

/sbin/modprobe ftdi_sio vendor=0x0403 product=0x8350
sleep 1
echo "0403 8350" > /sys/bus/usb-serial/drivers/ftdi_sio/new_id
sleep 1

-- edit

And you'll also need to add the user whose account you run the miner application under to the "dialout" group.

You didn't hit that road block yet, but you were probably gonna soon. 

Uh, NOT. 

scorch  (skôrch)
1. To burn superficially so as to discolor or damage the texture of. See Synonyms at burn1.
2. To wither or parch with intense heat.
3. To destroy (land and buildings) by or as if by fire so as to leave nothing salvageable to an enemy army.

Yep, life is hard.

Suck it up and deal with it.   

Then tell me what you're doing that's special. 

Is this thing fully self contained?

Or do you have to install either cgminer or bflminer also?

Anybody running BE USB devices *and* Cairnsmore CM1s on Raspbian and MPBM.

That combination crashes the machine when I tried it.

I can report the same thing. On OS X.

Initially tried it on Raspbian where I have a BFL FPGA and a couple of CM1s. But it *seems* like the combination of BE USB and CM1 causes a catastrophic failure with MPBM on Raspbian.

"Catastrophic" as in mining stops, ssh stops and the machine no longer responds to a ping. Sadly, no residue which I can find left in any log, either.

Currently MPBM on Raspbian is running two CM1s and MPBM on OS X is running a BFL Single (FPGA) and a BE USB.

Oh, but there might well be other issues.

For example, I can't get the stratum proxy to work with BitParking. But it works fine for me with BitMinter and BTCGuild.

Then thanks for updating my info on the blade's built-in capabilities.

My apologies for being a distraction / having wrong info.

So are you saying that "macminer" by itself is all that's needed?

IOWs, there is no need to also install either cgminer or bflminer?

What is the range of hw errors as a percent of accepted shares that you're getting, please?

On my working one it is running at about 0.9%. (IIRC, several other folks have reported getting about a 1% hw error rate.)

One which is now dead and in the process of getting replaced ran at about 10% hw errors for roughly eight hours. Then it died.

NOTE: I had a fan blowing over them. They were both 'warm to the touch'. Not the 'freaking hot' you encounter without active cooling.

IIRC, the blades do not directly support stratum and you must point it to a proxy in order to use stratum pool connections.

What is the range of hw errors as a percent of accepted shares that you're getting, please?

On my working one it is running at about 0.9%. (IIRC, several other folks have reported getting about a 1% hw error rate.)

One which is now dead and in the process of getting replaced ran at about 10% hw errors for roughly eight hours. Then it died.

-- edit

NOTE: I had a fan blowing over them. They were both 'warm to the touch'. Not the 'freaking hot' you encounter without active cooling.

I'm getting dead even with what I expect over the last 24hrs.