Re: Problem syncing Palm TX with jpilot on FreeBSD 8.0-BETA3
On Wed, Aug 26, 2009 at 06:54:25PM +0100, Tony McC wrote: Hello, I am running FreeBSD 8.0-BETA3 amd64 and am having trouble syncing my Palm TX with jpilot. This used to work with 7.2-STABLE amd64 and I suspect I'm just not using the usb: connection correctly but have not been able to find a solution by searching the archives. I am running a custom kernel with device uvisor commented out, though the same problem occurs if I recompile with uvisor included. [...] First you need to have uvisor(4) loaded (compiled in the kernel or via the loaded module). Last uvisor(4) revision was not merged in BETA3 so you will have to wait for the merge or directly grab it from http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/dev/usb/serial/uvisor.c?rev=1.12;content-type=text%2Fplain;only_with_tag=HEAD replace you src/sys/dev/usb/serial/uvisor.c with that one and rebuild your module/kernel Then if you plug your device and launch Hotsync on the Palm a /dev/cuaU0 device should appear. You should check that. If you have jpilot installed, palm/pilot-link tools are installed (be sure it was compiled with USB support), so once the /dev/cuaU0 device node is created you can type: # pilot-xfer -p /dev/cuaU0 -l this should list the installed files on your device, # pilot-xfer -p /dev/cuaU0 -b your_backup_dir to backup your palm on your PC. If these commands worked, then jpilot should work as well. -- Marc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem syncing Palm TX with jpilot on FreeBSD 8.0-BETA3
On Thu, 27 Aug 2009 09:36:22 +0200 Marc Fonvieille black...@freebsd.org wrote: First you need to have uvisor(4) loaded (compiled in the kernel or via the loaded module). Last uvisor(4) revision was not merged in BETA3 so you will have to wait for the merge or directly grab it from http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/dev/usb/serial/uvisor.c?rev=1.12;content-type=text%2Fplain;only_with_tag=HEAD replace you src/sys/dev/usb/serial/uvisor.c with that one and rebuild your module/kernel Then if you plug your device and launch Hotsync on the Palm a /dev/cuaU0 device should appear. You should check that. If you have jpilot installed, palm/pilot-link tools are installed (be sure it was compiled with USB support), so once the /dev/cuaU0 device node is created you can type: # pilot-xfer -p /dev/cuaU0 -l this should list the installed files on your device, # pilot-xfer -p /dev/cuaU0 -b your_backup_dir to backup your palm on your PC. If these commands worked, then jpilot should work as well. Marc, many thanks, that was a great help. I uncommented uvisor in the kernel config file, installed the newer uvisor.c, rebuilt and installed the new kernel. Pressing the hotsync button did indeed create a /dev/cuaU0 but I had to add myself to the 'dialer' group to use it. Palm syncing now works again with jpilot! BTW, when might that newer uvisor.c be merged into the RELENG_8 sources? Thanks also to Roland. I already had add path 'usb/*' in my /etc/devfs.rules. Best wishes, Tony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem syncing Palm TX with jpilot on FreeBSD 8.0-BETA3
On Thu, Aug 27, 2009 at 04:04:09PM +0100, Tony McC wrote: Marc, many thanks, that was a great help. I uncommented uvisor in the kernel config file, installed the newer uvisor.c, rebuilt and installed the new kernel. Pressing the hotsync button did indeed create a /dev/cuaU0 but I had to add myself to the 'dialer' group to use it. Palm syncing now works again with jpilot! Great! BTW, when might that newer uvisor.c be merged into the RELENG_8 sources? Hopefully, It should be available in 8.0-RELEASE. Thanks also to Roland. I already had add path 'usb/*' in my /etc/devfs.rules. Best wishes, Tony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Marc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problem syncing Palm TX with jpilot on FreeBSD 8.0-BETA3
Hello, I am running FreeBSD 8.0-BETA3 amd64 and am having trouble syncing my Palm TX with jpilot. This used to work with 7.2-STABLE amd64 and I suspect I'm just not using the usb: connection correctly but have not been able to find a solution by searching the archives. I am running a custom kernel with device uvisor commented out, though the same problem occurs if I recompile with uvisor included. When I plug in the Palm TX I get the following at the end of dmesg output: ugen0.4: Palm, Inc. at usbus0 ugen0.4: Palm, Inc. at usbus0 (disconnected) If I tell jpilot to sync with a Palm at usb: I get the following error message: dlp_OpenConduit() failed Sync canceled Exiting with status SYNC_ERROR_OPEN_CONDUIT Finished. I also have the following in my /etc/devfs.rules: add path 'ugen*' unhide mode 0660 group operator and I am a member of the operator group. What should I set to get hotsync working? Thanks all in anticipation, Tony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem syncing Palm TX with jpilot on FreeBSD 8.0-BETA3
On Wed, Aug 26, 2009 at 06:54:25PM +0100, Tony McC wrote: Hello, I am running FreeBSD 8.0-BETA3 amd64 and am having trouble syncing my Palm TX with jpilot. This used to work with 7.2-STABLE amd64 and I suspect I'm just not using the usb: connection correctly but have not been able to find a solution by searching the archives. I am running a custom kernel with device uvisor commented out, though the same problem occurs if I recompile with uvisor included. When I plug in the Palm TX I get the following at the end of dmesg output: ugen0.4: Palm, Inc. at usbus0 ugen0.4: Palm, Inc. at usbus0 (disconnected) If I tell jpilot to sync with a Palm at usb: I get the following error message: dlp_OpenConduit() failed Sync canceled Exiting with status SYNC_ERROR_OPEN_CONDUIT Finished. I also have the following in my /etc/devfs.rules: add path 'ugen*' unhide mode 0660 group operator and I am a member of the operator group. What should I set to get hotsync working? I think you have to add the following add path 'usb/*' mode 0660 group operator It seems that the new libusb in 8.x doesn't use the ugen devices anymore, it uses the new /dev/usb/* devices. Adding the above fixed gphoto2 for me on 8-BETA2. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp2jmRHxCqqj.pgp Description: PGP signature
