USB serial converter to RS232- HELP Please.

Hi All.

I am using Linux Kernel 2.6.5-7.108-default on i686 athlon and everything
except USB serial devices work fine. I have a USB2.0 hub and another 4 USB
ports off the motherboard (A7N8X Asus) with 1GB of RAM and 1 x Raid 5
controller(380GB), 1 x Raid 0 controller(500GB), 1 x USB HDA 250GB, 1 x
firewire DVD 2 layer writer, plus numerous Stick and Flash Cards controllers
off the USB.

The two USB serial devices are:

USB-Serial Controller
Manufacturer: Prolific Technology Inc.
Speed: 12Mb/s (full)
USB Version:Â*Â*1.10
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 0557
Product Id: 2008
Revision Number:Â*Â*3.00

and

usbserial
Speed: 12Mb/s (full)
USB Version:Â*Â*1.10
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 8
Number of Configurations: 1
Vendor Id: 067b
Product Id: 2303
Revision Number:Â*Â*2.02

Enclosed in the attachment are:
lsusb, lsmod|grep usb, ls -l /dev/usb/ttyUSB[0,1], cat /proc/devices
cat /proc/interrupts, cat /proc/tty/drivers, lspci, cat ioports,
and finally ls -l /sys/bus/usb-serial/drivers/PL-2303/.

You can see that the USB serial I/O is registered, seen and no
reason not to work. BUT I cannot get any normal tty I/O program
to talk, e.g: Minicom (its says device no available) and setserial
which just return back to the CLI prompt without any indication
of knowing, seeing or acknowledging ttyUSB ports.

I need help please. I need a extra serial port to program/debug
embedded controllers and this is my only option. In particular I need
to know what device (/dev/usb/tyUSB0 || /dev/ttyUSB0 || whatever device)
the driver expects to communicate with.

All assistance greatly appreciated.
Cheers. Grahame
(grahame AT wildpossum DOT com)

Grahame <(E-Mail Removed)> wrote:

> I am using Linux Kernel 2.6.5-7.108-default on i686 athlon and
> everything except USB serial devices work fine. I have a USB2.0 hub
> and another 4 USB ports off the motherboard (A7N8X Asus) with 1GB of
> RAM and 1 x Raid 5 controller(380GB), 1 x Raid 0 controller(500GB),
> 1 x USB HDA 250GB, 1 x firewire DVD 2 layer writer, plus numerous
> Stick and Flash Cards controllers off the USB.

> The two USB serial devices are:

> USB-Serial Controller
> Manufacturer: Prolific Technology Inc.
> Speed: 12Mb/s (full)
> USB Version:Â*Â*1.10
> Device Class: 00(>ifc )
> Device Subclass: 00
> Device Protocol: 00
> Maximum Default Endpoint Size: 64
> Number of Configurations: 1
> Vendor Id: 0557
> Product Id: 2008
> Revision Number:Â*Â*3.00

> and

> usbserial
> Speed: 12Mb/s (full)
> USB Version:Â*Â*1.10
> Device Class: 00(>ifc )
> Device Subclass: 00
> Device Protocol: 00
> Maximum Default Endpoint Size: 8
> Number of Configurations: 1
> Vendor Id: 067b
> Product Id: 2303
> Revision Number:Â*Â*2.02

> Enclosed in the attachment are:
> lsusb, lsmod|grep usb, ls -l /dev/usb/ttyUSB[0,1], cat /proc/devices
> cat /proc/interrupts, cat /proc/tty/drivers, lspci, cat ioports,
> and finally ls -l /sys/bus/usb-serial/drivers/PL-2303/.

> You can see that the USB serial I/O is registered, seen and no
> reason not to work. BUT I cannot get any normal tty I/O program
> to talk, e.g: Minicom (its says device no available) and setserial
> which just return back to the CLI prompt without any indication
> of knowing, seeing or acknowledging ttyUSB ports.

> I need help please. I need a extra serial port to program/debug
> embedded controllers and this is my only option. In particular I need
> to know what device (/dev/usb/tyUSB0 || /dev/ttyUSB0 || whatever device)
> the driver expects to communicate with.

....

> glider:/ # cat /proc/tty/drivers
> /dev/tty /dev/tty 5 0 system:/dev/tty
> /dev/console /dev/console 5 1 system:console
> /dev/ptmx /dev/ptmx 5 2 system
> /dev/vc/0 /dev/vc/0 4 0 system:vtmaster
> usbserial /dev/ttyUSB 188 0-254 serial <-----------------
> serial /dev/ttyS 4 64-111 serial
> pty_slave /dev/pts 136 0-1048575 pty:slave
> pty_master /dev/ptm 128 0-1048575 pty:master
> pty_slave /dev/ttyp 3 0-255 pty:slave
> pty_master /dev/pty 2 0-255 pty:master
> unknown /dev/tty 4 1-63 console

Given that I know zip about USB-to-serial connections, I'd guess
that you need to use /dev/ttyUSB0 and, judging from the dates
on the "ls -l /dev/usb/ttyUSB[0,1]" output, have been trying to
use /dev/usb/ttyUSB0.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* 97.3% of all statistics are made up. */

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.networking Grahame <(E-Mail Removed)> suggested:
> [-- text/plain, encoding 8bit, charset: utf-8, 58 lines --]

> Hi All.

> I am using Linux Kernel 2.6.5-7.108-default on i686 athlon and everything
> except USB serial devices work fine. I have a USB2.0 hub and another 4 USB

Had some trouble and some devices not working at all with kernel
2.6, until 2.6.7-bk15, which had some cleanups for USB, I'd try
updating at first.

Good luck

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBXeFrAkPEju3Se5QRAnPXAJ4ieL/1k+eM9J7/8kcqcmOgzXH63ACfdFlN
t6AGNWI1ZbaDhJN8AclG7Bo=
=+8ad
-----END PGP SIGNATURE-----