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
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
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
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
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
