Discussion:
[Synce-devel] Cannot establish PPP with WM5
Paul Stanisci
2007-11-13 23:00:49 UTC
Permalink
Hello,

I have an iPaq rx1950 which I'd like to sync with kmail on Ubuntu 7.10.
Everything seems to work fine until synce tries to establish the PPP
connection, which fails almost immediately:

---- SNIP ----
Nov 13 17:30:46 nox kernel: [ 1680.181474] PPP generic driver version 2.4.2
Nov 13 17:30:46 nox kernel: [ 1680.264218] ip_tables: (C) 2000-2006 Netfilter
Core Team
Nov 13 17:30:46 nox synce-serial-start: Executing '/usr/sbin/pppd call
synce-device'
Nov 13 17:30:46 nox pppd[6984]: pppd 2.4.4 started by root, uid 0
Nov 13 17:30:47 nox pppd[6984]: Serial connection established.
Nov 13 17:30:47 nox pppd[6984]: Using interface ppp0
Nov 13 17:30:47 nox pppd[6984]: Connect: ppp0 <--> /dev/ttyUSB0
Nov 13 17:30:48 nox kernel: [ 1682.154953] PPP BSD Compression module
registered
Nov 13 17:30:48 nox kernel: [ 1682.231406] PPP Deflate Compression module
registered
Nov 13 17:30:48 nox pppd[6984]: Cannot determine ethernet address for proxy
ARP
Nov 13 17:30:48 nox pppd[6984]: local IP address 192.168.131.102
Nov 13 17:30:48 nox pppd[6984]: remote IP address 192.168.131.201
Nov 13 17:30:51 nox pppd[6984]: LCP terminated by peer
Nov 13 17:30:51 nox pppd[6984]: Connect time 0.1 minutes.
Nov 13 17:30:51 nox pppd[6984]: Sent 400 bytes, received 986 bytes.
Nov 13 17:30:54 nox pppd[6984]: Connection terminated.
Nov 13 17:30:54 nox pppd[6984]: Modem hangup
Nov 13 17:30:54 nox pppd[6984]: Exit.
---- SNIP ----

synce was configured sying synce-serial-config, and produced the ppp
configuration file "/etc/ppp/peers/synce-device":

---- SNIP ----
# Modifications to this file will be lost next time you run
synce-serial-config
/dev/ttyUSB0 115200
connect '/usr/bin/synce-serial-chat'
nodefaultroute
noauth
local
192.168.131.102:192.168.131.201
ms-dns 192.168.131.102
crtscts
linkname synce-device
#debug
#kdebug 255
---- SNIP ----

(I added the debug settings)

I've read that this could be a password setting, but there is no password set
on my PDA.


The device is recognized by the kernel's ipaq module and is assigned as
ttyUSB0:

---- SNIP ----
Nov 13 17:30:33 nox kernel: [ 1667.615205] usb 5-4.1: new full speed USB
device using ehci_hcd and address 13
Nov 13 17:30:35 nox kernel: [ 1669.679567] usb 5-4.1: configuration #1 chosen
from 1 choice
Nov 13 17:30:35 nox kernel: [ 1669.680453] ipaq 5-4.1:1.0: PocketPC PDA
converter detected
Nov 13 17:30:35 nox kernel: [ 1669.680983] usb 5-4.1: PocketPC PDA converter
now attached to ttyUSB0
---- SNIP ----


vdccm is running, but outputs nothing during my connection attempt:

---- SNIP ----
dccm -f -d 3
dccm[7290]: Running in foreground
dccm[7290]: Listening for connections on port 5679

---- SNIP ----


While connected, the usbserial driver displays the vendor and product ID:

---- SNIP ----
cat ./tty/driver/usbserial
usbserinfo:1.0 driver:2.0
0: module:ipaq name:"PocketPC PDA" vendor:03f0 product:1016 num_ports:1 port:1
path:usb-0000:00:1a.7-4.1
---- SNIP ----

I tried load the module with specifying the vendor and product, but it didn't
help:

# modprobe ipaq vendor=0x03f0 product=0x1016


Here is my device's lsusb output:

---- SNIP ----
Bus 005 Device 012: ID 03f0:1016 Hewlett-Packard Jornada 548 / iPAQ HW6515
Pocket PC
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x03f0 Hewlett-Packard
idProduct 0x1016 Jornada 548 / iPAQ HW6515 Pocket PC
bcdDevice 0.00
iManufacturer 1 HP
iProduct 2 Generic Serial
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0001
Self Powered
---- SNIP ----


My iPaq's synchronization mode is set to usb-serial mode. There is no password
set as far as I can tell. Does someobdy have any idea why this isn't working?

I can supply a log file with kernel & ppp debugging output if it helps.

Thanks,

~Paul

--
Paul Stanisci
2byteconsulting.com
Paul Stanisci
2007-11-14 01:45:05 UTC
Permalink
I see the version of synce in Ubuntu 7.10 is only 0.9, which does not support
WM5. I believe I think I should be using synce 0.10, but no apt sources exist
for this version. Could this explain the failure to establish a PPP
connection to the device?

Have any Ubuntu/Kubuntu 7.10 users succesfully used the version of synce from
the repository with a WM5 device?

I'll try compiling the latest synce from source..

~Paul
Paul Stanisci
2007-11-14 02:32:23 UTC
Permalink
Another follow up to my previous post.

I removed the Ubuntu synce packages to try and get synce workign with version
0.10 compiled from source.


I installed the following packages from the sourceforge sources:

libsynce-0.10.0
synce-sync-engine-0.10.0
synce-serial-0.10.0
odccm-0.10.0

All the packages built and installed once their depedencies were installed.
However I could not get odccm to start:

# odccm -f

** ERROR **: Failed to get bus name: Connection ":1.35" is not allowed to own
the service "org.synce.odccm" due to security policies in the configuration
file aborting...
Aborted (core dumped)

I've tried executing odccm as my normal user and root. Each time I run it, the
number following 'Connection ":1.' changes, seemlingly incremental by one on
each try.

I installed vdccm so I could finish the testing.

Once complete, I plugged in the ipaq:

