http://qa.mandrakesoft.com/show_bug.cgi?id=3381
------- Additional Comments From [EMAIL PROTECTED] 2003-03-26 23:10 ------- this is what `grep isor' on /var/log/messages produces: Mar 26 11:32:58 localhost kernel: usbserial.c: USB Serial support registered for Handspring Visor Mar 26 11:32:58 localhost kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Cli� driver v1.5 Mar 26 11:32:47 localhost usb: Loading USB visor succeeded Mar 26 21:04:40 localhost kernel: usbserial.c: USB Serial support registered for Handspring Visor Mar 26 21:04:40 localhost kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Cli� driver v1.5 Mar 26 21:04:29 localhost usb: Loading USB visor succeeded Mar 26 21:41:57 localhost kernel: usbserial.c: USB Serial support registered for Handspring Visor / Palm 4.0 / Cli� 4.x Mar 26 21:41:57 localhost kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Cli� driver v1.6 Mar 26 21:45:12 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter detected Mar 26 21:45:12 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Cli� 4.x: Number of ports: 1 Mar 26 21:45:12 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Cli� 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 26 21:45:12 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs) Mar 26 21:45:12 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs) Mar 26 21:45:16 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 26 21:46:15 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter now disconnected from ttyUSB0 Mar 26 21:46:15 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter now disconnected from ttyUSB1 Mar 26 21:49:42 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter detected Mar 26 21:49:42 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Cli� 4.x: Number of ports: 1 Mar 26 21:49:42 localhost kernel: visor.c: Handspring Visor / Palm 4.0 / Cli� 4.x: port 1, is for HotSync use and is bound to ttyUSB0 Mar 26 21:49:42 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs) Mar 26 21:49:42 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs) Mar 26 21:49:46 localhost /etc/hotplug/usb.agent: Setup visor for USB product 830/50/100 Mar 26 21:49:58 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 26 21:50:09 localhost kernel: visor.c: Device lied about number of ports, please use a lower one. Mar 26 21:50:44 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter now disconnected from ttyUSB0 Mar 26 21:50:44 localhost kernel: usbserial.c: Handspring Visor / Palm 4.0 / Cli� 4.x converter now disconnected from ttyUSB1 /dev/pilot is created and points to /dev/usb/tts/1 Doing pilot-xfer -l -p /dev/pilot (or /dev/usb/tts/1) produces: No $PILOTPORT specified and no -p <port> given. Defaulting to '/dev/pilot' ERROR: No such device (19) Press the HotSync button first and relaunch this conduit.. Unable to bind to port: /dev/pilot Please use --help for more information Hope this helps, Owen On Wednesday 26 Mar 2003 1:41 pm, fcrozat wrote: ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Having read the pilot-link web pages, how-tos, man pages etc. I was expecting to `lsmod' and see usbcore, usb-uhci, usbserial and visor. All I see is usbcore and usb-uhci. Pressing the Hot Sync button on the Palm produces a KPilot icon on the KDe desktop. Pressing this launches KPilot which reports: 22:11:53 Trying to open device... 22:11:53 Could not open device: /dev/pilot (will retry) `lsmod' output is usbcore and usb-uhci /dev/pilot is a symbolic link to /dev/usb/tts/1 `modprobe'ing usbserial and visor make no difference at all `lsmod' produces the output: visor 10440 0 usbserial 21468 0 [visor] usb-uhci 24652 0 (unused) usbcore 72992 1 [usbdnet visor usbserial usb-uhci] The Pilot is connected via the cradle cable into the USB port. It makes no difference if "Cradle/Cable" or "Direct USB/Serial" options are chosen on the Pilot before doing the Hot Sync. Running `addresses' outputs: No $PILOTPORT specified and no -p <port> given. Defaulting to '/dev/pilot' ERROR: No such device (19) Press the HotSync button first and relaunch this conduit.. Unable to bind to port: /dev/pilot None of the pilot-link programs can contact it. How does KDE pick up the fact that there is a Palm attached when none of the USB modules know about it ?!?!
