[svlug] Problems with usb visor under Debian Woody

Rafael Skodlar,,, raffi at linwin.com
Tue Jul 30 22:52:11 PDT 2002


On Tue, Jul 30, 2002 at 09:34:51AM -0700, Wayne Earl wrote:
> I've just migrated my home system from a Red Hat install to Debian, and
> I am having a problem communicating with my usb visor that doesn't make
> sence to me. Before, the visor was /dev/ttyUSB1, so I am assuming this
> continues to be the case now.
> 
> Permissions seem correct:
> wayne at vimes:~$ ls -al /dev/ttyUSB1
> crw-rw----    1 root     dialout  188,   1 Mar 14 13:54 /dev/ttyUSB1

Have you tried:
chmod 666 /dev/ttyUSB1

If you are the only one using the system that whould not be a security
issue.

> 
> wayne at vimes:~$ cat /etc/group | grep dialout
> dialout:x:20:wayne,root
> 
> The kernel knows about the hardware (kernel-image-2.4.18-686 from woody):
> wayne at vimes:~$ lspci
> ...
> 00:07.2 USB Controller: Intel Corp. 82371AB PIIX4 USB (rev 01)
> 
> The module is loaded into memory:
> wayne at vimes:~$ /sbin/lsmod
> Module                  Size  Used by    Not tainted
> ...
> visor                  10048   0 (unused)
> usbserial              17824   0 [visor]
> usbcore                48192   0 [visor usbserial]
> 
> wayne at vimes:~$ dmesg | grep usb
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> usb.c: registered new driver serial
> usbserial.c: USB Serial support registered for Generic
> usbserial.c: USB Serial Driver core v1.4
> usbserial.c: USB Serial support registered for Handspring Visor
> usbserial.c: USB Serial support registered for Palm 4.0
> usbserial.c: USB Serial support registered for Sony Clié 3.5
> usbserial.c: USB Serial support registered for Sony Clié 4.0

I see one more line in dmesg on my system (it's RH7.2 though)

visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.5

and later on

usb.c: kmalloc IF d4620460, numif 1
usb.c: new device strings: Mfr=1, Product=2, SerialNumber=0
usb.c: USB device number 2 default language ID 0x409
Manufacturer: Handspring Inc
Product: Handspring Visor
usbserial.c: Handspring Visor converter detected
visor.c: Handspring Visor: Number of ports: 2
visor.c: Handspring Visor: port 1, is for Generic use and is bound to
ttyUSB0
visor.c: Handspring Visor: port 2, is for HotSync use and is bound to
ttyUSB1
usbserial.c: Handspring Visor converter now attached to ttyUSB0 (or
usb/tts/0 for devfs)
usbserial.c: Handspring Visor converter now attached to ttyUSB1 (or
usb/tts/1 for devfs)
usb.c: serial driver claimed interface d4620460
usb.c: kusbd: /sbin/hotplug add 2
hub.c: port 1 connection change
hub.c: port 1, portstatus 100, change 3, 12 Mb/s
usb.c: USB disconnect on device 2
usbserial.c: Handspring Visor converter now disconnected from ttyUSB0
usbserial.c: Handspring Visor converter now disconnected from ttyUSB1

My kernel uncludes USB, no loadable modules needed.

When I plug in my Visor in I see the following in the log file

Jul 30 22:34:00 salmon kernel: hub.c: USB new device connect on bus1/1,
assigned
device number 4
Jul 30 22:34:00 salmon kernel: Manufacturer: Handspring Inc
Jul 30 22:34:00 salmon kernel: Product: Handspring Visor
Jul 30 22:34:00 salmon kernel: usbserial.c: Handspring Visor converter
detected
Jul 30 22:34:00 salmon kernel: visor.c: Handspring Visor: Number of
ports: 2
Jul 30 22:34:00 salmon kernel: visor.c: Handspring Visor: port 1, is for
Generic
use and is bound to ttyUSB0
Jul 30 22:34:00 salmon kernel: visor.c: Handspring Visor: port 2, is for
HotSync
use and is bound to ttyUSB1
Jul 30 22:34:00 salmon kernel: usbserial.c: Handspring Visor converter
now attached to ttyUSB0 (or usb/tts/0 for devfs)
Jul 30 22:34:00 salmon kernel: usbserial.c: Handspring Visor converter
now attached to ttyUSB1 (or usb/tts/1 for devfs)
Jul 30 22:34:00 salmon /sbin/hotplug: arguments (usb) env
(PWD=/etc/hotplug HOSTNAME=salmon.linwin.com DEVICE=/proc/bus/usb/001/004
INTERFACE=255/0/0 ACTION=add DEBUG=kernel MACHTYPE=i386-redhat-linux-gnu
OLDPWD=/ DEVFS=/proc/bus/usb TYPE=0/0/0 SHLVL=1 SHELL=/bin/bash
HOSTTYPE=i386 OSTYPE=linux-gnu HOME=/ TERM=dumb
PATH=/bin:/sbin:/usr/sbin:/usr/bin PRODUCT=82d/100/100 _=/usr/bin/env)
Jul 30 22:34:00 salmon /sbin/hotplug: invoke /etc/hotplug/usb.agent ()
Jul 30 22:34:00 salmon /etc/hotplug/usb.agent: ... no drivers for USB
product 82d/100/100

It seems there are two lines used for connection to Visor:

Jul 30 22:35:06 salmon kernel: visor.c: Handspring Visor: port 1, is for
Generic
use and is bound to ttyUSB0
Jul 30 22:35:06 salmon kernel: visor.c: Handspring Visor: port 2, is for
HotSync
use and is bound to ttyUSB1

Permissions I use:
crw-rw----    1 root     uucp     188,   0 Aug 30  2001 /dev/ttyUSB0
crw-rw-rw-    1 root     uucp     188,   1 Aug 30  2001 /dev/ttyUSB1

I hope my messages remind you of what you used to have working before.

I had more luck with compiling the kernel with appropriate drivers
included than trying to install modules.

> 
> But trying to synk, using either jpilot or pilot-xfer doesn't seem to
> work. Attempting to access either /dev/ttyUSB0 or /dev/ttyUSB1 doesn't
> work.
> 
> Previously, I would have to press the sync button before selecting sync
> or running pilot-xfer. Under the old Red Hat system, doing this would
> generate syslog messages that the visor was now available on
> /dev/ttyUSB1 (I can't remember the specific messages). Now, I get no
> messages (and no sync).
> 
> Anyone have any ideas?
> 
> -- 
> Wayne Earl <wayne at qconcepts.net>
> gpg public key: http://www.qconcepts.net/key.txt
> gpg key fingerprint: 3CE4 0558 635E DADB 327C 73AB 11CA 9A6B B209 E8C5

-- 
Rafael
The Gap Between the Rich and the Poor is Constant.



More information about the svlug mailing list