SynCE in OpenSuSE 11.3 - Cannot connect to Samsung Jack

[John Cooper]

I can't seem to connect to my Samsung Jack using synce-kpm, or even pls, even though I have all the packages listed in the wiki installed. Here's the terminal output:

***@linux-twom:~> pls
** Message: Device /org/freedesktop/Hal/devices/usb_device_4e8_6619_32484557_5054_0801_fd5f_76803fbd49d0_if0_serial_usb_0 not fully set in Hal, skipping
** Message: Odccm is not running, ignoring
pls: Could not find configuration at path '(Default)'

... and here are the contents of the sync-engine.log file:

2011-02-28 20:34:15,220 DEBUG syncengine : running main loop
2011-02-28 20:34:15,221 DEBUG syncengine : creating SyncEngine object
2011-02-28 20:34:15,253 INFO engine.syncengine.kernel : __init__: connected device found
2011-02-28 20:34:15,259 DEBUG syncengine : installing signal handlers

So ... why isn't this working, and how can I fix it?

[Mark Ellis]

Post by John Cooper
** Message: Device /org/freedesktop/Hal/devices/usb_device_4e8_6619_32484557_5054_0801_fd5f_76803fbd49d0_if0_serial_usb_0 not fully set in Hal, skipping
** Message: Odccm is not running, ignoring
pls: Could not find configuration at path '(Default)'

If pls doesn't work then nothing else will.

Do you have a firewall ? Whats the output of

iptables -L

Post by John Cooper
2011-02-28 20:34:15,220 DEBUG syncengine : running main loop
2011-02-28 20:34:15,221 DEBUG syncengine : creating SyncEngine object
2011-02-28 20:34:15,253 INFO engine.syncengine.kernel : __init__: connected device found
2011-02-28 20:34:15,259 DEBUG syncengine : installing signal handlers
So ... why isn't this working, and how can I fix it?
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
SynCE-Users mailing list
https://lists.sourceforge.net/lists/listinfo/synce-users

[John Cooper]

You know, now that I think about it, NetworkManager was acting a little funny when I connected it ... but I need that running on this laptop in order to handle my Wi-fi connection (which was a pain to get working in the 1st place), so is there any possible way to make that Daemon "play nice" with SynCE?

Subject: Re: SynCE in OpenSuSE 11.3 - Cannot connect to Samsung Jack
Date: Thursday, March 3, 2011, 11:28 AM
On 01/03/11 04:22, John Cooper

Post by John Cooper
I can't seem to connect to my Samsung Jack using

synce-kpm, or even pls, even though I have all the packages
listed in the wiki installed.  Here's the terminal

Post by John Cooper
** Message: Device

/org/freedesktop/Hal/devices/usb_device_4e8_6619_32484557_5054_0801_fd5f_76803fbd49d0_if0_serial_usb_0
not fully set in Hal, skipping

Post by John Cooper
** Message: Odccm is not running, ignoring
pls: Could not find configuration at path '(Default)'
... and here are the contents of the sync-engine.log
2011-02-28 20:34:15,220 DEBUG syncengine : running

main loop

Post by John Cooper
2011-02-28 20:34:15,221 DEBUG syncengine : creating

SyncEngine object

Post by John Cooper
2011-02-28 20:34:15,253 INFO engine.syncengine.kernel

: __init__: connected device found

Post by John Cooper
2011-02-28 20:34:15,259 DEBUG syncengine : installing

signal handlers

Post by John Cooper
So ... why isn't this working, and how can I fix it?
   

Two common possibilities are firewall interfering or
NetworkManager
interfering.
Do you have SuSEfirewall2 enabled? Did you allow the
"SynCE" service /
or move the interface to the internal zone?
If it's not that, or NetworkManager, edit
/etc/synce-hal.conf -
uncomment "#loglevel: debug"; try connecting your device
again; and post
the relevant lines from /var/log/messages.
Regards,
Tejas

[John Cooper]

Pertinent output from /var/log/messages :