--- SNIP ---
Nov 13 21:27:18 nox kernel: [ 8375.665888] usb 1-4.2: new full speed USB
device using ehci_hcd and address 20
Nov 13 21:27:18 nox kernel: [ 8375.760104] usb 1-4.2: configuration #1 chosen
from 1 choice
Nov 13 21:27:18 nox kernel: [ 8375.761017] ipaq 1-4.2:1.0: PocketPC PDA
converter detected
Nov 13 21:27:18 nox kernel: [ 8375.761539] usb 1-4.2: PocketPC PDA converter
now attached to ttyUSB0
1-4.2: PocketPC PDA converter now attached to ttyUSB0
--- SNIP ---

Executed vdccm:

$ vdccm -f -d 3

Configured and ran the connection script:

--- SNIP ---
$ sudo synce-serial-config ttyUSB0

You can now run synce-serial-start to start a serial connection.

$ sudo synce-serial-start

synce-serial-start is now waiting for your device to connect
--- SNIP ---

This time the device did indeed connect! The connection progress pop-up was
shown on the ipaq, and once complete the activesync icon was shown.

PPP output:

--- SNIP ---
Nov 13 21:28:11 nox synce-serial-start: Executing '/usr/sbin/pppd call
synce-device'
Nov 13 21:28:11 nox pppd[2981]: pppd 2.4.4 started by root, uid 0
Nov 13 21:28:12 nox pppd[2981]: Serial connection established.
Nov 13 21:28:12 nox pppd[2981]: Using interface ppp0
Nov 13 21:28:12 nox pppd[2981]: Connect: ppp0 <--> /dev/ttyUSB0
Nov 13 21:28:13 nox kernel: [ 8430.512079] PPP BSD Compression module
registered
Nov 13 21:28:13 nox kernel: [ 8430.599441] PPP Deflate Compression module
registered
Nov 13 21:28:13 nox pppd[2981]: local IP address 192.168.131.102
Nov 13 21:28:13 nox pppd[2981]: remote IP address 192.168.131.201
--- SNIP ---


Hopefully this is helpful for other people using WM5 and Ubuntu. The packages
are just too old, and I can't seem to find alternate sources for packages
based on the 0.10 release.

If some do exist, please let me know. I'll contact the package maintainers to
ask about upgrading synce in Ubuntu.

I'd still appreciate any help on why odccm fails to run... Please let me know
if I can help with debugging.

Thanks,

~Paul
Post by Paul Stanisci
I see the version of synce in Ubuntu 7.10 is only 0.9, which does not
support WM5. I believe I think I should be using synce 0.10, but no apt
sources exist for this version. Could this explain the failure to establish
a PPP connection to the device?
Have any Ubuntu/Kubuntu 7.10 users succesfully used the version of synce
from the repository with a WM5 device?
I'll try compiling the latest synce from source..
~Paul
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel
--
--
Paul Stanisci
System Samurai
Owner & Senior Consultant
2byteconsulting.com
c: 613.301.3134
John Carr
2007-11-14 05:43:01 UTC
Permalink
Hi

I'm in the process of prepping jonnylambs debian packages for upload to
launchpad - they will (in theory) support every supported version of
Ubuntu.

We strongly suggest trying to get odccm working. As far as I know its
the only way to sync at the moment(?). Also, vdccm may be gone in 0.11 -
so its important you help us work out any kinks! Because you are running
your device in legacy mode you will need to use the SVN version of
odccm, and there is a switch to turn on legacy mode...

Is there any reason you aren't using RNDIS mode on your phone/pda? That
is supported for most devices, is faster, and removes the step of having
to start a PPP connection.

John
Post by Paul Stanisci
Another follow up to my previous post.
I removed the Ubuntu synce packages to try and get synce workign with version
0.10 compiled from source.
libsynce-0.10.0
synce-sync-engine-0.10.0
synce-serial-0.10.0
odccm-0.10.0
All the packages built and installed once their depedencies were installed.
# odccm -f
** ERROR **: Failed to get bus name: Connection ":1.35" is not allowed to own
the service "org.synce.odccm" due to security policies in the configuration
file aborting...
Aborted (core dumped)
I've tried executing odccm as my normal user and root. Each time I run it, the
number following 'Connection ":1.' changes, seemlingly incremental by one on
each try.
I installed vdccm so I could finish the testing.
--- SNIP ---
Nov 13 21:27:18 nox kernel: [ 8375.665888] usb 1-4.2: new full speed USB
device using ehci_hcd and address 20
Nov 13 21:27:18 nox kernel: [ 8375.760104] usb 1-4.2: configuration #1 chosen
from 1 choice
Nov 13 21:27:18 nox kernel: [ 8375.761017] ipaq 1-4.2:1.0: PocketPC PDA
converter detected
Nov 13 21:27:18 nox kernel: [ 8375.761539] usb 1-4.2: PocketPC PDA converter
now attached to ttyUSB0
1-4.2: PocketPC PDA converter now attached to ttyUSB0
--- SNIP ---
$ vdccm -f -d 3
--- SNIP ---
$ sudo synce-serial-config ttyUSB0
You can now run synce-serial-start to start a serial connection.
$ sudo synce-serial-start
synce-serial-start is now waiting for your device to connect
--- SNIP ---
This time the device did indeed connect! The connection progress pop-up was
shown on the ipaq, and once complete the activesync icon was shown.
--- SNIP ---
Nov 13 21:28:11 nox synce-serial-start: Executing '/usr/sbin/pppd call
synce-device'
Nov 13 21:28:11 nox pppd[2981]: pppd 2.4.4 started by root, uid 0
Nov 13 21:28:12 nox pppd[2981]: Serial connection established.
Nov 13 21:28:12 nox pppd[2981]: Using interface ppp0
Nov 13 21:28:12 nox pppd[2981]: Connect: ppp0 <--> /dev/ttyUSB0
Nov 13 21:28:13 nox kernel: [ 8430.512079] PPP BSD Compression module
registered
Nov 13 21:28:13 nox kernel: [ 8430.599441] PPP Deflate Compression module
registered
Nov 13 21:28:13 nox pppd[2981]: local IP address 192.168.131.102
Nov 13 21:28:13 nox pppd[2981]: remote IP address 192.168.131.201
--- SNIP ---
Hopefully this is helpful for other people using WM5 and Ubuntu. The packages
are just too old, and I can't seem to find alternate sources for packages
based on the 0.10 release.
If some do exist, please let me know. I'll contact the package maintainers to
ask about upgrading synce in Ubuntu.
I'd still appreciate any help on why odccm fails to run... Please let me know
if I can help with debugging.
Thanks,
~Paul
Post by Paul Stanisci
I see the version of synce in Ubuntu 7.10 is only 0.9, which does not
support WM5. I believe I think I should be using synce 0.10, but no apt
sources exist for this version. Could this explain the failure to establish
a PPP connection to the device?
Have any Ubuntu/Kubuntu 7.10 users succesfully used the version of synce
from the repository with a WM5 device?
I'll try compiling the latest synce from source..
~Paul
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel
--
--
Paul Stanisci
System Samurai
Owner & Senior Consultant
2byteconsulting.com
c: 613.301.3134
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel
Paul Stanisci
2007-11-14 14:45:36 UTC
Permalink
Hello John,

