synce, ipaq, ppp

Discussion:

synce, ipaq, ppp

W***@abercrombie.com

2010-10-01 19:38:26 UTC

Forgot to mention that openSuse 10/11 is the system here, so is udev to be
blamed here?

From:
Wei Wang/Abercrombie
To:
synce-***@lists.sourceforge.net
Date:
10/01/2010 03:14 PM
Subject:
synce, ipaq, ppp

Please help with this inconsistency we found out about ipaq/synce/ppp.
(Sorry, not sure which one is at fault, thus needing help). The ppp daemon
failed to start on Oct 1, comparing to Sep 30 as shown below. Any ideas?
What exactly gets ppp started? Thanks.

Wei

Sep 30 21:42:06 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 24
Sep 30 21:42:06 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Sep 30 21:42:06 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Sep 30 21:42:06 kernel: usb 3-2.3: PocketPC PDA converter now attached to
ttyUSB0
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device found, idVendor=05f9,
idProduct=04ce
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Sep 30 21:42:06 pppd[3180]: pppd 2.4.5 started by root, uid 0

Oct 1 11:11:29 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 6
Oct 1 11:11:29 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Oct 1 11:11:29 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Oct 1 11:11:29 kernel: usb 3-2.3: PocketPC PDA converter now attached to
ttyUSB0
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device found, idVendor=05f9,
idProduct=04ce
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Oct 1 11:12:01 /usr/sbin/cron[25072]: ......

W***@abercrombie.com

2010-10-01 19:14:52 UTC

Permalink

Please help with this inconsistency we found out about ipaq/synce/ppp.
(Sorry, not sure which one is at fault, thus needing help). The ppp daemon
failed to start on Oct 1, comparing to Sep 30 as shown below. Any ideas?
What exactly gets ppp started? Thanks.

Wei

Sep 30 21:42:06 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 24
Sep 30 21:42:06 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Sep 30 21:42:06 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Sep 30 21:42:06 kernel: usb 3-2.3: PocketPC PDA converter now attached to
ttyUSB0
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device found, idVendor=05f9,
idProduct=04ce
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Sep 30 21:42:06 pppd[3180]: pppd 2.4.5 started by root, uid 0

Oct 1 11:11:29 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 6
Oct 1 11:11:29 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Oct 1 11:11:29 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Oct 1 11:11:29 kernel: usb 3-2.3: PocketPC PDA converter now attached to
ttyUSB0
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device found, idVendor=05f9,
idProduct=04ce
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Oct 1 11:12:01 /usr/sbin/cron[25072]: ......

W***@abercrombie.com

2010-10-04 18:19:09 UTC

Permalink

After doing some research on my own, I suspect this inconsistent behavior
is likely caused by hal or synce-hal. I recall when I ran lsusb and dmesg,
both reported the device is connected. That matches what the kernel had
reported. But somehow pppd was not called, which is the responsibility of
/usr/lib/hal/scripts/hal-synce-serial.

This one is hard to troubleshoot as it only happens randomly. Any help is
very much appreciated, thanks!

Wei

From:
Wei Wang/Abercrombie
To:
synce-***@lists.sourceforge.net
Date:
10/01/2010 03:38 PM
Subject:
Re: synce, ipaq, ppp

Forgot to mention that openSuse 10/11 is the system here, so is udev to be
blamed here?

From:
Wei Wang/Abercrombie
To:
synce-***@lists.sourceforge.net
Date:
10/01/2010 03:14 PM
Subject:
synce, ipaq, ppp

Please help with this inconsistency we found out about ipaq/synce/ppp.
(Sorry, not sure which one is at fault, thus needing help). The ppp daemon
failed to start on Oct 1, comparing to Sep 30 as shown below. Any ideas?
What exactly gets ppp started? Thanks.

Wei

Sep 30 21:42:06 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 24
Sep 30 21:42:06 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Sep 30 21:42:06 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Sep 30 21:42:06 kernel: usb 3-2.3: PocketPC PDA converter now attached to
ttyUSB0
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device found, idVendor=05f9,
idProduct=04ce
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Sep 30 21:42:06 pppd[3180]: pppd 2.4.5 started by root, uid 0

