From: "RKTMB . M . A" <rktmb@wanadoo.fr>

> On Thursday 24 July 2003 14:06, Adriaan de Groot wrote:
>
> First , to be conform with the way to submit problems:
> [ x86 ]
> [ Linux kernel 2.4.20 / Slackware9 ]
> [ Palm Zire ]
> [ Qt 3.1.2 ]
> [ KDE 3.1 ]
> [ pilot-link_0.11.8 ]
> [ kpilot_4.3.8 ]
>
>
> > uvisor perhaps?
> i dont have that kind of modules available ....
> ( Linux 2.4.20 )

That should be 'visor'.
>
> Jul 24 15:17:52 darkstar kernel: hub.c: new USB device 00:10.1-2, assigned
> addre                                       ss 16
> Jul 24 15:17:52 darkstar kernel: Manufacturer: Palm, Inc.
> Jul 24 15:17:52 darkstar kernel: Product: Palm Handheld
> Jul 24 15:17:52 darkstar kernel: SerialNumber: PalmSN12345678
>
>
> 2°)
> pilot-xfer -p /dev/tts/0 -L
>
> > Have you configured KPilot to use /dev/tts/0 ?
>
> yes , sir . i have .

Why?  Just kidding, but everything I've seen puts the usb palms on /dev/ttyUSB1
(which is how mine works).  otoh, you obviously get better recognition from
hotplug than I do - mine works just fine, but it is reported as just a series of
numbers rather than a "Palm".

I can't help thinking that if you have hub.c recognizing your link, then your
best bet is you're trying to connect to the wrong device.


_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/