Mar 3 18:03:34 linux-twom kernel: [ 9261.553092] usb 2-1: new high speed USB device using ehci_hcd and address 5
Mar 3 18:03:34 linux-twom kernel: [ 9261.671156] usb 2-1: New USB device found, idVendor=04e8, idProduct=6619
Mar 3 18:03:34 linux-twom kernel: [ 9261.671162] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 3 18:03:34 linux-twom kernel: [ 9261.671166] usb 2-1: Product: SGH-i637
Mar 3 18:03:34 linux-twom kernel: [ 9261.671170] usb 2-1: Manufacturer: Samsung Electronics
Mar 3 18:03:34 linux-twom kernel: [ 9261.671173] usb 2-1: SerialNumber: 32484557-5054-0801-fd5f-76803fbd49d0
Mar 3 18:03:34 linux-twom kernel: [ 9261.672512] ipaq 2-1:1.0: PocketPC PDA converter detected
Mar 3 18:03:34 linux-twom kernel: [ 9261.674104] usb 2-1: PocketPC PDA converter now attached to ttyUSB0
Mar 3 18:03:34 linux-twom hal-synce-serial[8144] DEBUG : running as addon for device /dev/ttyUSB0
Mar 3 18:03:34 linux-twom hal-synce-serial[8144] DEBUG : calling pppd as:
Mar 3 18:03:34 linux-twom hal-synce-serial[8144] DEBUG : ['/usr/sbin/pppd', '/dev/ttyUSB0', '115200', 'connect', '/usr/lib/synce-hal/synce-serial-chat', '192.168.131.1:192.168.131.129', 'ms-dns', '192.168.131.1', 'nodefaultroute', 'noauth', 'local', 'crtscts', 'updetach', 'linkname', 'synce-device0']
Mar 3 18:03:34 linux-twom pppd[8150]: pppd 2.4.5 started by root, uid 0
Mar 3 18:03:34 linux-twom pppd[8150]: Script /usr/lib/synce-hal/synce-serial-chat finished (pid 8151), status = 0x0
Mar 3 18:03:34 linux-twom pppd[8150]: Serial connection established.
Mar 3 18:03:34 linux-twom pppd[8150]: Using interface ppp0
Mar 3 18:03:34 linux-twom pppd[8150]: Connect: ppp0 <--> /dev/ttyUSB0
Mar 3 18:03:35 linux-twom pppd[8150]: local IP address 192.168.131.1
Mar 3 18:03:35 linux-twom pppd[8150]: remote IP address 192.168.131.129
Mar 3 18:03:35 linux-twom hal-synce-serial[8144] DEBUG : successfully configured interface
Mar 3 18:03:35 linux-twom hal-synce-serial[8144] DEBUG : starting hal-dccm ...
Mar 3 18:03:35 linux-twom hal-synce-serial[8144] DEBUG : calling hal-dccm as:
Mar 3 18:03:35 linux-twom hal-synce-serial[8144] DEBUG : ['/usr/lib/synce-hal/hal-dccm', '--device-ip=192.168.131.129', '--local-ip=192.168.131.1', '--log-level=6']
Mar 3 18:03:35 linux-twom hal-dccm[8144]: DEBUG: main: called with device-ip=192.168.131.129, local-ip=192.168.131.1
Mar 3 18:03:35 linux-twom hal-dccm[8144]: DEBUG: main: connected to hal, waiting for interface...
Mar 3 18:03:35 linux-twom hal-dccm[8144]: DEBUG: check_interface_cb: found device interface
Mar 3 18:03:35 linux-twom hal-dccm[8144]: DEBUG: check_interface_cb: listening for device
Mar 3 18:03:35 linux-twom SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Mar 3 18:03:35 linux-twom ip-up: SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'
Mar 3 18:03:35 linux-twom SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'
Mar 3 18:03:35 linux-twom SuSEfirewall2: using default zone 'ext' for interface ppp0
Mar 3 18:03:35 linux-twom SuSEfirewall2: batch committing...
Mar 3 18:03:35 linux-twom SuSEfirewall2: Firewall rules successfully set
Mar 3 18:03:35 linux-twom pppd[8157]: Script /etc/ppp/ip-up finished (pid 8158), status = 0x0

... on a side note, this is what happens now when I try pls again, even though I added SynCE as an allowed service:

***@linux-twom:~> pls
Unable to get the "My Documents" path.

... can someone please explain exactly what's going on here?

[Mark Ellis]

