Discussion:
synce on a post hal Linux kernel
Eugene Kanter
2012-11-19 02:58:46 UTC
Permalink
I've been using synce for many years. My current system is Fedora 14 which is long overdue for an upgrade.

However my initial tests can't confirm that fedora supplied synce packages work on anything newer the Fedora 14.

When device is connected it provides an IP address to NetworkManager but no synce driver is loaded.

Regards,
Eugene.
Mark Ellis
2012-11-22 13:52:28 UTC
Permalink
I see no reason why synce won't work, the latest version doesn't use
hal, but I can't comment on the fedora packages.

Mark
Post by Eugene Kanter
I've been using synce for many years. My current system is Fedora 14 which is long overdue for an upgrade.
However my initial tests can't confirm that fedora supplied synce packages work on anything newer the Fedora 14.
When device is connected it provides an IP address to NetworkManager but no synce driver is loaded.
Regards,
Eugene.
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
SynCE-Users mailing list
https://lists.sourceforge.net/lists/listinfo/synce-users
Eugene Kanter
2012-12-01 00:21:23 UTC
Permalink
Hi Mark,

Thanks for responding. I understand you can't comment on Fedora
packages, I am wondering if this list can provide generic diagnostic
help. Here is what I see in /var/log/messages after windows mobile 6
phone is plugged in.

Nov 30 19:14:25 localhost kernel: usb 3-3: new full-speed USB device number 6 using xhci_hcd
Nov 30 19:14:25 localhost kernel: usb 3-3: New USB device found, idVendor=04e8, idProduct=6662
Nov 30 19:14:25 localhost kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 30 19:14:25 localhost kernel: usb 3-3: Product: MITS USB RNDIS
Nov 30 19:14:25 localhost kernel: usb 3-3: Manufacturer: Samsung
Nov 30 19:14:25 localhost kernel: usb 3-3: SerialNumber: 43bf5000-bf39-0801-12c0-0103dafc6f86
Nov 30 19:14:25 localhost kernel: rndis_host 3-3:1.0: RNDIS_MSG_QUERY(0x00010202) failed, -47
Nov 30 19:14:25 localhost kernel: rndis_host 3-3:1.0: eth0: register 'rndis_host' at usb-0000:00:14.0-3, RNDIS device (poll status before control), 80:00:60:0f:e8:00
Nov 30 19:17:35 localhost mtp-probe: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3"
Nov 30 19:17:35 localhost mtp-probe: bus: 3, device: 6 was not an MTP device
Nov 30 19:17:35 localhost NetworkManager[25123]: <warn> failed to allocate link cache: (-10) Operation not supported
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): carrier is OFF
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): new Ethernet device (driver: 'rndis_host' ifindex: 11)
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/5
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): now managed
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): bringing up device.
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): carrier now ON (device state 20)
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): preparing device.
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): deactivating device (reason 'managed') [2]
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/net/eth0
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Auto-activating connection 'Wired connection 1'.
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) starting connection 'Wired connection 1'
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> dhclient started with pid 25634
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Beginning IP6 addrconf.
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Nov 30 19:17:35 localhost dhclient[25634]: Internet Systems Consortium DHCP Client 4.2.4-P2
Nov 30 19:17:35 localhost dhclient[25634]: Copyright 2004-2012 Internet Systems Consortium.
Nov 30 19:17:35 localhost dhclient[25634]: All rights reserved.
Nov 30 19:17:35 localhost dhclient[25634]: For info, please visit https://www.isc.org/software/dhcp/
Nov 30 19:17:35 localhost dhclient[25634]:
Nov 30 19:17:35 localhost NetworkManager[25123]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Nov 30 19:17:35 localhost dhclient[25634]: Listening on LPF/eth0/80:00:60:0f:e8:00
Nov 30 19:17:35 localhost dhclient[25634]: Sending on LPF/eth0/80:00:60:0f:e8:00
Nov 30 19:17:35 localhost dhclient[25634]: Sending on Socket/fallback
Nov 30 19:17:35 localhost dhclient[25634]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0xd847a05)
Nov 30 19:17:36 localhost avahi-daemon[801]: Registering new address record for fe80::8200:60ff:fe0f:e800 on eth0.*.
Nov 30 19:17:42 localhost dhclient[25634]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0xd847a05)
Nov 30 19:17:42 localhost dhclient[25634]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0xd847a05)
Nov 30 19:17:42 localhost dhclient[25634]: DHCPOFFER from 169.254.2.1
Nov 30 19:17:42 localhost dhclient[25634]: DHCPACK from 169.254.2.1 (xid=0xd847a05)
Nov 30 19:17:42 localhost dhclient[25634]: bound to 169.254.2.2 -- renewal in 1075986 seconds.
Nov 30 19:17:42 localhost NetworkManager[25123]: <info> (eth0): DHCPv4 state changed preinit -> bound
Nov 30 19:17:42 localhost NetworkManager[25123]: <info> address 169.254.2.2
Nov 30 19:17:42 localhost NetworkManager[25123]: <info> prefix 24 (255.255.255.0)
Nov 30 19:17:42 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Nov 30 19:17:42 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
Nov 30 19:17:42 localhost avahi-daemon[801]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.2.2.
Nov 30 19:17:42 localhost avahi-daemon[801]: New relevant interface eth0.IPv4 for mDNS.
Nov 30 19:17:42 localhost avahi-daemon[801]: Registering new address record for 169.254.2.2 on eth0.IPv4.
Nov 30 19:17:43 localhost NetworkManager[25123]: <info> (eth0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Nov 30 19:17:43 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
Nov 30 19:17:43 localhost NetworkManager[25123]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 30 19:17:44 localhost NetworkManager[25123]: <info> Activation (eth0) successful, device activated.
Nov 30 19:17:44 localhost dbus-daemon[803]: dbus[803]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 30 19:17:44 localhost dbus[803]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 30 19:17:44 localhost dbus-daemon[803]: dbus[803]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 30 19:17:44 localhost dbus[803]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 30 19:17:44 localhost systemd[1]: Stopping Sendmail Mail Transport Client...
Nov 30 19:17:44 localhost systemd[1]: Stopping Sendmail Mail Transport Agent...
Nov 30 19:17:44 localhost systemd[1]: Starting Sendmail Mail Transport Agent...
Nov 30 19:17:44 localhost systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start.
Nov 30 19:17:44 localhost systemd[1]: Started Sendmail Mail Transport Agent.
Nov 30 19:17:44 localhost systemd[1]: Starting Sendmail Mail Transport Client...
Nov 30 19:17:44 localhost systemd[1]: Started Sendmail Mail Transport Client.
Nov 30 19:17:56 localhost NetworkManager[25123]: <info> (eth0): IP6 addrconf timed out or failed.
Nov 30 19:17:56 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Nov 30 19:17:56 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Nov 30 19:17:56 localhost NetworkManager[25123]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.

# rpm -qa | grep synce
libsynce-0.15.1-4.fc18.x86_64
synce-gnomevfs-0.13-5.fc18.x86_64
synce-gnome-0.11-7.fc18.noarch
synce-connector-0.15.2-5.fc17.x86_64
synce-trayicon-0.15.2-0.4.20110523svn.fc18.x86_64
synce-sync-engine-0.15.1-5.fc18.x86_64
synce-software-manager-0.9.0-17.fc18.x86_64

Am I missing anything?

Regards,
Eugene.

-----Original Message-----
From: Mark Ellis <***@mpellis.org.uk>
Reply-to: synce-***@lists.sourceforge.net
To: synce-***@lists.sourceforge.net
Subject: Re: synce on a post hal Linux kernel
Date: Thu, 22 Nov 2012 13:52:28 +0000

I see no reason why synce won't work, the latest version doesn't use
hal, but I can't comment on the fedora packages.

Mark
Post by Eugene Kanter
I've been using synce for many years. My current system is Fedora 14 which is long overdue for an upgrade.
However my initial tests can't confirm that fedora supplied synce packages work on anything newer the Fedora 14.
When device is connected it provides an IP address to NetworkManager but no synce driver is loaded.
Regards,
Eugene.
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
SynCE-Users mailing list
https://lists.sourceforge.net/lists/listinfo/synce-users
Mark Ellis
2012-12-31 12:16:44 UTC
Permalink
Post by Eugene Kanter
Hi Mark,
Thanks for responding. I understand you can't comment on Fedora
packages, I am wondering if this list can provide generic diagnostic
help. Here is what I see in /var/log/messages after windows mobile 6
phone is plugged in.
Nov 30 19:14:25 localhost kernel: usb 3-3: new full-speed USB device number 6 using xhci_hcd
Nov 30 19:14:25 localhost kernel: usb 3-3: New USB device found, idVendor=04e8, idProduct=6662
Nov 30 19:14:25 localhost kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 30 19:14:25 localhost kernel: usb 3-3: Product: MITS USB RNDIS
Nov 30 19:14:25 localhost kernel: usb 3-3: Manufacturer: Samsung
Nov 30 19:14:25 localhost kernel: usb 3-3: SerialNumber: 43bf5000-bf39-0801-12c0-0103dafc6f86
Nov 30 19:14:25 localhost kernel: rndis_host 3-3:1.0: RNDIS_MSG_QUERY(0x00010202) failed, -47
Nov 30 19:14:25 localhost kernel: rndis_host 3-3:1.0: eth0: register 'rndis_host' at usb-0000:00:14.0-3, RNDIS device (poll status before control), 80:00:60:0f:e8:00
That part looks fine, but there is nothing else in the log from synce.
Post by Eugene Kanter
# rpm -qa | grep synce
libsynce-0.15.1-4.fc18.x86_64
synce-gnomevfs-0.13-5.fc18.x86_64
synce-gnome-0.11-7.fc18.noarch
synce-connector-0.15.2-5.fc17.x86_64
I can't tell from this whether connector has been built for udev or hal.
Can you provide a list of the package contents ?
Post by Eugene Kanter
synce-trayicon-0.15.2-0.4.20110523svn.fc18.x86_64
synce-sync-engine-0.15.1-5.fc18.x86_64
synce-software-manager-0.9.0-17.fc18.x86_64
Am I missing anything?
Regards,
Eugene.
-----Original Message-----
Subject: Re: synce on a post hal Linux kernel
Date: Thu, 22 Nov 2012 13:52:28 +0000
I see no reason why synce won't work, the latest version doesn't use
hal, but I can't comment on the fedora packages.
Mark
Post by Eugene Kanter
I've been using synce for many years. My current system is Fedora 14 which is long overdue for an upgrade.
However my initial tests can't confirm that fedora supplied synce packages work on anything newer the Fedora 14.
When device is connected it provides an IP address to NetworkManager but no synce driver is loaded.
Regards,
Eugene.
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
SynCE-Users mailing list
https://lists.sourceforge.net/lists/listinfo/synce-users
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
SynCE-Users mailing list
https://lists.sourceforge.net/lists/listinfo/synce-users
------------------------------------------------------------------------------
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
_______________________________________________
SynCE-Users mailing list
https://lists.sourceforge.net/lists/listinfo/synce-users
Eugene Kanter
2013-01-02 02:55:34 UTC
Permalink
Mark,

Here is the listing:

$ rpm -ql synce-connector
/etc/dbus-1/system.d/org.synce.dccm.conf
/etc/ppp/ip-up.d/synce-udev-bt-ipup
/etc/ppp/peers/synce-bt-peer
/lib/udev/rules.d/85-synce.rules
/lib/udev/synce-udev-rndis
/lib/udev/synce-udev-serial
/usr/bin/synce-serial
/usr/bin/synce-unlock
/usr/libexec/dccm
/usr/libexec/synce-serial-chat
/usr/share/dbus-1/system-services/org.synce.dccm.service
/usr/share/doc/synce-connector-0.15.2
/usr/share/doc/synce-connector-0.15.2/AUTHORS
/usr/share/doc/synce-connector-0.15.2/COPYING
/usr/share/doc/synce-connector-0.15.2/ChangeLog
/usr/share/doc/synce-connector-0.15.2/README
/usr/share/doc/synce-connector-0.15.2/TODO
/usr/share/synce-connector
/usr/share/synce-connector/dhclient.conf
/usr/share/synce-connector/synceconnector.py
/usr/share/synce-connector/synceconnector.pyc
/usr/share/synce-connector/synceconnector.pyo
/usr/share/synce-connector/udev-synce-rndis
/usr/share/synce-connector/udev-synce-serial

Eugene.

-----Original Message-----
From: Mark Ellis
Reply-to: synce-***@lists.sourceforge.net
To: synce-***@lists.sourceforge.net
Subject: Re: synce on a post hal Linux kernel
Date: Mon, 31 Dec 2012 12:16:44 +0000
Post by Eugene Kanter
Hi Mark,
Thanks for responding. I understand you can't comment on Fedora
packages, I am wondering if this list can provide generic diagnostic
help. Here is what I see in /var/log/messages after windows mobile 6
phone is plugged in.
Nov 30 19:14:25 localhost kernel: usb 3-3: new full-speed USB device number 6 using xhci_hcd
Nov 30 19:14:25 localhost kernel: usb 3-3: New USB device found, idVendor=04e8, idProduct=6662
Nov 30 19:14:25 localhost kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 30 19:14:25 localhost kernel: usb 3-3: Product: MITS USB RNDIS
Nov 30 19:14:25 localhost kernel: usb 3-3: Manufacturer: Samsung
Nov 30 19:14:25 localhost kernel: usb 3-3: SerialNumber: 43bf5000-bf39-0801-12c0-0103dafc6f86
Nov 30 19:14:25 localhost kernel: rndis_host 3-3:1.0: RNDIS_MSG_QUERY(0x00010202) failed, -47
Nov 30 19:14:25 localhost kernel: rndis_host 3-3:1.0: eth0: register 'rndis_host' at usb-0000:00:14.0-3, RNDIS device (poll status before control), 80:00:60:0f:e8:00
That part looks fine, but there is nothing else in the log from synce.
Post by Eugene Kanter
# rpm -qa | grep synce
libsynce-0.15.1-4.fc18.x86_64
synce-gnomevfs-0.13-5.fc18.x86_64
synce-gnome-0.11-7.fc18.noarch
synce-connector-0.15.2-5.fc17.x86_64
I can't tell from this whether connector has been built for udev or hal.
Can you provide a list of the package contents ?
Post by Eugene Kanter
synce-trayicon-0.15.2-0.4.20110523svn.fc18.x86_64
synce-sync-engine-0.15.1-5.fc18.x86_64
synce-software-manager-0.9.0-17.fc18.x86_64
Am I missing anything?
Regards,
Eugene.
-----Original Message-----
From: Mark Ellis
Subject: Re: synce on a post hal Linux kernel
Date: Thu, 22 Nov 2012 13:52:28 +0000
I see no reason why synce won't work, the latest version doesn't use
hal, but I can't comment on the fedora packages.
Mark
Post by Eugene Kanter
I've been using synce for many years. My current system is Fedora 14 which is long overdue for an upgrade.
However my initial tests can't confirm that fedora supplied synce packages work on anything newer the Fedora 14.
When device is connected it provides an IP address to NetworkManager but no synce driver is loaded.
Regards,
Eugene.
Loading...