Hm, this doesn't look right.
It looks like you compiled usb support in. Did you happen to have the
keyspan device plugged in from a previous boot to windows? The firmware in
the device doesn't look right (the device id should NOT be 0104 BEFORE the
usb-serial driver is even loaded by the usb core.)
Try removing the device, and then plugging it in after Linux has booted
and the usb-serial driver is loaded. If you still have problems then, could
you sent me / the list the full system log (with debugging for usb-serial
turned on if you could) showing the enumeration cycle as the device is
plugged in?
Thanks,
greg k-h
[EMAIL PROTECTED]
On Tue, Apr 11, 2000 at 12:27:21PM -0500, Peter E. Berger wrote:
> Hi all:
>
> I'm new to USB and to this list. Thanks to all of you for your splendid
> work on this stuff! I've reviewed the mailing list archives but I still
> have a question.
>
> I'm trying to get a Keyspan USB PDA adapter working with my system (Intel
> box running 2.3.99pre4-5 and Greg Kroah-Hartman's usbserial patches from
> this weekend), but the usb-serial module Oops'es in keyspan_pda_startup().
>
> I did some investigation and see that the Oops stems from the fact that
> serial->port[0].read_urb is NULL when we call keyspan_pda_startup(),
> so the FILL_INT_URB trying to setup the receive interrupt urb fails.
> Looking back at the system messages file, I see that the USB subsystem
> finds only two endpoints on the Keyspan device: an "Interrupt in" and a
> "Bulk out". Shouldn't there also be a "Bulk in"? It looks like the
> code in "usb_serial_probe" depends on finding a "Bulk in" endpoint for
> setting up the serial structure that it passes to keyspan_pda_startup().
>
> Does it look like I have faulty hardware or do I need to do some more
> digging in the code to track down my problem? Thanks for any suggestions.
>
> --Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
