Re: cannot even log in with IIIc
- From: Rusty Carruth <rusty_carruth credence com>
- To: "gnome-pilot-list gnome org" <gnome-pilot-list gnome org>
- Subject: Re: cannot even log in with IIIc
- Date: Fri, 28 Sep 2007 16:32:08 -0700
On Mon, 2007-09-17 at 13:14 -0700, Rusty Carruth wrote:
Ok, so I've got a Palm IIIc (color) that worked some years ago, with
much older software.
I had upgraded some time back, and my sync quit working.
To which I've gotten two replies, one from Matt, and one from George.
I'll first handle Matt's reply below (and I will reply within his reply):
Hi Rusty,
Here's a checklist:
0. What version of pilot-link and gnome-pilot do you have?
pilot-link-0.12.0-pre2 (I've used 0.11.8 a long time ago, it seems)
pilot-xfer says that its 'pilot-xfer, from pilot-link version 0.12.1
Build target: i686-pc-linux-gnu
Build date: Sep 22 2006
And, I'm actually using kpilot, which says:
Version: KPilot 4.9.0 (depth9)
Version: pilot-link 0.12.1
Version: KDE 3.5.5
Version: Qt 3.3.7
1. Can you sync using Windows with your IIIc and the same cables?
Yes, just tried it, it worked fine (for windows' value of fine ;-) using
serial, but did not
work using USB, even if I tell Palm's HotSync Manager 4.1.0 to only look
on USB - so
it sounds like my cable won't do USB even if IIIc will, so I'll drop the
USB attempt until
after I get serial working again. (I would have been extremely
surprised if serial on
DB9 had failed, as I'd used this same cable 2 years ago when it worked,
but wires
DO break... :-)
We need to rule out problems with your cables first.
2. Try getting 'pilot-xfer -p /dev/whatever -l' working first.
This is the basic test of linux connectivity. Without this,
jpilot/kpilot/gnome-pilot are not going to work. Make sure
you kill any gpilotd/gpilot-applet processes before trying
pilot-xfer.
3. First try with your DB9 cable. Run pilot-xfer -p /dev/ttyS0 -l,
if you're sure you're connected to ttyS0. What do you get?
You can try turning on pilot-link debugging by setting the
environment variables:
env PILOT_DEBUG="DEV SLP CMP PADP NET SOCK" \
PILOT_DEBUG_LEVEL="DEBUG" pilot-xfer -p /dev/ttyS0 -l
Lots of stuff comes out in that case. The whole thing is available, but
let me skip most of the
first bunch of stuff:
DEV SPEED unixserial switch to 9600 bps
DEV POLL unixserial found data on fd: 3
SOCK fd=3 auto=1
SOCK proto=DLP (6)
DEV RX unixserial read 8 bytes
DEV RX unixserial read 8 bytes from read-ahead buffer
(LOTS of these, numbers are 2,1,9,1,1,9,1,1,9 (repeats this 1,1,9
sequence for a
long time))
DEV RX unixserial read 1 bytes
using PADP/SLP protocol (skipped 120 bytes)
CMP RX len=10 flags=0x00
PADP RX expect=10 flags=0x0000
SLP RX len=1028 flags=0x0000
DEV RX unixserial read 3 bytes from read-ahead buffer
DEV RX unixserial read 7 bytes from read-ahead buffer
DEV RX unixserial read 6 bytes
DEV RX unixserial read 8 bytes
DEV RX unixserial read 2 bytes
SLP RX 3->3 type=2 txid=0xff len=0x000e checksum=0xaf
0000 01 c0 00 0a 01 00 01 02 00 00 00 01 c2 00 ..............
PADP RX FL type=DATA len=10
0000 01 00 01 02 00 00 00 01 c2 00 ..........
PADP TX FL type=ACK len=10
DEV TX unixserial wrote 16 bytes
SLP TX 3->3 type=2 txid=0xff len=0x0004 checksum=0xa5
0000 02 c0 00 0a ....
CMP RX WAKE Type: 0x01 Flags: 0x00 Version: 0x1020000 Baud: 115200
CMP TX INIT Type: 0x02 Flags: 0x80 Version: 0x1020000 Baud: 115200
PADP TX FL type=DATA len=10
0000 02 80 01 02 00 00 00 01 c2 00 ..........
DEV TX unixserial wrote 26 bytes
SLP TX 3->3 type=2 txid=0xff len=0x000e checksum=0xaf
0000 01 c0 00 0a 02 80 01 02 00 00 00 01 c2 00 ..............
SLP RX len=1030 flags=0x0000
SLP RX Read Error
PADP TX FL type=DATA len=10
0000 02 80 01 02 00 00 00 01 c2 00 ..........
DEV TX unixserial wrote 26 bytes
SLP TX 3->3 type=2 txid=0xff len=0x000e checksum=0xaf
0000 01 c0 00 0a 02 80 01 02 00 00 00 01 c2 00 ..............
SLP RX len=1030 flags=0x0000
SLP RX Read Error
PADP TX FL type=DATA len=10
0000 02 80 01 02 00 00 00 01 c2 00 ..........
DEV TX unixserial wrote 26 bytes
SLP TX 3->3 type=2 txid=0xff len=0x000e checksum=0xaf
0000 01 c0 00 0a 02 80 01 02 00 00 00 01 c2 00 ..............
SLP RX len=1030 flags=0x0000
SLP RX Read Error
PADP TX FL type=DATA len=10
0000 02 80 01 02 00 00 00 01 c2 00 ..........
DEV TX unixserial wrote 26 bytes
SLP TX 3->3 type=2 txid=0xff len=0x000e checksum=0xaf
0000 01 c0 00 0a 02 80 01 02 00 00 00 01 c2 00 ..............
SLP RX len=1030 flags=0x0000
SLP RX Read Error
PADP TX FL type=DATA len=10
0000 02 80 01 02 00 00 00 01 c2 00 ..........
DEV TX unixserial wrote 26 bytes
SLP TX 3->3 type=2 txid=0xff len=0x000e checksum=0xaf
0000 01 c0 00 0a 02 80 01 02 00 00 00 01 c2 00 ..............
SLP RX len=1030 flags=0x0000
SLP RX Read Error
PADP TX FL type=DATA len=10
0000 02 80 01 02 00 00 00 01 c2 00 ..........
DEV TX unixserial wrote 26 bytes
SLP TX 3->3 type=2 txid=0xff len=0x000e checksum=0xaf
0000 01 c0 00 0a 02 80 01 02 00 00 00 01 c2 00 ..............
SLP RX len=1030 flags=0x0000
SLP RX Read Error
PADP TX FL type=DATA len=10
0000 02 80 01 02 00 00 00 01 c2 00 ..........
DEV TX unixserial wrote 26 bytes
SLP TX 3->3 type=2 txid=0xff len=0x000e checksum=0xaf
0000 01 c0 00 0a 02 80 01 02 00 00 00 01 c2 00 ..............
SLP RX len=1030 flags=0x0000
SLP RX Read Error
PADP TX FL type=DATA len=10
0000 02 80 01 02 00 00 00 01 c2 00 ..........
DEV TX unixserial wrote 26 bytes
SLP TX 3->3 type=2 txid=0xff len=0x000e checksum=0xaf
0000 01 c0 00 0a 02 80 01 02 00 00 00 01 c2 00 ..............
SLP RX len=1030 flags=0x0000
SLP RX Read Error
PADP TX FL type=DATA len=10
0000 02 80 01 02 00 00 00 01 c2 00 ..........
DEV TX unixserial wrote 26 bytes
SLP TX 3->3 type=2 txid=0xff len=0x000e checksum=0xaf
0000 01 c0 00 0a 02 80 01 02 00 00 00 01 c2 00 ..............
SLP RX len=1030 flags=0x0000
SLP RX Read Error
PADP TX FL type=DATA len=10
0000 02 80 01 02 00 00 00 01 c2 00 ..........
DEV TX unixserial wrote 26 bytes
SLP TX 3->3 type=2 txid=0xff len=0x000e checksum=0xaf
0000 01 c0 00 0a 02 80 01 02 00 00 00 01 c2 00 ..............
SLP RX len=1030 flags=0x0000
SLP RX Read Error
PADP TX too many retriesDEV CLOSE unixserial fd: 3
Error accepting data on /dev/ttyS0
Interesting to me that it sets 115200, but I told the Palm to go 9600, since
I saw it try 9600. I tried setting the palm for 115200, still does not
work.
Perhaps the serial port is hosed? I plan to try hooking the computer up to
some kind of terminal or something, once I can find one!
4. As regards USB, connect USB and attempt a sync. If you don't
see any palm-related messages with a 'dmesg' command, you
are in trouble. I can't see why you wouldn't unless you have
a faulty USB cable or hub. Maybe a dead hub port?
It was directly connected - but it failed when directly connected to
windows, so I"m
going to drop this task till later.
That should get you started, anyway.
Thanks!
Now, George said:
The "overcurrent" message indicates your USB port can't
handle the charge current demands of the Palm (or possibly a
short in the cable). You should fix that before attempting to use
USB. You have to tell the Palm to sync using USB, and once
Umm - where is this 'tell the palm to sync to USB' place on the
palm? I have not seen that anywhere in the hotsync stuff on my
palm IIIc.
you have hit "sync" on the Palm, it should appear in the output
of lsusb.
I'm even thinking of getting a new cable, given that it doesn't
work with windows either. In any case, I'm dropping the usb
investigation until I can either get a known-working usb to
palm arrangement or I have more time on my hands than I
expect :-)
... end of George's reply.....
Thanks all! I'll be investigating the serial port on my computer
(even though I *did* try another linux computer and had similar
failures) and/or getting a known working USB setup.
I'll report back once I've gotten somewhere.
rc
This transmission is intended for the sole use of the individual and entity to whom it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. You are hereby notified that any use, dissemination, distribution or duplication of this transmission by someone other than the intended addressee or its designated agent is strictly prohibited. If you have received this transmission in error, please notify this company immediately by reply to this transmission and delete it from your computer. Thank You. Credence Systems Corporation.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
