Okay, I have a Qualcomm (Kyocera 7135) cell phone with a built in Palm Pilot. I am attempting to sync it with my RH9 Linux system and with Evolution. I know my system has a USB controller and that it works wtih RH9 even though my kernel is pre 2.4.21. I see it found during boot and the USB printer connected to it works fine (well, usually). I have previously posted parts of this question, since I still haven't got it working I am posting the whole thing again... The kernel version is 2.4.20-8smp, with the following software versions installed: gnome-pilot-conduits-2.0.10-0.ximian.6.1 pilot-link095-compat-0.9.5-22 gnome-pilot-devel-2.0.10-0.ximian.6.1 pilot-link-devel-0.11.5-4 jpilot-0.99.2-11 evolution-pilot-1.4.6-0.ximian.6.6 gnome-pilot-applet-2.0.10-0.ximian.6.1 pilot-link-0.11.5-4 gnome-pilot-2.0.10-0.ximian.6.1 Following the faq (http://pilot-link.org/README.usb) this is what happens: First modprobe produces strange results, to wit: # /sbin/modprobe usb-ohci /lib/modules/2.4.20-8smp/kernel/drivers/usb/usb-ohci.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.20-8smp/kernel/drivers/usb/usb-ohci.o: insmod /lib/modules/2.4.20-8smp/kernel/drivers/usb/usb-ohci.o failed /lib/modules/2.4.20-8smp/kernel/drivers/usb/usb-ohci.o: insmod usb-ohci failed # /sbin/modprobe usb-uhci # /sbin/modprobe usb modprobe: Can't locate module usb But running # lsmod produces: usb-uhci 27404 0 (unused) usbcore 82592 1 [usbserial printer hid usb-uhci] and then running # /sbin/modprobe usbserial produces: Jul 14 19:08:30 broadsword kernel: usb.c: registered new driver serial Jul 14 19:08:30 broadsword kernel: usbserial.c: USB Serial support registered for Generic Jul 14 19:08:30 broadsword kernel: usbserial.c: USB Serial Driver core v1.4 and # /sbin/modprobe visor produces the output: Jul 14 19:14:34 broadsword kernel: usbserial.c: USB Serial support registered for Handspring Visor / Palm 4.0 / Clié 4.x Jul 14 19:14:34 broadsword kernel: usbserial.c: USB Serial support registered for Sony Clié 3.5 Jul 14 19:14:34 broadsword kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.6 /sbin/lsmod now produces: Module Size Used by Not tainted visor 11436 0 (unused) usbserial 22268 0 [visor] usb-uhci 27404 0 (unused) usbcore 82592 1 [visor usbserial printer hid usb-uhci] next comes mknod, here is the mknod output: # /bin/mknod /dev/ttyUSB0 c 188 0 /bin/mknod: `/dev/ttyUSB0': File exists # /bin/mknod /dev/ttyUSB1 c 188 1 /bin/mknod: `/dev/ttyUSB1': File exists which was to be expected since the printer is on one of these... Finally, running HotSync produces: Jul 14 19:42:11 broadsword kernel: hub.c: new USB device 00:12.2-2, assigned address 4 Jul 14 19:42:11 broadsword kernel: usb.c: USB device 4 (vend/prod 0xc88/0x21) is not claimed by any active driver. Jul 14 19:42:15 broadsword /etc/hotplug/usb.agent: ... no modules for USB product c88/21/100 which according to the faq: "In this case, you will need to upgrade your 'visor' driver to a more current version. You can do this with a kernel upgrade, or by simply replacing the visor.c and visor.h files with more recent versions. " So assuming that I did, in fact, do everything right, (did I?) where do I find these "more recent versions" of visor.c and visor.h? Or is something else necessary that I missed? According to at least one posting I found through Google, this was supposed to be a plug and play operation <VBG>. -- L. Parker chief cook, bottle washer and sometime sysadmin cacaphony.net
Attachment:
signature.asc
Description: This is a digitally signed message part