On Thu, 2004-12-09 at 17:06 -0400, Rodolfo Alcázar wrote:
> El jue, 09-12-2004 a las 13:40 -0700, Craig White escribió:
> > # 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
>
> You did not specify if you deleted /dev/pilot, as I told you. udev MUST
> create this files.
>
> But that was the difficult part. Now comes to easy. If udev has created
> the necessary files, and gpilotd is not syncing, gpuilotd is your
> problem. Second reason: dlpsh and your other program are working
> with /dev/pilot.
>
> I have gpilot-applet on my taskbar. I use configure my palm from there.
> If any error occurs, I use
>
> # killall gpilot-applet gpilotd
>
> so the applet reloads and gpilotd starts again. If you do not kill this
> apps, and there is a gpilotd pid, you'll never sync.
>
> Check your gpilotd configuration. Probably the error is there.
>
----
actually, I have never created /dev/pilot - it was always put there by
udev/rules.d/10-udev.rules and originally, the rule you had me comment
out - thus, when device is not sync
#BUS="usb", SYSFS{serial}="0000:00:02.1", NAME="pilot"
# ls -l /dev/pilot /dev/ttyUSB*
ls: /dev/pilot: No such file or directory
ls: /dev/ttyUSB*: No such file or directory
and when it is sync
# ls -l /dev/pilot /dev/ttyUSB*
lrwxrwxrwx 1 root root 7 Dec 9 14:19 /dev/pilot -> ttyUSB1
crw-rw---- 1 root uucp 188, 0 Dec 9 14:19 /dev/ttyUSB0
crw------- 1 craig uucp 188, 1 Dec 9 14:19 /dev/ttyUSB1
and when I (as root) #killall gpilot-applet
it pops up a window on my user desktop asking me if I want to reload it
and I answer yes.
at the moment - I cannot get it to reconnect to gpilotd - even after
repeating previous steps of moving $HOME/.gnome2/gnome-pilotd directory
and going through set up procedure - exasperating...
Craig
