installing John's packages & Python

Discussion:

Achim Zirner

2008-02-14 21:21:49 UTC

Hi,

Now that John created packages for Debian I'd like to give it a go
(again). Runnning Ubuntu 7.10 I used git-clone to get the repositories
and now .....? I thought that I could build a deb-package with
dpkg-buildpackage -rfakeroot -b

And then just install it.

However, I get messages such as:

***@achim-laptop:~/s5/synce-sync-engine$ ls
debian
***@achim-laptop:~/s5/synce-sync-engine$ dpkg-buildpackage -rfakeroot
-b
dpkg-buildpackage: source package is synce-sync-engine
dpkg-buildpackage: source version is 0.11-1
dpkg-buildpackage: source changed by Jonny Lamb
<***@jonnylamb.com>
dpkg-buildpackage: host architecture i386
dpkg-buildpackage: source version without epoch 0.11-1
fakeroot debian/rules clean
test -x debian/rules
test "`id -u`" = 0
dh_clean
cd . && python setup.py clean -a
python: can't open file 'setup.py': [Errno 2] No such file or directory
make: [python-clean-2.5] Fehler 2 (ignoriert)
rm -f python-build-stamp-*
find . -name '*.pyc' -exec rm '{}' ';'
rm -rf SyncEngine.egg-info
debian/rules build
test -x debian/rules
mkdir -p "."
cd . && python setup.py build
--build-base="/home/achim/s5/synce-sync-engine/./build"
python: can't open file 'setup.py': [Errno 2] No such file or directory
make: *** [python-build-stamp-2.5] Fehler 2
***@achim-laptop:~/s5/synce-sync-engine$

I'm not that knowledgeable about compiling, but I thought that the usual
way:
./confiure
make
sudo make install

would also work, ut thee is no "make-file"

It seems there is a different way doing things or am I missing
something?

There was an issue about dependency with python: python_rapi2 depends
on python < 2.5 which causes problems with ubuntu where python 2.5 ist
standard. I believe Mark was working on this. Right?
Is there any news on this?

Cheers,

achim

John Carr

2008-02-14 21:39:43 UTC

Permalink

Post by Achim Zirner
Hi,
Now that John created packages for Debian I'd like to give it a go
(again). Runnning Ubuntu 7.10 I used git-clone to get the repositories
and now .....? I thought that I could build a deb-package with
dpkg-buildpackage -rfakeroot -b
And then just install it.
debian
-b
dpkg-buildpackage: source package is synce-sync-engine
dpkg-buildpackage: source version is 0.11-1
dpkg-buildpackage: source changed by Jonny Lamb
dpkg-buildpackage: host architecture i386
dpkg-buildpackage: source version without epoch 0.11-1
fakeroot debian/rules clean
test -x debian/rules
test "`id -u`" = 0
dh_clean
cd . && python setup.py clean -a
python: can't open file 'setup.py': [Errno 2] No such file or directory
make: [python-clean-2.5] Fehler 2 (ignoriert)
rm -f python-build-stamp-*
find . -name '*.pyc' -exec rm '{}' ';'
rm -rf SyncEngine.egg-info
debian/rules build
test -x debian/rules
mkdir -p "."
cd . && python setup.py build
--build-base="/home/achim/s5/synce-sync-engine/./build"
python: can't open file 'setup.py': [Errno 2] No such file or directory
make: *** [python-build-stamp-2.5] Fehler 2
I'm not that knowledgeable about compiling, but I thought that the usual
./confiure
make
sudo make install
would also work, ut thee is no "make-file"
It seems there is a different way doing things or am I missing
something?
There was an issue about dependency with python: python_rapi2 depends
on python < 2.5 which causes problems with ubuntu where python 2.5 ist
standard. I believe Mark was working on this. Right?
Is there any news on this?
Cheers,
achim

Hi

I've published Ubuntu Feisty, Gutsy and Hardy versions of Jonnylambs
packages in a Launchpad PPA. The PPA is at:

https://launchpad.net/~synce/+archive

I also started updating the wiki page "SynceWithUbuntu" to match the
updated packages:

http://www.synce.org/moin/SynceWithUbuntu

These notes aren't considered "production ready" so they aren't linked
to from the main page, but should get you going.

John

Mark Ellis

2008-02-15 10:25:38 UTC

Permalink

Post by John Carr

Wild guess, have you put the debian directory in the unpacked source ?
Jonny's stuff is only the build architecture, it doesn't actually
include the source.

Post by John Carr

Post by Achim Zirner
There was an issue about dependency with python: python_rapi2 depends
on python < 2.5 which causes problems with ubuntu where python 2.5 ist
standard. I believe Mark was working on this. Right?
Is there any news on this?

Jonny got this fixed. If you build with his debian dirs in git, it
should use the python versions available on your distro. Note it will
build for all available versions, so if ubuntu supports other versions
than 2.5, you may have to install them as well.

Post by John Carr
Hi
I've published Ubuntu Feisty, Gutsy and Hardy versions of Jonnylambs
https://launchpad.net/~synce/+archive
I also started updating the wiki page "SynceWithUbuntu" to match the
http://www.synce.org/moin/SynceWithUbuntu
These notes aren't considered "production ready" so they aren't linked
to from the main page, but should get you going.
John

Or you could just use John's, which is probably easier :)

Mark

Achim Zirner

2008-02-16 12:43:47 UTC

Permalink

Hi Folks,

things are looking better, but not good yet!

got most of the packages installed smoothly with synaptics (and
aptitude) ;-)

However, there is an issue with the usb-rndis package. Apparently it
can't reach the lauch pad packages since it just lists the 0.10 version.

So I tried building the packages myself. Supprisingly it
worked !( thanks Johnny!). But still no connection.

I started odccm (as root) but it didn't connect. running pls gives me:

***@achim-laptop:~$ pls
pls: symbol lookup error: pls: undefined symbol: rapi_connection_from_name

This point to the python version issue.. right?

Also, I'm a bit confused about the usb-rndis vs. usb-rndis-lite issue. I
thought that the lite-version is the more up-to-date version but we're
using the other-version?

How many of my problems could be caused by to failed installtion /
unclean removals? I tried to removed everything I thought was related
to sycne an started from scratch, but you never know where some filed hides...

Cheers,

achim

Post by Mark Ellis

Post by John Carr

Wild guess, have you put the debian directory in the unpacked source ?
Jonny's stuff is only the build architecture, it doesn't actually
include the source.

Post by John Carr

Or you could just use John's, which is probably easier :)
Mark
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel

John Carr

2008-02-16 13:17:50 UTC

Permalink

Post by Achim Zirner
However, there is an issue with the usb-rndis package. Apparently it
can't reach the lauch pad packages since it just lists the 0.10 version.

At the moment, the 0.11 package won't build on launchpad. There is a
fix and it should be uploaded as soon as my laptop is unbroken enough
to be able to install a few needed tools...

Post by Achim Zirner
pls: symbol lookup error: pls: undefined symbol: rapi_connection_from_name
This point to the python version issue.. right?

Yep. If you do `strace pls` and look through the output for mentions
of /usr/local/ you'll probably see that there is stuff in the /local/
python site-packages folder to do with opensync and/or synce. This
will be used instead of the versions in /usr and break things.

Post by Achim Zirner
Also, I'm a bit confused about the usb-rndis vs. usb-rndis-lite issue. I
thought that the lite-version is the more up-to-date version but we're
using the other-version?

If my understanding is correct, usb-rndis-lite is like a branch of
usb-rndis. The usb-rndis package you are installing is prepared from
usb-rndis-lite.

Post by Achim Zirner
How many of my problems could be caused by to failed installtion /
unclean removals? I tried to removed everything I thought was related
to sycne an started from scratch, but you never know where some filed hides...

Achim Zirner

2008-02-17 13:17:18 UTC

Permalink

moving along... slowly but surely....

After cleaning up my system things installed fine. For usb-rndis I
buildt my own "0.11" package and it also installed fine.

However, it still doesn't connect. This is all I get:

########
***@achim-laptop:~$ sudo odccm -f
[sudo] password for achim:
** (odccm:10581): DEBUG: PDA network interface discovered!
udi='/org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00'

#########

***@achim-laptop:~$ pls
** (process:10663): WARNING **: No devices connected to odccm
pls: Could not find configuration at path '(Default)'
***@achim-laptop:~$

########

Having a look at the user list, it seems that a lot of people are having
issues connecting the 0.11 Version with a WM6 device. I had a connection
going with a 0.10-setup. It seems something changed between 0.10 and
0.11. Ok, that's a no brainer! But what I mean something changed in the
wrong way ;-)

Is there anyone out there who has successfully connected a WM6 device
with a 0.11 setup?

Any thoughts? Any information I can provide?

Cheers,

Achim

Post by John Carr
Hi

Post by Achim Zirner
However, there is an issue with the usb-rndis package. Apparently it
can't reach the lauch pad packages since it just lists the 0.10 version.

At the moment, the 0.11 package won't build on launchpad. There is a
fix and it should be uploaded as soon as my laptop is unbroken enough
to be able to install a few needed tools...

Post by Achim Zirner
pls: symbol lookup error: pls: undefined symbol: rapi_connection_from_name
This point to the python version issue.. right?

Post by Achim Zirner
Also, I'm a bit confused about the usb-rndis vs. usb-rndis-lite issue. I
thought that the lite-version is the more up-to-date version but we're
using the other-version?

If my understanding is correct, usb-rndis-lite is like a branch of
usb-rndis. The usb-rndis package you are installing is prepared from
usb-rndis-lite.

Lots and lots, if not all :-) I was trying to help someone with a
problem on #synce yesterday and kept hitting walls. strace revealed i
had old versions of opensync in /usr/local... Clearing them out got it
working for me.
Jogb
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel

Guido Diepen

2008-02-17 13:51:52 UTC

Permalink

Hi,

Post by Achim Zirner
########
** (odccm:10581): DEBUG: PDA network interface discovered!
udi='/org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00'
#########
** (process:10663): WARNING **: No devices connected to odccm
pls: Could not find configuration at path '(Default)'
########
Having a look at the user list, it seems that a lot of people are having
issues connecting the 0.11 Version with a WM6 device. I had a connection
going with a 0.10-setup. It seems something changed between 0.10 and
0.11. Ok, that's a no brainer! But what I mean something changed in the
wrong way ;-)

WM6 devices should not at all be any problem for the 0.11 release.

The fact that you don't see any device information popping up by odccm after
connecting a device can be caused by multiple things:
* A firewall blocking traffic on the newly created interface. The way a
connection is set up is by the host sending a UDP packet to the phone and the
phone creates a connection to the host.
* An old version of the usb-rndis-lite driver. Are you 100% sure that the
driver currently loaded in the kernel is the 0.11 version?
* You phone makes use of a different IP address than the default one of
169.254.2.1. This you can test by connecting the device and run dhclient on
this new device. If you get that the address of the computer becomes
169.254.2.2, while the DHCP server (=phone) is 169.254.2.1 this is NOT your
problem. If instead you get another address (especially motorola phones are
known for this at the moment), you must supply this information to odccm

As far as i know, those are the only possibilities there are at the moment.

Post by Achim Zirner
Is there anyone out there who has successfully connected a WM6 device
with a 0.11 setup?

All of the time, so it should not be any problem at all.

Guido Diepen

Post by Achim Zirner
Any thoughts? Any information I can provide?
Cheers,
Achim

Post by John Carr
Hi

Post by Achim Zirner
However, there is an issue with the usb-rndis package. Apparently it
can't reach the lauch pad packages since it just lists the 0.10 version.

