Re: F9: libusb palm syncing not working
On Wed, 2008-06-04 at 17:50 -0700, Brian Mury wrote:
BTW, I followed the instructions
in /usr/share/doc/pilot-link-0.12.3/README.fedora to set up the visor
module. I can synchronize this way by pointing gome-pilot
at /dev/ttyUSB0, but the /dev/pilot link does not get created.
[snip]
An extremely minor issue to be sure, but I'm curious why I don't
get /dev/pilot. Ideas?
What does lsusb show when the handheld is connected?
The description for USB devices changed upstream relatively recently
(which comes down from http://www.linux-usb.org/usb.ids via the hwdata
package) and may not trigger the
SYSFS{product}==Palm Handheld*|Handspring*
match in 60-pilot.rules any more. If so, you could try changing the
match string.
A more thorough method might be to replace 60-pilot.rules with a
modified 60-libpisock.rules (a copy should be
in /usr/share/pilot-link/udev/), which matches from a list of all the
Palm USB VID/PIDs. For Fedora you'll need to change the GROUP to uucp
and if you want a /dev/pilot symlink add a SYMLINK=pilot to each line.
e.g.
ATTRS{idVendor}==054c, ATTRS{idProduct}==0038, GROUP=uucp, MODE=0660,
SYMLINK=pilot
Let us know how you get on and we can change README.fedora if necessary.
Using the visor module and these udev rules has always been problematic,
which is why we're migrating to libusb. It doesn't seem like there's any
reason the m130 shouldn't work with libusb except that it hadn't been
tested. The pilot-link maintainer has generously offered to try and buy
an m130 to work it out, so you may want to follow developments on
pilot-link-general too.
cheers,
kev.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F9: libusb palm syncing not working
On Thu, 2008-06-05 at 10:29 +0100, Kevin Page wrote:
What does lsusb show when the handheld is connected?
Bus 003 Device 067: ID 0830:0050 Palm, Inc. m130
The full verbose output is at the end of this email if you want to see
it. I wonder if the weird iProduct value is to blame?
idVendor 0x0830 Palm, Inc.
idProduct 0x0050 m130
bcdDevice1.00
iManufacturer 1 Palm, Inc.
iProduct2 ^P^RC3$9CF79F
iSerial 5 PalmSN12345678
The description for USB devices changed upstream relatively recently
(which comes down from http://www.linux-usb.org/usb.ids via the hwdata
package) and may not trigger the
SYSFS{product}==Palm Handheld*|Handspring*
match in 60-pilot.rules any more. If so, you could try changing the
match string.
I tried changing it to match various strings output by libusb (Palm*,
*m130, etc) with no success.
A more thorough method might be to replace 60-pilot.rules with a
modified 60-libpisock.rules (a copy should be
That worked. I needed to add KERNEL==ttyUSB[02468] to get the symlink
to point to the right device (it creates two devices, for me they are
ttyUSB0 and ttyUSB1, the first one is the correct one).
an m130 to work it out, so you may want to follow developments on
pilot-link-general too.
Too many email lists already, and as long as I can sync (which I can) I
am happy, but I have added myself to the CC list of the bugzilla bug.
Thanks for the help Kevin!
= Verbose libusb output =
Bus 003 Device 066: ID 0830:0050 Palm, Inc. m130
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize016
idVendor 0x0830 Palm, Inc.
idProduct 0x0050 m130
bcdDevice1.00
iManufacturer 1 Palm, Inc.
iProduct2 ^P^RC3$9CF79F
iSerial 5 PalmSN12345678
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes2
Transfer TypeBulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes2
Transfer TypeBulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 0
Device Status: 0x0001
Self Powered
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F9: libusb palm syncing not working
On Mon, 2008-05-19 at 15:07 -0500, Paul Johnson wrote: On Mon, May 19, 2008 at 1:37 PM, Brian Mury [EMAIL PROTECTED] wrote: I am trying to get my Palm M130 working with F9 using libusb. When I start the hotsync, /var/log/messages shows this: [snip] However, pilot-xfer -p usb: -l just sits there saying Listening for incoming connection on usb:... forever. [snip] I help a guy who has a Palm Lifedrive and w had same experience with Fedora 8 and never did get it to work. There's a long long thread about it Another m130 user has experienced problems with F8; there is a thread discussing this on pilot-link-general: http://lists.pilot-link.org/pipermail/pilot-link-general/2008-May/003351.html http://lists.pilot-link.org/pipermail/pilot-link-general/2008-June/003374.html It seems very likely that this is an incompatibility between the pilot-link libusb code and m130 handhelds (and therefore a problem with libusb on all distributions), not a problem with the PolicyKit config in F9. This specific m130 issue is now in bugzilla at: https://bugzilla.redhat.com/show_bug.cgi?id=449968 In the meantime m130 users may want to try dropping back to using the visor module (see README.fedora, as others have mentioned). In the course of the discussion the lead pilot-link developer also implied that the LifeDrive is unsupported: http://lists.pilot-link.org/pipermail/pilot-link-general/2008-May/003364.html (as I understand it, Palm hasn't publicly documented the magic initialisation codes to stop the LifeDrive from going into drive mode when connected by USB). Have you tried network hotsync using pilot-link? cheers, kev. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F9: libusb palm syncing not working
On Wed, 2008-06-04 at 22:35 +0100, Kevin Page wrote: It seems very likely that this is an incompatibility between the pilot-link libusb code and m130 handhelds (and therefore a problem with libusb on all distributions), not a problem with the PolicyKit config in F9. Yeah, that's the conclusion I had come to, but it's nice to have some confirmation. BTW, I followed the instructions in /usr/share/doc/pilot-link-0.12.3/README.fedora to set up the visor module. I can synchronize this way by pointing gome-pilot at /dev/ttyUSB0, but the /dev/pilot link does not get created. Here's what I get in /var/log/messages when I press the cradle's hotsync button: Jun 4 17:42:48 localhost kernel: hub 1-0:1.0: unable to enumerate USB device on port 3 Jun 4 17:42:48 localhost kernel: usb 3-1: new full speed USB device using ohci_hcd and address 8 Jun 4 17:42:48 localhost kernel: usb 3-1: configuration #1 chosen from 1 choice Jun 4 17:42:48 localhost kernel: visor 3-1:1.0: Handspring Visor / Palm OS converter detected Jun 4 17:42:48 localhost kernel: usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB0 Jun 4 17:42:48 localhost kernel: usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB1 Jun 4 17:42:48 localhost kernel: usb 3-1: New USB device found, idVendor=0830, idProduct=0050 Jun 4 17:42:48 localhost kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Jun 4 17:42:48 localhost kernel: usb 3-1: Product: FFF79F Jun 4 17:42:48 localhost kernel: usb 3-1: Manufacturer: Palm, Inc. Jun 4 17:42:48 localhost kernel: usb 3-1: SerialNumber: PalmSN12345678 An extremely minor issue to be sure, but I'm curious why I don't get /dev/pilot. Ideas? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F9: libusb palm syncing not working
Am Montag, den 19.05.2008, 11:37 -0700 schrieb Brian Mury: I am trying to get my Palm M130 working with F9 using libusb. When I start the hotsync, /var/log/messages shows this: May 19 11:32:41 localhost kernel: hub 1-0:1.0: unable to enumerate USB device on port 3 may bi the culprit. See https://bugzilla.redhat.com/show_bug.cgi?id=446845 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