Oct 1 11:11:29 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 6
Oct 1 11:11:29 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Oct 1 11:11:29 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Oct 1 11:11:29 kernel: usb 3-2.3: PocketPC PDA converter now attached to
ttyUSB0
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device found, idVendor=05f9,
idProduct=04ce
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Oct 1 11:12:01 /usr/sbin/cron[25072]: ......

Tejas Guruswamy

2010-10-04 21:03:39 UTC

Permalink

Post by W***@abercrombie.com
After doing some research on my own, I suspect this inconsistent
behavior is likely caused by hal or synce-hal. I recall when I ran
lsusb and dmesg, both reported the device is connected. That matches
what the kernel had reported. But somehow pppd was not called, which
is the responsibility of /usr/lib/hal/scripts/hal-synce-serial.
This one is hard to troubleshoot as it only happens randomly. Any help
is very much appreciated, thanks!
Wei
Forgot to mention that openSuse 10/11 is the system here, so is udev
to be blamed here?
Please help with this inconsistency we found out about ipaq/synce/ppp.
(Sorry, not sure which one is at fault, thus needing help). The ppp
daemon failed to start on Oct 1, comparing to Sep 30 as shown below.
Any ideas? What exactly gets ppp started? Thanks.
Wei
Sep 30 21:42:06 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 24
Sep 30 21:42:06 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Sep 30 21:42:06 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Sep 30 21:42:06 kernel: usb 3-2.3: PocketPC PDA converter now attached
to ttyUSB0
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device found,
idVendor=05f9, idProduct=04ce
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Sep 30 21:42:06 pppd[3180]: pppd 2.4.5 started by root, uid 0
Oct 1 11:11:29 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 6
Oct 1 11:11:29 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Oct 1 11:11:29 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Oct 1 11:11:29 kernel: usb 3-2.3: PocketPC PDA converter now attached
to ttyUSB0
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device found,
idVendor=05f9, idProduct=04ce
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Oct 1 11:12:01 /usr/sbin/cron[25072]: ......

Could you edit /etc/synce-hal.conf to uncomment the "loglevel: debug"
entry and post new info from /var/log/messages? It should have some
extra debug output from synce-hal.

Regards,
Tejas

W***@abercrombie.com

2010-10-04 21:33:51 UTC

Permalink

Looks like hal-synce-serial was not invoked. Hal problem, kernel problem?
Thanks. -Wei

Oct 4 14:08:19 kernel: usb 3-1.3: new full speed USB device using
uhci_hcd and address 12
Oct 4 14:08:19 kernel: usb 3-1.3: configuration #1 chosen from 1 choice
Oct 4 14:08:19 kernel: ipaq 3-1.3:1.0: PocketPC PDA converter detected
Oct 4 14:08:19 kernel: usb 3-1.3: PocketPC PDA converter now attached to
ttyUSB0
Oct 4 14:08:19 kernel: usb 3-1.3: New USB device found, idVendor=05f9,
idProduct=04ce
Oct 4 14:08:19 kernel: usb 3-1.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Oct 4 14:08:19 hal-synce-serial[13190] DEBUG : running as addon for
device /dev/ttyUSB0
Oct 4 14:08:19 hal-synce-serial[13190] DEBUG : calling pppd as: ...
Oct 4 14:08:19 pppd[13193]: pppd 2.4.5 started by root, uid 0

Oct 4 14:26:29 kernel: usb 3-1.3: new full speed USB device using
uhci_hcd and address 21
Oct 4 14:26:29 kernel: usb 3-1.3: configuration #1 chosen from 1 choice
Oct 4 14:26:29 kernel: ipaq 3-1.3:1.0: PocketPC PDA converter detected
Oct 4 14:26:29 kernel: usb 3-1.3: PocketPC PDA converter now attached to
ttyUSB0
Oct 4 14:26:29 kernel: usb 3-1.3: New USB device found, idVendor=05f9,
idProduct=04ce
Oct 4 14:26:29 kernel: usb 3-1.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Oct 4 14:27:01 /usr/sbin/cron[14921]: ...

