I'm trying to setup my usb palmpilot (Palm Zire 71) to sync with my desktop; digging through the forums has not revealed anything concrete for reasons outlined below.

The system is running Slackware 10 with kernel 2.6.7. I've compiled visor.o and usbserial.o directly into the kernel to keep things simple. Of 4 USB slots two are used by the USB mouse and keyboard (which work fine); one other has the palm cradle plugged in. Udev is being used as per default installation but I'm having a lot of difficulty interacting with it. The pda is being recognized (more or less), but I have no idea what device node is being created nor where to symlink /dev/pilot.

Ideally I'd like to use Kpilot for syncing, but even just trying to use something like pilot-xfer requires that I symlink /dev/pilot to some particular device.

For what it's worth there is NO instance of /dev/usb anywhere, which prevents linking to /dev/pilot. The only thing I can find is that when I press the cradle hotsync button I notice that /dev/tts/USB0 and /dev/tts/USB1 appear, and disappear when the pilot turns off. When I hit the cradle button the following "lsusb" output appears:

Bus 004 Device 001: ID 0000:0000
Bus 003 Device 003: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
Bus 003 Device 002: ID 0ede:0107
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 0830:0060 Palm, Inc. Palm Tungsten T
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

If anyone can help me out I would be grateful.

try /dev/sda1 this is the node I use for my usb flash, usb camera, usb zip... not sure if the palm is a "mass storage device" like those I mentioned but it's worth looking into. If this is the right /dev you can write a udev rule to create a symlink from /dev/sda1 to /dev/pilot.

I just added this to my rc.local, I couldn't get it right in udev.

insyte, I've done this as well sync'ing works perfectly fine. But I was hoping to find a more graceful solution; having to manually re-create (a la rc.local) the device upon booting seems kind of kludgy to me.

lupin_the_3rd, thanks for your suggestion. I guess if udev is meant to be the New Method I'd better just sit down and figure out how it works. If I come up with a working rule I'll post it to this thread.

http://www.reactivated.net/udevrules.php

specifically,

http://www.reactivated.net/udevrules...bstorage-extra


Found this :

# Linux: It is useful to have udev (the successor to devfs). Then you can use the following udev rules to create device links for a Sony Clié (which gets /dev/pilot) and any other Palm OS device (which gets /dev/pilot_any).

SYSFS{manufacturer}="Sony Corp.",
SYSFS{product}="Palm Handheld",
SYSFS{idVendor}="054c",
NAME="pilot"

SYSFS{product}="Palm Handheld",
NAME="pilot_any"

here: http://www.slac.com/pilone/kpilot_home/faq.html#r5

This should get you started!

Hello All,

I found the thread, and it depicts more or less the same situation I have.
Once, by chance I was able to synch my Zire31 with Kontact thru Kpilot.
But then it never worked again ... :-(

I have the following issues right now:
1. Playing with link and unlink, I think I deleted the /dev/pilot .. this is the default device that KPilot will look for when synching. Is there a way to re-create it?
2. I know thru KDE System Information, that my Palm gets detected in the system in the USB hub in the motherboard, but which is the "real device" that is going to so to make the symbolic link to /dev/pilot (I guess would be "link /dev/pilot /dev/????")
3. Udev? Maybe it's my answer ... I have never played with it ...

Thanks ...

personally, the only way i was finally able to sync my palm was by using Jpilot. i couldn't get kpilot to work, but jpilot works great for me...just another suggestion

I have a solution i've just found for my old ZIRE m150 on SLACKWARE 11 (come here search engines) (hell, some hours ago i didn't even know if it worked because the palm battery was dead)

You just have to put this rules on /etc/udev/rules.d/10-local.rules (or /etc/udev/rules.d/[whatever_you_like].rules) hint, if the file doesn't exist just create it, for those who doesn't RTFM:

---------------------------
# Rule needed to create the "pilot" device
BUS=="usb", SYSFS{product}=="Palm Handheld*", KERNEL=="ttyUSB[013579]", SYMLINK+
="pilot", MODE=="0666", GROUP=="users"

# Rule needed to establish the right permisions on the /dev/tts/USB* device
KERNEL=="ttyUSB[01]*", NAME="tts/USB%n", GROUP="users", MODE="0660"
---------------------------

That's it! sync and be happy, it'll work all the time, the reason many people report that it's not working for them is because they do not set the right permisions on the second file, go, try it manually, apply only the first rule and as root try this command:

chmod 666 /dev/tts/USB*

SYNC DONE!

Hope it helps

i have a Tungsten E palm pilot, i have issues here and there, but this is the deal, i don't always use udev, and i am running slackware 11 [maybe i will go full udev here shortly] - this is what i do, as it seems i HAVE to use udev to get Kpilot to work properly/sync with my palm EVERYTIME .... i have the following udev rule ;

> cat /etc/udev/rules.d/pilot.rules
BUS="usb" SYSFS{product}="Palm Handheld*" KERNEL="ttyUSB*" SYMLINK="pilot" MODE="666" KERNEL="ttyUSB*" SYMLINK="pilot"

then, i run this script IF for some reason Kpilot is being a bitch;

> cat /usr/bin/pilotbash.sh
#!/bin/bash
if [ ! -x /etc/rc.d/rc.udev ]; then `chmod 755 /etc/rc.d/rc.udev`;
fi
/etc/rc.d/rc.udev restart
pkill -9 pilotDaemon
if [ ! -e /dev/ttyUSB1 ] `rm /dev/ttyUSB1`; then #if /dev/ttyUSB1 does NOT exist
echo "<< File /dev/ttyUSB1 doesn't exist ... creating it now >>"
mknod /dev/ttyUSB1 c 188 1
fi

if [ ! -e /dev/pilot ] `rm /dev/pilot`; then #if /dev/pilot does NOT exist
echo "<< Symlink /dev/pilot doesn't exist ... creating it now, /dev/pilot = /dev/ttyUSB1 >>"
ln -s /dev/ttyUSB1 /dev/pilot
fi
chmod 777 /dev/ttyUSB1
chmod 777 /dev/pilot
chmod -x,ugo /etc/rc.d/rc.udev
n=`ls -al /dev/pilot`
t=`ls -al /dev/ttyUSB1`
echo "$n"
echo "$t"
echo "defining /etc/rc.d/rc.udev non-executable."
exit 0

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
fixes any problem i have with udev/palm pilot/Kpilot EVERYTIME... hope this helps ---- yeah, it's a hack - but it works =)

agentdcooper