fieldyweb

[Log in to get rid of this advertisement]

I installed this produce following these instructions found at:

http://synce.sourceforge.net/synce/howto.php

Install instructions

2. Installation of the SynCE software

Please note that this HOWTO is not yet finished!

For the time being, this part is very brief!

If you are running an RPM-based Linux distributions such as the ones in this list, install the latest RPM version of SynCE:

* Fedora
* RedHat
* Suse
* Mandrake

If you are running Debian Testing or Unstable, the latest version of SynCE should be available in your repository.

If you are running Gentoo, there is an ebuild for SynCE, but make sure it uses the latest SynCE version!

Went to the RPM Page, at http://synce.sourceforge.net/synce/rpms.php

And followed these instructions

SynCE - installing RPM packages

The RPM packages are for normal users only. Developers should compile the SynCE modules from source code.

Note: X.X-X is used as version number below. You will have to substitute this for the version you are installing.

1. Visit the project filelist (will be opened in a separate window) and download the following RPM packages:

* synce-X.X-X.i386.rpm (Note: this package includes the modules libsynce, librapi2, dccm, serial and rra.)
* synce-multisync_plugin-X.X-X.i386.rpm (for address book synchronization)
* synce-trayicon-X.X-X.i386.rpm (suggested for GNOME 2.x users)
* synce-gnomevfs-X.X-X.i386.rpm (suggested for GNOME 2.x users)
2. Make sure you are running as the root user.
3. Install the packages:

rpm -Uvh synce*.rpm

This command however didn't work, until i downloaded and installed Multisync RPM from

http://rpm.pbone.net/index.php3/stat/4/idpl/2113718/com/multisync-0.82-1.fc4.i386.rpm.html

Once that was installed, i ran the command


rpm -Uvh synce*.rpm

And it installed, so then went back to the SynCe Page and completed ithe install:

Find out USB information about your device

In order to find out if your Linux kernel is ready for your Windows CE device you shall connect the Windows CE device to the PC with the USB cable, but first you should save a list of the current USB devices, to make it easy to find the new device. Run this command:

cat /proc/bus/usb/devices > /tmp/before

Now connect your Windows CE device and make sure it is turned on. Wait a few seconds and run a similar command to get the list of USB devices including the Windows CE device:

cat /proc/bus/usb/devices > /tmp/after

After running the command above you should disconnect your Windows CE device.

Now you shall compare the two files to find out the USB information about your device:

diff /tmp/before /tmp/after

The output from the above command will look something like this:

23a24,31
> T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 10 Spd=12 MxCh= 0
> D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
> P: Vendor=049f ProdID=0003 Rev= 0.00
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
> I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ipaq
> E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 16 Ivl=0ms
>

Important parts of the output have been marked with red color, and may be referenced in the instructions below.
The number of USB configurations

First look at the value of #Cfgs=. If it's 1, skip to The Driver entry below! If it's 2 or more, please send a mail to synce-devel@lists.sourceforge.net and tell us:

1. brand and model of your device
2. the output from diff /tmp/before /tmp/after
3. if it worked properly with this HOWTO

The Driver entry

Second you look at the Driver entry. Read more in the apropriate section below.

Driver=ipaq or Driver=usbserial Your kernel driver recognized your device, good!

Driver=(none) Your kernel driver did not recognize your device. You need to perform some special configuration:

1.

Only if your Linux kernel is 2.6.10 or later: please send a mail to synce-devel@lists.sourceforge.net and tell us...
1. your kernel version
2. brand and model of your device
3. vendor/product USB IDs for your device (see Vendor= and ProdID=)
2.

Follow the instructions in Appendix A to add options like this, but replace the red digits with the corresponding ones from the output from the command you ran earlier:

vendor=0x049f product=0x0003

3.

If you have the file /etc/rc.local, open it with a text editor and add this line in order to have things working directly next time you restart your computer:

/sbin/modprobe ipaq

4.

Now run these commands to reload the ipaq module:

rmmod ipaq
modprobe ipaq

If you get the message ERROR: Module ipaq does not exist in /proc/modules when running the rmmod command, just ignore it.
5.

If you got no output from the modprobe command (meaning it succeeded), restart this HOWTO from the Find out USB information about your device section.
6.

If you get the message FATAL: Module ipaq not found, download kernel-2.6-driver.tar.gz, extract and follow the instructions in the README file.
7.

If you got another error message, ask for help!

Another Driver entry Ask for help!

The number of USB endpoints

Next you look at the #EPs= entry or count the number of lines beginning with E:, meaning the number of USB endpoints:

Two or three USB endpoints Nothing to do here, good!

Four USB endpoints You need some special action here. Either follow Stefan Langeland's instructions or these:

First, even if you already did this in the Linux distribution section, download kernel-2.6-driver.tar.gz, extract, replace the file free_len_zero.patch with mitac_mio168.patch, and follow the instructions in the README file.

Second, follow the instructions in Appendix A to add the following option to the kernel module:

ttyUSB=1

Now unload the kernel module and load it again:

rmmod ipaq
modprobe ipaq

No output from the above commands means success.

Note: The support for devices with four USB enpoints will be simplied in the future!

Another number of endpoints Ask for help!

4. Configuration of the connection

Please note that this HOWTO is not yet finished!

Everything in this section should be performed as the root user.

1. Connect your Windows CE device
2.

Try the following synce-serial-config commands until one of them succeed:
* synce-serial-config ttyUSB0
* synce-serial-config tts/USB0
* synce-serial-config usb/tts/0
* synce-serial-config usb/ttyUSB0

Important! If you had four USB endpoints in the USB information for your device instead of the usual two, you should use 1 instead of 0 in the command above!

If you get the error message synce-serial-config was unable to find a character device named..., ask for help!

This does not have to be done again on your system unless your device appears on a different tty for some reason.
5. Starting the connection

For the time being, this part is very brief!

1.

As your own user (not root), start dccm:

dccm (if your device is not password-protected)
dccm -p password (if your device is password-protected)

This must be done after each time you have rebooted your computer.
2. Connect your Windows CE device
3.

As root, run this command:

synce-serial-start

6. Testing the connection

Applications and tools (except for synce-serial-*) that use SynCE must be executed by the same user as is running dccm (not root).

As your own user (not root), try this command:

pstatus (not on Debian)
synce-pstatus (on Debian, in the librapi2-tools package)

If you successfully got information about your device, congratulations for enduring all the quirks involved in setting up SynCE! :-)

Now is a good time to play with the other command line tools included with SynCE. However, don't forget steps 7 and 8 below!

If you get the message below, the connection failed, and you should make sure that you followed all the steps in this HOWTO properly.

pstatus: Unable to initialize RAPI: An unspecified failure has occurred

If you truly did follow the HOWTO, you may want to get help.
7. Disconnection

In order to properly disconnect your device, you should first close the network connection between Windows CE and SynCE. There are a couple of ways to do this.

Just unplugging the USB cable is not proper disconnection when using SynCE. (This will hopefully be fixed in the kernel driver some day.)

Before you unplug the cable you should do one of these actions, in order of preference:

1. Disconnect with the GNOME Tray Icon or with SynCE-KDE
2. Disconnect with the appropriate action on your PDA
3. Run killall -HUP dccm from the command line
4. Run synce-serial-abort. Please note that this command is only to be used when everything else fails. It also seems like it only works for USB connections while the USB cable is connected.


from the command line i can view, copy over files etc to this PDA, i am in the process of getting Evolution and Multisynce to work... Seems to be a little harder, however comms with the PDA and FC4 are working

LuisC-SM

I'm wondering where is APENDIX A, the red colors of (what)?...
It's always nice to find people who is willing to do this but please, revise this nice howto, it's very confused.

Keep on with this good job.

Luis C. Suarez