[chirp_users] Dumb 8900 queary
Robert Terzi
Tue Jun 7 07:37:59 PDT 2011
As an FYI, from the dmesg info you provided:
The cable that got unplugged and plugged back in is /dev/ttyUSB1 and that's
looks like the one you should be using with chirp.
ttyUSB0, the first USB serial port that gets plugged in is getting used
by the Linux printing system CUPS. I don't know if you actually have
a serially attached printer or if CUPS is misconfigured to use that port.
You have two USB to serial adapters on your system, one made by FTDI
and the other a Prolific PL-2303. As others have mentioned the
name of the port is going to be dependent on the order they get plugged in
so play close attention to which is which and watch out for CUPS opening the
wrong one.
You might want to try shutting down cupsd when you are trying to
debug the radio connectivity.
Hope this helps,
--Rob
On 6/7/2011 10:25 AM, Alvin Koffman wrote:
> alvin at dittohead:~/POD/HDC$ ls /dev/ttyUSB*
> /dev/ttyUSB0 /dev/ttyUSB1
> alvin at dittohead:~/POD/HDC$ dmesg | grep ttyUSB
> [928137.560437] type=1503 audit(1306535091.695:33): operation="open" pid=5141 parent=5136 profile="/usr/sbin/cupsd" requested_mask="w::" denied_mask="w::" fsuid=0 ouid=0 name="/dev/ttyUSB0"
> [1639614.301890] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
> [1639614.750609] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB0
> [1639988.405981] type=1503 audit(1307246960.387:40): operation="open" pid=8690 parent=8685 profile="/usr/sbin/cupsd" requested_mask="w::" denied_mask="w::" fsuid=0 ouid=0 name="/dev/ttyUSB0"
> [1701142.174785] usb 3-2: pl2303 converter now attached to ttyUSB1
> [1844891.613682] pl2303 ttyUSB1: pl2303 converter now disconnected from ttyUSB1
> [1844912.295495] usb 5-2: pl2303 converter now attached to ttyUSB1
>
> And they still wont talk to eachother
> **Alvin Koffman
> *
>
> *If you like computer viruses stay with windows but If you want to be virus free try.*
>
> *http://www.puppylinux.com/*
>
>
>
>
>
> On Tue, Jun 7, 2011 at 9:53 AM, Mike Heitmann <n0so at att.net <mailto:n0so at att.net>> wrote:
>
> Hi Alvin,
>
> Forgive me if you know all of this already:
> Linux allocates and removes the ttyUSB devices "on the fly" as they are inserted or removed. It usually adds them, in order of insertion, as ttyUSB0, ttyUSB1, etc. regardless of which USB connector they are plugged into. At least that's been my experience with the Ubuntu and Fedora distributions. I find it's very easy to get the ttyUSBx devices mixed up if you have more than one, especially when troubleshooting a problem. An example, FWIW:
>
> If you:
> 1. You plug in a USB serial device. Linux adds it as ttyUSB0
> 2. You start an application (let's use chirp for this example).
> 3. Chirp sees the device as ttyUSB0 and opens it.
> 4. The device appears to get "hung" for one reason or another.
> 4. The USB adapter is unplugged, then reinserted.
> 5. Linux makes the same USB adapter be ttyUSB1 this time because Linux thinks ttyUSB0 is still in use as far as Linux knows.
>
> That's why I usually run:
> dmesg | grep ttyUSB
> when I remove or insert USB serial adapters to verify what ttyUSB device Linux thinks it is.
>
> Do this before you start chirp so you know you've selected the correct USB device. If you only have one USB serial adapter it should be the only ttyUSB device chirp lists in the selection menu.
>
> Happy testing!
> Mike, N0SO (using a real keyboard this time)
>
>
>
>
> --- On *Tue, 6/7/11, Alvin Koffman /<ka9qlq at gmail.com <mailto:ka9qlq at gmail.com>>/* wrote:
>
>
> From: Alvin Koffman <ka9qlq at gmail.com <mailto:ka9qlq at gmail.com>>
> Subject: Re: [chirp_users] Dumb 8900 queary
> To: "Discussion of CHIRP" <chirp_users at intrepid.danplanet.com <mailto:chirp_users at intrepid.danplanet.com>>
> Date: Tuesday, June 7, 2011, 4:06 AM
>
>
> *
> *
> On Mon, Jun 6, 2011 at 10:28 PM, Dan Smith <dsmith at danplanet.com <http://mc/compose?to=dsmith@danplanet.com>> wrote:
>
> > /dev/ttyUSB0 /dev/ttyUSB1
> > That's the 2 Ext HD partitions.
>
> No, those are USB-to-serial adapters.
>
> > I'll see if I can get someone to check (wiggle) the plugs
>
> They're clearly connected and identified by the OS. Have you tried
> CHIRP against both of them?
>
> Yup just did got an error on both
>
> > (I have 5% use of 1 hand)
>
> For what it's worth, all of the Icom radios are fully remotely
>
> Ya wish I had a 706mkiig buuuut,
>
> Hay thanks for all the emails. I'll try plugging it in the front usb jack tomorrow.
> Alvin
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com <http://mc/compose?to=chirp_users@intrepid.danplanet.com>
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com <mailto:chirp_users at intrepid.danplanet.com>
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
>
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
More information about the chirp_users
mailing list