Yeah, this is probably a modern Ubuntu and derivatives problem, or I'm missing something critical that I am failing to understand.
If I had an SD card reader with me, I'd just use that, but I only have a microSD card reader with me.
Turns out that I grabbed the lifedrive I haven't refurbished instead of the one I have, so I'm not super concerned about getting it to work RIGHT NOW anyway, since I want to get it to work with my other lifedrive.
If I manually modprobe the visor driver, it does appear to recognize that the palm is on ttyUSB0 and ttyUSB1, but then when I press the hotsync button I get an error in dmesg that says
"usb 1-2: palm_os_4_probe - error -110 getting connection info"
which seems like a problem.
I'm going to try to reboot, and then try pilot-xfer instead of jpilot.
K, jpilot doesn't work and I don't know why, but pilot-xfer works if and only if I 1) press the hotsync button 2) check which USBTTY the palm pilot has connected to, 3) then start pilot-xfer.
If I start pilot-xfer and then press the hotsync button, it jumps to a different USBTTY?
Regardless, I now have the keyboard driver installed (on the wrong Lifedrive) and I can verify that it works.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!