Thanks for your reply.

My original attempts at using the rndis driver weren't very sucessful:

My kernel's built in rndis driver:
--- SNIP ----
Nov 14 09:38:07 nox kernel: [52181.556776] usb 1-4.2: new full speed USB
device using ehci_hcd and address 22
Nov 14 09:38:07 nox kernel: [52181.651319] usb 1-4.2: configuration #1 chosen
from 1 choice
Nov 14 09:38:07 nox kernel: [52181.756495] rndis_host: probe of 1-4.2:1.0
failed with error -110
--- SNIP ----

The RNDIS Lite driver from sourceforge:
--- SNIP ---
Nov 14 09:42:03 nox kernel: [52416.856180] usb 1-4.2: new full speed USB
device using ehci_hcd and address 26
Nov 14 09:42:03 nox kernel: [52416.950279] usb 1-4.2: configuration #1 chosen
from 1 choice
Nov 14 09:42:03 nox kernel: [52417.035889] rndis_host: probe of 1-4.2:1.0
failed with error -110
--- SNIP ---

I was a little confused as to which connection method I should be using, I
never found a good comparison between the two.

I decided to use the ipaq driver since the device did successfully connect.
However if rndis is better I can try to get it working instead.

As for odccm, I'll download the latest sources from SVN and give them a shot.
I may have the time to do that tonight.

Let me know if you want me to test your deb packages.

~Paul
Post by John Carr
Hi
I'm in the process of prepping jonnylambs debian packages for upload to
launchpad - they will (in theory) support every supported version of
Ubuntu.
We strongly suggest trying to get odccm working. As far as I know its
the only way to sync at the moment(?). Also, vdccm may be gone in 0.11 -
so its important you help us work out any kinks! Because you are running
your device in legacy mode you will need to use the SVN version of
odccm, and there is a switch to turn on legacy mode...
Is there any reason you aren't using RNDIS mode on your phone/pda? That
is supported for most devices, is faster, and removes the step of having
to start a PPP connection.
John
Post by Paul Stanisci
Another follow up to my previous post.
I removed the Ubuntu synce packages to try and get synce workign with
version 0.10 compiled from source.
libsynce-0.10.0
synce-sync-engine-0.10.0
synce-serial-0.10.0
odccm-0.10.0
All the packages built and installed once their depedencies were
# odccm -f
** ERROR **: Failed to get bus name: Connection ":1.35" is not allowed to
own the service "org.synce.odccm" due to security policies in the
configuration file aborting...
Aborted (core dumped)
I've tried executing odccm as my normal user and root. Each time I run
it, the number following 'Connection ":1.' changes, seemlingly
incremental by one on each try.
I installed vdccm so I could finish the testing.
--- SNIP ---
Nov 13 21:27:18 nox kernel: [ 8375.665888] usb 1-4.2: new full speed USB
device using ehci_hcd and address 20
Nov 13 21:27:18 nox kernel: [ 8375.760104] usb 1-4.2: configuration #1
chosen from 1 choice
Nov 13 21:27:18 nox kernel: [ 8375.761017] ipaq 1-4.2:1.0: PocketPC PDA
converter detected
Nov 13 21:27:18 nox kernel: [ 8375.761539] usb 1-4.2: PocketPC PDA
converter now attached to ttyUSB0
1-4.2: PocketPC PDA converter now attached to ttyUSB0
--- SNIP ---
$ vdccm -f -d 3
--- SNIP ---
$ sudo synce-serial-config ttyUSB0
You can now run synce-serial-start to start a serial connection.
$ sudo synce-serial-start
synce-serial-start is now waiting for your device to connect
--- SNIP ---
This time the device did indeed connect! The connection progress pop-up
was shown on the ipaq, and once complete the activesync icon was shown.
--- SNIP ---
Nov 13 21:28:11 nox synce-serial-start: Executing '/usr/sbin/pppd call
synce-device'
Nov 13 21:28:11 nox pppd[2981]: pppd 2.4.4 started by root, uid 0
Nov 13 21:28:12 nox pppd[2981]: Serial connection established.
Nov 13 21:28:12 nox pppd[2981]: Using interface ppp0
Nov 13 21:28:12 nox pppd[2981]: Connect: ppp0 <--> /dev/ttyUSB0
Nov 13 21:28:13 nox kernel: [ 8430.512079] PPP BSD Compression module
registered
Nov 13 21:28:13 nox kernel: [ 8430.599441] PPP Deflate Compression module
registered
Nov 13 21:28:13 nox pppd[2981]: local IP address 192.168.131.102
Nov 13 21:28:13 nox pppd[2981]: remote IP address 192.168.131.201
--- SNIP ---
Hopefully this is helpful for other people using WM5 and Ubuntu. The
packages are just too old, and I can't seem to find alternate sources for
packages based on the 0.10 release.
If some do exist, please let me know. I'll contact the package
maintainers to ask about upgrading synce in Ubuntu.
I'd still appreciate any help on why odccm fails to run... Please let me
know if I can help with debugging.
Thanks,
~Paul
Post by Paul Stanisci
I see the version of synce in Ubuntu 7.10 is only 0.9, which does not
support WM5. I believe I think I should be using synce 0.10, but no apt
sources exist for this version. Could this explain the failure to
establish a PPP connection to the device?
Have any Ubuntu/Kubuntu 7.10 users succesfully used the version of
synce from the repository with a WM5 device?
I'll try compiling the latest synce from source..
~Paul
-----------------------------------------------------------------------
-- This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel
--
--
Paul Stanisci
System Samurai
Owner & Senior Consultant
2byteconsulting.com
c: 613.301.3134
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel
John Carr
2007-11-14 15:33:43 UTC
Permalink
Hi Paul

