Hi Steven,
        Did the modprobe succeed? There doesn't seem to be anything
indicating it did. What are the contents of /proc/bus/usb/drivers now?

On Sat, 10 Jun 2000, 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?
> 
> 
> 
> David Brownell wrote:
> 
> > so did you modprobe usb-serial? you're building the serial
> > support into that module, you need it loaded ...
> >
> > ----- Original Message -----
> > From: "Steven Headley" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Cc: <[EMAIL PROTECTED]>
> > Sent: Saturday, 10 June, 2000 6:38 AM
> > Subject: Re: [linux-usb] help with setting up Visor
> >
> > > Still no luck. Here is my .config file:
> > >
> > > #
> > > # USB support
> > > #
> > > CONFIG_USB=y
> > > CONFIG_USB_DEBUG=y
> > >
> > > #
> > > # Miscellaneous USB options
> > > #
> > > CONFIG_USB_DEVICEFS=y
> > >
> > > #
> > > # USB Controllers
> > > #
> > > CONFIG_USB_UHCI=m
> > > CONFIG_USB_UHCI_ALT=m
> > > CONFIG_USB_OHCI=m
> > >
> > > #
> > > # USB Devices
> > > #
> > > CONFIG_USB_PRINTER=m
> > > CONFIG_USB_SCANNER=m
> > > CONFIG_USB_AUDIO=m
> > > CONFIG_USB_ACM=m
> > > CONFIG_USB_SERIAL=m
> > > CONFIG_USB_SERIAL_GENERIC=y
> > > CONFIG_USB_SERIAL_VISOR=y
> > > # CONFIG_USB_SERIAL_DEBUG is not set
> > > # CONFIG_USB_IBMCAM is not set
> > > # CONFIG_USB_OV511 is not set
> > > # CONFIG_USB_DC2XX is not set
> > > # CONFIG_USB_DABUSB is not set
> > > #
> > > # USB HID
> > > #
> > > # CONFIG_USB_HID is not set
> > > # CONFIG_USB_KBD is not set
> > > # CONFIG_USB_MOUSE is not set
> > > # CONFIG_USB_WACOM is not set
> > > # CONFIG_USB_WMFORCE is not set
> > > # CONFIG_INPUT_KEYBDEV is not set
> > > # CONFIG_INPUT_MOUSEDEV is not set
> > > # CONFIG_INPUT_JOYDEV is not set
> > > # CONFIG_INPUT_EVDEV is not set
> > >
> > > /proc/bus/usb/devices:
> > > T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
> > > B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
> > > D:  Ver= 1.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> > > P:  Vendor=0000 ProdID=0000 Rev= 0.00
> > > S:  Product=USB OHCI Root Hub
> > > S:  SerialNumber=c4875000
> > > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
> > > I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
> > > E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
> > >
> > > /proc/bus/usb/drivers:
> > >          hub
> > >          usbdevfs
> > >
> > > "Stephen J. Gowdy" wrote:
> > >
> > > > Hi Steve,
> > > >         Is the documention you mean this;
> > > >
> > > > http://usbvisor.sourceforge.net/Handspring-Visor-mini-HOWTO
> > > >
> > > >         Did you install the new kernel and it runs okay? Did you make the
> > > > usb serial a module or compile it into the kernel? If you compiled it into
> > > > the kernel then that is why modprobe wouldn't find it. You can do "cet
> > > > /proc/bus/usb/drivers" (once you mount the usbdevfs file system) to see if
> > > > the driver is in the kernel. It will also appear here once you load the
> > > > module. You may need to add this line to your /etc/conf.modules (but I
> > > > don't think so as you've obviously got some usb modules loaded - or again,
> > > > are they in the kernel?);
> > > >
> > > > keep
> > > > path[usb]=/lib/modules/`uname -r`
> > > >
> > > >         The HOWTO above is missing the "make modules_install" line. This
> > > > is a reason why the USB Guide refers you to the Kernel HOWTO. That should
> > > > generally be correct
> > > > (http://www.linuxdoc.org/HOWTO/Kernel-HOWTO.html). There you will find out
> > > > about modules and other interesting stuff.
> > > >         If you still have problems can you include the contents of
> > > > /proc/bus/usb/drivers, /proc/bus/usb/devices and your .config file for
> > > > your kernel build?
> > > >         Good luck!!
> > > >
> > > >                                                         regards,
> > > >
> > > >                                                         Stephen.
> > > >
> > > > On Fri, 9 Jun 2000, Steven Headley wrote:
> > > >
> > > > > Looks like you are right
> > > > > on modprobe it says:
> > > > >
> > > > > can't locate module visor.
> > > > >
> > > > > I am pretty new at this. Is there a man page which will point me to how to
> > > > > set up the visor module. I tried the HowTo for Linux Visor on sourceforge
> > > > > but dosen't seem to have that info.
> > > > >
> > > > > "Stephen J. Gowdy" wrote:
> > > > >
> > > > > > Hi Steven,
> > > > > >         You probably don't have the visor module loaded. Try "modprobe
> > > > > > visor".
> > > > > >
> > > > > >                                                         regards,
> > > > > >
> > > > > >                                                         Stephen.
> > > > > >
> > > > > > On Fri, 9 Jun 2000, Steven Headley wrote:
> > > > > >
> > > > > > > Jun  9 13:43:41 Headley kernel: usb.c: This device is not recognized by
> > > > > > > any installed USB driver.
> > > > > >
> > > > > > --
> > > > > >  /------------------------------+-=-=-=-=-+-------------------------\
> > > > > > |Stephen J. Gowdy               |A4000/040| Mail Stop 50A-2160, LBL, |
> > > > > > |http://www.ph.ed.ac.uk/~gowdy/ | 1GB   HD| 1 Cyclotron Rd, Berkeley,|
> > > > > > |                               |20MB  RAM| CA 94720, USA            |
> > > > > > |InterNet: [EMAIL PROTECTED]       |3.4xCDROM| Tel: +1 510 495 2796     |
> > > > > >  \------------------------------+-=-=-=-=-+-------------------------/
> > > > >
> > > >
> > > > --
> > > >  /------------------------------+-=-=-=-=-+-------------------------\
> > > > |Stephen J. Gowdy               |A4000/040| Mail Stop 50A-2160, LBL, |
> > > > |http://www.ph.ed.ac.uk/~gowdy/ | 1GB   HD| 1 Cyclotron Rd, Berkeley,|
> > > > |                               |20MB  RAM| CA 94720, USA            |
> > > > |InterNet: [EMAIL PROTECTED]       |3.4xCDROM| Tel: +1 510 495 2796     |
> > > >  \------------------------------+-=-=-=-=-+-------------------------/
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

-- 
 /------------------------------+-=-=-=-=-+-------------------------\
|Stephen J. Gowdy               |A4000/040| Mail Stop 50A-2160, LBL, |
|http://www.ph.ed.ac.uk/~gowdy/ | 1GB   HD| 1 Cyclotron Rd, Berkeley,|
|                               |20MB  RAM| CA 94720, USA            |
|InterNet: [EMAIL PROTECTED]       |3.4xCDROM| Tel: +1 510 495 2796     |
 \------------------------------+-=-=-=-=-+-------------------------/


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to