Description of problem: After upgrading from version 7 to 9, the module visor can't be loaded anymore. There's no more ttyUSB devices so I can't symlink to /dev/pilot for Handheld use. How reproducible: Always Steps to Reproduce: 1. I plug my Palm TX to usb port # dmesg hub 1-0:1.0: unable to enumerate USB device on port 1 usb 2-1: new full speed USB device using uhci_hcd and address 7 usb 2-1: configuration #1 chosen from 1 choice usb 2-1: New USB device found, idVendor=0830, idProduct=0061 usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5 usb 2-1: Product: Palm Handheld usb 2-1: Manufacturer: Palm, Inc. usb 2-1: SerialNumber: PN70M677V3N8 2. I get nothing with ls /dev/ttyU* and ls /dev/pilot 3. Looked for /etc/udev/rules.d/10-visor.rules BUS=="usb", SYSFS{product}=="Palm Handheld*", KERNEL=="ttyUSB[13579]", SYMLINK+="pilot",MODE="0666" 4. Looked for an entry on /etc/modprobe.d/blacklist file (there's no entry for visor) I assume that's ok 5. Tried to load visor module # modprobe visor FATAL: Error inserting visor (/lib/modules/2.6.25.4-30.fc9.i686/kernel/drivers/usb/serial/visor.ko): Invalid argument 6. # dmesg visor: `0830' invalid for parameter `vendor' Actual results: Can't use pilot-link utils or Jpilot app. The same usb port can be used for pendrives and bluetooth device (I rule out hardware problem) Additional info: # uname -a Linux dragonauta 2.6.25.4-30.fc9.i686 #1 SMP Wed May 21 18:12:35 EDT 2008 i686 athlon i386 GNU/Linux # cat /etc/redhat-release Fedora release 9 (Sulphur) Thanks!
Sorry... I find the solution. pilot-xfer -p usb: -l works fine, and for jpilot I use "usb:" as device instead /dev/pilot or /dev/ttyUSBn I know, I know... STFW!