There is a work around (from a synce user) for that problem in our SVN
patches folder. I've just applied it to usb-rndis-lite to get some wider
testing..

On ubuntu, this should be all you need to get going:

sudo apt-get install linux-headers-generic build-essential subversion
svn co http://synce.svn.sf.net/svnroot/synce/trunk/usb-rndis-lite
make
sudo ./clean.sh
sudo make install

After this, the version of odccm you have should work. Note that to get
around your original odccm error you probably need to go in the odccm
source directory and:

sudo cp data/dbus/odccm.conf /etc/dbus-1/system.d/

It's on the wiki somewhere, but i'm having network trouble so i can't
check...

I'll get back to you RE: the packages - they need a few more tweaks..

John
Post by Paul Stanisci
Hello John,
Thanks for your reply.
--- SNIP ----
Nov 14 09:38:07 nox kernel: [52181.556776] usb 1-4.2: new full speed USB
device using ehci_hcd and address 22
Nov 14 09:38:07 nox kernel: [52181.651319] usb 1-4.2: configuration #1 chosen
from 1 choice
Nov 14 09:38:07 nox kernel: [52181.756495] rndis_host: probe of 1-4.2:1.0
failed with error -110
--- SNIP ----
--- SNIP ---
Nov 14 09:42:03 nox kernel: [52416.856180] usb 1-4.2: new full speed USB
device using ehci_hcd and address 26
Nov 14 09:42:03 nox kernel: [52416.950279] usb 1-4.2: configuration #1 chosen
from 1 choice
Nov 14 09:42:03 nox kernel: [52417.035889] rndis_host: probe of 1-4.2:1.0
failed with error -110
--- SNIP ---
I was a little confused as to which connection method I should be using, I
never found a good comparison between the two.
I decided to use the ipaq driver since the device did successfully connect.
However if rndis is better I can try to get it working instead.
As for odccm, I'll download the latest sources from SVN and give them a shot.
I may have the time to do that tonight.
Let me know if you want me to test your deb packages.
~Paul
Post by John Carr
Hi
I'm in the process of prepping jonnylambs debian packages for upload to
launchpad - they will (in theory) support every supported version of
Ubuntu.
We strongly suggest trying to get odccm working. As far as I know its
the only way to sync at the moment(?). Also, vdccm may be gone in 0.11 -
so its important you help us work out any kinks! Because you are running
your device in legacy mode you will need to use the SVN version of
odccm, and there is a switch to turn on legacy mode...
Is there any reason you aren't using RNDIS mode on your phone/pda? That
is supported for most devices, is faster, and removes the step of having
to start a PPP connection.
John
Post by Paul Stanisci
Another follow up to my previous post.
I removed the Ubuntu synce packages to try and get synce workign with
version 0.10 compiled from source.
libsynce-0.10.0
synce-sync-engine-0.10.0
synce-serial-0.10.0
odccm-0.10.0
All the packages built and installed once their depedencies were
# odccm -f
** ERROR **: Failed to get bus name: Connection ":1.35" is not allowed to
own the service "org.synce.odccm" due to security policies in the
configuration file aborting...
Aborted (core dumped)
I've tried executing odccm as my normal user and root. Each time I run
it, the number following 'Connection ":1.' changes, seemlingly
incremental by one on each try.
I installed vdccm so I could finish the testing.
--- SNIP ---
Nov 13 21:27:18 nox kernel: [ 8375.665888] usb 1-4.2: new full speed USB
device using ehci_hcd and address 20
Nov 13 21:27:18 nox kernel: [ 8375.760104] usb 1-4.2: configuration #1
chosen from 1 choice
Nov 13 21:27:18 nox kernel: [ 8375.761017] ipaq 1-4.2:1.0: PocketPC PDA
converter detected
Nov 13 21:27:18 nox kernel: [ 8375.761539] usb 1-4.2: PocketPC PDA
converter now attached to ttyUSB0
1-4.2: PocketPC PDA converter now attached to ttyUSB0
--- SNIP ---
$ vdccm -f -d 3
--- SNIP ---
$ sudo synce-serial-config ttyUSB0
You can now run synce-serial-start to start a serial connection.
$ sudo synce-serial-start
synce-serial-start is now waiting for your device to connect
--- SNIP ---
This time the device did indeed connect! The connection progress pop-up
was shown on the ipaq, and once complete the activesync icon was shown.
--- SNIP ---
Nov 13 21:28:11 nox synce-serial-start: Executing '/usr/sbin/pppd call
synce-device'
Nov 13 21:28:11 nox pppd[2981]: pppd 2.4.4 started by root, uid 0
Nov 13 21:28:12 nox pppd[2981]: Serial connection established.
Nov 13 21:28:12 nox pppd[2981]: Using interface ppp0
Nov 13 21:28:12 nox pppd[2981]: Connect: ppp0 <--> /dev/ttyUSB0
Nov 13 21:28:13 nox kernel: [ 8430.512079] PPP BSD Compression module
registered
Nov 13 21:28:13 nox kernel: [ 8430.599441] PPP Deflate Compression module
registered
Nov 13 21:28:13 nox pppd[2981]: local IP address 192.168.131.102
Nov 13 21:28:13 nox pppd[2981]: remote IP address 192.168.131.201
--- SNIP ---
Hopefully this is helpful for other people using WM5 and Ubuntu. The
packages are just too old, and I can't seem to find alternate sources for
packages based on the 0.10 release.
If some do exist, please let me know. I'll contact the package
maintainers to ask about upgrading synce in Ubuntu.
I'd still appreciate any help on why odccm fails to run... Please let me
know if I can help with debugging.
Thanks,
~Paul
Post by Paul Stanisci
I see the version of synce in Ubuntu 7.10 is only 0.9, which does not
support WM5. I believe I think I should be using synce 0.10, but no apt
sources exist for this version. Could this explain the failure to
establish a PPP connection to the device?
Have any Ubuntu/Kubuntu 7.10 users succesfully used the version of
synce from the repository with a WM5 device?
I'll try compiling the latest synce from source..
~Paul
-----------------------------------------------------------------------
-- This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel
--
--
Paul Stanisci
System Samurai
Owner & Senior Consultant
2byteconsulting.com
c: 613.301.3134
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel
Paul Stanisci
2007-11-14 15:51:04 UTC
Permalink
Hello John,

