USB to serial converter, detected but not there - huh?
I am trying to get a USB to Serial converter working with my Slackware system. When I plug the converter into a USB port it works exactly as one would expect and hope, in /var/log/messages I see:- Aug 6 15:34:16 home kernel: usb 3-2: new full speed USB device using uhci_hcd and address 2 Aug 6 15:34:16 home kernel: usb 3-2: configuration #1 chosen from 1 choice Aug 6 15:34:16 home kernel: usbcore: registered new driver usbserial Aug 6 15:34:16 home kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic Aug 6 15:34:16 home kernel: usbcore: registered new driver usbserial_generic Aug 6 15:34:16 home kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core Aug 6 15:34:16 home kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303 Aug 6 15:34:16 home kernel: pl2303 3-2:1.0: pl2303 converter detected Aug 6 15:34:16 home kernel: usb 3-2: pl2303 converter now attached to ttyUSB0 Aug 6 15:34:16 home kernel: usbcore: registered new driver pl2303 Aug 6 15:34:16 home kernel: drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver if I unplug it and plug it back in I see:- Aug 6 15:53:18 home kernel: usb 3-2: USB disconnect, address 2 Aug 6 15:53:18 home kernel: pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 Aug 6 15:53:18 home kernel: pl2303 3-2:1.0: device disconnected Aug 6 15:53:41 home kernel: usb 3-2: new full speed USB device using uhci_hcd and address 3 Aug 6 15:53:41 home kernel: usb 3-2: configuration #1 chosen from 1 choice Aug 6 15:53:41 home kernel: pl2303 3-2:1.0: pl2303 converter detected Aug 6 15:53:41 home kernel: usb 3-2: pl2303 converter now attached to ttyUSB0 The only (?!) problem is that I don't actually get a /dev/ttyUSB0, so what's wrong and/or how can I diagnose it? -- Chris Green
Hi Chris, On 8/6/07, Chris G <cl@isbd.net> wrote:
The only (?!) problem is that I don't actually get a /dev/ttyUSB0, so what's wrong and/or how can I diagnose it?
This is probably some udev issue with not creating the device node. I had to create a device node manually. Off the top of my head, that device is major 188 and minor 0 (check /proc/devices for the major number). So just create the device node and things would work. Srdjan
On Mon, Aug 06, 2007 at 04:04:28PM +0100, Srdjan Todorovic wrote:
Hi Chris,
On 8/6/07, Chris G <cl@isbd.net> wrote:
The only (?!) problem is that I don't actually get a /dev/ttyUSB0, so what's wrong and/or how can I diagnose it?
This is probably some udev issue with not creating the device node. I had to create a device node manually. Off the top of my head, that device is major 188 and minor 0 (check /proc/devices for the major number).
So just create the device node and things would work.
.... as in 'mknod /dev/ttyUSB0 c 188 0' ? I have done that and now have a /dev/ttyUSB0 but it doesn't appear to work still. When the USB-Serial adapter is plugged in what *does* appear in /dev are the following:- crw-rw---- 1 root root 189, 259 2007-08-06 16:20 usbdev3.4 crw-rw---- 1 root root 442, 4099 2007-08-06 16:20 usbdev3.4_ep00 crw-rw---- 1 root root 442, 4099 2007-08-06 16:20 usbdev3.4_ep02 crw-rw---- 1 root root 442, 4099 2007-08-06 16:20 usbdev3.4_ep81 crw-rw---- 1 root root 442, 4099 2007-08-06 16:20 usbdev3.4_ep83 -- Chris Green
On Mon, Aug 06, 2007 at 04:31:34PM +0100, Chris G wrote:
On Mon, Aug 06, 2007 at 04:04:28PM +0100, Srdjan Todorovic wrote:
Hi Chris,
On 8/6/07, Chris G <cl@isbd.net> wrote:
The only (?!) problem is that I don't actually get a /dev/ttyUSB0, so what's wrong and/or how can I diagnose it?
This is probably some udev issue with not creating the device node. I had to create a device node manually. Off the top of my head, that device is major 188 and minor 0 (check /proc/devices for the major number).
So just create the device node and things would work.
.... as in 'mknod /dev/ttyUSB0 c 188 0' ?
I have done that and now have a /dev/ttyUSB0 but it doesn't appear to work still.
... silly me, I needed to set the permissions so that the jPilot software could write to /dev/ttyUSB0, all works fine now. Thanks for the help Srdjan. -- Chris Green
participants (2)
-
Chris G -
Srdjan Todorovic