Pilot sync/usb question
Aaron O'Hara
ajeo at hungryforlife.org
Thu May 26 03:33:13 UTC 2005
I named a grey hair after my Clie with Linux. I had similar
symptoms, /var/log/messages showed the device connecting, but jpilot,
gnomepilot, and kpilot all couldn't see the device.
The issue I had was related to the fact that the dynamically created dev
files (ttyUSB0 and ttyUSB1) didn't have sufficient permissions. When I
had my pilot program open, I pressed HotSync, followed by a chmod 777 of
ttyUSB* and voila, it was working. Of course, this is a hack. A long
term, proper, solution could be found in these URLs (provided by Craig
White on this list):
http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimerMisc.html
Not necessary for this but if you want a lot more info on usb/udev
etc...
http://www.reactivated.net/udevrules.php
Hope this helps,
-- Aaron
On Thu, 2005-26-05 at 03:05 +0000, William W. Austin wrote:
> I *know* I had this working earlier but after a disastrous series of
> updates with a corrupted filesystem and a complete reformat/reinstall
> (someone decided to upgrade *everthing* for me when I wasn't around and
> so I got to clean up the machine), I can no longer get a palm pilot to
> hot sync. (luckily apcupsd finds the ups ok, so I know the usb
> subsystem is working properly.
>
> Usbview shows the device is there and that palm is connected, and the
> modules are loaded properly, but neither kpilot nor jpilot can find the
> dev. The main problem is that I can't figure out (or find) the correct
> device any more. I have tried RTFM'ing, but haven't found it so far.
>
> Any pointers, how-to's etc., would be greatly appreciated.
>
> --
> William W. Austin waustin at speakeasy.net
> "Life is just a phase I'm going through. this time, anyway ..."
>
>
More information about the fedora-list
mailing list