[NCLUG] Visor troubleshooting...

Brett Johnson brett at hp.com
Mon Apr 28 15:00:18 MDT 2003


On Mon, 2003-04-28 at 14:11, dobbster wrote:

> I've used 'mknod' to create various /dev/ files as suggested (i.e.,
> /dev/ttyUSB0, etc., with perms 666), although I understand this should
> happen automatically.  It's not.

These files should be created automatically when a device makes itself
known on the USB bus (like when you push the hotsync button on your
palm).  They go away as soon as the hotsync is finished.  I think
they're created by the hotplug daemon.

> I suspect the issue has something to do with hot-plugging. 
> /var/log/messages reads:
> 
> Apr 28 13:43:08 dobbster68 kernel: hub.c: USB new device connect on
> bus1/2, assigned device number 7
> Apr 28 13:43:08 dobbster68 kernel: usb.c: USB device 7 (vend/prod
> 0x830/0x50) is not claimed by any active driver.
  ^^^^^^^^^^

Ugh, looks like the usbserial driver doesn't recognize your device.  Did
you say this was a new Zire?  Might be 'cause the Zire is a new device
(and palm changed the vendor/product ids).  From perusing the
usbserial.c source, it wasn't immediately apparent where the table of
vendor/product ids is stored.  Maybe there's someone who is familiar
with the usb architecture on the list that could help?

You should be getting some messages from the usbserial and visor modules
saying that they are claiming the device.  For example, I get these
messages from syslog:

Apr 28 14:44:48 bj6694 kernel: hub.c: new USB device 00:1d.1-2, assigned address 3
Apr 28 14:44:48 bj6694 kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter detected
Apr 28 14:44:48 bj6694 kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 2
Apr 28 14:44:48 bj6694 kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for Generic use and is bound to ttyUSB0
Apr 28 14:44:48 bj6694 kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 2, is for HotSync use and is bound to ttyUSB1

Cheers!
-- 
Brett Johnson <brett at hp.com>
   -  i  n  v  e  n  t  -



More information about the NCLUG mailing list