From:
Tejas Guruswamy <***@gmail.com>
To:
***@abercrombie.com
Cc:
synce-***@lists.sourceforge.net
Date:
10/04/2010 05:03 PM
Subject:
Re: synce, ipaq, ppp

On 04/10/10 19:19, ***@abercrombie.com wrote:
After doing some research on my own, I suspect this inconsistent behavior
is likely caused by hal or synce-hal. I recall when I ran lsusb and dmesg,
both reported the device is connected. That matches what the kernel had
reported. But somehow pppd was not called, which is the responsibility of
/usr/lib/hal/scripts/hal-synce-serial.

This one is hard to troubleshoot as it only happens randomly. Any help is
very much appreciated, thanks!

Wei

Forgot to mention that openSuse 10/11 is the system here, so is udev to be
blamed here?

Please help with this inconsistency we found out about ipaq/synce/ppp.
(Sorry, not sure which one is at fault, thus needing help). The ppp daemon
failed to start on Oct 1, comparing to Sep 30 as shown below. Any ideas?
What exactly gets ppp started? Thanks.

Wei

Sep 30 21:42:06 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 24
Sep 30 21:42:06 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Sep 30 21:42:06 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Sep 30 21:42:06 kernel: usb 3-2.3: PocketPC PDA converter now attached to
ttyUSB0
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device found, idVendor=05f9,
idProduct=04ce
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Sep 30 21:42:06 pppd[3180]: pppd 2.4.5 started by root, uid 0

Oct 1 11:11:29 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 6
Oct 1 11:11:29 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Oct 1 11:11:29 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Oct 1 11:11:29 kernel: usb 3-2.3: PocketPC PDA converter now attached to
ttyUSB0
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device found, idVendor=05f9,
idProduct=04ce
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Oct 1 11:12:01 /usr/sbin/cron[25072]: ......
Could you edit /etc/synce-hal.conf to uncomment the "loglevel: debug"
entry and post new info from /var/log/messages? It should have some extra
debug output from synce-hal.

Regards,
Tejas

Tejas Guruswamy

2010-10-05 07:40:16 UTC

Permalink

Post by W***@abercrombie.com
Looks like hal-synce-serial was not invoked. Hal problem, kernel
problem? Thanks. -Wei
Oct 4 14:08:19 kernel: usb 3-1.3: new full speed USB device using
uhci_hcd and address 12
Oct 4 14:08:19 kernel: usb 3-1.3: configuration #1 chosen from 1 choice
Oct 4 14:08:19 kernel: ipaq 3-1.3:1.0: PocketPC PDA converter detected
Oct 4 14:08:19 kernel: usb 3-1.3: PocketPC PDA converter now attached
to ttyUSB0
Oct 4 14:08:19 kernel: usb 3-1.3: New USB device found,
idVendor=05f9, idProduct=04ce
Oct 4 14:08:19 kernel: usb 3-1.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Oct 4 14:08:19 hal-synce-serial[13190] DEBUG : running as addon for
device /dev/ttyUSB0
Oct 4 14:08:19 hal-synce-serial[13190] DEBUG : calling pppd as: ...
Oct 4 14:08:19 pppd[13193]: pppd 2.4.5 started by root, uid 0
Oct 4 14:26:29 kernel: usb 3-1.3: new full speed USB device using
uhci_hcd and address 21
Oct 4 14:26:29 kernel: usb 3-1.3: configuration #1 chosen from 1 choice
Oct 4 14:26:29 kernel: ipaq 3-1.3:1.0: PocketPC PDA converter detected
Oct 4 14:26:29 kernel: usb 3-1.3: PocketPC PDA converter now attached
to ttyUSB0
Oct 4 14:26:29 kernel: usb 3-1.3: New USB device found,
idVendor=05f9, idProduct=04ce
Oct 4 14:26:29 kernel: usb 3-1.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Oct 4 14:27:01 /usr/sbin/cron[14921]: ...
After doing some research on my own, I suspect this inconsistent
behavior is likely caused by hal or synce-hal. I recall when I ran
lsusb and dmesg, both reported the device is connected. That matches
what the kernel had reported. But somehow pppd was not called, which
is the responsibility of /usr/lib/hal/scripts/hal-synce-serial.
This one is hard to troubleshoot as it only happens randomly. Any help
is very much appreciated, thanks!
Wei
Forgot to mention that openSuse 10/11 is the system here, so is udev
to be blamed here?
Please help with this inconsistency we found out about ipaq/synce/ppp.
(Sorry, not sure which one is at fault, thus needing help). The ppp
daemon failed to start on Oct 1, comparing to Sep 30 as shown below.
Any ideas? What exactly gets ppp started? Thanks.
Wei
Sep 30 21:42:06 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 24
Sep 30 21:42:06 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Sep 30 21:42:06 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Sep 30 21:42:06 kernel: usb 3-2.3: PocketPC PDA converter now attached
to ttyUSB0
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device found,
idVendor=05f9, idProduct=04ce
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Sep 30 21:42:06 pppd[3180]: pppd 2.4.5 started by root, uid 0
Oct 1 11:11:29 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 6
Oct 1 11:11:29 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Oct 1 11:11:29 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter detected
Oct 1 11:11:29 kernel: usb 3-2.3: PocketPC PDA converter now attached
to ttyUSB0
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device found,
idVendor=05f9, idProduct=04ce
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Oct 1 11:12:01 /usr/sbin/cron[25072]: ......
Could you edit /etc/synce-hal.conf to uncomment the "loglevel: debug"
entry and post new info from /var/log/messages? It should have some
extra debug output from synce-hal.
Regards,
Tejas

