Re: gpilot pilot-link messed up after hardware/software upgrade?

2006-05-26 Thread Matt Zagrabelny
On Wed, 2006-05-24 at 16:11 -0400, Matt Price wrote:
 [some of this is in the earlier message]
 
 hi ubuntu,

d-u is not ubuntu.

[stuff deleted]

 I of course know nothing about what this might mean.  In any case I'd
 love some advice on howto diagnose these issues further!  the
 evolution/palm combination has been crucial for me.  thanks,

could you try your palm on a windoze box?

other things that come to mind about the serial port:

* baud rate
* stop bits
* parity
* data length
* hardware flow control

you could use minicom or gtkterm to adjust these settings.

-- 
Matt Zagrabelny - [EMAIL PROTECTED] - (218) 726 8844
University of Minnesota Duluth
Information Technology Systems  Services
PGP key 1024D/84E22DA2 2005-11-07
Fingerprint: 78F9 18B3 EF58 56F5 FC85  C5CA 53E7 887F 84E2 2DA2

He is not a fool who gives up what he cannot keep to gain what he cannot
lose.
-Jim Elliot


signature.asc
Description: This is a digitally signed message part


gpilot pilot-link messed up after hardware/software upgrade?

2006-05-25 Thread Matt Price
[some of this is in the earlier message]

hi ubuntu,

I was until recently running debian sid on a middle-aged amd k7
system; after the motherboard fried, I upgraded to a very fast new
system (amd X2 3800+, A8N-SLI motherboard and installed ubuntu Dapper
and debian etch on a new disk.  The old system is still around on an
old disk, but hard to work with b/c I haven't reconfigured x etc.

On my old system, my PDA worked fine -- it's a Palm V, which I connect
through the serial cradle that came with it a million years ago.  I
also have a usb-to-serial connector for it, which in the past has also
worked *pretty* well via the kl5105kb kernel module.  Now, though, the
PDA doesn't work at all.  At first it seemed to be a problem with
evolution and gnome-pilot, and I *was* briefly able to access the
palm's info through pilot-link (pilot-xfer -p /dev/ttyUSB0 -l, IIRC).
Now even that won't work, and unscrewing the serial-to-usb adaptor 
plugging in directly to the serial port has no effect either.

Howver, if the palm is plugged in to usb through the serial-to-usb
cable, it *will* sync with jpilot  sometimes even with kpilot.  So
the problem is at least partly to do wo ith gnome-pilot and/or
pilot-link.  

I'm also a little concerned that the cradle itself is messed up somehow,
partly because of some strange stuff in dmesg.  

serial:

serial port seems to be recognized just fine by the kernel, early on
in the boot process:

[   85.877857] Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ 
sharing enabled
[   85.877964] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   85.879621] 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   85.880057] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 
blocksize

however, there's no traffic on /dev/ttyS0 (cat /dev/ttyS0, and then
pressing hotsync button, gives no output) while ttyS1 seems
fundamentally messed up:
$ cat /dev/ttyS1
cat: /dev/ttyS1: Input/output error

USB:  

If I connect my usb/serial converter, then I have similar problems.
Dmesg shows it being recognized, and at FIRST binds to /dev/ttyUSB0
and /dev/ttyUSB1, but if I unplug  replug, I only get /dev/ttyUSB0.  
[   99.174740] usbcore: registered new driver usbserial_generic
[   99.174742] drivers/usb/serial/usb-serial.c: USB Serial Driver core
[   99.176113] drivers/usb/serial/usb-serial.c: USB Serial support registered 
for Handspring Visor / Palm OS
[   99.176123] drivers/usb/serial/usb-serial.c: USB Serial support registered 
for Sony Clie 3.5
[   99.176132] drivers/usb/serial/usb-serial.c: USB Serial support registered 
for Sony Clie 5.0
[   99.176147] usbcore: registered new driver visor
[   99.176149] drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver
[ 5048.095365] usb 1-1: new full speed USB device using ohci_hcd and address 2
[ 5048.249360] usb 1-1: Handspring Visor / Palm OS converter now attached to 
ttyUSB0
[ 5048.249403] usb 1-1: Handspring Visor / Palm OS converter now attached to 
ttyUSB1
[ 5048.315832] drivers/usb/serial/usb-serial.c: USB Serial support registered 
for KL5KUSB105D / PalmConnect
[ 5048.316216] usbcore: registered new driver kl5kusb105d
[ 5048.316222] drivers/usb/serial/kl5kusb105.c: KLSI KL5KUSB105 chipset 
USB-Serial Converter driver v0.3a
[ 5048.352721] visor ttyUSB1: Device lied about number of ports, please use a 
lower one.
[ 5058.370432] usb 1-1: USB disconnect, address 2
[ 5058.370587] visor ttyUSB0: Handspring Visor / Palm OS converter now 
disconnected from ttyUSB0
[ 5058.370658] visor ttyUSB1: Handspring Visor / Palm OS converter now 
disconnected from ttyUSB1
[ 5071.074606] usb 1-1: new full speed USB device using ohci_hcd and address 3
[ 5071.225553] visor 1-1:1.0: KL5KUSB105D / PalmConnect converter detected
[ 5071.225632] usb 1-1: KL5KUSB105D / PalmConnect converter now attached to 
ttyUSB0
[ 5071.275482] drivers/usb/serial/kl5kusb105.c: klsi_105_chg_port_settings - 5 
byte block, baudrate 6, databits 8, u1 0, u2 1
[ 5071.278465] drivers/usb/serial/kl5kusb105.c: klsi_105_get_line_state - 
sending SIO Poll request
[ 5071.281463] drivers/usb/serial/kl5kusb105.c: klsi_105_get_line_state - read 
status 40 0
[ 5071.285485] drivers/usb/serial/kl5kusb105.c: kl5kusb105 port stats: 0 bytes 
in, 0 bytes out
[ 5076.487583] drivers/usb/serial/kl5kusb105.c: klsi_105_chg_port_settings - 5 
byte block, baudrate 6, databits 8, u1 0, u2 1
[ 5076.490573] drivers/usb/serial/kl5kusb105.c: klsi_105_get_line_state - 
sending SIO Poll request
[ 5076.493571] drivers/usb/serial/kl5kusb105.c: klsi_105_get_line_state - read 
status 40 0
[ 5083.217062] drivers/usb/serial/kl5kusb105.c: kl5kusb105 port stats: 0 bytes 
in, 0 bytes out
[ 5105.076854] usb 1-1: USB disconnect, address 3

-
moreover, if I'm running an SMP, preemptible kernel, I get this message on 
disconnecting the usb cable:
[ 1273.420238] usb 2-7: USB disconnect, address 2
[ 1273.420362] --- [cut here ] - [please bite here ] -
[