I've got a Fedora Core 3 system where I've installed pilot-link-0.12.0-0.pre2.0 and I still can't sync my Handspring Visor. Pilot-link can't talk to it and it can't talk to Pilot-Link. My system isn't seeing it, period. The drivers are all installed and the devices are there, but I just can't do anything. Can someone PLEASE give me a hand with this???

The LifeDrive:
Currently the LifeDrive is Palm's attempt to be relevant in the emerging portable media player market(PMP). It wokrs pretty well as a PDA and does a good job as a PMP. I recently purchased one and thought this would be a good place to comment on it's useabilty with Linux.

The Sync:

All hail the networksync feature of pilot-link. Without I would never have gotten the LifeDrive to sync. It ships with a usb cradle and this is the source of the problems. On most modern Linux distros you have dbus/hotplug enabled and the LifeDrive rports it self as a USB device as soon as you plug it in to teh cradle. This is good for drive mode, bad for hotsyncing. When you press teh hotsync butto the Lifedrive it resets the USB connection causing the /devpilot(/dev/tts/USB1 or /dev/ttyUSB1) to reset and breaking the connection. I have not found a awy around this yet. Luckly the Lifedrive comes with both Bluetooth and wifi. The device can sync over the wifi connection.


To setup Lifedrive for the network sync follow teh instruciton given in the Network Hotsync Document on the right side of the page. Be sure you have pilot-link installed, to test the connection use 'pilot-xfer -p net:any -l'. You should see pilot-xfer listening on port net:any message. Press teh hotsync button and watchit go, you should see a list of items from the Lifedrive.



The Desktop-

I use J-pilot for my desktop software. The LifeDrive supports all the features of the J-pilot. However, J-pilot does NOT support all of the LifeDrive features. Many of these features can be duplicated by using Drive Mode.



Drive Mode-

When the LifeDrive is set to Drive Mode it reports it self as 3.5 gig usb drive and allows you to move files back and forth with Nautilus and I would assume Konquer with out problem. Just be sure to turn off drive Mode be for unpluging the LifeDrive

As described in README.usb, some handhelds require newer versions of the kernel. Your kernel should be the version indicated in the tables here or a more-recent kernel version than those listed.

If you add data (such as new models, or vendor/product ids) to these tables, please send it to the pilot-link-devel list so it can be added to the plain text listing too.

** USB-to-Serial Adapters **

Prolific Technologies usb-to-serial adapter works with Linux, using the vendor/product ID of 067b/2303, and works with the pl2303 driver in Linux.

Untested on FreeBSD at this point.

Keyspan USA-19QW, works with Mac OS X 10.1.5 and Linux

**Footnotes**

The Palm M130 device does not support Network Hotsync in any capacity. Someone did actually hack it to allow Network HotSync to work. Follow the procedure below if you’re daring.

1. Extract the files "HotSync.prc" and "HotSync enUS.prc" from your M505 and save them to your HD as "HotSyn2.prc" and "HotSyn2 enUS.prc" (note the space).
2. Using a hex editor, change all occurrances of the string “sync” to “syn2”, and “Sync” to “Syn2” in both files. (NOTE: earlier revision changed “sync” to “sync2” — this would likely corrupt the file)
3. Change the byte at offset 0x21 to 0x09 in both files.

** Solution ID: 16309 **

Information on performing a Network HotSync® operation with the Palm™ Bluetooth™ Card in my Palm™ m125 or m130 handheld

The Palm™ m125 and m130 handhelds do not include the necessary components to setup the handheld for Network HotSync® operation, nor the desktop components needed to complete a Network HotSync operation.

**Solution ID: 16713**

Information on Network HotSync® not being available on certain Palm™ m1xx and Zire handhelds

Network HotSync® for specific Palm™ handhelds are not supported, see list below.
The conduits required for the Palm™ Desktop software to perform a Network HotSync® were
not included with the Palm desktop for these products. In addition, the Network HotSync®

settings on the device are not available to enable this feature.

List of handhelds that do not natively support Network HotSync®:

• Pilot 1000 and 5000
• PalmPilot Personal and Professional
• Palm m100, m125, m130
• Palm Zire