-------- Original Message --------
Subject: Re: [chirp_users] Cable Problem
From: Robert Terzi <rct@r-t.org>
Date: Mon, December 31, 2012 4:08 pm
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>

modprobe ftdi_sio vendor=0x403 product=0x6001

On 12/31/2012 2:59 PM, John Westerlage wrote:
[...]
> My cable is produced by RT Systems,
[...]
> The cable is not seen by CHIRP booted from the Live CD burnt from
> the download on 2012-12-27
>
> Nor is it seen by Kubuntu 8.04.1 (Hardy Heron, kernel 2.6.24-19).
[...]
> Doing a 'sudo lsusb -v' yields, among other stuff, this relevant info:
>
> Bus 002 Device 003: ID 0403:9e51 Future Technology Devices International, Ltd

Probably the USB Product ID isn't being matched to the FTDI driver under Linux.
RT Systems uses custom IDs for their cables.

Try unplugging the cable (and all FTDI based cables), then as root or using sudo bash try:

# make sure ftdi serial driver isn't loaded.
rmmod ftdi_sio

# (temporarily) associate your cable's USB Vendor and Product ID with the FTDI driver
modprobe ftdi_sio vendor=0x403 product=0x9e51

Then take a look at the logs and see if you got a USB serial driver created.

dmesg | tail -50

You should hopefully see something like:

usb 4-2: Detected FT2232C
...
usb 4-2: FTDI USB Serial Device converter now attached to ttyUSB0

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users