Another howto, folks:
Before you get started:
The Sony Clie' PEG-S360 is just recently supported in kernel 2.4.20, so you'll need to patch your exisiting Slack8.1 kernel source (2.4.18) with the 2.4.19 and 2.4.20 patches, then compile and install. There is a wealth of info on just how to do this on this forum and others.
After you're up and running with kernel 2.4.20, let's get started setting-up your Sony PDA:
1.) Set-up your USB system:
a.) Edit /etc/rc.d/rc.modules and uncomment-out the lines referencing to usb-uhci (Intel and VIA chips) and usbserial.
b.) Add the following line to the same file, just below usbserial:
2.) Turn on your Sony Clie', plug it in, then reboot.
3.) Check to make sure the required USB modules are loaded:
You need to verify that usbcore, usb-uhci, visor, and usbserial modules are loaded. If you're missing any of these, go back and check your /etc/rc.d/rc.modules file.
4.) Let's test it. Perform a hotsync on your Clie' by selecting it from the main menu. Then (as root):
$ dmesg |grep usb
You should see something similar to this:
Jan 2 13:46:03 kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter detected
Jan 2 13:46:03 kernel: visor.c: Handspring Visor / Palm 4.0 / Cli� 4.x: Number of ports: 2
Jan 2 13:46:03 kernel: visor.c: Handspring Visor / Palm 4.0 / Cli� 4.x: port 1, is for Generic use and is bound to ttyUSB0
Jan 2 13:46:03 kernel: visor.c: Handspring Visor / Palm 4.0 / Cli� 4.x: port 2, is for HotSync use and is bound to ttyUSB1
Jan 2 13:46:03 kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
Jan 2 13:46:03 kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
Got it? good...now let's move on...
5.) If you want to have access to your PDA as user, you'll need to perform the following as root:
$ chmod 666 /dev/ttyUSB1
(my PDA is bound to /dev/ttyUSB1 as shown above...yours might differ)
6.) As of this writing, the ONLY program I've found that works with the PEG-S360 is Pilot-Link 0.11.6...so grab yourself a copy from:
Untar the file, cd to it's directory, then do the usual:
$ make install
7.) Now that you've got Pilot-Link installed, let's test it:
$ dlpsh -p /dev/ttyUSB1
With regards to /dev/ttyUSB?, again, you need to check this with the message you got in step 4. Yours might be different.
If all went well, your PDA will make the hotsync-sound and you will be dumped into the pilot-link "DLP shell". Good so far? OK. Now exit the DLP shell by typing:
8.) Pilot-link has no front-end (that I know of), so I'm using JPilot. Get it:
Install it the same way you did with Pilot-Link above.
8.) JPilot will not work with the Clie' PEG-S360 on it's own. This is where Pilot-Link comes in.
First, we need to create the .jpilot directory in your home directory. As user:
JPilot should open up on the desktop and you should see an empty conduit. That's fine. JPilot has now created an empty .jpilot directory for you in your home directory. Close JPilot.
9.) Let's populate that .jpilot directory with the contents of your Clie':
Do a hotsync on your PDA, then immediately after, pull up a console and as user:
$ pilot-xfer -p /dev/ttyUSB1 -b ~/.jpilot
You should now see messages scroll by indicating that your Clie' is backing-up it's contents to the .jpilot directory in your home directory. When the backup is finished, run JPilot
10.) And there you are...all of your info is now loaded into JPilot's interface where you can edit and save as you will.
When you're ready to upload info from JPilot into your Clie, as user:
$ pilot-xfer -p /dev/ttyUSB1 -r ~/.jpilot
- This is obviously a work-around, as support for the Clie' PEG-S360 isn't out there yet (as of this writing), but it's better than nothing. Be sure to read all the readme's with both JPilot and Pilot-Link.