I assume that the top log is when it was working, and the bottom when it
was not; then yes, it looks like the problem is hal-synce-rndis is never
started.

Could you send the part of "lshal" output relevant to your device once
it is connected in a working/non-working state?

Regards,
Tejas

Mark Ellis

2010-10-05 11:23:00 UTC

Permalink

Is hal running ?

Post by W***@abercrombie.com
Product=0, SerialNumber=0
Oct 4 14:27:01 /usr/sbin/cron[14921]: ...
Tejas Guruswamy
10/04/2010 05:03 PM
Re: synce, ipaq, ppp
______________________________________________________________________
After doing some research on my own, I suspect this inconsistent
behavior is likely caused by hal or synce-hal. I recall when I ran
lsusb and dmesg, both reported the device is connected. That matches
what the kernel had reported. But somehow pppd was not called, which
is the responsibility of /usr/lib/hal/scripts/hal-synce-serial.
This one is hard to troubleshoot as it only happens randomly. Any help
is very much appreciated, thanks!
Wei
Forgot to mention that openSuse 10/11 is the system here, so is udev
to be blamed here?
Please help with this inconsistency we found out about ipaq/synce/ppp.
(Sorry, not sure which one is at fault, thus needing help). The ppp
daemon failed to start on Oct 1, comparing to Sep 30 as shown below.
Any ideas? What exactly gets ppp started? Thanks.
Wei
Sep 30 21:42:06 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 24
Sep 30 21:42:06 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Sep 30 21:42:06 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter
detected
Sep 30 21:42:06 kernel: usb 3-2.3: PocketPC PDA converter now attached
to ttyUSB0
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device found,
idVendor=05f9, idProduct=04ce
Sep 30 21:42:06 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Sep 30 21:42:06 pppd[3180]: pppd 2.4.5 started by root, uid 0
Oct 1 11:11:29 kernel: usb 3-2.3: new full speed USB device using
uhci_hcd and address 6
Oct 1 11:11:29 kernel: usb 3-2.3: configuration #1 chosen from 1 choice
Oct 1 11:11:29 kernel: ipaq 3-2.3:1.0: PocketPC PDA converter
detected
Oct 1 11:11:29 kernel: usb 3-2.3: PocketPC PDA converter now attached
to ttyUSB0
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device found,
idVendor=05f9, idProduct=04ce
Oct 1 11:11:29 kernel: usb 3-2.3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Oct 1 11:12:01 /usr/sbin/cron[25072]: ......
Could you edit /etc/synce-hal.conf to uncomment the "loglevel: debug"
entry and post new info from /var/log/messages? It should have some
extra debug output from synce-hal.
Regards,
Tejas

