Hello all! Thank you to those who have been trying to help me. At times the discussion became to technical for me. But now there is something new: suddenly this evening I managed to sync, but cannot repeat the operation! I made two changes to my settings in JP: - I modified the speed of the USB port to 115.200; - I modified my user name on the Zire so that it corresponded to that in JP When the sync does not work, some component of my laptop begins to work at full speed - my hard drive, I imagine - making a whining noise which I can only stop by rebooting. Any suggestions as to how to stop it? Below I reproduce part of my system log relative to syncing in the hope that it may throw some light on the problem. I have also replied below to some question David Desrosiers asked. Once again, thank you all for your help! Eamann Dec 2 20:36:19 localhost kernel: [17179741.568000] usb 2-2: new full speed USB device using uhci_hcd and address 3 Dec 2 20:36:19 localhost kernel: [17179741.732000] usb 2-2: configuration #1 chosen from 1 choice Dec 2 20:36:19 localhost kernel: [17179741.920000] usbcore: registered new driver usbserial Dec 2 20:36:19 localhost kernel: [17179741.920000] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic Dec 2 20:36:19 localhost kernel: [17179741.920000] usbcore: registered new driver usbserial_generic Dec 2 20:36:19 localhost kernel: [17179741.920000] drivers/usb/serial/usb-serial.c: USB Serial Driver core Dec 2 20:36:19 localhost kernel: [17179741.924000] drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS Dec 2 20:36:19 localhost kernel: [17179741.924000] drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5 Dec 2 20:36:19 localhost kernel: [17179741.924000] drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0 Dec 2 20:36:19 localhost kernel: [17179741.928000] visor 2-2:1.0: Handspring Visor / Palm OS converter detected Dec 2 20:36:19 localhost kernel: [17179741.928000] usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB0 Dec 2 20:36:19 localhost kernel: [17179741.928000] usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB1 Dec 2 20:36:19 localhost kernel: [17179741.928000] usbcore: registered new driver visor Dec 2 20:36:19 localhost kernel: [17179741.928000] drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver Dec 2 20:36:22 localhost kernel: [17179744.352000] usb 2-2: USB disconnect, address 3 Dec 2 20:36:22 localhost kernel: [17179744.352000] visor 2-2:1.0: device disconnected David A. Desrosiers wrote: >> Later, reading the posts here, I realised that perhaps Gnome-pilot >> was interfering with JP so I removed it. Unfortunately that did not >> enable me to sync.... >> > > But did you kill the daemon? It will auto-restart on login if > you don't disable it and kill it off. It's caused problems exactly > like you describe for hundreds of users in the past years. Its > unfortunate that it still sits there in the menus, but doesn't > identify itself as *NOT* for J-Pilot when you launch it. > Well, I used Synaptic to remove it so I think it is "dead". > >> When I set up JP in the first place I was able to sync a few times. >> Would it make sense to remove JP and delete all the associated files >> in the hope that when I reinstalled the programme it might sync >> again? >> > > No, this is Linux, not Windows. Uninstalling and reinstalling > won't fix this kind of problem (it will, however fix corrupted or > damaged applications files and libraries, but that's not what we're > dealing with here). > > >> I have already removed and reinstalled JP several times to no >> effect, but I know that there are a lot of files left over with >> "pilot" in their names and I did not dare try and delete them all. >> > > Well, let's try making sure that you are only running J-Pilot, > with no offending conflicting daemons in the background listening on > the port. > > Do you have your udev rules set up for your Palm device, so > the visor driver is loaded and the device in /dev gets created > automagically? See the README.usb documentation in the pilot-link > source for details on this (README.usb, *NOT* README.libusb in the > When I used search for files for README.usb, the machine tells me that there is no such file. Neither can I find pilot-xfer "command not found". > same tree). > > If you've got a working kernel, udev configuration, current > visor module loads when you press HotSync, and you still can't sync to > /dev/ttyUSB0 or /dev/ttyUSB1 (will vary, depending on your Palm model > and type), then the problem lies elsewhere. > > > David A. Desrosiers > desrod at gnu-designs.com > http://gnu-designs.com > _______________________________________________ > jpilot mailing list > jpilot at jpilot.org > http://www.jpilot.org/mailman/listinfo/jpilot > >
More information about the jpilot mailing list