I got the rndis-lite source from SVN, and it did work:

--- SNIP ---
Nov 14 10:44:50 nox kernel: [56180.603498] usb 1-4.2: new full speed USB
device using ehci_hcd and address 37
Nov 14 10:44:53 nox kernel: [56182.903891] usb 1-4.2: configuration #1 chosen
from 1 choice
Nov 14 10:44:54 nox kernel: [56184.531789] rndis0: register 'rndis_host' at
usb-0000:00:1a.7-4.2, RNDIS device, 80:00:60:0f:e8:00
--- SNIP ---

Odccm did work for me as well after copying the odccm dbus config, however I
had to run it as root instead of my normal user:

--- SNIP ---
$ sudo odccm -f
** (process:14124): DEBUG: PDA network interface discovered!
udi='/org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00'
** (process:14124): DEBUG: device_info_received
** (process:14124): DEBUG: 2f 44 ca 52 6d 75 84 10 85 1a da c4 4a 1a 62 1e 05
00 00 00 01 00 00 00 0a 00 00 00 6e 00 6f 00 70 00 6f 00 6c 00 65 00 73 00 70
00 61 00 71 00 00 00 05 01 a6 06 11 0a 00 00 05 00 00 00 5f 78 a2 6d 3c f8 53
11 0f 00 00 00 50 6f 63 6b 65 74 50 43 00 53 53 44 4b 00 00 0e 00 00 00 48 50
20 69 50 41 51 20 72 78 31 39 35 30 00 02 00 00 00 04 00 00 00 00 00 00 00 05
00 00 00 00 00 00 00 00 00 00 00
** (process:14124): DEBUG: device_info_received: registering object
path '/org/synce/odccm/Device/_52CA442F_756D_1084_851A_DAC44A1A621E_'
--- SNIP ---

I never did find the wiki info about that config file. I found the synce site
very fragmented. It may help others to have a page that describes the
difference between RNDIS vs USB-SERIAL. The synce wiki doesn't seem to
mention anything about ipaq.

I have some spare cycles these days, is there some way I can help??

~Paul
Post by John Carr
svn co http://synce.svn.sf.net/svnroot/synce/trunk/usb-rndis-lite
John Carr
2007-11-14 16:35:00 UTC
Permalink
Paul: The PPP stuff is under the WM2003 section, because we don't really
support PPP for 2005 devices.

All: I sat down to try and document somethings for the new wiki
(www.synce.org/moin) where we hope to consolidate everything and finally
switch off the old cruft. I got a bit stuck on my taxonomy, the desire
to be really exact for distros - making use of .debs and such, and not
duplicating too much.


**** Idea 1 ****

So I reckon there are the following sections:
* Base install
* libsynce/librapi/librra(?) and odccm
* Connecting your device
* USB RNDIS
* USB Serial
* Bluetooth PAN (no idea how this works)
* Bluetooth Serial (no idea how this works)
* Syncing your device
* Browsing your device
* Gnomevfs
* Fur
* Is there a KIO slave
* Adding and removing software
* Connecting to the internet from your device via your PC
* Connecting to the internet from your PC via your device
* Remote controlling your device (KCE Mirror)

Some of these bits will have distribution specific instructions, if not
all. So do we have a page for each distribution with a list like above?
So i'm going to setup the homepage as:

== Installation ==
* Installation on Debian/Ubuntu
* Installation on Gentoo
* Installation on other Linux's

Both will have pages as above, and where no distro specific pages exist
we link to the generic pages. I think the overhead of maintaining extra
pages is worth it to cut down on traffic on #synce and other support
areas.


**** Idea 2 ****

Homepage has the menu:

* Getting Ready
* libsynce/librapi/librra(?) and odccm
* Connecting your device
* USB RNDIS
* USB Serial
* Bluetooth PAN (no idea how this works)
* Bluetooth Serial (no idea how this works)
* Syncing your device
* Browsing your device
* Gnomevfs
* Fur
* Is there a KIO slave
* Adding and removing software
* Connecting to the internet from your device via your PC
* Connecting to the internet from your PC via your device
* Remote controlling your device (KCE Mirror)

Notes:
* Each page has the generic page (installing from tars) but first
offers links to packages/ebuilds.
* They will assume the user has followed Getting Ready which will talk
them through setting up repositories that might be needed.
* If the installation notes are long they may be delegated to a subpage
also, in which case (for example) "Syncing your device" just contains
instructions for running msynctool.

Thoughts?

