On Wed, May 28, 2003 at 02:22:55PM -0700, Samuel Flory wrote: > Greg KH wrote: > > >On Fri, May 23, 2003 at 10:08:07AM -0700, Samuel Flory wrote: > > > > > >> > >> > >>Under 2.5.69-bk6 the kernel sees both the keyspan, and iogear > >>(PL-2303) and assigns ttyUSB. Minicom will open the port, but I don't > >>see anything in response to my key strokes. > >> > >> > > > >Is the flow control and other line settings set up properly in minicom > >for you? The data should be flowing. You can load the drivers with > >"debug=1" to see the data in the kernel debug log if you have any > >questions about that. > > > > > > > > It appears that I can recieve fine. If I `echo "Can you see" > >/dev/ttyS1 on the system that I'm connected to. I can see this in > minicom. It seems to be sending stuff out that is the issue.
Don't use echo or cat to test usb-serial drivers. They are known to not work properly. Stick with using minicom on both ends (send and receive) and you should be fine. > I seem to be getting a lot of the following in dmesg: > > drivers/usb/serial/usb-serial.c: serial_write - port 0, 1 byte(s) > drivers/usb/serial/keyspan.c: keyspan_write - for port 0 (1 chars), flip=1 > drivers/usb/serial/keyspan.c: keyspan_write - endpoint 2 flip 1 > drivers/usb/serial/keyspan.c: usb_submit_urb(write bulk) failed (-19) Are you sure you are trying to write to a USB device that is still present in the system? That error (-ENODEV) would indicate otherwise... thanks, greg k-h ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
