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 On Wed, 2007-11-14 at 09:45 -0500, Paul Stanisci wrote: > 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 > > On Wednesday 14 November 2007 12:43:01 am John Carr wrote: > > 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 > > > > On Tue, 2007-11-13 at 21:32 -0500, Paul Stanisci wrote: > > > 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 > > > > > > On Tuesday 13 November 2007 8:45:05 pm Paul Stanisci wrote: > > > > 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 > > > > SynCE-Devel@lists.sourceforge.net > > > > 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 > > > SynCE-Devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/synce-devel > > ------------------------------------------------------------------------- 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 SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