Post by John Cooper
Mar 3 18:03:34 linux-twom kernel: [ 9261.553092] usb 2-1: new high speed USB device using ehci_hcd and address 5
Mar 3 18:03:34 linux-twom kernel: [ 9261.671156] usb 2-1: New USB device found, idVendor=04e8, idProduct=6619
Mar 3 18:03:34 linux-twom kernel: [ 9261.671162] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 3 18:03:34 linux-twom kernel: [ 9261.671166] usb 2-1: Product: SGH-i637
Mar 3 18:03:34 linux-twom kernel: [ 9261.671170] usb 2-1: Manufacturer: Samsung Electronics
Mar 3 18:03:34 linux-twom kernel: [ 9261.671173] usb 2-1: SerialNumber: 32484557-5054-0801-fd5f-76803fbd49d0
Mar 3 18:03:34 linux-twom kernel: [ 9261.672512] ipaq 2-1:1.0: PocketPC PDA converter detected
Mar 3 18:03:34 linux-twom kernel: [ 9261.674104] usb 2-1: PocketPC PDA converter now attached to ttyUSB0
Mar 3 18:03:34 linux-twom hal-synce-serial[8144] DEBUG : running as addon for device /dev/ttyUSB0
Mar 3 18:03:34 linux-twom hal-synce-serial[8144] DEBUG : ['/usr/sbin/pppd', '/dev/ttyUSB0', '115200', 'connect', '/usr/lib/synce-hal/synce-serial-chat', '192.168.131.1:192.168.131.129', 'ms-dns', '192.168.131.1', 'nodefaultroute', 'noauth', 'local', 'crtscts', 'updetach', 'linkname', 'synce-device0']
Mar 3 18:03:34 linux-twom pppd[8150]: pppd 2.4.5 started by root, uid 0
Mar 3 18:03:34 linux-twom pppd[8150]: Script /usr/lib/synce-hal/synce-serial-chat finished (pid 8151), status = 0x0
Mar 3 18:03:34 linux-twom pppd[8150]: Serial connection established.
Mar 3 18:03:34 linux-twom pppd[8150]: Using interface ppp0
Mar 3 18:03:34 linux-twom pppd[8150]: Connect: ppp0 <--> /dev/ttyUSB0
Mar 3 18:03:35 linux-twom pppd[8150]: local IP address 192.168.131.1
Mar 3 18:03:35 linux-twom pppd[8150]: remote IP address 192.168.131.129
Mar 3 18:03:35 linux-twom hal-synce-serial[8144] DEBUG : successfully configured interface
Mar 3 18:03:35 linux-twom hal-synce-serial[8144] DEBUG : starting hal-dccm ...
Mar 3 18:03:35 linux-twom hal-synce-serial[8144] DEBUG : ['/usr/lib/synce-hal/hal-dccm', '--device-ip=192.168.131.129', '--local-ip=192.168.131.1', '--log-level=6']
Mar 3 18:03:35 linux-twom hal-dccm[8144]: DEBUG: main: called with device-ip=192.168.131.129, local-ip=192.168.131.1
Mar 3 18:03:35 linux-twom hal-dccm[8144]: DEBUG: main: connected to hal, waiting for interface...
Mar 3 18:03:35 linux-twom hal-dccm[8144]: DEBUG: check_interface_cb: found device interface
Mar 3 18:03:35 linux-twom hal-dccm[8144]: DEBUG: check_interface_cb: listening for device
Mar 3 18:03:35 linux-twom SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Mar 3 18:03:35 linux-twom ip-up: SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'
Mar 3 18:03:35 linux-twom SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'

Firewall.

Post by John Cooper
Mar 3 18:03:35 linux-twom SuSEfirewall2: using default zone 'ext' for interface ppp0
Mar 3 18:03:35 linux-twom SuSEfirewall2: batch committing...
Mar 3 18:03:35 linux-twom SuSEfirewall2: Firewall rules successfully set
Mar 3 18:03:35 linux-twom pppd[8157]: Script /etc/ppp/ip-up finished (pid 8158), status = 0x0
Unable to get the "My Documents" path.
... can someone please explain exactly what's going on here?
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
SynCE-Users mailing list
https://lists.sourceforge.net/lists/listinfo/synce-users

[John Cooper]

Ok, now I can connect to it ... but when I try to sync it, I get a message saying that ActiveSync has encountered an error, with a support code of 0x80070006 ... I have already added an exception for the SynCE service to the firewall, and again, disabling NetworkManager is *not* an option; so again, why is this happening, and how do I fix it?

[Tejas Guruswamy]

Post by John Cooper
Ok, now I can connect to it ... but when I try to sync it, I get a message saying that ActiveSync has encountered an error, with a support code of 0x80070006 ... I have already added an exception for the SynCE service to the firewall, and again, disabling NetworkManager is *not* an option; so again, why is this happening, and how do I fix it?

If you see activity in nm-applet (gnome) or plasmoid-networkmanagement
(kde) when you connect your device, then:

Edit /etc/NetworkManager/nm-system-settings.conf and add the following lines
"
[main]
plugins=keyfile,ifcfg-suse

[keyfile]
unmanaged-devices=mac:<your:device:mac:address>
"
e.g.
unmanaged-devices=mac:80:00:60:0f:e7:00

You can find the MAC address of your device in the output of lshal (look
for net.address of the relevant device).
If it's not NetworkManager or the firewall, some more log info would be
helpful. Edit /etc/synce-hal.conf and uncomment the "loglevel: debug"
line, then post relevant bits from /var/log/messages.

Tejas