Based on some Web research, it seems that the "proper" way these days to use modern Palms with jpilot, pilot-link et al. is to set them to use the usb: device then let udev (?) link the two up, skipping the visor module entirely. I think I missed out on this because the visor module has always worked.
However, using usb: is not working either: >> device connected [ 1849.776124] usb 1-3: new high speed USB device using ehci_hcd and address 15 [ 1849.909491] usb 1-3: configuration #1 chosen from 1 choice >> executed pilot-dlpsh -p usb: -i [ 1972.557307] usb 1-3: USB disconnect, address 15 [ 1972.558349] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd pilot-dlpsh rqt 194 rq 4 len 20 ret -108 [ 1975.124129] usb 1-3: new high speed USB device using ehci_hcd and address 16 [ 1975.257385] usb 1-3: configuration #1 chosen from 1 choice It doesn't crash the LifeDrive, though, so that's good ;) I could use some guidance from someone who understands this more thoroughly in order to get this bug targeted properly. There are definitely two issues though, AFAIK: 1. the visor module has begun crashing Palms, and 2. the usb: method (which I understand gnome-pilot also uses?) is not working -- [karmic] visor module crashes PalmOS handhelds (tested: LifeDrive, CLIÉ) https://bugs.launchpad.net/bugs/421673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
