Palm under Linux ============= - see http://code.pilot-link.org/README.libusb - use libusb instead of visor kernel module Now things get interesting. Below are the necessary programs and versions you'll need. These are the MINIMUM versions you can use. Anything earlier than these versions WILL NOT work. - pilot-link....: 0.12.0 - libusb........: 0.1 - libusb-dev....: 0.1 headers - udev..........: 0.70 - Linux kernel..: 2.4.21 or 2.6.10 You'll also need the libpisock9.rules file included in the latest pilot-link release. A copy of the current file can be found at the following URL: - setting up the rules file for udev see: http://code.pilot-link.org/libpisock9.rules Put the libpisock9.rules file in: /etc/udev/rules.d/libpisock9.rules and restart udev. - mount the kernel's usbfs --------------------------------------------------- Make sure you have usbfs mounted, which can be found in fstab, by adding the following line: # none /proc/bus/usb usbfs defaults Then 'mount -a' to make sure its mounted. You should now have a /proc/bus/usb directory heirarchy. The "new" udev and libusb will be using /dev/bus/usb, but many applications still use /proc/bus/usb, so we'll mount it until that gets deprecated. blacklist the kernel visor driver --------------------------------- In order to use libusb, you'll want to make sure the kernel 'visor' driver does NOT load when it sees a Palm device connecting to the USB root hub on your system. udev method (for newer udev versions, no hotplug) ------------------------------------------------- If your udev is new enough and you no longer use hotplug, you'll need to blacklist the visor driver so it does not load when it sees Palm devices connecting to the USB bus. You can blacklist the visor module by adding 'blacklist visor' to /etc/modprobe.d/blacklist-palm. If that file doesn't exist, create it. older method (for systems still using hotplug) ------------------------------------------------- You can blacklist list by adding 'visor' to the /etc/hotplug/blacklist file to stop hotplug from loading it at connect time. Restart hotplug to re-read the blacklist file. pilot-link --------------------------------------------------- You'll need to compile pilot-link by passing the --enable-libusb option at configure time. When you configure it with libusb support, you should see the following output in the summary page: Direct USB support...... : yes, libusb If you do not see that, you are missing some critical build dependency. Check config.log, search for libusb and see what went wrong. Remember, you'll need the libusb *HEADERS* to build the support into pilot-link for it, not the runtime. This will be a libusb-dev or libusb-devel package on most distributions. - basic prg: palm-link-package