W***@abercrombie.com

2010-10-05 13:07:04 UTC

Permalink

Hal is definitely running. lshal reports the same. lsusb reports the same.
dmesg reports the same.

The device is sitting in a cradle, which is connected to the host via USB
cable. If I take the device out of the cradle and set it back in, it gets
ppp running 99.9%. The other 0.1% is what you see below that ppp never
starts.

Wei

From:
Mark Ellis <***@mpellis.org.uk>
To:
<synce-***@lists.sourceforge.net>
Date:
10/05/2010 07:23 AM
Subject:
Re: synce, ipaq, ppp

Is hal running ?

[attachment "signature.asc" deleted by Wei Wang/Abercrombie]
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb_______________________________________________

SynCE-Users mailing list
SynCE-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-users

W***@abercrombie.com

2010-10-05 16:02:58 UTC

Permalink

Sorry, I was wrong. lshal shows different output. This part is missing
when synce fail to start. udi
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0' is present
in both, but
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0_serial_usb_0'
is not.

udi =
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0_serial_usb_0'
access_control.file = '/dev/ttyUSB0' (string)
access_control.type = 'modem' (string)
info.addons = {'hal-synce-serial'} (string list)
info.callouts.add = {'hal-acl-tool --add-device'} (string list)
info.callouts.remove = {'hal-acl-tool --remove-device'} (string list)
info.capabilities = {'serial', 'access_control', 'sync', 'pda'} (string
list)
info.category = 'pda' (string)
info.interfaces = {'org.freedesktop.Hal.Device.Synce'} (string list)
info.parent =
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0' (string)
info.product = 'Pocket PC PDA' (string)
info.subsystem = 'tty' (string)
info.udi =
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0_serial_usb_0'
(string)
linux.device_file = '/dev/ttyUSB0' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'tty' (string)
linux.sysfs_path =
'/sys/devices/pci0000:00/0000:00:10.1/usb3/3-1/3-1.3/3-1.3:1.0/ttyUSB0/tty/ttyUSB0'
(string)
pda.platform = 'pocketpc' (string)
pda.pocketpc.cpu_type = 2577 (0xa11) (uint64)
pda.pocketpc.current_partner_id = 0 (0x0) (uint64)
......
pda.pocketpc.os_major = 4 (0x4) (uint64)
pda.pocketpc.os_minor = 20 (0x14) (uint64)
pda.pocketpc.password = 'unset' (string)
pda.pocketpc.platform = 'Falcon Platform' (string)
pda.pocketpc.version = 0 (0x0) (uint64)
serial.device = '/dev/ttyUSB0' (string)
serial.originating_device =
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0' (string)
serial.port = 0 (0x0) (int)
serial.type = 'usb' (string)
sync.engine = 'opensync' (string)
sync.plugin = 'synce' (string)
usb.interface.description = 'Windows Mobile Data Provider' (string)
usb.product = 'Windows Mobile Device' (string)

From:
Mark Ellis <***@mpellis.org.uk>
To:
<synce-***@lists.sourceforge.net>
Date:
10/05/2010 07:23 AM
Subject:
Re: synce, ipaq, ppp

Is hal running ?

W***@abercrombie.com

2010-10-05 16:30:58 UTC

Permalink

Here is the different output from lshal. I can send you the complete
output if you need it.

GOOD:

