On Tuesday 18 February 2003 08:12 pm, Jack Coates wrote: > how about pilot-xfer -l? If that works, you know pilot-link is > doing its job... however, this is all terribly buggy territory and > has been for years and probably isn't going to get unbuggy any time > soon. pilot-link usually works pretty well, note that it's up to > version 0.11.7 now. Programs that work closely with it like jpilot > work. gnome-pilot and kpilot are generally not likely to work > reliably.
Well, I set up pilot-xfer and ran pilot-xfer --port /dev/ttyUSB1 --backup /home/robbo/visor/ and it should have listened to /dev/ttyUSB1 where the message logs indicate that the Visor is connected to. But it never saw /dev/ttyUSB1 (I am running devfs...but old style addresses are still symlinked). J-Pilot did not see it either. I am currently running pilot-link-0.11.3-2mdk, I attempted to upgrade to 0.11.7 from source, but was unable to compile it, as I would have had to rebuild too much of my machine. The logs from the recent test are basically like before. usbserial gives /dev/ttyUSB0 and 1 to the visor for use, and pilot-xfer, KPilot, JPilot and the like miss the connection. Is something else necessary to be running? Any ideas? > On Tue, 2003-02-18 at 18:57, Rob Blomquist wrote: > > I am suffering with KPilot on Mandrake 9.0, running the rpms from > > Mandrake of KDE 3.1.0. > > > > KPilot appears to be trying to access /dev/ttyUSB0 (as I have > > told it to), but it cant find it. the Kernel log is showing that > > the visor is bound to /dev/ttyUSB0 and ttyUSB1, but the 2 are not > > communicating. And quite frankly it doesn't matter if I tell it > > ttyUSB1 either. There is still no connect. > > > > Can anyone tell me why this isn't working? > > > > The full logs appear below: > > Version: KPilot 4.3.6 (3_1_BRANCH) > > Version: pilot-link 0.11.3 > > Version: KDE 3.1.0 > > Version: Qt 3.1.1 > > > > HotSync Log > > > > 21:52:24 Pilot device /dev/ttyUSB0 doesn't exist. Assuming the > > device uses DevFS. > > 21:52:25 Trying to open device... > > 21:52:25 Could not open device: /dev/ttyUSB0 (will retry) > > 21:53:45 HotSyncing. Please press the HotSync button. > > > > /var/log/messages: > > > > Feb 17 21:51:44 timmy2 kernel: hub.c: USB new device connect on > > bus2/3, assigned device number 6 > > Feb 17 21:51:44 timmy2 kernel: usbserial.c: Handspring Visor > > converter detected > > Feb 17 21:51:44 timmy2 kernel: visor.c: Handspring Visor: Number > > of ports: 2 > > Feb 17 21:51:44 timmy2 kernel: visor.c: Handspring Visor: port 1, > > is for Generic use and is bound to ttyUSB0 > > Feb 17 21:51:44 timmy2 kernel: visor.c: Handspring Visor: port 2, > > is for HotSync use and is bound to ttyUSB1 > > Feb 17 21:51:44 timmy2 kernel: usbserial.c: Handspring Visor > > converter now attached to ttyUSB0 (or usb/tts/0 for devfs) > > Feb 17 21:51:44 timmy2 kernel: usbserial.c: Handspring Visor > > converter now attached to ttyUSB1 (or usb/tts/1 for devfs) > > Feb 17 21:51:45 timmy2 kernel: Device not ready. Make sure there > > is a disc in the drive. > > Feb 17 21:51:45 timmy2 kernel: Device busy for revalidation > > (usage=1) Feb 17 21:51:48 timmy2 /etc/hotplug/usb.agent: Setup > > visor for USB product 82d/100/100 > > Feb 17 21:52:37 timmy2 kernel: usb.c: USB disconnect on device 6 > > Feb 17 21:52:37 timmy2 kernel: usbserial.c: Handspring Visor > > converter now disconnected from ttyUSB0 > > Feb 17 21:52:37 timmy2 kernel: usbserial.c: Handspring Visor > > converter now disconnected from ttyUSB1 > > Feb 17 21:53:40 timmy2 kernel: hub.c: USB new device connect on > > bus2/3, assigned device number 7 > > Feb 17 21:53:40 timmy2 kernel: usbserial.c: Handspring Visor > > converter detected > > Feb 17 21:53:40 timmy2 kernel: visor.c: Handspring Visor: Number > > of ports: 2 > > Feb 17 21:53:40 timmy2 kernel: visor.c: Handspring Visor: port 1, > > is for Generic use and is bound to ttyUSB0 > > Feb 17 21:53:40 timmy2 kernel: visor.c: Handspring Visor: port 2, > > is for HotSync use and is bound to ttyUSB1 > > Feb 17 21:53:40 timmy2 kernel: usbserial.c: Handspring Visor > > converter now attached to ttyUSB0 (or usb/tts/0 for devfs) > > Feb 17 21:53:40 timmy2 kernel: usbserial.c: Handspring Visor > > converter now attached to ttyUSB1 (or usb/tts/1 for devfs) > > Feb 17 21:53:40 timmy2 kernel: Device not ready. Make sure there > > is a disc in the drive. > > Feb 17 21:53:40 timmy2 kernel: Device busy for revalidation > > (usage=1) Feb 17 21:53:43 timmy2 /etc/hotplug/usb.agent: Setup > > visor for USB product 82d/100/100 > > Feb 17 21:54:32 timmy2 kernel: usb.c: USB disconnect on device 7 > > Feb 17 21:54:32 timmy2 kernel: usbserial.c: Handspring Visor > > converter now disconnected from ttyUSB0 > > Feb 17 21:54:32 timmy2 kernel: usbserial.c: Handspring Visor > > converter now disconnected from ttyUSB1 > > > > And during the same period KPilot is reporting: > > > > Version: KPilot 4.3.6 (3_1_BRANCH) > > Version: pilot-link 0.11.3 > > Version: KDE 3.1.0 > > Version: Qt 3.1.1 > > > > HotSync Log > > > > 21:52:24 Pilot device /dev/ttyUSB0 doesn't exist. Assuming the > > device uses DevFS. > > 21:52:25 Trying to open device... > > 21:52:25 Could not open device: /dev/ttyUSB0 (will retry) > > 21:53:45 HotSyncing. Please press the HotSync button. -- Rob Blomquist Kirkland, WA On the side of the software box, in the 'System Requirements' section, it said 'Requires Windows 95 or better'. So I installed Linux and lived happily ever after.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