At the moment, the 0.11 package won't build on launchpad. There is a
fix and it should be uploaded as soon as my laptop is unbroken enough
to be able to install a few needed tools...

Post by Achim Zirner
rapi_connection_from_name
This point to the python version issue.. right?

Post by Achim Zirner
Also, I'm a bit confused about the usb-rndis vs. usb-rndis-lite issue.
I thought that the lite-version is the more up-to-date version but
we're using the other-version?

If my understanding is correct, usb-rndis-lite is like a branch of
usb-rndis. The usb-rndis package you are installing is prepared from
usb-rndis-lite.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel

--
Aviation is proof that given the will, we have the
capacity to achieve the impossible.
--Eddie Rickenbacker

Achim Zirner

2008-02-17 16:57:52 UTC

Permalink

Hi Guido

I don't have a firewall running, so we can rule that out!

Why now use the usb-rndis-lite driver? John Carr noted, that the current
usb-rndis package is based on the "lite" version so I thought that the
rndis0.11 would be good.... I'm confused! Will give it a shot with the
lite version now. Will the over write the old (installed) version? it
should,right?

will keep you posted!

achim

Post by Guido Diepen
WM6 devices should not at all be any problem for the 0.11 release.
The fact that you don't see any device information popping up by odccm after
* A firewall blocking traffic on the newly created interface. The way a
connection is set up is by the host sending a UDP packet to the phone and the
phone creates a connection to the host.
* An old version of the usb-rndis-lite driver. Are you 100% sure that the
driver currently loaded in the kernel is the 0.11 version?
* You phone makes use of a different IP address than the default one of
169.254.2.1. This you can test by connecting the device and run dhclient on
this new device. If you get that the address of the computer becomes
169.254.2.2, while the DHCP server (=phone) is 169.254.2.1 this is NOT your
problem. If instead you get another address (especially motorola phones are
known for this at the moment), you must supply this information to odccm
As far as i know, those are the only possibilities there are at the moment.

Post by Achim Zirner
Is there anyone out there who has successfully connected a WM6 device
with a 0.11 setup?

All of the time, so it should not be any problem at all.
Guido Diepen

Post by Achim Zirner
Any thoughts? Any information I can provide?
Cheers,
Achim

Post by John Carr
Hi

Post by Achim Zirner
However, there is an issue with the usb-rndis package. Apparently it
can't reach the lauch pad packages since it just lists the 0.10 version.

At the moment, the 0.11 package won't build on launchpad. There is a
fix and it should be uploaded as soon as my laptop is unbroken enough
to be able to install a few needed tools...

Post by Achim Zirner
rapi_connection_from_name
This point to the python version issue.. right?

Post by Achim Zirner
Also, I'm a bit confused about the usb-rndis vs. usb-rndis-lite issue.
I thought that the lite-version is the more up-to-date version but
we're using the other-version?

If my understanding is correct, usb-rndis-lite is like a branch of
usb-rndis. The usb-rndis package you are installing is prepared from
usb-rndis-lite.

Mark Ellis

2008-02-18 09:34:17 UTC

Permalink

Post by Achim Zirner
Hi Guido
I don't have a firewall running, so we can rule that out!
Why now use the usb-rndis-lite driver? John Carr noted, that the current
usb-rndis package is based on the "lite" version so I thought that the
rndis0.11 would be good.... I'm confused! Will give it a shot with the
lite version now. Will the over write the old (installed) version? it
should,right?
will keep you posted!
achim

I probably confused you more in a reply I just sent !

The packages are generally called usb-rndis, so if you see an 0.11
release of this it should be the right one. In subversion it's called
usb-rndis-lite.

Mark

Achim Zirner

2008-02-17 18:56:20 UTC

Permalink

Hi,
I'm pretty sure, that I've got usb-rnds0.11 running. However, how can I
make sure?

I'm getting an ethernet connection,. Here's the some log data from
daemon.log

