Hello,

  I'm having trouble using a second Keyspan USA49W USB->serial port box.
The problem is, the first one works flawlessly (we've been using it for
months) and the second one is seen by the driver and initialized OK (or
so it seems).  The kernel sees it and assigns its ports to
ttyUSB04 - ttyUSB07.  I created device files to match up to these
new ports and can even verify that the device is visible through them.

  For instance, 'echo > /dev/ttyUSB04' exits cleanly when the second
box is plugged in, but returns 'No such device' if you do it with the
second box unplugged.

  Trying to access one of the ports in minicom causes it (minicom) to
just hang.

  The related dmesg output is below.

  I saw an earlier post from 2001 where someone was having this same
problem but no indication he got it resolved.

  Any help would be appreciated.

Thanks,
Cengiz

------
usb.c: USB disconnect on device 5
usbserial.c: Keyspan USA49W converter now disconnected from ttyUSB0
usbserial.c: Keyspan USA49W converter now disconnected from ttyUSB1
usbserial.c: Keyspan USA49W converter now disconnected from ttyUSB2
usbserial.c: Keyspan USA49W converter now disconnected from ttyUSB3
hub.c: USB new device connect on bus1/1, assigned device number 6
usb.c: USB new device connect, assigned device number 6
hub.c: USB hub found
hub.c: 4 ports detected
hub.c: USB new device connect on bus1/1/1, assigned device number 7
usb.c: USB new device connect, assigned device number 7
usbserial.c: Keyspan USA49W - (without firmware) converter detected
usb.c: USB device 7 (vend/prod 0x6cd/0x109) is not claimed by any active
driver.
usb.c: USB disconnect on device 7
hub.c: USB new device connect on bus1/1/1, assigned device number 8
usb.c: USB new device connect, assigned device number 8
usbserial.c: Keyspan USA49W converter detected
usbserial.c: Keyspan USA49W converter now attached to ttyUSB0 (or
usb/tts/0 for devfs)
usbserial.c: Keyspan USA49W converter now attached to ttyUSB1 (or
usb/tts/1 for devfs)
usbserial.c: Keyspan USA49W converter now attached to ttyUSB2 (or
usb/tts/2 for devfs)
usbserial.c: Keyspan USA49W converter now attached to ttyUSB3 (or
usb/tts/3 for devfs)
hub.c: USB new device connect on bus1/1/3, assigned device number 9
usb.c: USB new device connect, assigned device number 9
usbserial.c: Keyspan USA49W - (without firmware) converter detected
usb.c: USB device 9 (vend/prod 0x6cd/0x109) is not claimed by any active
driver.
usb.c: USB disconnect on device 9
hub.c: USB new device connect on bus1/1/3, assigned device number 10
usb.c: USB new device connect, assigned device number 10
usbserial.c: Keyspan USA49W converter detected
usbserial.c: Keyspan USA49W converter now attached to ttyUSB4 (or
usb/tts/4 for devfs)
usbserial.c: Keyspan USA49W converter now attached to ttyUSB5 (or
usb/tts/5 for devfs)
usbserial.c: Keyspan USA49W converter now attached to ttyUSB6 (or
usb/tts/6 for devfs)
usbserial.c: Keyspan USA49W converter now attached to ttyUSB7 (or
usb/tts/7 for devfs)





-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to