Paul: Your input on beating the new wiki into shape would be
appreciated, but I want to make sure we get the structure right first.
Theres already a crufty page or two :(

Jonnylamb: Can we get synce.org rebooted or something :-\ Its dead
here...

John
Paul Stanisci
2007-11-14 16:54:43 UTC
Permalink
What about the procedure for configuring the synchronization software for
e-mail & contacts (like opensync).

As a new user, now that my device communicates with my PC, I'm still a little
confused about what's involved to perform the syncronisation with my mail
program. I realize this is outside the scope of the synce project, but the
documentation should list the programs that can use synce for syncing and
provide links their respective project websites.

Maybe the different sync tools would be mentioned under "Syncing your device"?

I do agree that the site should have instructions for installing synce in the
major distros (Gentoo, Debian/Ubuntu, RedHat/CentOS).

~Paul

BTW, synce.org is working again for me.
Post by John Carr
Paul: The PPP stuff is under the WM2003 section, because we don't really
support PPP for 2005 devices.
All: I sat down to try and document somethings for the new wiki
(www.synce.org/moin) where we hope to consolidate everything and finally
switch off the old cruft. I got a bit stuck on my taxonomy, the desire
to be really exact for distros - making use of .debs and such, and not
duplicating too much.
**** Idea 1 ****
* Base install
* libsynce/librapi/librra(?) and odccm
* Connecting your device
* USB RNDIS
* USB Serial
* Bluetooth PAN (no idea how this works)
* Bluetooth Serial (no idea how this works)
* Syncing your device
* Browsing your device
* Gnomevfs
* Fur
* Is there a KIO slave
* Adding and removing software
* Connecting to the internet from your device via your PC
* Connecting to the internet from your PC via your device
* Remote controlling your device (KCE Mirror)
Some of these bits will have distribution specific instructions, if not
all. So do we have a page for each distribution with a list like above?
== Installation ==
* Installation on Debian/Ubuntu
* Installation on Gentoo
* Installation on other Linux's
Both will have pages as above, and where no distro specific pages exist
we link to the generic pages. I think the overhead of maintaining extra
pages is worth it to cut down on traffic on #synce and other support
areas.
**** Idea 2 ****
* Getting Ready
* libsynce/librapi/librra(?) and odccm
* Connecting your device
* USB RNDIS
* USB Serial
* Bluetooth PAN (no idea how this works)
* Bluetooth Serial (no idea how this works)
* Syncing your device
* Browsing your device
* Gnomevfs
* Fur
* Is there a KIO slave
* Adding and removing software
* Connecting to the internet from your device via your PC
* Connecting to the internet from your PC via your device
* Remote controlling your device (KCE Mirror)
* Each page has the generic page (installing from tars) but first
offers links to packages/ebuilds.
* They will assume the user has followed Getting Ready which will talk
them through setting up repositories that might be needed.
* If the installation notes are long they may be delegated to a subpage
also, in which case (for example) "Syncing your device" just contains
instructions for running msynctool.
Thoughts?
Paul: Your input on beating the new wiki into shape would be
appreciated, but I want to make sure we get the structure right first.
Theres already a crufty page or two :(
Jonnylamb: Can we get synce.org rebooted or something :-\ Its dead
here...
John
John Carr
2007-11-14 17:10:23 UTC
Permalink
Post by Paul Stanisci
What about the procedure for configuring the synchronization software for
e-mail & contacts (like opensync).
Thats what the "Syncing your device" section will be for, although I
would to avoid duplicating their documentation if possible. We would
cover SynCE specific parts perhaps, or provide a sample configuration
with links to the relevant opensync documentation.
Post by Paul Stanisci
As a new user, now that my device communicates with my PC, I'm still a little
confused about what's involved to perform the syncronisation with my mail
program. I realize this is outside the scope of the synce project, but the
documentation should list the programs that can use synce for syncing and
provide links their respective project websites.
AFAIK, we don't synchronise mail. IMO, by far the best option is to look
at IMAP. You could probably download mail by IMAP through your PC's
internet connection. Gmail now provides IMAP... Of course, IMAP email is
so outside of our scope that its in your user manual!

Syncing your contacts and calendar can only be done by opensync and its
assorted GUIs and would be covered by the "Syncing your device" section.

I am aware of z-push, Funambol and ScheduleWorld, but they don't touch
any of our stack and we don't know anything about how they work so
cannot really justify spending what little time we have trying to
support them... z-push is probably the most interesting, but written in
PHP (iirc, others require installing crap on your device).
Post by Paul Stanisci
Maybe the different sync tools would be mentioned under "Syncing your device"?
Great minds think alike...
Post by Paul Stanisci
I do agree that the site should have instructions for installing synce in the
major distros (Gentoo, Debian/Ubuntu, RedHat/CentOS).
We need someone to step forward for RedHat/Fedora. Gentoo we can
probably cover based on whats in the old wiki.
Post by Paul Stanisci
~Paul
BTW, synce.org is working again for me.
Cheers
Post by Paul Stanisci
Post by John Carr
Paul: The PPP stuff is under the WM2003 section, because we don't really
support PPP for 2005 devices.
All: I sat down to try and document somethings for the new wiki
(www.synce.org/moin) where we hope to consolidate everything and finally
switch off the old cruft. I got a bit stuck on my taxonomy, the desire
to be really exact for distros - making use of .debs and such, and not
duplicating too much.
**** Idea 1 ****
* Base install
* libsynce/librapi/librra(?) and odccm
* Connecting your device
* USB RNDIS
* USB Serial
* Bluetooth PAN (no idea how this works)
* Bluetooth Serial (no idea how this works)
* Syncing your device
* Browsing your device
* Gnomevfs
* Fur
* Is there a KIO slave
* Adding and removing software
* Connecting to the internet from your device via your PC
* Connecting to the internet from your PC via your device
* Remote controlling your device (KCE Mirror)
<snip>
Paul Stanisci
2007-11-14 17:20:21 UTC
Permalink
I agree, any part of the synce documentation pertaining to opensync (or
similar) should simply explain synce's role in the operation, and leave the
rest to the other project.

I figured mail wouldn't be sync'd. :( Frankly I'm very dissapoitned with
WM5's mail support. It only supports a single account that must sync with the
local account in Outlook. It was obviously designed with corporate users in
mind who's mail account is hosted by Exchange. It turns out WM5's mail
handling was 100% useless for my purpouses since I access all my mail over
IMAP. :(

Using IMAP on my handheld always crashed or worked so slowly it was unusable.
I bought WebIS FlexMail which is very feature rich and supports IMAP, but my
handheld is too slow to run it and it often ends up crashing.

At this point I'd settle for just having the sync program copy text files of
my mail messages so I could at least read them. ;)

--
Paul Stanisci
System Samurai
Owner & Senior Consultant
2byteconsulting.com
Post by John Carr
Post by Paul Stanisci
What about the procedure for configuring the synchronization software for
e-mail & contacts (like opensync).
Thats what the "Syncing your device" section will be for, although I
would to avoid duplicating their documentation if possible. We would
cover SynCE specific parts perhaps, or provide a sample configuration
with links to the relevant opensync documentation.
Post by Paul Stanisci
As a new user, now that my device communicates with my PC, I'm still a
little confused about what's involved to perform the syncronisation with
my mail program. I realize this is outside the scope of the synce
project, but the documentation should list the programs that can use
synce for syncing and provide links their respective project websites.
AFAIK, we don't synchronise mail. IMO, by far the best option is to look
at IMAP. You could probably download mail by IMAP through your PC's
internet connection. Gmail now provides IMAP... Of course, IMAP email is
so outside of our scope that its in your user manual!
Syncing your contacts and calendar can only be done by opensync and its
assorted GUIs and would be covered by the "Syncing your device" section.
I am aware of z-push, Funambol and ScheduleWorld, but they don't touch
any of our stack and we don't know anything about how they work so
cannot really justify spending what little time we have trying to
support them... z-push is probably the most interesting, but written in
PHP (iirc, others require installing crap on your device).
Post by Paul Stanisci
Maybe the different sync tools would be mentioned under "Syncing your device"?
Great minds think alike...
Post by Paul Stanisci
I do agree that the site should have instructions for installing synce in
the major distros (Gentoo, Debian/Ubuntu, RedHat/CentOS).
We need someone to step forward for RedHat/Fedora. Gentoo we can
probably cover based on whats in the old wiki.
Post by Paul Stanisci
~Paul
BTW, synce.org is working again for me.
Cheers
Post by Paul Stanisci
Post by John Carr
Paul: The PPP stuff is under the WM2003 section, because we don't
really support PPP for 2005 devices.
All: I sat down to try and document somethings for the new wiki
(www.synce.org/moin) where we hope to consolidate everything and
finally switch off the old cruft. I got a bit stuck on my taxonomy, the
desire to be really exact for distros - making use of .debs and such,
and not duplicating too much.
**** Idea 1 ****
* Base install
* libsynce/librapi/librra(?) and odccm
* Connecting your device
* USB RNDIS
* USB Serial
* Bluetooth PAN (no idea how this works)
* Bluetooth Serial (no idea how this works)
* Syncing your device
* Browsing your device
* Gnomevfs
* Fur
* Is there a KIO slave
* Adding and removing software
* Connecting to the internet from your device via your PC
* Connecting to the internet from your PC via your device
* Remote controlling your device (KCE Mirror)
<snip>
John Carr
2007-11-14 17:33:26 UTC
Permalink
Post by Paul Stanisci
I agree, any part of the synce documentation pertaining to opensync (or
similar) should simply explain synce's role in the operation, and leave the
rest to the other project.
I figured mail wouldn't be sync'd. :( Frankly I'm very dissapoitned with
WM5's mail support. It only supports a single account that must sync with the
local account in Outlook. It was obviously designed with corporate users in
mind who's mail account is hosted by Exchange. It turns out WM5's mail
handling was 100% useless for my purpouses since I access all my mail over
IMAP. :(
Using IMAP on my handheld always crashed or worked so slowly it was unusable.
I bought WebIS FlexMail which is very feature rich and supports IMAP, but my
handheld is too slow to run it and it often ends up crashing.
At this point I'd settle for just having the sync program copy text files of
my mail messages so I could at least read them. ;)
How odd. When I had WM5 i only ever had POP3 accounts, and could have
multiple accounts. WM6 has multiple IMAP accounts for sure - my main
host and Gmail are playing nicely, if a tad slow over GPRS.

z-push might be suited to your mail needs - iirc it can act as a
ActiveSync to IMAP bridge. At some point i'd like to try and port the
relevant bits of code...

John
Paul Stanisci
2007-11-14 17:05:41 UTC
Permalink
John,

A few more thoughts...

I don't believe there is a place in the breakdown below for a compatability
list. The current WM5 device list on the synce.org wiki mentiones only HTC
devices. There are obviously more devices like the ipaq that can connect to
synce.

Also, under "Base Install", should a sub page be created to explain the
difference between vdccm and odccm, and when to use each one? Should users
of non-WM5 devices continue to use vdccm, or will it soon be deprecated?

Lastly, a summary should be created to explain from a high-level what's
involved in syncing a WM device to the PC. It should quickly cover the entire
process from requring one of the two kernel drivers, vdccm/odccm and some
sync software. It would help new users to better understand the purpose of
synce. and the other tools.

Just a few thoughts...

~Paul
Post by John Carr
Paul: The PPP stuff is under the WM2003 section, because we don't really
support PPP for 2005 devices.
All: I sat down to try and document somethings for the new wiki
(www.synce.org/moin) where we hope to consolidate everything and finally
switch off the old cruft. I got a bit stuck on my taxonomy, the desire
to be really exact for distros - making use of .debs and such, and not
duplicating too much.
**** Idea 1 ****
* Base install
* libsynce/librapi/librra(?) and odccm
* Connecting your device
* USB RNDIS
* USB Serial
* Bluetooth PAN (no idea how this works)
* Bluetooth Serial (no idea how this works)
* Syncing your device
* Browsing your device
* Gnomevfs
* Fur
* Is there a KIO slave
* Adding and removing software
* Connecting to the internet from your device via your PC
* Connecting to the internet from your PC via your device
* Remote controlling your device (KCE Mirror)
Some of these bits will have distribution specific instructions, if not
all. So do we have a page for each distribution with a list like above?
== Installation ==
* Installation on Debian/Ubuntu
* Installation on Gentoo
* Installation on other Linux's
Both will have pages as above, and where no distro specific pages exist
we link to the generic pages. I think the overhead of maintaining extra
pages is worth it to cut down on traffic on #synce and other support
areas.
**** Idea 2 ****
* Getting Ready
* libsynce/librapi/librra(?) and odccm
* Connecting your device
* USB RNDIS
* USB Serial
* Bluetooth PAN (no idea how this works)
* Bluetooth Serial (no idea how this works)
* Syncing your device
* Browsing your device
* Gnomevfs
* Fur
* Is there a KIO slave
* Adding and removing software
* Connecting to the internet from your device via your PC
* Connecting to the internet from your PC via your device
* Remote controlling your device (KCE Mirror)
* Each page has the generic page (installing from tars) but first
offers links to packages/ebuilds.
* They will assume the user has followed Getting Ready which will talk
them through setting up repositories that might be needed.
* If the installation notes are long they may be delegated to a subpage
also, in which case (for example) "Syncing your device" just contains
instructions for running msynctool.
Thoughts?
Paul: Your input on beating the new wiki into shape would be
appreciated, but I want to make sure we get the structure right first.
Theres already a crufty page or two :(
Jonnylamb: Can we get synce.org rebooted or something :-\ Its dead
here...
John
John Carr
2007-11-14 17:25:32 UTC
Permalink
Wow, thanks for your thoughts!
Post by Paul Stanisci
John,
A few more thoughts...
I don't believe there is a place in the breakdown below for a compatability
list. The current WM5 device list on the synce.org wiki mentiones only HTC
devices. There are obviously more devices like the ipaq that can connect to
synce.
The compatibility list is a bad idea IMHO. OpenSync have ditched theirs
recently and I think we should too. If it supports ActiveSync then we
support it, if we don't its a bug. What i'm saying is, there is barely
no distinction between devices as far as our project is concerned and we
have more problems with localisation/language issues and distro issues
than we do with specific devices.
Post by Paul Stanisci
Also, under "Base Install", should a sub page be created to explain the
difference between vdccm and odccm, and when to use each one? Should users
of non-WM5 devices continue to use vdccm, or will it soon be deprecated?
Unless someone steps forward, we'll only document odccm, which has a legacy
mode to support WM2003 users. We've considered it deprecated for some time
and will probably move it to legacy/ in svn for 0.11...
Post by Paul Stanisci
Lastly, a summary should be created to explain from a high-level what's
involved in syncing a WM device to the PC. It should quickly cover the entire
process from requring one of the two kernel drivers, vdccm/odccm and some
sync software. It would help new users to better understand the purpose of
synce. and the other tools.
This will require some thinkery. Specifically, the kernel and
dccm/vdccm/odccm foo isn't specific to syncing - its probably wrong to
document this as part of synchronisation. Perhaps a "stack overview"
page is called for, but i don't think that belongs as part of
installation. Perhaps a link in overview?
Post by Paul Stanisci
Just a few thoughts...
~Paul
Paul Stanisci
2007-11-14 17:41:02 UTC
Permalink
Comments inline...
Post by John Carr
Wow, thanks for your thoughts!
Post by Paul Stanisci
John,
A few more thoughts...
I don't believe there is a place in the breakdown below for a
compatability list. The current WM5 device list on the synce.org wiki
mentiones only HTC devices. There are obviously more devices like the
ipaq that can connect to synce.
The compatibility list is a bad idea IMHO. OpenSync have ditched theirs
recently and I think we should too. If it supports ActiveSync then we
support it, if we don't its a bug. What i'm saying is, there is barely
no distinction between devices as far as our project is concerned and we
have more problems with localisation/language issues and distro issues
than we do with specific devices.
That makes good sense. I too figured most WM5 devices would be very similar. I
guess the "Connecting Your Device" could state that most devices should be
supported, and to file a bug with the pertinent device information if it
doesn't work.
Post by John Carr
Post by Paul Stanisci
Also, under "Base Install", should a sub page be created to explain the
difference between vdccm and odccm, and when to use each one? Should
users of non-WM5 devices continue to use vdccm, or will it soon be
deprecated?
Unless someone steps forward, we'll only document odccm, which has a legacy
mode to support WM2003 users. We've considered it deprecated for some time
and will probably move it to legacy/ in svn for 0.11...
If odccm will handle WM2003 and WM5 users, I guess there is little point to
document and maintain old version of dccm. Though, the documentation should
state that old version of dccm exist and that the user should use odccm
instead.
Post by John Carr
Post by Paul Stanisci
Lastly, a summary should be created to explain from a high-level what's
involved in syncing a WM device to the PC. It should quickly cover the
entire process from requring one of the two kernel drivers, vdccm/odccm
and some sync software. It would help new users to better understand the
purpose of synce. and the other tools.
This will require some thinkery. Specifically, the kernel and
dccm/vdccm/odccm foo isn't specific to syncing - its probably wrong to
document this as part of synchronisation. Perhaps a "stack overview"
page is called for, but i don't think that belongs as part of
installation. Perhaps a link in overview?
Sorry, my terminology was obviously wrong. My main point here is that a brief
summary should explain the purpose of synce in the grand scheme of things,
and hint at what else the user will need to perform a sync with their device.
This could be fairly short and may not warrant needing a whole page. Maybe
this could be explained in a paragraph on the "About synce" page.
Post by John Carr
Post by Paul Stanisci
Just a few thoughts...
~Paul
h
Mark Ellis
2007-11-23 09:31:34 UTC
Permalink
Post by Paul Stanisci
Post by John Carr
Post by Paul Stanisci
Also, under "Base Install", should a sub page be created to explain the
difference between vdccm and odccm, and when to use each one? Should
users of non-WM5 devices continue to use vdccm, or will it soon be
deprecated?
Unless someone steps forward, we'll only document odccm, which has a legacy
mode to support WM2003 users. We've considered it deprecated for some time
and will probably move it to legacy/ in svn for 0.11...
If odccm will handle WM2003 and WM5 users, I guess there is little point to
document and maintain old version of dccm. Though, the documentation should
state that old version of dccm exist and that the user should use odccm
instead.
Just a quick comment on the vdccm/odccm stance. AFAIK raki won't work
with odccm, not sure about the rest of synce-kde because I don't use it.
It would be nice if someone could implement odccm's dbus interface in
raki, unfortunately my C++ is not up to the task. An interim possibility
I've considered is a dummy vdccm that sits between odccm and synce-kde,
but again, because I use gnome it's at the bottom of my list.

Mark
Volker Christian
2007-11-23 11:44:53 UTC
Permalink
Post by Mark Ellis
Post by Paul Stanisci
Post by John Carr
Post by Paul Stanisci
Also, under "Base Install", should a sub page be created to explain
the difference between vdccm and odccm, and when to use each one?
Should users of non-WM5 devices continue to use vdccm, or will it
soon be deprecated?
Unless someone steps forward, we'll only document odccm, which has a
legacy mode to support WM2003 users. We've considered it deprecated for
some time and will probably move it to legacy/ in svn for 0.11...
If odccm will handle WM2003 and WM5 users, I guess there is little point
to document and maintain old version of dccm. Though, the documentation
should state that old version of dccm exist and that the user should use
odccm instead.
Just a quick comment on the vdccm/odccm stance. AFAIK raki won't work
with odccm, not sure about the rest of synce-kde because I don't use it.
It would be nice if someone could implement odccm's dbus interface in
raki, unfortunately my C++ is not up to the task. An interim possibility
I've considered is a dummy vdccm that sits between odccm and synce-kde,
but again, because I use gnome it's at the bottom of my list.
Hi,
maybe we shall list all features of vdccm and odccm to compare them directly
as i guess, that some features of vdccm are missing in odccm and vice versa.

So for vdccm we have:
- Support for PocketPC 2003 devices
- Support for WM 5 devices
- Support for multiple devices simultaneously
- Support for SynCE-KDE (raki) and all of those tools which rely on
the "active_connection"-file in the ~/.synce/ directory
- Support of a socket-connection for controll-messages to and from other
synce-tools (e.g. raki) like password-request and password-offer
messages, ...
- Connected devices can be identified either by their ip-addresses or by their
logical device-name.
- Acts as device-proxy for WM 5 devices mediating between the synce-tools and
the devices.

If someone can also list all features of odccm we are able to compare them
helping deciding what should be declared depreciated or should be implemented
either in vdccm or in odccm.

regards
voc

Loading...