Re: Handspring Visor (Palm OS) USB sync with gpilotd or?
Hi,
I've got a similar problem. Mine is that the device seems not to be
claimed by any driver.
I am using a Treo 270 and I have synchronized it before with SuSE.
Dec 25 22:51:40 hamlet kernel: hub.c: USB new device connect on bus1/1,
assigned device number 4
Dec 25 22:51:40 hamlet kernel: Manufacturer: Handspring Inc
Dec 25 22:51:40 hamlet kernel: Product: Handspring Treo
Dec 25 22:51:40 hamlet kernel: usb.c: USB device 4 (vend/prod
0x82d/0x100) is not claimed by any active driver.
Dec 25 22:51:40 hamlet kernel: Length = 18
Dec 25 22:51:40 hamlet kernel: DescriptorType = 01
Dec 25 22:51:40 hamlet kernel: USB version = 1.00
Dec 25 22:51:40 hamlet kernel: Vendor:Product = 082d:0100
Dec 25 22:51:40 hamlet kernel: MaxPacketSize0 = 16
Dec 25 22:51:40 hamlet kernel: NumConfigurations = 1
Dec 25 22:51:40 hamlet kernel: Device version = 1.00
Dec 25 22:51:40 hamlet kernel: Device Class:SubClass:Protocol =
00:00:00
Dec 25 22:51:40 hamlet kernel: Per-interface classes
Dec 25 22:51:40 hamlet kernel: Configuration:
Dec 25 22:51:40 hamlet kernel: bLength = 9
Dec 25 22:51:40 hamlet kernel: bDescriptorType = 02
Dec 25 22:51:40 hamlet kernel: wTotalLength = 002e
Dec 25 22:51:40 hamlet kernel: bNumInterfaces = 01
Dec 25 22:51:40 hamlet kernel: bConfigurationValue = 01
Dec 25 22:51:40 hamlet kernel: iConfiguration = 00
Dec 25 22:51:40 hamlet kernel: bmAttributes = c0
Dec 25 22:51:40 hamlet kernel: MaxPower = 2mA
Dec 25 22:51:40 hamlet kernel:
Dec 25 22:51:40 hamlet kernel: Interface: 0
Dec 25 22:51:40 hamlet kernel: Alternate Setting: 0
Dec 25 22:51:40 hamlet kernel: bLength = 9
Dec 25 22:51:40 hamlet kernel: bDescriptorType = 04
Dec 25 22:51:40 hamlet kernel: bInterfaceNumber = 00
Dec 25 22:51:40 hamlet kernel: bAlternateSetting = 00
Dec 25 22:51:40 hamlet kernel: bNumEndpoints = 04
Dec 25 22:51:40 hamlet kernel: bInterface Class:SubClass:Protocol
= ff:00:00
Dec 25 22:51:40 hamlet kernel: iInterface = 00
Dec 25 22:51:40 hamlet kernel: Endpoint:
Dec 25 22:51:40 hamlet kernel: bLength = 7
Dec 25 22:51:40 hamlet kernel: bDescriptorType = 05
Dec 25 22:51:40 hamlet kernel: bEndpointAddress = 81 (in)
Dec 25 22:51:40 hamlet kernel: bmAttributes = 02 (Bulk)
Dec 25 22:51:40 hamlet kernel: wMaxPacketSize = 0010
Dec 25 22:51:40 hamlet kernel: bInterval = 0a
Dec 25 22:51:40 hamlet kernel: Endpoint:
Dec 25 22:51:40 hamlet kernel: bLength = 7
Dec 25 22:51:40 hamlet kernel: bDescriptorType = 05
Dec 25 22:51:40 hamlet kernel: bEndpointAddress = 01 (out)
Dec 25 22:51:40 hamlet kernel: bmAttributes = 02 (Bulk)
Dec 25 22:51:40 hamlet kernel: wMaxPacketSize = 0010
Dec 25 22:51:40 hamlet kernel: bInterval = 00
Dec 25 22:51:40 hamlet kernel: Endpoint:
Dec 25 22:51:40 hamlet kernel: bLength = 7
Dec 25 22:51:40 hamlet kernel: bDescriptorType = 05
Dec 25 22:51:40 hamlet kernel: bEndpointAddress = 82 (in)
Dec 25 22:51:40 hamlet kernel: bmAttributes = 02 (Bulk)
Dec 25 22:51:40 hamlet kernel: wMaxPacketSize = 0040
Dec 25 22:51:40 hamlet kernel: bInterval = 00
Dec 25 22:51:40 hamlet kernel: Endpoint:
Dec 25 22:51:40 hamlet kernel: bLength = 7
Dec 25 22:51:40 hamlet kernel: bDescriptorType = 05
Dec 25 22:51:40 hamlet kernel: bEndpointAddress = 02 (out)
Dec 25 22:51:40 hamlet kernel: bmAttributes = 02 (Bulk)
Dec 25 22:51:40 hamlet kernel: wMaxPacketSize = 0040
Dec 25 22:51:40 hamlet kernel: bInterval = 00
Dec 25 22:51:45 hamlet kernel: usb.c: USB disconnect on device 4
Mariano
On Wed, 2002-12-25 at 21:56, Bret Comstock Waldow wrote:
> No, I've covered that (but thanks for the report). I'm syncing on
> ttyUSB1. I've been doing this for months in Redhat 7.3, and it's been
> working fine (the info from Ximian's support section is quite good).
>
> It only isn't working in my Woody install, and the error message I'm
> getting in /var/log/messages points to the hotplug scripts. It's not
> working in JPilot either,on Woody, although that also works in Redhat
> 7.3.
>
> Here is the line from /var/log/messages:
> Dec 20 10:49:50 ganesha /etc/hotplug/usb.agent: missing kernel or user
> mode driver visor
>
> Despite what the line above says, lsmod says the module is loaded in
> Woody. I've even recompiled the module, and nothing changes - it still
> doesn't work.
>
> I'd still like to hear from anyone who is using the hotplug system -
> with gpilotd in Redhat it's like it works in Windows - put the Visor in
> the cradle and press the hotsync button.
>
> I've been using Evolution as my client, but that's not part of the
> problem - Evolution doesn't need to be running to do a hotplug hotsync -
> just the hotplug system and gpilotd.
>
> Still hoping for information...
> Bret
>
>
> On Wed, 2002-12-25 at 14:43, Robert L. Harris wrote:
> >
> >
> >
> > I'm using jpilot under debian with great success. Part of the problem
> > was the device is /dev/ttyUSB1 (not 0).
> >
> > Thus spake Bret Comstock Waldow (bwaldow@compuserve.com):
> >
> > > Hi,
> > >
> > > Is ANYONE successfully hotsyncing a Visor or other Palm OS device via
> > > the USB hotplug system? I've been using gpilotd with Redhat 7.3, and
> > > I'm trying to switch to Debian.
> > >
> > > /var/log/messages shows the visor is recognized, but times out without
> > > transferring anything, and there is a message from the hotplug scripts
> > > that say there is no kernel or user module for it (even though lsmod
> > > shows it's loaded). It seems there's something wrong with the hotplug
> > > system, but it would be great to hear if anyone else has it working.
> > >
> > > JPilot doesn't work either, for the same reasons.
> > >
> > > Thanks,
> > > Bret
> > >
> > >
> > >
> > >
> > >
> > > --
> > > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> > > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> >
> >
> >
> > :wq!
> > ---------------------------------------------------------------------------
> > Robert L. Harris | PGP Key ID: FC96D405
> >
> > DISCLAIMER:
> > These are MY OPINIONS ALONE. I speak for no-one else.
> > FYI:
> > perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
> >
>
--
Mariano Kamp <mariano.kamp@web.de>
JLOGIC
Reply to: