I have been playing with synCE the last few days and can provide some details on how to get it working, what you should see, etc. jonboy's link looks good, I didn't have to recompile the kernel to get my AXIM talking to my RedHat box.
If you have kernel version 2.4.20 and greater, you can try using this instead of recompiling the ipaq kernel module .....
((Details were better
here for getting the Linux stuff going))
insmod usbserial
(I like modprobe usbserial, personally - you may already have another usbserial device running. My VFD is connected via usbserial, for instance.)
then
insmod ipaq vendor=0x413c product=0x3001
This
should load the ipaq kernel module for the Axim. I would suggest tailing the system message file while doing this, so you can watch what happens...
in a new terminal window type:
tail -f /var/log/messages
You should see your workstation detect the Axim.
Captured output:
# insmod ipaq vendor=0x413c product=0x3001
Using /lib/modules/2.4.20-8smp/kernel/drivers/usb/serial/ipaq.o
# tail -f /var/log/messages
kernel: usbserial.c: PocketPC PDA converter detected
kernel: usbserial.c: PocketPC PDA converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
/etc/hotplug/usb.agent: Setup ipaq for USB product 413c/4001/0
devlabel: devlabel service started/restarted
kernel: usbserial.c: USB Serial deregistering driver PocketPC PDA
kernel: usbserial.c: PocketPC PDA converter now disconnected from ttyUSB0
kernel: ipaq.c: USB PocketPC PDA driver v0.5
kernel: usbserial.c: USB Serial support registered for PocketPC PDA
Now you can configure the SynCE program. This output in the system message file tells you which port to configure synce to use ....
[I] synce-serial-config ttyUSB0 [/]
followed by
synce-serial-start
You will see:
synce-serial-start is now waiting for your device to connect
You may also receive a warning about your firewall rules. The SynCE website gives you some hint about fixing that.
:exc:
Safety Tip
The SynCE application(s) require you to NOT be ROOT when you're working with the tools that access the PDA. That being said you have to run 'dccm' as a a non-privledged user. This 'dccm' application is what created the RAPI that someone above referenced. Before you run synce-serial-start you ned to have 'dccm' running.
Once you've done all this you should see something like this in your /var/log/messages file....
kernel: CSLIP: code copyright 1989 Regents of the University of California
kernel: PPP generic driver version 2.4.2
pppd[10854]: pppd 2.4.1 started by root, uid 0
pppd[10854]: Serial connection established.
pppd[10854]: Using interface ppp0
pppd[10854]: Connect: ppp0 <--> /dev/ttyUSB0
/etc/hotplug/net.agent: assuming ppp0 is already up
kernel: PPP Deflate Compression module registered
pppd[10854]: local IP address 192.168.131.102
pppd[10854]: remote IP address 192.168.131.201
You should have a 'Connected' message on the AXIM at this point.
Back over in the terminal window you ran 'dccm' from you can now issue a 'pstatus' and you can look at the output...
$ pstatus
Version
=======
Version: 3.0.11171 (Merlin: Pocket PC 2002)
Platform: 3 (Windows CE)
Details: ""
System
======
Processor architecture: 5 (ARM)
Processor type: 2577 (StrongARM)
Page size: 0x10000
Power
=====
ACLineStatus: 01 (Online)
.....
jonboy's tip on pcp and CAB files can be used and you can download the KDE or GNOME tools you like from synCE's sourceforge website.
dlaw...
... the WiFi thing is pretty easy actually, but you first have to sync via USB to create the partnership and the registry ID's on the server. After that you can sync via WiFi...
...catching my breath from all the typing...