[jp] Re: JPilot, T3 and Fedora 2

David A. Desrosiers hacker at gnu-designs.com
Tue Jun 15 07:55:35 EDT 2004


> - /dev/usb/ttyUSB1 indeed is readable and writeable.

	Are you running devfs? Try making a real inode, and pointing it
there. This is covered in my README:

	http://pilot-link.org/README.usb

> So it seems like it can't find it now.

	Is hotplug getting in the way here? Is your 'visor' module loaded at
boot time? Or does it automatically get loaded when you press HotSync on the
T3/cradle?

> lsusb gives me:
> Bus 004 Device 001: ID 0000:0000
> Bus 003 Device 001: ID 0000:0000
> Bus 002 Device 001: ID 0000:0000
> Bus 001 Device 001: ID 0000:0000
>
> Which looks suspicious to me.

	That's because you haven't connected any devices yet. If you hit
HotSync on your T3, then ru lsusb in another window, you should see
different results.

	USB Palm devices aren't connected to the hardware until you make the
electrical connection. That connection is made by pressing the HotSync
button on the cradle, or tapping the HotSync icon on the Palm screen. This
is how USB works.

> Agreed, that would be handy.

	Are you volunteering? ;)

d.




More information about the Jpilot mailing list