On Sat, Jun 10, 2000 at 10:17:33AM -0500, Steven Headley wrote:
> With modprobe of usb-serial I still get the following message in the logs:
>
> Jun 10 09:38:43 Headley kernel: usb.c: USB new device connect, assigned device n
> umber 2
> Jun 10 09:38:43 Headley kernel: Manufacturer: Handspring Inc
> Jun 10 09:38:43 Headley kernel: Product: Handspring Visor
> Jun 10 09:38:43 Headley kernel: usb.c: This device is not recognized by any inst
> alled USB driver.
> Jun 10 09:38:43 Headley kernel: Length = 18
> Jun 10 09:38:43 Headley kernel: DescriptorType = 01
> Jun 10 09:38:43 Headley kernel: USB version = 1.00
> Jun 10 09:38:43 Headley kernel: Vendor:Product = 082d:0100
> Jun 10 09:38:43 Headley kernel: MaxPacketSize0 = 16
> Jun 10 09:38:43 Headley kernel: NumConfigurations = 1
> Jun 10 09:38:43 Headley kernel: Device version = 1.00
> Jun 10 09:38:43 Headley kernel: Device Class:SubClass:Protocol = 00:00:00
> Jun 10 09:38:43 Headley kernel: Per-interface classes
>
> but the pilot-xfer /dev/visor -l gives me:
> Unable to bind to port '/dev/visor'.
> (Please see 'man pilot-xfer' or 'pilot-xfer --help' for information on setting the
> port).
>
> How does one check the port to see if it is configurad correctly?
The usb-serial module needs to be loaded before pressing the hot-sync
button on the Visor (actually I think some people have gotten around this,
but I don't recommend it yet.)
It does not look like the usb-serial module is loaded. Try that, and make
sure you have created the device nodes and the symlink (as it looks like
you want to do it that way) before trying to sync the Visor.
Let me / us know if you still have problems.
greg k-h
greg@(kroah|wirex).com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
