Package: synce-serial
Version: 0.9.1-3
Severity: grave
Justification: renders package unusable


ppp can't get a connection to my ipaq when starting it with synce-serial-start 
when using kernel 2.6.18.
I also tried a newer kernel 2.6.19.1
With kernel 2.6.17 it can get a connection.

Using tail -f /var/log/meesages I see something like (with kernel 2.6.17 is 
different with an established connection):
Jan 13 18:53:02 ulli3 kernel: usb 2-2.4: configuration #1 chosen from 1 choice
Jan 13 18:53:02 ulli3 kernel: PPP generic driver version 2.4.2
Jan 13 18:53:02 ulli3 kernel: usbcore: registered new interface driver usbserial
Jan 13 18:53:02 ulli3 kernel: drivers/usb/serial/usb-serial.c: USB Serial 
Driver core
Jan 13 18:53:02 ulli3 kernel: drivers/usb/serial/usb-serial.c: USB Serial 
support registered for PocketPC PDA
Jan 13 18:53:02 ulli3 kernel: drivers/usb/serial/ipaq.c: USB PocketPC PDA 
driver v0.5
Jan 13 18:53:02 ulli3 kernel: ipaq 2-2.4:1.0: PocketPC PDA converter detected
Jan 13 18:53:02 ulli3 kernel: usb 2-2.4: PocketPC PDA converter now attached to 
ttyUSB0
Jan 13 18:53:02 ulli3 kernel: usbcore: registered new interface driver ipaq
Jan 13 18:53:02 ulli3 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 13 18:53:03 ulli3 synce-serial-start: Executing '/usr/sbin/pppd call 
synce-device'
Jan 13 18:53:03 ulli3 last message repeated 3 times
Jan 13 18:53:03 ulli3 pppd[8456]: pppd 2.4.4 started by root, uid 0
Jan 13 18:53:03 ulli3 pppd[8457]: pppd 2.4.4 started by root, uid 0
Jan 13 18:53:03 ulli3 pppd[8457]: Device ttyipaq is locked by pid 8456
Jan 13 18:53:03 ulli3 pppd[8457]: Exit.
Jan 13 18:53:03 ulli3 pppd[8460]: pppd 2.4.4 started by root, uid 0
Jan 13 18:53:03 ulli3 pppd[8460]: Device ttyipaq is locked by pid 8456
Jan 13 18:53:03 ulli3 pppd[8460]: Exit.
Jan 13 18:53:03 ulli3 pppd[8492]: pppd 2.4.4 started by root, uid 0
Jan 13 18:53:03 ulli3 pppd[8492]: Device ttyipaq is locked by pid 8456
Jan 13 18:53:03 ulli3 pppd[8492]: Exit.
Jan 13 18:53:03 ulli3 synce-serial-start: Executing '/usr/sbin/pppd call 
synce-device'
Jan 13 18:53:03 ulli3 pppd[8500]: pppd 2.4.4 started by root, uid 0
Jan 13 18:53:03 ulli3 pppd[8500]: Device ttyipaq is locked by pid 8456
Jan 13 18:53:03 ulli3 pppd[8500]: Exit.
Jan 13 18:53:03 ulli3 synce-serial-start: Executing '/usr/sbin/pppd call 
synce-device'
Jan 13 18:53:03 ulli3 pppd[8502]: pppd 2.4.4 started by root, uid 0
Jan 13 18:53:03 ulli3 pppd[8502]: Device ttyipaq is locked by pid 8456
Jan 13 18:53:03 ulli3 pppd[8502]: Exit.
Jan 13 18:53:03 ulli3 synce-serial-start: Executing '/usr/sbin/pppd call 
synce-device'
Jan 13 18:53:03 ulli3 pppd[8522]: pppd 2.4.4 started by root, uid 0
Jan 13 18:53:03 ulli3 pppd[8522]: Device ttyipaq is locked by pid 8456
Jan 13 18:53:03 ulli3 pppd[8522]: Exit.
Jan 13 18:53:04 ulli3 pppd[8456]: Exit.

I don't know, why it starts synce-serial-start very offen, possibly because of 
my udev configuration:
BUS=="usb" SYSFS{idProduct}=="00ce" SYSFS{idVendor}=="0bb4" name="ttyipaq" 
group="dialout" RUN+="/usr/bin/synce-serial-start"

ppp-synce configuration /etc/ppp/peers/synce-device:
# Modifications to this file will be lost next time you run synce-serial-config
/dev/ttyipaq 115200
connect '/usr/bin/synce-serial-chat'
nodefaultroute
noauth
local
192.168.131.102:192.168.131.201
ms-dns 192.168.131.102
crtscts
linkname synce-device




-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.1.ullismall
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages synce-serial depends on:
ii  debconf [debconf-2.0]        1.5.11      Debian configuration management sy
ii  libc6                        2.3.6.ds1-8 GNU C Library: Shared libraries
ii  ppp                          2.4.4rel-4  Point-to-Point Protocol (PPP) daem

synce-serial recommends no packages.

-- debconf information:
  synce-serial/dnsip:
  synce-serial/remoteip: 192.168.131.201
  synce-serial/tty: /dev/ttyUSB0
  synce-serial/localip: 192.168.131.102


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to