Matt Davey <mcdavey at mrao.cam.ac.uk> writes: > On Sun, 2006-12-24 at 19:25 +0000, Joe Wells wrote: >> I'm completely failing to get a working connection to a Palm V via a >> USB-to-serial adapter. Can anyone help me? > [,,,] >> After this, I see "Identifying user" on the Palm V. Then there is a >> delay. Then I see this output from pilot-dlpsh: >> >> Error read system info on /dev/ttyUSB0 >> > [...] >> My USB-to-serial adapter is by Keyspan. After I plug it in, I can >> learn from "lsusb" that the product ID is 0x0104 and this is >> associated with the string "PDA [prerenum]". These are the kernel log >> messages I see when I plug in my USB-to-serial adapter: [...] >> I don't know why it always seems to connect, disconnect, and then >> reconnect, but this happens every time I unplug it and plug it back >> in. When using this USB-to-serial adapter, the "visor" kernel module >> does *not* get loaded. > > The visor module recognises a compiled-in list of usb vendor/product ID > pairs. You can load the module and supply your vendor/product ID using > a command line like: > modprobe visor vendor=0x830 product=0x0061 > > I don't know whether this is the source of your problem, but it's worth > trying. Thanks very much for your remark! I'm confused by your suggestion. I thought the visor module was for PDAs that have a USB interface. My Palm V is old enough that it has only a serial port. The fact that I am providing my computer with a serial port by a USB-to-serial adapter should (in some idealized theoretical world!) be completely transparent, and I only mention the details because maybe something is going wrong with my USB-to-serial adapter. Is there some way the visor module can possibly help in this case? -- Thanks, Joe
More information about the pilot-link-general mailing list