On Wed, 2005-03-30 at 19:59 -0500, Lorn Miller wrote: > I know these happen often, and I've searched through the archive, but I > can't find any info there (or on google) that's at all helpful. I'm > trying to connect a Sony Clie PEG-SL10/U to my FC 3 box. The Clie is > out-of-the-box clean. I try Kpilot's autodetect, but it times out. I'm > connecting through usb. > > Clie OS: Palm OS software v.4.1 > > [ldmiller@phoenixdragon ~]$ rpm -q kernel > kernel-2.6.10-1.766_FC3 > kernel-2.6.10-1.770_FC3 > [ldmiller@phoenixdragon ~]$ rpm -qa | grep pilot > pilot-link-0.11.8-8 > gnome-pilot-2.0.12-4 > gnome-pilot-conduits-2.0.12-3 > gnome-pilot-devel-2.0.12-4 > pilot-link-devel-0.11.8-8 > [ldmiller@phoenixdragon ~]$ > > I'm running kernel 2.6.10-1.770_FC3 > > Any more info I can give to help? Any solutions? I'd really hate to > have to boot into Windows to use the clie. ---- first issue - detection at device level... probably more than you ever wanted to know... <http://www.reactivated.net/udevrules.php> problem is that you have to figure out how to 'identify' your Clie and make a rule for it which creates a device on the fly... normally, you would create /etc/udev/rules.d/10-udev.rules /etc/udev/permissions.d/10-udev.permissions this is what my Kyocera 7135 looks like... # cat /etc/udev/rules.d/10-udev.rules KERNEL="ttyUSB1",SYMLINK="pilot" # cat /etc/udev/permissions.d/10-udev.permissions pilot*:root:usb:0666 then it should probably work with JPilot or KPilot if it's set to /dev/pilot and you press the 'sync' button on the cradle If you want to use gpilotd (gnome pilot - evolution...) you would probably want to edit if your Clie isn't there... /usr/share/gnome-pilot/devices.xml Craig
