Quote from: SnitraM on May 27, 2013, 02:40:53 PM

Quote from: kano on May 25, 2013, 12:13:34 AM

However, if your CMR is FT232H product=0x6014 (gingernuts is product=0x8350) it would be good to provide 2 things:
usbmon (or direct access to it via /sys or /proc or /dev or wherever your Linux OS puts it - yes it must be Linux)
output of plugging it in and also running the usbtest.py that comes with cgminer current git like:
./usbtest.py /dev/ttyUSB? icarus (whatever the USB? is)
and make sure it gave the right answers (or rerun it)
and lsusb -v of the device
If it actually creates multiple /dev/ttyUSB? you'll need to run that whole process on each of them (from plug in to usbtest.py)

Is it important for your tests to have product=0x6014 or product=0x8350? I don't know which one I have
but my Cairnsmores are early ones, from summer 2012.

sudo lsusb will tell you.
as will cgminer --usb-list-all -n (note that the parameter order there does matter)
On linux the above two look like:

Code:

Bus 002 Device 008: ID 0403:6014 Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC

and

Code:

.USB dev 0: Bus 2 Device 8 ID: 0403:6014
Manufacturer: 'Butterfly Labs'
Product: 'BitFORCE SHA256 SC'

The ID numbers are what I'm referring to

The 0x6014 is what I don't have the full details for yet for Cairnsmore1 but I presume it will be the same as BFL but with a different baud rate.