Re: gpilotd not working stable with my Clie SJ30



Hi List,
> 
> You must press the hotsync button first because unfortunately palm
> devices do not exist until that time.  Make sure you have a decent
> kernel as well (2.4.19 or 2.4.20) for palm devices.
> 
> -JP

As stated in another message, it sometimes works, sometimes not. Here is
again what I do:

1) Connect Clie to cable to USB

2) start a konsole and tail -f /var/log/messages

3) start another console and type "gpilotd" and wait

4) press Hotsync on the Clie and wait until /var/log/messages shows
this:

-- snip --
Dec 29 21:15:20 romanic kernel: hub.c: port 1, portstatus 303, change 0,
1.5 Mb/s
Dec 29 21:15:20 romanic kernel: hub.c: port 2, portstatus 101, change 1,
12 Mb/s
Dec 29 21:15:20 romanic kernel: hub.c: port 2 connection change
Dec 29 21:15:20 romanic kernel: hub.c: port 2, portstatus 101, change 1,
12 Mb/s
Dec 29 21:15:21 romanic kernel: hub.c: port 2, portstatus 101, change 0,
12 Mb/s
Dec 29 21:15:21 romanic last message repeated 3 times
Dec 29 21:15:21 romanic kernel: hub.c: port 2, portstatus 103, change 0,
12 Mb/s
Dec 29 21:15:21 romanic kernel: hub.c: new USB device 00:07.2-2,
assigned address 9
Dec 29 21:15:21 romanic kernel: usb.c: kmalloc IF da2117c0, numif 1
Dec 29 21:15:21 romanic kernel: usb.c: new device strings: Mfr=1,
Product=2, SerialNumber=0
Dec 29 21:15:21 romanic kernel: usb.c: USB device number 9 default
language ID 0x409
Dec 29 21:15:21 romanic kernel: Manufacturer: Palm, Inc.
Dec 29 21:15:21 romanic kernel: Product: Palm Handheld
Dec 29 21:15:21 romanic kernel: usbserial.c: Handspring Visor / Palm 4.0
/ Clié 4.x converter detected
Dec 29 21:15:21 romanic kernel: visor.c: Handspring Visor / Palm 4.0 /
Clié 4.x: Number of ports: 2
Dec 29 21:15:21 romanic kernel: visor.c: Handspring Visor / Palm 4.0 /
Clié 4.x: port 1, is for Generic use and is bound to ttyUSB0
Dec 29 21:15:21 romanic kernel: visor.c: Handspring Visor / Palm 4.0 /
Clié 4.x: port 2, is for HotSync use and is bound to ttyUSB1
Dec 29 21:15:21 romanic kernel: usb-uhci.c: interrupt, status 2, frame#
2025
Dec 29 21:15:24 romanic kernel: usb_control/bulk_msg: timeout
Dec 29 21:15:24 romanic kernel: visor.c: visor_startup - error getting
first unknown palm command
Dec 29 21:15:27 romanic kernel: usb_control/bulk_msg: timeout
Dec 29 21:15:27 romanic kernel: visor.c: visor_startup - error getting
second unknown palm command
Dec 29 21:15:27 romanic kernel: usbserial.c: Handspring Visor / Palm 4.0
/ Clié 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
Dec 29 21:15:27 romanic kernel: usbserial.c: Handspring Visor / Palm 4.0
/ Clié 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
Dec 29 21:15:27 romanic kernel: usb.c: serial driver claimed interface
da2117c0
Dec 29 21:15:27 romanic kernel: usb.c: kusbd: /sbin/hotplug add 9
Dec 29 21:15:27 romanic kernel: hub.c: port 1, portstatus 303, change 0,
1.5 Mb/s
Dec 29 21:15:27 romanic kernel: hub.c: port 2, portstatus 103, change 0,
12 Mb/s
-- snap --

After that last line my Notebook gives a BEEP 

5) on the other konsole with gpilotd waiting press Enter immediately
after the BEEP. That worked exactly ONE time out of my TEN++ trials in
the last minutes. The Hotsync took about 4 Minutes (!!!), giving lots of
status lines on the konsole.

6) The other tries ended up with this:
--- snip ---
(imagine a BEEP here)
fungata romanic:~> gpilotd
gpilotd-Message: gnome-pilot 0.1.71 starting...
gpilotd-Message: compiled for pilot-link version ..
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpilotd-Message: Watching ClieUSB (/dev/pilot)
gpilotd-Message: setting PILOTRATE=57600

gpilotd-WARNING **: pi_accept_to: Connection timed out

gpilotd-WARNING **: pi_accept_to: timeout was 2 secs

--- snap ---

Now as I write this I wonder why it says 
  "compiled for pilot-link version .." (DotDot)
This is what I also got from the ./configure I did before compiling
gpilotd again just before. (this time as fungata, only "make install" as
root, of course, and after completely removing the build Dir and
unpacking the tarball again) There it says after the configure has run
trough:

--- snip ---
...
...
...
sed: can't read ./intl/po2tbl.sed.in: No such file or directory
checking for glib-config... /usr/bin/glib-config
checking for GLIB - version >= 1.2.0... yes
checking for pi-version.h... yes
checking for pi_accept in -lpisock... yes
cat: /usr/include/pi-version.h: No such file or directory
cat: /usr/include/pi-version.h: No such file or directory
cat: /usr/include/pi-version.h: No such file or directory
cat: /usr/include/pi-version.h: No such file or directory
>>>> checking for pilot-link version >= 0.11.4... yes (found ..) <<<<
...
...
...
  Configuration :

          gnome-vfs    : yes
          network sync : yes
          usb          : yes
          gob          : yes
          pilot-link   : ..
--- snap ---

The line I marked >>> <<< looks strange. Does v. 0.11.7 as I got
compiled and running give ".." as version number?????

Another thing that is strange is in the syslog above. There it says

Dec 29 21:15:21 romanic kernel: Manufacturer: Palm, Inc.
Dec 29 21:15:21 romanic kernel: Product: Palm Handheld

Palm??? I got a SONY. Is my visor-module to old (though it IS kernel
2.4.20-ac2, compiled yesterday and running fine) or has Sony only bought
some m505 and pressed it into another case? I wouldn't believe that!

BTW. I was only able to get the brand new Clie to beeing recognized by
the gnome-control-center-pilot-setup AFTER a complete Hotsync under
Windows. Before that Gnome didn't talk to the Clie, i.e. it was unable
to retrieve or write the User ID from/to the Clie. Strange?!?

So any more Ideas why my baby doesn't want what I want? 

Regards Lars


-- 
Lars Weissflog <L RS-W DE>





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]