Feb 17 19:40:13 achim-laptop NetworkManager: <debug> [1203273613.986453]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_if0').
Feb 17 19:40:13 achim-laptop NetworkManager: <debug> [1203273613.986947]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_if1').
Feb 17 19:40:13 achim-laptop NetworkManager: <debug> [1203273613.987656]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080').
Feb 17 19:40:13 achim-laptop NetworkManager: <debug> [1203273613.987785]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_usbraw').
Feb 17 19:40:16 achim-laptop NetworkManager: <debug> [1203273616.996226]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080').
Feb 17 19:40:17 achim-laptop NetworkManager: <debug> [1203273617.121835]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080_if0').
Feb 17 19:40:17 achim-laptop NetworkManager: <debug> [1203273617.169590]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080_usbraw').
Feb 17 19:40:28 achim-laptop NetworkManager: <debug> [1203273628.155363]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080_if0').
Feb 17 19:40:28 achim-laptop NetworkManager: <debug> [1203273628.165419]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080_usbraw').
Feb 17 19:40:28 achim-laptop NetworkManager: <debug> [1203273628.177613]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080').
Feb 17 19:40:31 achim-laptop NetworkManager: <debug> [1203273631.670280]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080').
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Joining mDNS multicast
group on interface eth3.IPv4 with address 169.254.2.2.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: New relevant interface
eth3.IPv4 for mDNS.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Registering new address
record for 169.254.2.2 on eth3.IPv4.
Feb 17 19:40:31 achim-laptop NetworkManager: <debug> [1203273631.888617]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_if1').
Feb 17 19:40:31 achim-laptop NetworkManager: <debug> [1203273631.889880]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_if0').
Feb 17 19:40:31 achim-laptop NetworkManager: <debug> [1203273631.890443]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00').
Feb 17 19:40:31 achim-laptop odccm[6014]: DEBUG: PDA network interface
discovered! udi='/org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00'
Feb 17 19:40:31 achim-laptop NetworkManager: <info> eth3: Device is
fully-supported using driver 'rndis_host'.
Feb 17 19:40:31 achim-laptop NetworkManager: <info> nm_device_init():
waiting for device's worker thread to start
Feb 17 19:40:31 achim-laptop NetworkManager: <info> nm_device_init():
device's worker thread started, continuing.
Feb 17 19:40:31 achim-laptop NetworkManager: <info> Now managing wired
Ethernet (802.3) device 'eth3'.
Feb 17 19:40:31 achim-laptop NetworkManager: <info> Deactivating device
eth3.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Withdrawing address
record for 169.254.2.2 on eth3.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Leaving mDNS multicast
group on interface eth3.IPv4 with address 169.254.2.2.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Interface eth3.IPv4 no
longer relevant for mDNS.
Feb 17 19:40:31 achim-laptop NetworkManager: <debug> [1203273631.955889]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_usbraw').
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Joining mDNS multicast
group on interface eth3.IPv4 with address 169.254.2.2.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: New relevant interface
eth3.IPv4 for mDNS.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Registering new address
record for 169.254.2.2 on eth3.IPv4.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Withdrawing address
record for 169.254.2.2 on eth3.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Leaving mDNS multicast
group on interface eth3.IPv4 with address 169.254.2.2.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Interface eth3.IPv4 no
longer relevant for mDNS.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Joining mDNS multicast
group on interface eth3.IPv4 with address 169.254.2.2.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: New relevant interface
eth3.IPv4 for mDNS.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Registering new address
record for 169.254.2.2 on eth3.IPv4.

It looks like the IPs are correct. IFCONFIG shows me that the interface
is up.
I did a "hardware reset" on the PDA. Could it be that the settings in
the PDA got screwed up? Can't remember if had any special settings when
I had it running with 0.10 versions.

Still trying...

Achim

Post by Guido Diepen
Hi,

