Ok, I've figured out how to reproduce the problem.
Initially, usbcore and usb-uhci are the only USB drivers loaded. If I
load usbserial and keyspan seperately ("modprobe usbserial ; sleep 5 ;
modprobe keyspan") everything works correctly. The problem occurs when
I let modprobe pull in usbserial behind the scenes as a dependency. The
keyspan driver (usually) doesn't detect the device, and /proc/modules
forever lists it as "initializing". The module won't unload at this
point, so the driver's unusable until the next reboot.
Unfortunately I have no idea how/where to fix this. Anyone want to
take a stab at it?
On Sat, Jun 30, 2001 at 01:37:52PM -0500, Gregory T. Norris wrote:
> It seems to be working now, although I'm not really sure what fixed
> it... my kernel configuration is essentially unchanged. I'm suspicious
> that the adapter might have a bad connection, or something similar.
>
> Cheers!
>
> On Sat, Jun 30, 2001 at 12:33:23AM -0500, Gregory T. Norris wrote:
> > I'm trying to use a Keyspan USA-19 to enable access to a Palm m500 on a
> > serial cradle. Whenever I try to modprobe the keyspan module I get the
> > message "Warning: /lib/modules/2.4.5/kernel/drivers/usb/serial/usbserial.o
> > symbol for parameter vendor not found"... the module loads anyway, but
> > doesn't seem to detect the device.
> >
> > As far as I can see, everything seems to be setup correctly (.config
> > attached). Pointers and suggestions would be greatly appreciated.
> > Thanx!
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-users