udi =
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0_serial_usb_0'
access_control.file = '/dev/ttyUSB0' (string)
access_control.type = 'modem' (string)
info.addons = {'hal-synce-serial'} (string list)
info.callouts.add = {'hal-acl-tool --add-device'} (string list)
info.callouts.remove = {'hal-acl-tool --remove-device'} (string list)
info.capabilities = {'serial', 'access_control', 'sync', 'pda'} (string
list)
info.category = 'pda' (string)
info.interfaces = {'org.freedesktop.Hal.Device.Synce'} (string list)
info.parent =
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0' (string)
info.product = 'Pocket PC PDA' (string)
info.subsystem = 'tty' (string)
info.udi =
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0_serial_usb_0'
(string)
linux.device_file = '/dev/ttyUSB0' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'tty' (string)
linux.sysfs_path =
'/sys/devices/pci0000:00/0000:00:10.0/usb2/2-1/2-1:1.0/ttyUSB0/tty/ttyUSB0'
(string)
pda.platform = 'pocketpc' (string)
pda.pocketpc.cpu_type = 2577 (0xa11) (uint64)
pda.pocketpc.current_partner_id = 0 (0x0) (uint64)
......
pda.pocketpc.os_major = 4 (0x4) (uint64)
pda.pocketpc.os_minor = 20 (0x14) (uint64)
pda.pocketpc.password = 'unset' (string)
pda.pocketpc.platform = 'Falcon Platform' (string)
pda.pocketpc.version = 0 (0x0) (uint64)
serial.device = '/dev/ttyUSB0' (string)
serial.originating_device =
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0' (string)
serial.port = 0 (0x0) (int)
serial.type = 'usb' (string)
sync.engine = 'opensync' (string)
sync.plugin = 'synce' (string)
usb.interface.description = 'Windows Mobile Data Provider' (string)
usb.product = 'Windows Mobile Device' (string)

BAD:

udi =
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_serial_usb_0'
access_control.file = '/dev/ttyUSB0' (string)
access_control.type = 'modem' (string)
info.callouts.add = {'hal-acl-tool --add-device'} (string list)
info.callouts.remove = {'hal-acl-tool --remove-device'} (string list)
info.capabilities = {'serial', 'access_control'} (string list)
info.category = 'serial' (string)
info.parent = '/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial'
(string)
info.product = '1.1 root hub' (string)
info.subsystem = 'tty' (string)
info.udi =
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_serial_usb_0'
(string)
linux.device_file = '/dev/ttyUSB0' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'tty' (string)
linux.sysfs_path =
'/sys/devices/pci0000:00/0000:00:10.0/usb2/2-1/2-1:1.0/ttyUSB0/tty/ttyUSB0'
(string)
serial.device = '/dev/ttyUSB0' (string)
serial.originating_device =
'/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial' (string)
serial.port = 0 (0x0) (int)
serial.type = 'usb' (string)

W***@abercrombie.com

2010-10-06 14:43:24 UTC

Permalink

I attached both lshal output. It seems to me the bad one somehow built
/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_serial_usb_0 off
the wrong parent. Instead of it being the child of
/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0, it is being
built as its sibling. Both extends from
/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial.

Thanks.

Wei

W***@abercrombie.com

2010-10-11 18:30:37 UTC

Permalink

I am not making any progress on this one. Please help, any ideas?

Wei

From:
Wei Wang/Abercrombie
To:
Mark Ellis <***@mpellis.org.uk>
Cc:
synce-***@lists.sourceforge.net
Date:
10/06/2010 10:43 AM
Subject:
Re: synce, ipaq, ppp

I attached both lshal output. It seems to me the bad one somehow built
/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_serial_usb_0 off
the wrong parent. Instead of it being the child of
/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0, it is being
built as its sibling. Both extends from
/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial.

Thanks.

Wei

[attachment "hal-good.txt" deleted by Wei Wang/Abercrombie] [attachment
"hal-bad.txt" deleted by Wei Wang/Abercrombie]

Tejas Guruswamy

2010-10-24 08:52:33 UTC

Permalink

Post by W***@abercrombie.com
I am not making any progress on this one. Please help, any ideas?
Wei
I attached both lshal output. It seems to me the bad one somehow built
/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_serial_usb_0
off the wrong parent. Instead of it being the child of
/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial_if0, it is
being built as its sibling. Both extends from
/org/freedesktop/Hal/devices/usb_device_5f9_4ce_noserial.
Thanks.
Wei

It looks like a hal issue. Maybe someone on the hal mailing list / IRC
could understand better what was going on? It's way beyond my level
anyway, sorry...

http://lists.freedesktop.org/mailman/listinfo/hal

The fact that it doesn't happen every time just makes it so much harder
to debug too ...

Regards,
Tejas