WM6 devices should not at all be any problem for the 0.11 release.
The fact that you don't see any device information popping up by odccm after
* A firewall blocking traffic on the newly created interface. The way a
connection is set up is by the host sending a UDP packet to the phone and the
phone creates a connection to the host.
* An old version of the usb-rndis-lite driver. Are you 100% sure that the
driver currently loaded in the kernel is the 0.11 version?
* You phone makes use of a different IP address than the default one of
169.254.2.1. This you can test by connecting the device and run dhclient on
this new device. If you get that the address of the computer becomes
169.254.2.2, while the DHCP server (=phone) is 169.254.2.1 this is NOT your
problem. If instead you get another address (especially motorola phones are
known for this at the moment), you must supply this information to odccm
As far as i know, those are the only possibilities there are at the moment.

Post by Achim Zirner
Is there anyone out there who has successfully connected a WM6 device
with a 0.11 setup?

All of the time, so it should not be any problem at all.
Guido Diepen

Post by Achim Zirner
Any thoughts? Any information I can provide?
Cheers,
Achim

Mark Ellis

2008-02-18 10:02:27 UTC

Permalink

Post by Achim Zirner
Hi,
I'm pretty sure, that I've got usb-rnds0.11 running. However, how can I
make sure?
I'm getting an ethernet connection,. Here's the some log data from
daemon.log
Feb 17 19:40:13 achim-laptop NetworkManager: <debug> [1203273613.986453]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_if0').
Feb 17 19:40:13 achim-laptop NetworkManager: <debug> [1203273613.986947]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_if1').
Feb 17 19:40:13 achim-laptop NetworkManager: <debug> [1203273613.987656]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080').
Feb 17 19:40:13 achim-laptop NetworkManager: <debug> [1203273613.987785]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_usbraw').
Feb 17 19:40:16 achim-laptop NetworkManager: <debug> [1203273616.996226]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080').
Feb 17 19:40:17 achim-laptop NetworkManager: <debug> [1203273617.121835]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080_if0').
Feb 17 19:40:17 achim-laptop NetworkManager: <debug> [1203273617.169590]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080_usbraw').
Feb 17 19:40:28 achim-laptop NetworkManager: <debug> [1203273628.155363]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080_if0').
Feb 17 19:40:28 achim-laptop NetworkManager: <debug> [1203273628.165419]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080_usbraw').
Feb 17 19:40:28 achim-laptop NetworkManager: <debug> [1203273628.177613]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_ce_3fbf5000_7351_0801_3583_750100947080').
Feb 17 19:40:31 achim-laptop NetworkManager: <debug> [1203273631.670280]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080').
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Joining mDNS multicast
group on interface eth3.IPv4 with address 169.254.2.2.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: New relevant interface
eth3.IPv4 for mDNS.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Registering new address
record for 169.254.2.2 on eth3.IPv4.
Feb 17 19:40:31 achim-laptop NetworkManager: <debug> [1203273631.888617]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_if1').
Feb 17 19:40:31 achim-laptop NetworkManager: <debug> [1203273631.889880]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_if0').
Feb 17 19:40:31 achim-laptop NetworkManager: <debug> [1203273631.890443]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00').
Feb 17 19:40:31 achim-laptop odccm[6014]: DEBUG: PDA network interface
discovered! udi='/org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00'
Feb 17 19:40:31 achim-laptop NetworkManager: <info> eth3: Device is
fully-supported using driver 'rndis_host'.
waiting for device's worker thread to start
device's worker thread started, continuing.
Feb 17 19:40:31 achim-laptop NetworkManager: <info> Now managing wired
Ethernet (802.3) device 'eth3'.
Feb 17 19:40:31 achim-laptop NetworkManager: <info> Deactivating device
eth3.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Withdrawing address
record for 169.254.2.2 on eth3.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Leaving mDNS multicast
group on interface eth3.IPv4 with address 169.254.2.2.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Interface eth3.IPv4 no
longer relevant for mDNS.
Feb 17 19:40:31 achim-laptop NetworkManager: <debug> [1203273631.955889]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_bb4_b0d_3fbf5000_7351_0801_3583_750100947080_usbraw').
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Joining mDNS multicast
group on interface eth3.IPv4 with address 169.254.2.2.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: New relevant interface
eth3.IPv4 for mDNS.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Registering new address
record for 169.254.2.2 on eth3.IPv4.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Withdrawing address
record for 169.254.2.2 on eth3.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Leaving mDNS multicast
group on interface eth3.IPv4 with address 169.254.2.2.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Interface eth3.IPv4 no
longer relevant for mDNS.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Joining mDNS multicast
group on interface eth3.IPv4 with address 169.254.2.2.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: New relevant interface
eth3.IPv4 for mDNS.
Feb 17 19:40:31 achim-laptop avahi-daemon[6273]: Registering new address
record for 169.254.2.2 on eth3.IPv4.
It looks like the IPs are correct. IFCONFIG shows me that the interface
is up.

