[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Samsung I500 (USB Palm device) and udev



I should like ultimately to sync my Samsung I500 device with
gnome-pilot, but I'm having problems just getting basic
connectivity established.  For the moment, I should be happy
to have 'pilot-xfer -b backup_d' work properly.

I'm using the latest kernel image 2.6.8-1-686-smp, the
latest hotplug, the latest udev.  I'm mounting sysfs on /sys
in /etc/fstab.

I have some local udev stuff defined:

----------begin /etc/udev/rules.d/local.rules----------
# USB devices
BUS="usb", SYSFS{product}="SAMSUNG CDMA Technologies", NAME="pilot"
KERNEL="ttyUSB*", NAME="%k"
----------end /etc/udev/rules.d/local.rules----------

----------begin /etc/udev/permissions.d/local.permissions----------
pilot:::0666
ttyUSB*:::0666
----------end /etc/udev/permissions.d/local.permissions----------

I notice that after boot-up, my local udev config seems to
produce a /dev/pilot node:

crw-rw-rw-  1 root root 188, 3 Sep 15 14:15 /dev/pilot

(Notably absent, however, are any /dev/ttyUSB* nodes.  In
the past, when I have tried to sync a palm device, I always
used /dev/ttyUSB1---not /dev/ttyUSB0---I think.  I have been
unable to get /dev/ttyUSB* to appear with udev and am
interested to know about this, too.)

The problem is that when I run 'pilot-xfer -b backup_d', the
program crashes with an error message (kernel messages
included):

----------begin pilot-xfer output----------
visor ttyUSB3: Device lied about number of ports, please use
a lower one.
visor ttyUSB2: Handspring Visor / Palm OS converter now
disconnected from ttyUSB2
visor ttyUSB3: Handspring Visor / Palm OS converter now
disconnected from ttyUSB3
   Port not connected, sleeping for 2 seconds, 5 retries..
   The device /dev/pilot does not exist..
   Possible solution:

        mknod /dev/pilot c <major> <minor>

   Unable to bind to port: /dev/pilot
----------end pilot-xfer output----------

Any help is appreciated.

-- 
Thomas E. Vaughan   (303) 939-6386   Ball Aerospace, Boulder



Reply to: