T-Mobile MDA compact III - no joy
|
View:
New views
18 Messages
—
Rating Filter:
Alert me
|
 |
T-Mobile MDA compact III - no joy
by Tilman Schmidt-2
::
Rate this Message:
|
|
|
Re: T-Mobile MDA compact III - no joy
by Mark Ellis
::
Rate this Message:
On Fri, 2009-09-25 at 15:16 +0200, Tilman Schmidt wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > While trying to get SynCE to talk to my T-Mobile MDA compact III on > openSUSE 10.3 I'm encountering a series of problems making me wonder if > I am missing something basic, or if this is supposed to work at all. > > The MDA is made by HTC, Model ARTE110 according to a label in the > battery compartment, and runs Windows Mobile 5.0 (OS 5.1.342 Build > 15096.3.0.0 according to System Info.) My PC is a Pentium D on an Intel > DQ965GF mainboard, running openSUSE 10.3 with Gnome desktop and all > online updates installed. I am connecting the MDA to the PC via its USB > cable, and it is identified by lsusb as: > ID 0bb4:0bce High Tech Computer Corp. Vario MDA know. > I am trying to follow the instructions on > http://www.synce.org/moin/SynceInstallation/OpenSuse and have installed > SynCE via the 1-click link > http://download.opensuse.org/repositories/system://SynCE/openSUSE_10.3/synce-gnome.ymp > > Problem #0 - bugs in the ymp file: > At the end of the install, YaST complained that it couldn't install the > packages "gcemirror" (which doesn't seem to exist, only "kcemirror" > does), "libopensynce-plugin-synce" (note the extra 'e' after "opensync") > and "synce-gvfs" (the correct name is "synce-gnomevfs"). Not a big deal, > but annoying, and it left me wondering whether anybody actually tried > this before me. > gnome version then gvfs is correct, its the replacement to gnomevfs. > Problem #1 - a Linux kernel bug: > The ipaq driver claims the MDA's RNDIS interface (USB interface #0), > only to throw a NULL pointer BUG as soon as it was asked to actually do > anything with it. Apparently a known and recurring bug, twice reported > as fixed in Kernel Bugzilla > (http://bugzilla.kernel.org/show_bug.cgi?id=8094 and > http://bugzilla.kernel.org/show_bug.cgi?id=10868) but still regularly > reported on http://kerneloops.org. The bug occurred with openSUSE kernel > 2.6.22.19-0.4 as well as the then latest vanilla kernel 2.6.31. After > discussing it on the linux-usb mailing list, Alan Stern provided a > preliminary patch (http://lkml.org/lkml/2009/9/20/188). With that patch > applied to kernel 2.6.31, the ipaq driver now claims only interface 1, > leaving interface 0 to the rndis_host driver which I guess is correct. > Note that this patch still has to make it into the official kernel. > device is in rndis (advanced) mode, ipaq shouldn't try to claim it, but I think at some point someone got carried away about putting device ids in the ipaq driver. The safest way is to blacklist the ipaq driver if its getting in the way. > Problem #2 - rndis_host error: > Even with that patch in place, the first attempt of the rndis_host > driver to attach to interface 0 always fails with the kernel message: > > rndis_host: probe of 3-2:1.0 failed with error -16 > Dont know what that one means. > After unplugging the USB cable and plugging it in again, it will emit > another error message, followed by something that looks like it now > attached successfully: > > rndis_host 3-2:1.0: RNDIS_MSG_QUERY(0x00010202) failed, -47 > eth1: register 'rndis_host' at usb-0000:00:1a.1-2, RNDIS device, > 80:00:60:0f:e8:00 > That looks reasonable. > Problem #3 - synce-serial-chat hang: > After unplugging the USB cable as described above, CPU load went to 100% > from the process /usr/lib/synce-hal/synce-serial-chat, child of > > /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 > That shouldn't be running. Definitely blacklist ipaq > Killing it produced the syslog messages > > pppd[4813]: Connect script failed > xenon pppd[4813]: Exit. > xenon powersaved[3942]: WARNING (filter_function:201) Hal service > stopped. Battery information no longer available > > and indeed, the haldaemon service was dead, though I could restart it > without a problem and everything seemed well again. > > Problem #4: bad dhclient.conf: > After rndis_host registered its eth device, dhclient complained to syslog: > > dhclient: Internet Systems Consortium DHCP Client V3.0.6 > dhclient: Copyright 2004-2007 Internet Systems Consortium. > dhclient: All rights reserved. > dhclient: For info, please visit http://www.isc.org/sw/dhcp/ > dhclient: > dhclient: /usr/share/synce-hal/dhclient.conf line 8: no option named > domain-search > dhclient: domain-name, domain-name-servers, domain-search, > dhclient: ^ > dhclient: /usr/share/synce-hal/dhclient.conf line 9: interface-mtu: > expected option name. > dhclient: netbios-name-servers, netbios-scope, interface-mtu; > dhclient: ^ > dhclient: Listening on LPF/eth2/80:00:60:0f:e8:00 > dhclient: Sending on LPF/eth2/80:00:60:0f:e8:00 > dhclient: Can't bind to dhcp address: Address already in use > dhclient: Please make sure there is no other dhcp server > dhclient: running and that there's no entry for dhcp or > dhclient: bootp in /etc/inetd.conf. Also make sure you > [snip] > dhclient: > dhclient: exiting. > hal-synce-rndis[5071] ERROR : dhclient failed with return code 1 > > There is no other DHCP *server* running on this PC; there is, however, > another DHCP *client* running, since that's how it gets its regular > Ethernet IP address. Surely that shouldn't prevent the use of SynCE? > because the early stages didn't work. As for the option errors above, whoever prepares the suse packages needs to compensate if a particular version complains. > Problem #5 - synce-trayicon crash: > Meanwhile, on the Gnome desktop, a Bug-Buddy window appeared, announcing > "The application synce-trayicon has crashed." This window reappeared > each time I closed it, until I disconnected the USB cable again. > It wont work because you're not connected, but I'd hope it doesn't crash. What version ? > Problem #6 - Troubleshooting dead end: > Following the "Troubleshooting" section of the Wiki article, I tried to > run the pls command as instructed (while the USB cable was still > connected, of course - just leaving the Bug-Buddy window open), but it > only emits: > > pls: Could not find configuration at path '(Default)' > > I classified that as "not seeing a list of files on your device" and > tried to follow the "see below" link, but the #Information anchor > doesn't seem to exist. Blacklist ipaq and try again. > > Any chance of getting this to work? > > TIA, > Tilman > > - -- > Tilman Schmidt E-Mail: tilman@... > Bonn, Germany > Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. > Ungeöffnet mindestens haltbar bis: (siehe Rückseite) > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.4 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFKvMKTQ3+did9BuFsRAiHJAJsHTt7SPfek3euYYLm9RH6cxkbxHACfdEKW > XPGntf5DVupNrsmM1O7C+4s= > =ah3Z > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > SynCE-Users mailing list > SynCE-Users@... > https://lists.sourceforge.net/lists/listinfo/synce-users ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
|
Re: T-Mobile MDA compact III - no joy
by masterpatricko
::
Rate this Message:
|
|
|
Re: T-Mobile MDA compact III - no joy
by Tilman Schmidt-2
::
Rate this Message:
|
|
|
Re: T-Mobile MDA compact III - no joy
by Tilman Schmidt-2
::
Rate this Message:
|
|
|
Re: T-Mobile MDA compact III - no joy
by masterpatricko
::
Rate this Message:
|
|
|
Re: T-Mobile MDA compact III - no joy
by Mark Ellis
::
Rate this Message:
On Tue, 2009-09-29 at 12:38 +0200, Tilman Schmidt wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Mark, > > thanks a lot for your answer. > > On Tue, 2009-09-29 07:18:53 +0100, Mark Ellis wrote: > > Please send a verbose output from lsusb, it may not help but you never > > know. > > ts@xenon:~> sudo lsusb -v -d 0bb4: > > Bus 003 Device 002: ID 0bb4:0bce High Tech Computer Corp. Vario MDA > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 239 Miscellaneous Device > bDeviceSubClass 1 ? > bDeviceProtocol 1 Microsoft ActiveSync > bMaxPacketSize0 64 > idVendor 0x0bb4 High Tech Computer Corp. > idProduct 0x0bce Vario MDA > bcdDevice 0.00 > iManufacturer 1 HTC > iProduct 2 Generic RNDIS > iSerial 3 66460e0b-5ccf-7103-e800-0050bf3f5173 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 62 > bNumInterfaces 2 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xc0 > Self Powered > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 239 Miscellaneous Device > bInterfaceSubClass 1 ? > bInterfaceProtocol 1 Microsoft ActiveSync > iInterface 0 > ** UNRECOGNIZED: 05 24 01 00 01 > ** UNRECOGNIZED: 04 24 02 00 > ** UNRECOGNIZED: 05 24 02 00 01 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 1 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 10 CDC Data > bInterfaceSubClass 0 Unused > bInterfaceProtocol 0 > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 EP 3 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 0 > Device Status: 0x0000 > (Bus Powered) > > >> Problem #5 - synce-trayicon crash: > >> Meanwhile, on the Gnome desktop, a Bug-Buddy window appeared, announcing > >> "The application synce-trayicon has crashed." This window reappeared > >> each time I closed it, until I disconnected the USB cable again. > > > > It wont work because you're not connected, but I'd hope it doesn't > > crash. What version ? > > ts@xenon:~> rpm -q synce-trayicon > synce-trayicon-0.13-3.7 > > >> pls: Could not find configuration at path '(Default)' > > > You're not connected yet. > > > > Blacklist ipaq and try again. > > Will do. > > So the ipaq driver isn't supposed to attach to that device at all? mode than in rndis mode, and ipaq should only attach to the serial version. > Would it be a good idea if I submitted a kernel patch to remove > its USB ID from the list of IDs the ipaq driver claims to handle? Yep, that would be good. At some point someone got carried away and put tons of ids in the ipaq driver, but a lot of them are probably rndis ones. > > Thanks again, > Tilman > > - -- > Tilman Schmidt E-Mail: tilman@... > Bonn, Germany > Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. > Ungeöffnet mindestens haltbar bis: (siehe Rückseite) > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.4 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFKweOhQ3+did9BuFsRAsZRAJ93TvunlQEnbdCR7+roc+Tv3VrnjACgmoMa > 37owdiUTLPF4y9oC7UWxcj0= > =4Ojc > -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
|
Re: T-Mobile MDA compact III - no joy
by Tilman Schmidt-2
::
Rate this Message:
On Tue, 2009-09-29 07:18:53 +0100, Mark Ellis wrote:
> Blacklist ipaq and try again. Did that now, but it didn't change much. The pls command still reports: pls: Could not find configuration at path '(Default)' Syslog looks more or less like before, except for the absence of ipaq. I have activated "loglevel: debug" in /etc/synce-hal.conf, and this is what I see in syslog now, from when I connect the device: Sep 29 23:56:50 xenon kernel: [616401.074588] usb usb2: usb resume Sep 29 23:56:50 xenon kernel: [616401.074597] ehci_hcd 0000:00:1a.7: resume root hub Sep 29 23:56:50 xenon kernel: [616401.195262] ehci_hcd 0000:00:1a.7: port 4 full speed --> companion Sep 29 23:56:50 xenon kernel: [616401.195273] ehci_hcd 0000:00:1a.7: GetStatus port 4 status 003801 POWER OWNER sig=j CONNECT Sep 29 23:56:50 xenon kernel: [616401.206034] hub 2-0:1.0: hub_resume Sep 29 23:56:50 xenon kernel: [616401.206087] ehci_hcd 0000:00:1a.7: GetStatus port 4 status 003002 POWER OWNER sig=se0 CSC Sep 29 23:56:50 xenon kernel: [616401.307154] usb usb3: usb resume Sep 29 23:56:50 xenon kernel: [616401.307162] usb usb3: wakeup_rh Sep 29 23:56:50 xenon kernel: [616401.307177] hub 2-0:1.0: state 7 ports 4 chg 0000 evt 0000 Sep 29 23:56:50 xenon kernel: [616401.339032] hub 3-0:1.0: hub_resume Sep 29 23:56:50 xenon kernel: [616401.339066] uhci_hcd 0000:00:1a.1: port 2 portsc 0093,00 Sep 29 23:56:50 xenon kernel: [616401.339075] hub 3-0:1.0: port 2: status 0101 change 0001 Sep 29 23:56:50 xenon kernel: [616401.440160] hub 3-0:1.0: state 7 ports 2 chg 0004 evt 0000 Sep 29 23:56:50 xenon kernel: [616401.440186] hub 3-0:1.0: port 2, status 0101, change 0000, 12 Mb/s Sep 29 23:56:50 xenon kernel: [616401.542149] usb 3-2: new full speed USB device using uhci_hcd and address 6 Sep 29 23:56:50 xenon kernel: [616401.685060] usb 3-2: skipped 3 descriptors after interface Sep 29 23:56:50 xenon kernel: [616401.690060] usb 3-2: default language 0x0409 Sep 29 23:56:50 xenon kernel: [616401.706090] usb 3-2: udev 6, busnum 3, minor = 261 Sep 29 23:56:50 xenon kernel: [616401.706097] usb 3-2: New USB device found, idVendor=0bb4, idProduct=0bce Sep 29 23:56:50 xenon kernel: [616401.706103] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 29 23:56:50 xenon kernel: [616401.706108] usb 3-2: Product: Generic RNDIS Sep 29 23:56:50 xenon kernel: [616401.706112] usb 3-2: Manufacturer: HTC Sep 29 23:56:50 xenon kernel: [616401.706116] usb 3-2: SerialNumber: 66460e0b-5ccf-7103-e800-0050bf3f5173 Sep 29 23:56:50 xenon kernel: [616401.706286] PM: Adding info for usb:3-2 Sep 29 23:56:50 xenon kernel: [616401.706326] usb 3-2: uevent Sep 29 23:56:50 xenon kernel: [616401.706364] usb 3-2: usb_probe_device Sep 29 23:56:50 xenon kernel: [616401.706371] usb 3-2: configuration #1 chosen from 1 choice Sep 29 23:56:50 xenon kernel: [616401.709080] usb 3-2: adding 3-2:1.0 (config #1, interface 0) Sep 29 23:56:50 xenon kernel: [616401.709148] PM: Adding info for usb:3-2:1.0 Sep 29 23:56:50 xenon kernel: [616401.709161] usb 3-2:1.0: uevent Sep 29 23:56:50 xenon kernel: [616401.709238] PM: Adding info for No Bus:ep_81 Sep 29 23:56:50 xenon kernel: [616401.709246] usb 3-2: adding 3-2:1.1 (config #1, interface 1) Sep 29 23:56:50 xenon kernel: [616401.709288] PM: Adding info for usb:3-2:1.1 Sep 29 23:56:50 xenon kernel: [616401.709299] usb 3-2:1.1: uevent Sep 29 23:56:50 xenon kernel: [616401.709371] PM: Adding info for No Bus:ep_82 Sep 29 23:56:50 xenon kernel: [616401.709407] PM: Adding info for No Bus:ep_03 Sep 29 23:56:50 xenon kernel: [616401.709447] PM: Adding info for No Bus:ep_00 Sep 29 23:56:52 xenon kernel: [616403.705837] usbcore: registered new interface driver cdc_ether Sep 29 23:56:53 xenon kernel: [616403.806866] rndis_host 3-2:1.0: usb_probe_interface Sep 29 23:56:53 xenon kernel: [616403.806875] rndis_host 3-2:1.0: usb_probe_interface - got id Sep 29 23:56:53 xenon kernel: [616403.943139] rndis_host 3-2:1.0: RNDIS_MSG_QUERY(0x00010202) failed, -47 Sep 29 23:56:53 xenon kernel: [616403.949267] PM: Adding info for No Bus:eth1 Sep 29 23:56:53 xenon kernel: [616403.952273] eth1: register 'rndis_host' at usb-0000:00:1a.1-2, RNDIS device, 80:00:60:0f:e8:00 Sep 29 23:56:53 xenon kernel: [616403.952980] usbcore: registered new interface driver rndis_host Sep 29 23:56:53 xenon kernel: [616403.958017] udev: renamed network interface eth1 to eth2 Sep 29 23:56:53 xenon kernel: [616403.997153] hub 2-0:1.0: hub_suspend Sep 29 23:56:53 xenon kernel: [616403.997169] usb usb2: bus auto-suspend Sep 29 23:56:53 xenon kernel: [616403.997174] ehci_hcd 0000:00:1a.7: suspend root hub Sep 29 23:56:54 xenon ifup: eth2 Sep 29 23:56:54 xenon ifup: No configuration found for eth2 Sep 29 23:56:57 xenon hal-synce-rndis[18531] DEBUG : running as addon for interface eth2 Sep 29 23:56:57 xenon hal-synce-rndis[18531] DEBUG : attempting dynamic ip configuration Sep 29 23:56:58 xenon dhclient: Internet Systems Consortium DHCP Client V3.0.6 Sep 29 23:56:58 xenon dhclient: Copyright 2004-2007 Internet Systems Consortium. Sep 29 23:56:58 xenon dhclient: All rights reserved. Sep 29 23:56:58 xenon dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Sep 29 23:56:58 xenon dhclient: Sep 29 23:56:58 xenon dhclient: /usr/share/synce-hal/dhclient.conf line 8: no option named domain-search Sep 29 23:56:58 xenon dhclient: domain-name, domain-name-servers, domain-search, Sep 29 23:56:58 xenon dhclient: ^ Sep 29 23:56:58 xenon dhclient: /usr/share/synce-hal/dhclient.conf line 9: interface-mtu: expected option name. Sep 29 23:56:58 xenon dhclient: netbios-name-servers, netbios-scope, interface-mtu; Sep 29 23:56:58 xenon dhclient: ^ Sep 29 23:56:58 xenon kernel: [616409.339239] uhci_hcd 0000:00:1a.1: reserve dev 6 ep81-INT, period 2, phase 1, 17 us Sep 29 23:56:59 xenon dhclient: Listening on LPF/eth2/80:00:60:0f:e8:00 Sep 29 23:56:59 xenon dhclient: Sending on LPF/eth2/80:00:60:0f:e8:00 Sep 29 23:56:59 xenon dhclient: Can't bind to dhcp address: Address already in use Sep 29 23:56:59 xenon dhclient: Please make sure there is no other dhcp server Sep 29 23:56:59 xenon dhclient: running and that there's no entry for dhcp or Sep 29 23:56:59 xenon dhclient: bootp in /etc/inetd.conf. Also make sure you Sep 29 23:56:59 xenon dhclient: are not running HP JetAdmin software, which Sep 29 23:56:59 xenon dhclient: includes a bootp server. Sep 29 23:56:59 xenon dhclient: Sep 29 23:56:59 xenon dhclient: If you did not get this software from ftp.isc.org, please Sep 29 23:56:59 xenon dhclient: get the latest from ftp.isc.org and install that before Sep 29 23:56:59 xenon dhclient: requesting help. Sep 29 23:56:59 xenon dhclient: Sep 29 23:56:59 xenon dhclient: If you did get this software from ftp.isc.org and have not Sep 29 23:56:59 xenon dhclient: yet read the README, please read it before requesting help. Sep 29 23:56:59 xenon dhclient: If you intend to request help from the dhcp-server@... Sep 29 23:56:59 xenon dhclient: mailing list, please read the section on the README about Sep 29 23:56:59 xenon dhclient: submitting bug reports and requests for help. Sep 29 23:56:59 xenon dhclient: Sep 29 23:56:59 xenon dhclient: Please do not under any circumstances send requests for Sep 29 23:56:59 xenon dhclient: help directly to the authors of this software - please Sep 29 23:56:59 xenon dhclient: send them to the appropriate mailing list as described in Sep 29 23:56:59 xenon dhclient: the README file. Sep 29 23:56:59 xenon dhclient: Sep 29 23:56:59 xenon dhclient: exiting. Sep 29 23:56:59 xenon hal-synce-rndis[18531] ERROR : dhclient failed with return code 1 Sep 29 23:56:59 xenon hal-synce-rndis[18531] INFO : error running dhclient, trying static config Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : attempting static ip configuration Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : ifconfig succeeded Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : successfully configured interface Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : starting hal-dccm ... Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : calling hal-dccm as: Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : ['/usr/lib/synce-hal/hal-dccm', '--rndis', '--device-ip=169.254.2.1', '--local-ip=169.254.2.2', '--log-level=6'] Sep 29 23:56:59 xenon avahi-daemon[3924]: Joining mDNS multicast group on interface eth2.IPv4 with address 169.254.2.2. Sep 29 23:56:59 xenon avahi-daemon[3924]: New relevant interface eth2.IPv4 for mDNS. Sep 29 23:56:59 xenon avahi-daemon[3924]: Registering new address record for 169.254.2.2 on eth2.IPv4. Sep 29 23:56:59 xenon avahi-daemon[3924]: Withdrawing address record for 169.254.2.2 on eth2. Sep 29 23:56:59 xenon avahi-daemon[3924]: Leaving mDNS multicast group on interface eth2.IPv4 with address 169.254.2.2. Sep 29 23:56:59 xenon avahi-daemon[3924]: Interface eth2.IPv4 no longer relevant for mDNS. Sep 29 23:56:59 xenon avahi-daemon[3924]: Joining mDNS multicast group on interface eth2.IPv4 with address 169.254.2.2. Sep 29 23:56:59 xenon avahi-daemon[3924]: New relevant interface eth2.IPv4 for mDNS. Sep 29 23:56:59 xenon avahi-daemon[3924]: Registering new address record for 169.254.2.2 on eth2.IPv4. Sep 29 23:56:59 xenon avahi-daemon[3924]: Registering new address record for fe80::8200:60ff:fe0f:e800 on eth2.*. Sep 29 23:57:00 xenon hal-dccm[18531]: DEBUG: main: called with device-ip=169.254.2.1, local-ip=169.254.2.2 Sep 29 23:57:00 xenon hal-dccm[18531]: DEBUG: main: connected to hal, waiting for interface... Sep 29 23:57:00 xenon hal-dccm[18531]: DEBUG: check_interface_cb: found device interface Sep 29 23:57:00 xenon hal-dccm[18531]: DEBUG: check_interface_cb: listening for device Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: client_connected_cb: have a connection to port 990 Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: synce_device_init: running for udi /org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00 Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: synce_device_rndis_info_received Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: 81 11 c0 fe 82 50 01 33 81 1a e7 78 25 83 56 0b 05 00 00 00 01 00 00 00 0a 00 00 00 57 00 4d 00 5f 00 54 00 69 00 6c 00 6d 00 61 00 6e 00 32 00 00 00 05 01 56 01 11 0a 00 00 05 00 00 00 e4 4e 12 12 00 00 00 00 0f 00 00 00 50 6f 63 6b 65 74 50 43 00 53 53 44 4b 00 00 09 00 00 00 41 52 54 45 31 31 30 30 30 00 02 00 00 00 04 00 00 00 00 00 00 00 05 00 00 00 00 00 00 00 32 e6 07 00 Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: synce_device_change_password_flags: setting password flags provide Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: synce_device_rndis_info_received: notify hal that device is ready to be advertised Sep 29 23:57:08 xenon kernel: [616419.648018] eth2: no IPv6 routers present At the same time, the MDA device pops up a message (translated from German by yours truly): Windows CE Network The address assigned by the server cannot be retrieved. Try again later or enter an IP address in the network settings. (I didn't notice that message before I blacklisted ipaq, but I cannot say for sure whether it really wasn't there.) Meanwhile, there seems to be a TCP/IP connection to the MDA device. I can ping the APIPA address 169.254.2.1 which is reported in syslog as "device-ip" and also on the MDA itself under Settings - Connections - Configure Network Cards when selecting adapter "Remote RNDIS Host". If I run pls with maximum debugging level it reports: ts@xenon:~> pls -d 3 [synce_info_from_file:50] unable to open file: /home/ts/.synce/active_connection pls: Could not find configuration at path '(Default)' The directory /home/ts/.synce contains only an empty directory "scripts": ts@xenon:~> ls -lR /home/ts/.synce /home/ts/.synce: insgesamt 4 drwx------ 2 ts users 4096 20. Sep 14:16 scripts /home/ts/.synce/scripts: insgesamt 0 Any other ideas? Thanks, Tilman -- Tilman Schmidt E-Mail: tilman@... Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite) ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
|
Re: T-Mobile MDA compact III - no joy
by Mark Ellis
::
Rate this Message:
On Wed, 2009-09-30 at 00:32 +0200, Tilman Schmidt wrote:
> On Tue, 2009-09-29 07:18:53 +0100, Mark Ellis wrote: > > Blacklist ipaq and try again. > > Did that now, but it didn't change much. The pls command still reports: > > pls: Could not find configuration at path '(Default)' > Is that all you get ? If there is a connection problem, that is expected, but there should be messages about no devices on hal or odccm as well. Can you try pstatus instead of pls. > Syslog looks more or less like before, except for the absence of ipaq. > I have activated "loglevel: debug" in /etc/synce-hal.conf, and this is > what I see in syslog now, from when I connect the device: > > Sep 29 23:56:50 xenon kernel: [616401.074588] usb usb2: usb resume > Sep 29 23:56:50 xenon kernel: [616401.074597] ehci_hcd 0000:00:1a.7: resume root hub > Sep 29 23:56:50 xenon kernel: [616401.195262] ehci_hcd 0000:00:1a.7: port 4 full speed --> companion > Sep 29 23:56:50 xenon kernel: [616401.195273] ehci_hcd 0000:00:1a.7: GetStatus port 4 status 003801 POWER OWNER sig=j CONNECT > Sep 29 23:56:50 xenon kernel: [616401.206034] hub 2-0:1.0: hub_resume > Sep 29 23:56:50 xenon kernel: [616401.206087] ehci_hcd 0000:00:1a.7: GetStatus port 4 status 003002 POWER OWNER sig=se0 CSC > Sep 29 23:56:50 xenon kernel: [616401.307154] usb usb3: usb resume > Sep 29 23:56:50 xenon kernel: [616401.307162] usb usb3: wakeup_rh > Sep 29 23:56:50 xenon kernel: [616401.307177] hub 2-0:1.0: state 7 ports 4 chg 0000 evt 0000 > Sep 29 23:56:50 xenon kernel: [616401.339032] hub 3-0:1.0: hub_resume > Sep 29 23:56:50 xenon kernel: [616401.339066] uhci_hcd 0000:00:1a.1: port 2 portsc 0093,00 > Sep 29 23:56:50 xenon kernel: [616401.339075] hub 3-0:1.0: port 2: status 0101 change 0001 > Sep 29 23:56:50 xenon kernel: [616401.440160] hub 3-0:1.0: state 7 ports 2 chg 0004 evt 0000 > Sep 29 23:56:50 xenon kernel: [616401.440186] hub 3-0:1.0: port 2, status 0101, change 0000, 12 Mb/s > Sep 29 23:56:50 xenon kernel: [616401.542149] usb 3-2: new full speed USB device using uhci_hcd and address 6 > Sep 29 23:56:50 xenon kernel: [616401.685060] usb 3-2: skipped 3 descriptors after interface > Sep 29 23:56:50 xenon kernel: [616401.690060] usb 3-2: default language 0x0409 > Sep 29 23:56:50 xenon kernel: [616401.706090] usb 3-2: udev 6, busnum 3, minor = 261 > Sep 29 23:56:50 xenon kernel: [616401.706097] usb 3-2: New USB device found, idVendor=0bb4, idProduct=0bce > Sep 29 23:56:50 xenon kernel: [616401.706103] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > Sep 29 23:56:50 xenon kernel: [616401.706108] usb 3-2: Product: Generic RNDIS > Sep 29 23:56:50 xenon kernel: [616401.706112] usb 3-2: Manufacturer: HTC > Sep 29 23:56:50 xenon kernel: [616401.706116] usb 3-2: SerialNumber: 66460e0b-5ccf-7103-e800-0050bf3f5173 > Sep 29 23:56:50 xenon kernel: [616401.706286] PM: Adding info for usb:3-2 > Sep 29 23:56:50 xenon kernel: [616401.706326] usb 3-2: uevent > Sep 29 23:56:50 xenon kernel: [616401.706364] usb 3-2: usb_probe_device > Sep 29 23:56:50 xenon kernel: [616401.706371] usb 3-2: configuration #1 chosen from 1 choice > Sep 29 23:56:50 xenon kernel: [616401.709080] usb 3-2: adding 3-2:1.0 (config #1, interface 0) > Sep 29 23:56:50 xenon kernel: [616401.709148] PM: Adding info for usb:3-2:1.0 > Sep 29 23:56:50 xenon kernel: [616401.709161] usb 3-2:1.0: uevent > Sep 29 23:56:50 xenon kernel: [616401.709238] PM: Adding info for No Bus:ep_81 > Sep 29 23:56:50 xenon kernel: [616401.709246] usb 3-2: adding 3-2:1.1 (config #1, interface 1) > Sep 29 23:56:50 xenon kernel: [616401.709288] PM: Adding info for usb:3-2:1.1 > Sep 29 23:56:50 xenon kernel: [616401.709299] usb 3-2:1.1: uevent > Sep 29 23:56:50 xenon kernel: [616401.709371] PM: Adding info for No Bus:ep_82 > Sep 29 23:56:50 xenon kernel: [616401.709407] PM: Adding info for No Bus:ep_03 > Sep 29 23:56:50 xenon kernel: [616401.709447] PM: Adding info for No Bus:ep_00 > Sep 29 23:56:52 xenon kernel: [616403.705837] usbcore: registered new interface driver cdc_ether > Sep 29 23:56:53 xenon kernel: [616403.806866] rndis_host 3-2:1.0: usb_probe_interface > Sep 29 23:56:53 xenon kernel: [616403.806875] rndis_host 3-2:1.0: usb_probe_interface - got id > Sep 29 23:56:53 xenon kernel: [616403.943139] rndis_host 3-2:1.0: RNDIS_MSG_QUERY(0x00010202) failed, -47 > Sep 29 23:56:53 xenon kernel: [616403.949267] PM: Adding info for No Bus:eth1 > Sep 29 23:56:53 xenon kernel: [616403.952273] eth1: register 'rndis_host' at usb-0000:00:1a.1-2, RNDIS device, 80:00:60:0f:e8:00 > Sep 29 23:56:53 xenon kernel: [616403.952980] usbcore: registered new interface driver rndis_host > Sep 29 23:56:53 xenon kernel: [616403.958017] udev: renamed network interface eth1 to eth2 > Sep 29 23:56:53 xenon kernel: [616403.997153] hub 2-0:1.0: hub_suspend > Sep 29 23:56:53 xenon kernel: [616403.997169] usb usb2: bus auto-suspend > Sep 29 23:56:53 xenon kernel: [616403.997174] ehci_hcd 0000:00:1a.7: suspend root hub > Sep 29 23:56:54 xenon ifup: eth2 > Sep 29 23:56:54 xenon ifup: No configuration found for eth2 > Sep 29 23:56:57 xenon hal-synce-rndis[18531] DEBUG : running as addon for interface eth2 > Sep 29 23:56:57 xenon hal-synce-rndis[18531] DEBUG : attempting dynamic ip configuration > Sep 29 23:56:58 xenon dhclient: Internet Systems Consortium DHCP Client V3.0.6 > Sep 29 23:56:58 xenon dhclient: Copyright 2004-2007 Internet Systems Consortium. > Sep 29 23:56:58 xenon dhclient: All rights reserved. > Sep 29 23:56:58 xenon dhclient: For info, please visit http://www.isc.org/sw/dhcp/ > Sep 29 23:56:58 xenon dhclient: > Sep 29 23:56:58 xenon dhclient: /usr/share/synce-hal/dhclient.conf line 8: no option named domain-search > Sep 29 23:56:58 xenon dhclient: domain-name, domain-name-servers, domain-search, > Sep 29 23:56:58 xenon dhclient: ^ > Sep 29 23:56:58 xenon dhclient: /usr/share/synce-hal/dhclient.conf line 9: interface-mtu: expected option name. > Sep 29 23:56:58 xenon dhclient: netbios-name-servers, netbios-scope, interface-mtu; > Sep 29 23:56:58 xenon dhclient: ^ > Sep 29 23:56:58 xenon kernel: [616409.339239] uhci_hcd 0000:00:1a.1: reserve dev 6 ep81-INT, period 2, phase 1, 17 us > Sep 29 23:56:59 xenon dhclient: Listening on LPF/eth2/80:00:60:0f:e8:00 > Sep 29 23:56:59 xenon dhclient: Sending on LPF/eth2/80:00:60:0f:e8:00 > Sep 29 23:56:59 xenon dhclient: Can't bind to dhcp address: Address already in use > Sep 29 23:56:59 xenon dhclient: Please make sure there is no other dhcp server > Sep 29 23:56:59 xenon dhclient: running and that there's no entry for dhcp or > Sep 29 23:56:59 xenon dhclient: bootp in /etc/inetd.conf. Also make sure you > Sep 29 23:56:59 xenon dhclient: are not running HP JetAdmin software, which > Sep 29 23:56:59 xenon dhclient: includes a bootp server. > Sep 29 23:56:59 xenon dhclient: > Sep 29 23:56:59 xenon dhclient: If you did not get this software from ftp.isc.org, please > Sep 29 23:56:59 xenon dhclient: get the latest from ftp.isc.org and install that before > Sep 29 23:56:59 xenon dhclient: requesting help. > Sep 29 23:56:59 xenon dhclient: > Sep 29 23:56:59 xenon dhclient: If you did get this software from ftp.isc.org and have not > Sep 29 23:56:59 xenon dhclient: yet read the README, please read it before requesting help. > Sep 29 23:56:59 xenon dhclient: If you intend to request help from the dhcp-server@... > Sep 29 23:56:59 xenon dhclient: mailing list, please read the section on the README about > Sep 29 23:56:59 xenon dhclient: submitting bug reports and requests for help. > Sep 29 23:56:59 xenon dhclient: > Sep 29 23:56:59 xenon dhclient: Please do not under any circumstances send requests for > Sep 29 23:56:59 xenon dhclient: help directly to the authors of this software - please > Sep 29 23:56:59 xenon dhclient: send them to the appropriate mailing list as described in > Sep 29 23:56:59 xenon dhclient: the README file. > Sep 29 23:56:59 xenon dhclient: > Sep 29 23:56:59 xenon dhclient: exiting. > Sep 29 23:56:59 xenon hal-synce-rndis[18531] ERROR : dhclient failed with return code 1 > Sep 29 23:56:59 xenon hal-synce-rndis[18531] INFO : error running dhclient, trying static config > Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : attempting static ip configuration > Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : ifconfig succeeded > Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : successfully configured interface > Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : starting hal-dccm ... > Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : calling hal-dccm as: > Sep 29 23:56:59 xenon hal-synce-rndis[18531] DEBUG : ['/usr/lib/synce-hal/hal-dccm', '--rndis', '--device-ip=169.254.2.1', '--local-ip=169.254.2.2', '--log-level=6'] > Sep 29 23:56:59 xenon avahi-daemon[3924]: Joining mDNS multicast group on interface eth2.IPv4 with address 169.254.2.2. > Sep 29 23:56:59 xenon avahi-daemon[3924]: New relevant interface eth2.IPv4 for mDNS. > Sep 29 23:56:59 xenon avahi-daemon[3924]: Registering new address record for 169.254.2.2 on eth2.IPv4. > Sep 29 23:56:59 xenon avahi-daemon[3924]: Withdrawing address record for 169.254.2.2 on eth2. > Sep 29 23:56:59 xenon avahi-daemon[3924]: Leaving mDNS multicast group on interface eth2.IPv4 with address 169.254.2.2. > Sep 29 23:56:59 xenon avahi-daemon[3924]: Interface eth2.IPv4 no longer relevant for mDNS. > Sep 29 23:56:59 xenon avahi-daemon[3924]: Joining mDNS multicast group on interface eth2.IPv4 with address 169.254.2.2. > Sep 29 23:56:59 xenon avahi-daemon[3924]: New relevant interface eth2.IPv4 for mDNS. > Sep 29 23:56:59 xenon avahi-daemon[3924]: Registering new address record for 169.254.2.2 on eth2.IPv4. > Sep 29 23:56:59 xenon avahi-daemon[3924]: Registering new address record for fe80::8200:60ff:fe0f:e800 on eth2.*. > Sep 29 23:57:00 xenon hal-dccm[18531]: DEBUG: main: called with device-ip=169.254.2.1, local-ip=169.254.2.2 > Sep 29 23:57:00 xenon hal-dccm[18531]: DEBUG: main: connected to hal, waiting for interface... > Sep 29 23:57:00 xenon hal-dccm[18531]: DEBUG: check_interface_cb: found device interface > Sep 29 23:57:00 xenon hal-dccm[18531]: DEBUG: check_interface_cb: listening for device > Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: client_connected_cb: have a connection to port 990 > Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: synce_device_init: running for udi /org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00 > Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: synce_device_rndis_info_received > Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: 81 11 c0 fe 82 50 01 33 81 1a e7 78 25 83 56 0b 05 00 00 00 01 00 00 00 0a 00 00 00 57 00 4d 00 5f 00 54 00 69 00 6c 00 6d 00 61 00 6e 00 32 00 00 00 05 01 56 01 11 0a 00 00 05 00 00 00 e4 4e 12 12 00 00 00 00 0f 00 00 00 50 6f 63 6b 65 74 50 43 00 53 53 44 4b 00 00 09 00 00 00 41 52 54 45 31 31 30 30 30 00 02 00 00 00 04 00 00 00 00 00 00 00 05 00 00 00 00 00 00 00 32 e6 07 00 > Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: synce_device_change_password_flags: setting password flags provide > Sep 29 23:57:01 xenon hal-dccm[18531]: DEBUG: synce_device_rndis_info_received: notify hal that device is ready to be advertised > Sep 29 23:57:08 xenon kernel: [616419.648018] eth2: no IPv6 routers present > > At the same time, the MDA device pops up a message (translated from German > by yours truly): > > Windows CE Network > The address assigned by the server cannot be retrieved. > Try again later or enter an IP address in the network settings. > Never seen this before... > (I didn't notice that message before I blacklisted ipaq, but I cannot > say for sure whether it really wasn't there.) > > Meanwhile, there seems to be a TCP/IP connection to the MDA device. > I can ping the APIPA address 169.254.2.1 which is reported in syslog > as "device-ip" and also on the MDA itself under > Settings - Connections - Configure Network Cards > when selecting adapter "Remote RNDIS Host". > > If I run pls with maximum debugging level it reports: > > ts@xenon:~> pls -d 3 > [synce_info_from_file:50] unable to open file: /home/ts/.synce/active_connection > pls: Could not find configuration at path '(Default)' > > The directory /home/ts/.synce contains only an empty directory "scripts": That is the old way of getting connection information for client tools, it's actually a bit misleading now. > > ts@xenon:~> ls -lR /home/ts/.synce > /home/ts/.synce: > insgesamt 4 > drwx------ 2 ts users 4096 20. Sep 14:16 scripts > > /home/ts/.synce/scripts: > insgesamt 0 > > Any other ideas? > > Thanks, > Tilman > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
|
Re: T-Mobile MDA compact III - no joy
by Tilman Schmidt-2
::
Rate this Message:
On Sat, 2009-10-03 11:01:36 +0100, Mark Ellis wrote:
> On Wed, 2009-09-30 at 00:32 +0200, Tilman Schmidt wrote: >> On Tue, 2009-09-29 07:18:53 +0100, Mark Ellis wrote: >>> Blacklist ipaq and try again. >> Did that now, but it didn't change much. The pls command still reports: >> >> pls: Could not find configuration at path '(Default)' > > Is that all you get ? If there is a connection problem, that is > expected, but there should be messages about no devices on hal or odccm > as well. > Can you try pstatus instead of pls. Same difference: ts@xenon:~/kernel> pstatus pstatus: Could not find configuration at path '(Default)' ts@xenon:~/kernel> >> At the same time, the MDA device pops up a message (translated from German >> by yours truly): >> >> Windows CE Network >> The address assigned by the server cannot be retrieved. >> Try again later or enter an IP address in the network settings. >> > > Never seen this before... Doesn't always do it, by the way. And I noticed it once or twice when connecting to a Windows PC with ActiveSync, too, but synchronization works there, anyway. So perhaps it's harmless. >> If I run pls with maximum debugging level it reports: >> >> ts@xenon:~> pls -d 3 >> [synce_info_from_file:50] unable to open file: /home/ts/.synce/active_connection >> pls: Could not find configuration at path '(Default)' > > Looks almost like it's not trying a hal connection, try pstatus. ts@xenon:~/kernel> pstatus -d 3 [synce_info_from_file:50] unable to open file: /home/ts/.synce/active_connection pstatus: Could not find configuration at path '(Default)' ts@xenon:~/kernel> Nothing appearing in syslog, either. "strace pstatus" ends in: brk(0x806d000) = 0x806d000 getuid32() = 1000 socket(PF_FILE, SOCK_STREAM, 0) = 3 fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = 0 send(3, "\2\0\0\0\v\0\0\0\7\0\0\0passwd\0", 19, MSG_NOSIGNAL) = 19 poll([{fd=3, events=POLLIN|POLLERR|POLLHUP, revents=POLLIN|POLLHUP}], 1, 5000) = 1 recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"passwd\0", 7}], msg_controllen=16, {cmsg_len=16, cmsg_level=SOL_SOCKET, cmsg_type=SCM_RIGHTS, {4}}, msg_flags=0}, 0) = 7 fstat64(4, {st_mode=S_IFREG|0600, st_size=217016, ...}) = 0 pread64(4, "\1\0\0\0h\0\0\0,\0\0\0\1\0\0\0/\234\306J\0\0\0\0\323\0\0\0\0L\3\0"..., 104, 0) = 104 mmap2(NULL, 217016, PROT_READ, MAP_SHARED, 4, 0) = 0xb7c43000 close(4) = 0 close(3) = 0 stat64("/home/ts/.synce", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 stat64("/home/ts/.synce/active_connection", 0xbfa99dc4) = -1 ENOENT (No such file or directory) write(2, "pstatus: Could not find configur"..., 58pstatus: Could not find configuration at path '(Default)' ) = 58 futex(0xb7f95404, FUTEX_WAKE, 2147483647) = 0 exit_group(1) = ? Now I don't know anything about how a hal or odccm query would look like, but to my untrained eye there's nothing of the sort happening here. Isn't there a way to tell pls or pstatus explicitly: "Look on this IP address, 169.254.2.1"? Thanks, Tilman -- Tilman Schmidt E-Mail: tilman@... Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite) ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
|
Re: T-Mobile MDA compact III - no joy
by Tilman Schmidt-2
::
Rate this Message:
Ok, I'm one step further. Somehow the ymp file installation had
pulled in a bad libsynce version from the Packman repository: libsynce-0.10.0-0.pm.0 I manually replaced that by libsynce0-0.14-1.2 and now I get this much more promising result: ts@xenon:~> pls -d 3 [get_connection_from_hal:397] get_connection_from_hal: Failed to get a connection for /org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00: WM_Tilman2: Not authenticated, you need to call ProvidePassword with the correct password. [synce_socket_write:307] Invalid file descriptor [rapi_buffer_send:561] synce_socket_write failed [rapi2_context_call:638] rapi_buffer_send failed Unable to get the "My Documents" path. ts@xenon:~> Unfortunately the only instructions I found on the Wiki how to handle the "you need to call ProvidePassword" error are for Ubuntu, marked as "OLD INSTRUCTIONS", and seem to involve installing synce-trayicon which, as we already established, is not an option. Is there another way to provide the password? Thanks, Tilman -- Tilman Schmidt E-Mail: tilman@... Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite) ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
|
Re: T-Mobile MDA compact III - no joy
by Tilman Schmidt-2
::
Rate this Message:
|
|
|
Re: T-Mobile MDA compact III - no joy
by Mark Ellis
::
Rate this Message:
On Sat, 2009-10-03 at 16:13 +0200, Tilman Schmidt wrote:
> Ok, I'm one step further. Somehow the ymp file installation had > pulled in a bad libsynce version from the Packman repository: > libsynce-0.10.0-0.pm.0 > I manually replaced that by > libsynce0-0.14-1.2 That makes much more sense, that old libsynce has no support for synce-hal > and now I get this much more promising result: > > ts@xenon:~> pls -d 3 > [get_connection_from_hal:397] get_connection_from_hal: Failed to get a connection for /org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00: WM_Tilman2: Not authenticated, you need to call ProvidePassword with the correct password. > [synce_socket_write:307] Invalid file descriptor > [rapi_buffer_send:561] synce_socket_write failed > [rapi2_context_call:638] rapi_buffer_send failed > Unable to get the "My Documents" path. > ts@xenon:~> > > Unfortunately the only instructions I found on the Wiki how to handle > the "you need to call ProvidePassword" error are for Ubuntu, marked > as "OLD INSTRUCTIONS", and seem to involve installing synce-trayicon > which, as we already established, is not an option. > > Is there another way to provide the password? > But thankfully synce-hal 0.14 provides a small python script called synce-unlock.py, run it to get a hint on how to use it (assuming it's been installed by suse). Mark ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
|
Re: T-Mobile MDA compact III - no joy
by Tilman Schmidt-2
::
Rate this Message:
Am 05.10.2009 18:26 schrieb Mark Ellis:
> On Sat, 2009-10-03 at 16:13 +0200, Tilman Schmidt wrote: >> >> ts@xenon:~> pls -d 3 >> [get_connection_from_hal:397] get_connection_from_hal: Failed to get a connection for /org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00: WM_Tilman2: Not authenticated, you need to call ProvidePassword with the correct password. >> [synce_socket_write:307] Invalid file descriptor >> [rapi_buffer_send:561] synce_socket_write failed >> [rapi2_context_call:638] rapi_buffer_send failed >> Unable to get the "My Documents" path. >> ts@xenon:~> >> >> Unfortunately the only instructions I found on the Wiki how to handle >> the "you need to call ProvidePassword" error are for Ubuntu, marked >> as "OLD INSTRUCTIONS", and seem to involve installing synce-trayicon >> which, as we already established, is not an option. > > That would be the best way > >> Is there another way to provide the password? > > But thankfully synce-hal 0.14 provides a small python script called > synce-unlock.py, run it to get a hint on how to use it (assuming it's > been installed by suse). ts@xenon:~> synce-unlock.py -p Enter password: geheim <-- yes, it appeared in clear; I changed it, though Unlocking device connected at udi /org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00 with name WM_Tilman2 Authorization required for device WM_Tilman2. Traceback (most recent call last): File "/usr/bin/synce-unlock.py", line 137, in <module> rc = unlock_device(found_device, password) File "/usr/bin/synce-unlock.py", line 57, in unlock_device rc = deviceObject.ProvidePassword(password, dbus_interface='org.freedesktop.Hal.Device.Synce') NameError: global name 'deviceObject' is not defined ts@xenon:~> I don't speak Python myself, but I know a couple of other programming languages, and browsing through the source I thought it odd indeed that the name 'deviceObject' appeared nowhere else in the script but on this very line. Perhaps a simple typo? Thanks, Tilman -- Tilman Schmidt E-Mail: tilman@... Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite) ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
|
Re: T-Mobile MDA compact III - no joy
by Mark Ellis
::
Rate this Message:
On Tue, 2009-10-06 at 18:24 +0200, Tilman Schmidt wrote:
> Am 05.10.2009 18:26 schrieb Mark Ellis: > > On Sat, 2009-10-03 at 16:13 +0200, Tilman Schmidt wrote: > >> > >> ts@xenon:~> pls -d 3 > >> [get_connection_from_hal:397] get_connection_from_hal: Failed to get a connection for /org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00: WM_Tilman2: Not authenticated, you need to call ProvidePassword with the correct password. > >> [synce_socket_write:307] Invalid file descriptor > >> [rapi_buffer_send:561] synce_socket_write failed > >> [rapi2_context_call:638] rapi_buffer_send failed > >> Unable to get the "My Documents" path. > >> ts@xenon:~> > >> > >> Unfortunately the only instructions I found on the Wiki how to handle > >> the "you need to call ProvidePassword" error are for Ubuntu, marked > >> as "OLD INSTRUCTIONS", and seem to involve installing synce-trayicon > >> which, as we already established, is not an option. > > > > That would be the best way > > > >> Is there another way to provide the password? > > > > But thankfully synce-hal 0.14 provides a small python script called > > synce-unlock.py, run it to get a hint on how to use it (assuming it's > > been installed by suse). > > Indeed it is, but it has a problem: > > ts@xenon:~> synce-unlock.py -p > Enter password: geheim <-- yes, it appeared in clear; I changed it, though > Unlocking device connected at udi /org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00 with name WM_Tilman2 > Authorization required for device WM_Tilman2. > Traceback (most recent call last): > File "/usr/bin/synce-unlock.py", line 137, in <module> > rc = unlock_device(found_device, password) > File "/usr/bin/synce-unlock.py", line 57, in unlock_device > rc = deviceObject.ProvidePassword(password, dbus_interface='org.freedesktop.Hal.Device.Synce') > NameError: global name 'deviceObject' is not defined > ts@xenon:~> > on that line to "device". > I don't speak Python myself, but I know a couple of other programming > languages, and browsing through the source I thought it odd indeed > that the name 'deviceObject' appeared nowhere else in the script but > on this very line. Perhaps a simple typo? > > Thanks, > Tilman > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
|
Re: T-Mobile MDA compact III - no joy
by Mark Ellis
::
Rate this Message:
On Mon, 2009-10-05 at 10:51 +0200, Tilman Schmidt wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > JFTR, this: > > > > Windows CE Network > > The address assigned by the server cannot be retrieved. > > Try again later or enter an IP address in the network settings. > > > > turns out to be a well-known problem with Windows Mobile which > also happens with ActiveSync. (Indeed I have in the meantime > seen it once when synchronizing my MDA with a Windows PC, too.) > > The problem is triggered by entering the Settings dialog of the > "Remote NDIS Host" network interface. The defauts settings of > that adapter are: "fixed address", IP address field empty, > netmask 255.255.255.0, DNS server field empty. But those very > settings are rejected as invalid when you try to close the > dialog again, and it doesn't have an Abort button either, so > you are forced to change those settings in order to get rid of > the dialog again. If you choose "address assigned by DHCP" > (which I did) you get the message cited above, and the MDA will > use the address 169.254.2.1 which works just fine. Setting that > address as fixed address seems to be the recommended workaround > for people (like me) who do not want to do a factory reset just > to get their standard network settings back. > > HTH > > - -- > Tilman Schmidt E-Mail: tilman@... > Bonn, Germany > Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. > Ungeöffnet mindestens haltbar bis: (siehe Rückseite) > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.4 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFKybOGQ3+did9BuFsRAk/OAJ9QNydXG3UB7C7T3fy0jAeRUUmlNwCfWPWc > r03fTIy8vWRfMzIVC6DvqeY= > =duU6 > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > SynCE-Users mailing list > SynCE-Users@... > https://lists.sourceforge.net/lists/listinfo/synce-users ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
|
Re: T-Mobile MDA compact III - no joy
by Tilman Schmidt-2
::
Rate this Message:
On Thu, 2009-10-08 19:30:30 +0100, Mark Ellis wrote:
> On Tue, 2009-10-06 at 18:24 +0200, Tilman Schmidt wrote: >> ts@xenon:~> synce-unlock.py -p >> Enter password: geheim <-- yes, it appeared in clear; I changed it, though >> Unlocking device connected at udi /org/freedesktop/Hal/devices/net_80_00_60_0f_e8_00 with name WM_Tilman2 >> Authorization required for device WM_Tilman2. >> Traceback (most recent call last): >> File "/usr/bin/synce-unlock.py", line 137, in <module> >> rc = unlock_device(found_device, password) >> File "/usr/bin/synce-unlock.py", line 57, in unlock_device >> rc = deviceObject.ProvidePassword(password, dbus_interface='org.freedesktop.Hal.Device.Synce') >> NameError: global name 'deviceObject' is not defined >> ts@xenon:~> > > Ah, not very well tested that script. Try just changing "deviceObject" > on that line to "device". "Authorization succeeded", and after that, pls works, too. Thanks a lot for all your help! -- Tilman Schmidt E-Mail: tilman@... Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite) ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
|
Re: T-Mobile MDA compact III - joy!
by Tilman Schmidt-2
::
Rate this Message:
Am 29.09.2009 13:58 schrieb Tilman Schmidt:
> On Tue, 2009-09-29 10:38:27 +0100, Tejas Guruswamy wrote: > >> However it's not long till 10.3 becomes discontinued, so if you want the >> SynCE connection working *now* and don't have too much else holding you >> back you may want to look at upgrading to 11.1. > > I'm not quite prepared to reinstall my working machine right now. I was > planning to switch to 11.2 once it's out. Just wanted to let you know I did that now, and synce-trayicon works fine for me with openSUSE 11.2 x86_64. (After disabling SuSEfirewall, that is.) Thanks a lot, Tilman -- Tilman Schmidt E-Mail: tilman@... Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite) ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ SynCE-Users mailing list SynCE-Users@... https://lists.sourceforge.net/lists/listinfo/synce-users |
signature.asc (204 bytes) | Free embeddable forum powered by Nabble | Forum Help |
