Re: no /dev/pilot for pilot-link to use

From: Jim Patterson (jim-patterson_at_ncf.ca)
Date: 01/27/05 

Date: Wed, 26 Jan 2005 22:56:50 -0500

Mark Healey wrote:
> On Tue, 25 Jan 2005 23:50:13 -0500, Jim Patterson wrote:
>
>
>>Mark Healey wrote:
>
>> So, You're saying I should plug it it after I boot? It is usually there
>> charging (sucky battery life). Or, are you saying I should hit the sync
>> button on the cradle and then look at dmesg. What should I look for in
>> dmesg anyway?

The sequence is pretty odd with the Pilot USB devices. I don't think it
matters when you plug it in; what matters is when you hit the hotsync
button. The USB device isn't actually created until you do that, so you
have to start the sync from the palm (phone), and then run pilot-xfer or
whatever you're using to sync with. You'll need to set up the
/dev/pilot link as someone described above, or just specify the port via
-p/dev/ttyUSB1 (if you're using pilot-xfer). You need permissiosn to the
device as well; the "udev" manpage has info on that.

The link I posted leads to this one
http://www.linuxpda.com/visor/howto/current/t1.html, which had a few
bits of information like that. Mostly it's just info on rebuilding a
kernel etc., though, which you shouldn't need to do on FC3.

Loading