Re: Treo 755p and General Tips

Hi Jay,

On Mon, 2008-09-01 at 11:51 -0400, Jay Bloodworth wrote:
> The immediate issue: I'm trying to get my Treo 755p to talk to
> gnome-pilot.  This is under Fedora 8.  I go through the configuration
> wizard, but the sync times out before a connection is made.  Relevant
> dmesg follows:
> 
> hub 2-0:1.0: unable to enumerate USB device on port 4
> usb 7-2: new full speed USB device using uhci_hcd and address 12
> usb 7-2: configuration #1 chosen from 1 choice
> usb 7-2: New USB device found, idVendor=0830, idProduct=0061
> usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
> usb 7-2: Product: Palm Handheld
> usb 7-2: Manufacturer: Palm, Inc.
> usb 7-2: SerialNumber: PalmSN12345678
> 
> This repeats a number of times, perhaps once per attempt to hotsync,
> certainly more than once per time I've plugged in the USB cable.
> 
> There is no /dev/pilot.  Isn't udev supposed to create this?
> 
> The larger issue: I can't find any documentation about how the various
> technologies and configuration files relating to gnome-pilot interact.
> Based on searching, it seems my problem could be related to udev,
> libusb, devices.xml, hal, or goodness knows what else.  It's very
> difficult to know where to start troubleshooting.

The most useful support documentation for gnome-pilot currently is
probably the archives of this mailing list, followed (hopefully) by the
Gnome Live wiki page: http://live.gnome.org/GnomePilot
The runtime help (launchable from the configuration applet or the panel
applet) also contains reasonable information.  The README
under /usr/share/doc/gnome-pilot is pretty out of date.

For your current problem, my guesses are either:
  1.  You haven't specified "usb:" as your device file name.  If there
      is no /dev/pilot then that probably means your system is set up
      to disable the 'visor' usbserial driver and should be using libusb
      directly.  Instead of specifying '/dev/pilot' use 'usb:'.
  2.  It is possible you are affected by bug #484509:
      http://bugzilla.gnome.org/show_bug.cgi?id=484509
      This is a bug caused by changes in HAL since your version of
      gnome-pilot was released.  There is a workaround, discussed on
      this list, of suspending the 'hald' process when starting (or
      restarting) gpilotd.  Better, of course, is to apply a patch
      and rebuild gnome-pilot from source, or get your fedora package
      maintainer to do so.

Hope this helps,

Matt

Matt Davey        What do you call books that aren't cooked?
[email protected] 	Rare.