Clie T-665C with JPilot on RedHat 7.3

These instructions may work for other Clie models, but these instructions reflect only my experiences with the Clie T-655c handheld PalmOS organizer and cradle. You may wish to search ClieSource for additional help with other models if these instructions do not work for you.

  1. Install the CheckInstall RPM if you do not have it in your system. Download it from http://asic-linux.com.mx/~izto/checkinstall/ as an RPM.
  2. Upgrade the kernel to 2.4.20. If you do not use GRUB, I cannot help you.
    1. Download the RPMs from here: https://rhn.redhat.com/errata/RHSA-2003-187.html
    2. Have an NVidia card?
      1. Download the NVidia driver software from: http://www.nvidia.com/view.asp?IO=linux
      2. Choose the Linux IA 32 latest version link.
      3. Download the Readme.txt file.
      4. Download the NVidia*.run file.
      5. Remember where you put these.
    3. Upgrade the quota RPM.
    4. Install the kernel packages using rpm -ihv kernel*.rpm.
  3. Download the pilot-link and jpilot tarballs. Get them from http://www.pilot-link.org/ and http://jpilot.org. As of this writing pilot-link is at version 0.11.7.
  4. Reboot your Linux PC. Choose the new kernel (not the "BOOT" kernel) at startup.
  5. Verify the driver finds the Clie.
    1. Plug in the power to the cradle, then plug the cradle into your Linux PC USB port if you have not done so already. Do not put the Clie in the cradle yet.
    2. Log in as root.
    3. Run a "tail -f /var/log/messages" to watch the kernel messages.
    4. Put the Clie in the cradle and push the HotSync button. Watch the tail messages.
    5. You should see the new device be seen by the kernel as a Palm Handheld. You should even see the Clie mentioned as device ttyUSB0 and/or ttyUSB1. If you do not, go no farther, and reboot to your old kernel. I cannot help you.
  6. Install the NVidia driver (if you have an NVidia card). This is normal for you to do when you upgrade
    your kernel and is not directly related to support
    for the handheld.
    1. Log in and become root, but do not start X-Windows.
    2. Navigate to the directory with the NVidia driver in it.
    3. Execute the NVidia*.run file using sh NVidia*.run. Replace the * with the remainder of the real filename.
    4. Follow the instructions. Do not panic if it takes a while to work, and do not be surprised if it does not find a precompiled binary for your kernel. It will compile one. This is very impressive work from NVidia.
    5. Start X-Windows, probably using "startx". You should see the NVidia splash screen and be in business.
  7. Build and install pilot-link.
    1. Uncompress the pilot-link software using "tar tvfz" to test the file then "tar xvfz" to uncompress it.
    2. Enter the directory. Do the "./configure" then "make" steps.
    3. Use checkinstall to install it as an RPM by running "checkinstall make install". Follow directions and choose R for creating RPM. Even if you have an older version of pilot-link installed, this will overwrite it with this newer version. Just be sure to remove the pilot-link-devel package if you have one installed with the older version name.
  8. Set the USB port to be readable and writable.
    1. Become root.
    2. Go to the devices directory "cd /dev".
    3. Set the ttyUSB0 and ttyUSB1 devices to be universally readable and writable by running "chmod 777 /dev/ttyUSB0" and "chmod 777 /dev/ttyUSB1".
    4. Create a symbolic link for "pilot" to the ttyUSB0 device. If you already have one for another Palm device, remove that link first by running "rm /dev/pilot".
      Create the link by running "ln -s /dev/ttyUSB0 /dev/pilot".
  9. Test pilot-link. Type "pilot-xfer -l" but do not push Enter.
    Push the HotSync button and wait 3 seconds. It takes that long to connect up to the USB subsystem.
    Now push Enter. You should see a list of packages installed on the handheld. If so, it is working and ready for JPilot.

  10. Build and install jpilot.
    1. Get the source from http://jpilot.org/
    2. Uncompress it, "./configure" it, and "make" it.
    3. Use "checkinstall make install" to build an RPM and install it. Remember to choose R for RPM during the interactive process.
  11. Configure JPilot. Open the Preferences box under File. Set the connector to be /dev/pilot.
  12. How to Sync: Whether you are syncing or restoring old Palm data to your new device, here is how it must work:
    1. Click the hotsync button on the cradle.
    2. WAIT for three seconds for it to connect up to the USB subsystem. Counting helps. Until that button is pushed and the few seconds pass, Linux will not have a USB device at /dev/ttyUSB0 or /dev/pilot that is linked to it.
    3. Push the Sync button on JPilot.
  13. Mounting the Memory Stick This kernel supports mounting of the memory stick.
    1. Run "modprobe usb-storage", "modprobe sg" and "modprobe sd_mod". These set up SCSI filesystem support for the memory stick.
    2. Put the Clie in the cradle, run the MS Import utility.
    3. The MS Import application should show you are connected.
    4. Make a directory to mount to. E.g. "mkdir /mnt/memorystick".
    5. "mount -t vfat /dev/sda1/ /mnt/memorystick/" to mount. It may take a few tries to work.
    6. When you are finished copying data, remember to "umount /dev/memorystick"
    7. Then choose Disconnect on the MS Import on the Clie.
  14. All of my USB devices broke! I found that a few days after using this setup, none of my USB devices would work anymore. The /var/log/messages would show nothing happening when removing or plugging in a USB device. I found that rebooting the machine, running "depmod -a" then an "ldconfig" fixed this in at least one case.

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <embed> <object> <param>
  • Lines and paragraphs break automatically.
  • You can use BBCode tags in the text. URLs will automatically be converted to links.

More information about formatting options

CAPTCHA
Be ye bot or be ye not?