PalmOS devices
From MEPIS Documentation Wiki
Contents |
Introduction
PalmOS devices work pretty well with Linux, and offer many advanced possibilities. All interactions depend on pilot-link, a suite of tools that is installed by default with MEPIS 7.x but not in MEPIS 8. A number of different frontends are available to use this backend on MEPIS, including Kpilot and Jpilot.
Precautions:
- Make sure all your device entries are correct, including spelling and capitalization
- Make sure your handheld data are backed up before you start.
- If you are using a Palm device that has been used on another PC, restore the factory defaults (hard reset) by following these directions.
- Make sure that the modules you need are loaded: visor, usbserial and uhci_hcd or ehci_hcd.
MEPIS 8
The technique listed for MEPIS 7.x and KPilot also works for MEPIS 8. Before you begin, however, it will be necessary to install
pilot-link
using the usual methods.
MEPIS 7.x and KPilot
The following technique works on MEPIS 7 for a Tungsten T2 and a Tungsten E, following most of the tips listed under Troubleshooting below.
1. Make sure your handheld data are backed up before you start.
2. Using any installation method, install these packages:
kpilot libpisock9
3. Connect your Palm handheld to the computer
4. Open Kpilot and do one of the following:
--Click Settings --> Configure Kpilot, and click the button Configuration Wizard in the main panel. Follow the directions to let Kpilot try to establish the relationship automatically. This routinely causes KPilot to crash, but you may get lucky.
--Connect manually by clicking on Settings --> Configure Kpilot and click on Device in the left panel. Set the following parameters:
Pilot device: /dev/ttyUSB0 OR /dev/ttyUSB1 Speed: 115200 (unless serial connection, then try 19200) Workarounds: None (check another choice if applicable) Encoding: default, unless you know differently Pilot user: user name for your handheld
NOTE: some users have found that ttyUSB0 does not work for them as the device name, but that usb: does.
5. If you are synching with Kontact for addresses, click on Addressbook in the left panel, and check vCard file as the Sync Destination
6. Handheld files (in Palm format) are stored here:
/home/UserName/.kde/share/apps/kpilot/conduits
7. Once setup has worked, you can perform a hot sync simply by starting KPilot and pressing the hot sync button on your handheld or its cradle.
8. KPilot's Palm DOC conduit does not convert text files to PalmDoc format and send them to the handheld. Nor does KPalmDOC, available in the repos. This is a minor problem because you can easily use KWord (save as Palm Document) or the online resource listed below to convert the files. Once converted, they can be transfered with KPilot's File Installer, and read with a reader such as Weasel or CSpotRun.
MEPIS 6.5 and KPilot
You will need the following packages installed:
libpisock8 or libpisock9, kpilot, korganizer, libusb-0.x.x, knotes (optional)
1. Connect your Palm to your computer with the USB cable.
2. Leave your Palm OFF.
3. Run KPilot
4. If the Configuration Wizard doesn't run then go to the Settings menu, select Configuration Wizard.
5. In the Pilot Info dialog blank the Device field.
Now, in this order (the order is important)...
1. Select the Automatically Detect Handheld & User Name button.
2. Let it get to about 5% in the detection process.
3. Turn your Palm ON
4. Run HotSync on your Palm and then press the the HotSync button.
It should detect your Palm and fill in the User name and the Device path.
In General Setup --> Device --> Workarounds, select:
Zire31, 72, Tungsten T5 (any Palm with OS 5 or greater, or if your Palm has the Media application).
If you have Palm Zire or Tungsten ensure you have the following entered in General Setup --> Backup --> No backup:
[a86k],ArmLog,[Arng],FATFS,GrxViewGifLibARM,GrxViewJpegLibARM,ImgFile-Foto,Jpeg-Foto,[lnch],Net Library,[PmDB]
Without this, jpeg-foto and other files will cause KPilot to crash.
MEPIS 6.x and JPilot
The following technique using J-Pilot works on MEPIS 6.5 for many PDAs running Palm OS:
1. Using any installation method, install these four packages:
jpilot jpilot-plugins libpisock8 libpisock9
You should already have installed all the necessary backend packages such as pilot-link.
2. Once J-Pilot installs, it shows up in Kmenu --> Office --> J-Pilot; you may need to reboot first.
3. Plug in your Palm device to a USB port
4. Start J-Pilot
5. Press the hotsync button on the Palm.
6. Click the hotsync icon on the lower left in J-Pilot. It should start syncing.
Note: With some Treos you may need to count to 5 between pressing the hotsync button on the Palm and the hotsync icon in JPilot.
Tips and Tricks
- Many of the applications that claim to be able to convert a *.txt file to a *.pdb file may not work. KWord seems to be very solid, however, and it can save a file in the native PalmDoc format that can be picked up by any of the free readers.
Wireless
To get your Palm to connect wirelessly with advanced security such as WPA2, you may need extra software. In this example for the Palm TX, you will need to go to the Palm software store and purchase package Wi-Fi Enterprise Security Update (ESU) for the Palm T|X Handheld.
Download it to your computer where you can find it. Then right click on it (TX security upgrade will be the title). Choose Extract to TX_Security_Upgrade. This will make a folder. From this folder you will need to add these files:
enUS.prc TX_updater.prc WiFiProfileCopy_enUS.prc
Transfer these to the Palm using Kpilot, Jpilot or a SD card (just drop them into the Launcher folder, which is in the Palm folder).
Fire up your WiFi by clicking on the icon 4th from the right. From the pop up Wi-Fi box, choose “on”. Then choose Scan/Setup. Click on the Wireless network you want to connect to and then tap “Edit”. From the pop up tap on “Configure” For “Security” you will have a choice of “Open” “Personal” or “Enterprise”. Next will be “Mode”, your choices are “WEP” or “WPA-PSK”. Then Encryption, you can choose “TKIP” or “AES” or “Auto(TKIP/AES). Then tap your “Key” box and fill in your passphrase. If you are using “Enterprise” you may need a user name as well. Then tap “OK”. Palm with then ask you if you want to connect now, and off you go.
Troubleshooting
- If you have trouble connecting, plug your handheld directly into the PC (no hub).
- If problems with HotSync occur, try modifying or even unchecking a conduit (such as Addressbook)
- From the palm-link listserve:
The *ONLY* things which prohibit a USB Palm device from connecting to a Linux desktop are the following:
1. A broken Palm device or desktop hardware. This can be a wedged serial port (which a soft reset cures), or a physically damaged unit (bent pins for example). Or a Palm LifeDrive, which attempts to use > "Drive Mode" to mount the device at connect time, before HotSync is even pressed. Incorrect USB ports, wacky USB hub configurations and so on can make it hard to diagnose and sync a Palm device. Eliminate the obvious.
2. Invalid configuration. This can be bad distribution patches/packages, invalid udev/kernel configuration and rules or any number of other things... all easily fixed, if you know which parts are affecting it.
3. Incorrect use of the VERY fragile timing aspect. Timing is completely device + desktop + configuration dependent. Some Palm devices require waiting up to 7 seconds between hitting HotSync and initiating a sync, while others take 1/2 second. You'll need to play around with that until you find one that works for your device.
- For other help, such as with particular handhelds, consult the pilot-link blog.
Links
- Data collection with a Palm
- KPilot handbook -- also available from the app's Help menu.
- Palm/Linux Connection
- Palm support -- to find a handbook, bluetooth info, etc.
- Linux applications for Palm
- PalmOS projects on SourceForge
- Makedoc - online conversion tool from text to PalmDoc format
- Detailed pilot-link directions -- if needed!

