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: <FF><F7><9F> 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 [email protected] To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