Can you ping the device ?

network manager might be confusing odccm, though I would've thought if
the interface was up it wouldn't matter.

Try adding this line to /etc/network/interfaces

iface eth0 inet dhcp

and make sure there is nothing else in there for eth3. The networking
system won't bring this up automatically without an 'auto eth3' line,
and neither will network manager, which may give odccm a fighting
chance.

Post by Achim Zirner
I did a "hardware reset" on the PDA. Could it be that the settings in
the PDA got screwed up? Can't remember if had any special settings when
I had it running with 0.10 versions.

Cant think it would be a problem.

Mark

Post by Achim Zirner
Still trying...
Achim

Post by Guido Diepen
Hi,

Post by Achim Zirner
Is there anyone out there who has successfully connected a WM6 device
with a 0.11 setup?

All of the time, so it should not be any problem at all.
Guido Diepen

Post by Achim Zirner
Any thoughts? Any information I can provide?
Cheers,
Achim

Mark Ellis

2008-02-18 09:29:39 UTC

Permalink

Post by Achim Zirner
Hi Folks,
things are looking better, but not good yet!
got most of the packages installed smoothly with synaptics (and
aptitude) ;-)
However, there is an issue with the usb-rndis package. Apparently it
can't reach the lauch pad packages since it just lists the 0.10 version.
So I tried building the packages myself. Supprisingly it
worked !( thanks Johnny!). But still no connection.
pls: symbol lookup error: pls: undefined symbol: rapi_connection_from_name
This point to the python version issue.. right?

No, but similar. You have an old version of librapi2-tools installed
that you should remove.

Post by Achim Zirner
Also, I'm a bit confused about the usb-rndis vs. usb-rndis-lite issue. I
thought that the lite-version is the more up-to-date version but we're
using the other-version?

Use -lite.

To find that old version of pls, run

which pls

should point you in the right direction, probably /usr/local

Post by Achim Zirner
Cheers,
achim

Post by Mark Ellis

Post by John Carr

Wild guess, have you put the debian directory in the unpacked source ?
Jonny's stuff is only the build architecture, it doesn't actually
include the source.

Post by John Carr

Jonny Lamb

2008-02-15 10:56:50 UTC

Permalink

Post by Achim Zirner
Now that John created packages for Debian I'd like to give it a go
(again). Runnning Ubuntu 7.10 I used git-clone to get the repositories
and now .....? I thought that I could build a deb-package with

[...]

Post by Achim Zirner
python: can't open file 'setup.py': [Errno 2] No such file or directory

Make sure you are doing:

wget http://downloads.sf.net/synce/sync-engine-0.11.tar.gz
git clone git://git.jonnylamb.com/git/packaging/synce-sync-engine.git
tar zxf sync-engine-0.11.tar.gz
mv synce-sync-engine/debian sync-engine-0.11/
cd sync-engine-0.11/
dpkg-buildpackage

--
Jonny Lamb, UK ***@jonnylamb.com
http://jonnylamb.com GPG: 0x2E039402