On Tue, 2005-10-04 at 17:20 -0400, David Hollis wrote:
> On Tue, 2005-10-04 at 14:15 -0700, Craig White wrote:
> > just got a new treo 650
> >
> > trying to hot-sync but can't get out of box as it doesn't
> > initialize /dev/ttyUSX
> >
> > I plug it in and press the hotsync and dmesg & /var/log/messages notice
> > it's presence...
> >
> > Oct 4 13:45:52 lin-workstation kernel: usb 3-3: new full speed USB
> > device using ohci_hcd and address 5
> > Oct 4 13:47:19 lin-workstation kernel: usb 3-3: USB disconnect, address
> > 5
> > Oct 4 13:50:56 lin-workstation kernel: ohci_hcd 0000:00:02.1: wakeup
> > Oct 4 13:50:56 lin-workstation kernel: usb 3-3: new full speed USB
> > device using ohci_hcd and address 6
> > Oct 4 13:53:06 lin-workstation kernel: usb 3-3: USB disconnect, address
> > 6
> > Oct 4 13:53:10 lin-workstation kernel: ohci_hcd 0000:00:02.1: wakeup
> > Oct 4 13:53:10 lin-workstation kernel: usb 3-3: new full speed USB
> > device using ohci_hcd and address 7
> > Oct 4 13:55:21 lin-workstation kernel: usb 3-3: USB disconnect, address
> > 7
>
>
> Looks like visor isn't picking it up. While the device is trying to
> hotsync, run a /sbin/lsusb to see what the PID/VID is for it. It may
> need to be added to visor. You should be able to load visor by hand
> adding 'product=0x???? vendor=0x????' substituting the appropriate
> values from lsusb and it may pick it up.
----
applied Windows solution (reboot) and that somewhat helped. Now it
definitely shows up as /dev/ttyUSB0 & /dev/ttyUSB1 (hooray - I knew
without that, it would be hopeless).
# cat /etc/udev/rules.d/10-udev.rules
BUS="scsi", SYSFS{model}="iPod ", KERNEL="sdp2", NAME="%k",
SYMLINK="ipod"
BUS="usb", SYSFS{product}="Palm*", KERNEL="ttyUSB*", SYMLINK="pilot"
# cat /etc/udev/permissions.d/10-udev.permissions
pilot*:craig:usb:0666
ttyUSB1:$local:uucp:0660
clearly should work...but still struggling here...
# pilot-xfer -p /dev/pilot -L
Listening to port: /dev/pilot
Please press the HotSync button now...
Error accepting data on /dev/pilot
;-(
getting closer though - thanks Kevin/Dave
Craig
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
