On Thu, 2004-12-09 at 16:10 -0400, Rodolfo Alcázar wrote:
> maybe you could delete the BUS and SERIAL stuff...
>
> > KERNEL="ttyUSB1",SYMLINK="pilot"
---
OK
# cat /etc/udev/rules.d/10-udev.rules
#BUS="usb", SYSFS{serial}="0000:00:02.1", NAME="pilot"
KERNEL="ttyUSB0",SYMLINK="pilot"
---
> > 2 - why does dlpsh and pilot-xfer -p /dev/pilot -L work but gpilotd
> > pointed to /dev/pilot never connect?
>
> Don't know. Anybody can help us with this point?
>
> > 3 - is this a bugzilla issue or user that doesn't get it?
>
> Just as I told you.
----
ok changing 10-udev.rules as you suggest
# ls -l /dev/ttyUSB* /dev/pilot
lrwxrwxrwx 1 root root 7 Dec 9 13:25 /dev/pilot -> ttyUSB1
crw-rw---- 1 root uucp 188, 0 Dec 9 13:25 /dev/ttyUSB0
crw------- 1 craig uucp 188, 1 Dec 9 13:25 /dev/ttyUSB1
so far - so good - perhaps better since the devices for ttyUSB0 & 1 show
but gpilotd doesn't connect
pilot-xfer does though...
# pilot-xfer -p /dev/pilot -L
Listening to port: /dev/pilot
Please press the HotSync button now... Connected
Reading list of databases in RAM and ROM...
HST-CTig
<a whole bunch of files on palm phone listed>
List complete. 295 files found.
Time elapsed: 0:00:08
I have figured out that there are 2 directories for gpilotd
~/.gnome/gnome-pilotd and ~/.gnome2/gnome-pilotd and I suspect that this
has something to do with upgrade from FC-1 to FC-3 and evidently,
configuration data is in .gnome2 subdirectory.
after moving .gnome2/gnome-pilot.d to a backup and then restarting
gpilotd-applet it takes me through a configuration that wants to
retrieve username and id from palm for initial setup - which after some
connect / disconnect worked - thanks - well, it worked once and hasn't
connected again but it's progress.
I rebooted on 2.6.9-1.667 which does work with USB visor. Obviously
2.6.9-1.681_FC3 doesn't and I will wait for updated kernel for the
moment rather than install kernel-testing.
Thanks for your help...it was the kind of spooky stuff I would see on
Windows and not at all Linux like.
Craig
