I followed dbrett's suggestion and grepped dmesg to find out which USB
ports were active.  My mouse was plugged in to USB port 2, but port 1
was free.  Then I had to chmod ttyUSB1 and make /dev/pilot a symlink to
/dev/ttyUSB1, then manually start gpilotd.  Once all that was done, it
worked like a charm.


On Sat, 2003-03-08 at 12:12, Joe Polk wrote:
> You have to be sure you're using the right port. You can fool JPilot too
> by simple creating a symlink to the USB device and calling it
> /dev/pilot.  Also, I found that I occassionally have to soft-reset my
> Clie' to get it to sync.
> 
> <<JAV>>
> 
> On Sat, 2003-03-08 at 14:53, dbrett wrote:
> > If you get this working let me know. I am in exactly the same boat as you.
> > 
> > Things I know and suspect are the following:
> > 
> > - if you look in the messages log you will see reference to the port when
> > you connect to usb cradle.  I tried setting the port to these and it still
> > did not work.
> > 
> > - I suspect, it may require a recompile of the kernel with some more
> > options enables.  I came across these by accident, when I was going
> > through KDE configuration menus.  I have no idea how to compile a kernel.
> > the little I have read confused me, rather than helped.
> > 
> > - I was using J-Pilot, for quit a while but have since I can't get it to
> > sync throught the USB port.  There is a link on the page which may help as
> > well
> > http://nick.kreucher.net/clie/#Setup
> > 
> > - I have a usb mouse which works and usb to serial cable which works. But
> > I cannot get the palm to sync up
> > 
> > Please let me know if you get this working and what you did. I will do the
> > same, if I suceed.
> > 
> > david
> > On 7 Mar 2003, Richard S. Crawford wrote:
> > 
> > > I'm trying to get my new Palm m515 to talk to my Linux box.  It's a USB
> > > sync, so I know I ought to point /dev/pilot at one of my USB ports. 
> > > Trouble is, I have four such ports, and I don't know which one is
> > > reflected by which device in my /dev directory.  So I assume that I need
> > > to point /dev/pilot at /dev/ttyUSB0 or ttyUSB1 or some such thing.
> > > 
> > > My system already has a USB mouse which works perfectly; I assume that
> > > it's talking to /dev/ttyUSB0 but I'm not sure.  How do I find that out,
> > > and how do I figure out which USB device I should point my /dev/pilot
> > > symlink at?
> > > 
> > > -- 
> > > Slainte,
> > > Richard S. Crawford
> > > AIM: Buffalo2K / Y!: rscrawford / ICQ: 11640404
> > > http://www.mossroot.com http://www.stonegoose.com
> > > "It is only with our heart that we can see clearly.  What is essential
> > > is
> > > invisible to the eye."  --Antoine de Saint Exupery
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > -- 
> > redhat-list mailing list
> > unsubscribe mailto:[EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/redhat-list
> 
> 
-- 
Slainte,
Richard S. Crawford
AIM: Buffalo2K / Y!: rscrawford / ICQ: 11640404
http://www.mossroot.com http://www.stonegoose.com
"It is only with our heart that we can see clearly.  What is essential
is
invisible to the eye."  --Antoine de Saint Exupery



Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to