Richard Crawford sent me this info quite a while back and it worked for me, maybe it will solve your issue as well... <snip> Try creating a file called /etc/udev/rules.d/10-visor.rules with this content: BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL="ttyUSB*", SYMLINK="pilot" Seemed to do the trick for me. If it doesn't work, you can also try adding a file called /etc/udev/permissions.d/10-visor.permissions with this content: ttyUSB1:$local:uucp:0660 </snip> On Friday 26 August 2005 07:56, Steven W. Orr wrote: > On Friday, Aug 26th 2005 at 09:53 +0200, quoth Omar: > > =>Hi all, > => I am tryint to sync my visor. Never had a chance to do so, it used to > work =>just fine with Mandrake 10.1. > =>This is the message I get from the log > => usb 4-2: new full speed USB device using uhci_hcd and address 12 > =>kernel: usb 4-2: Handspring Visor / Palm OS: port 1, is for Generic use > =>kernel: usb 4-2: Handspring Visor / Palm OS: port 2, is for HotSync use > =>kernel: usb 4-2: Handspring Visor / Palm OS: Number of ports: 2 > =>Kernel: visor 4-2:1.0: Handspring Visor / Palm OS converter detected > =>kernel: usb 4-2: Handspring Visor / Palm OS converter now attached to > ttyUSB0 =>kernel: usb 4-2: Handspring Visor / Palm OS converter now > attached to ttyUSB1 => > =>Now when I try using Kpilot, or Jpilot, and I tell it that the device is > =>at /dev/ttyUSB0, or /dev/ttyUSB1 nothing happens. I tried the gnome > pilot =>wizard as well. > =>Any and all help is appreciated, still new to FC3 but I love it.. > => Thanks is advance > > There is a sync problem with pilot-link and jpilot/kpilot. You must use > the older versions from core 3. The combination in core 4 is broken. > > -- > Time flies like the wind. Fruit flies like a banana. Stranger things have > .0. happened but none stranger than this. Does your driver's license say > Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We > are all- 000 individuals! What if this weren't a hypothetical question? > steveo at syslang.net