Gentlemen, syncing my real Palm here on Debian "experimental" works real nice: $ pilot-xfer -p usb: ... However for the device mentioned in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=340547 I still must do # modprobe visor vendor=0x502 product=0x1 $ pilot-xfer -p /dev/ttyUSB1 ... So I asked myself "why can't I use -p usb:?" So I looked in /usr/share/doc/pilot-link/README.libusb.gz etc. etc. and then in /etc/udev/rules.d/z60_libpisock9.rules I copied the palm line ATTRS{idVendor}=="0830", ATTRS{idProduct}=="0002", GROUP="dialout", MODE="0664" to this line that I made looking at what dmesg told me ATTRS{idVendor}=="0502", ATTRS{idProduct}=="0001", GROUP="dialout", MODE="0664" and even rebooted the machine, however upon pushing the sync button on the acer, the /dev/usbdev2.*_ep0* files appear in /dev just like with the palm, but -p usb: just hangs. By the way, here's a patch --- /tmp/z60_libpisock9.rules 2008-01-03 16:15:23.000000000 +0800 +++ /etc/udev/rules.d/z60_libpisock9.rules 2009-08-09 04:28:37.000000000 +0800 @@ -22,6 +22,7 @@ # Palm, Inc. and palmOne handheld devices ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6601", GROUP="dialout", MODE="0664" ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="8001", GROUP="dialout", MODE="0664" +ATTRS{idVendor}=="0502", ATTRS{idProduct}=="0001", GROUP="dialout", MODE="0664" ATTRS{idVendor}=="0830", ATTRS{idProduct}=="0001", GROUP="dialout", MODE="0664" ATTRS{idVendor}=="0830", ATTRS{idProduct}=="0002", GROUP="dialout", MODE="0664" ATTRS{idVendor}=="0830", ATTRS{idProduct}=="0003", GROUP="dialout", MODE="0664" -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
